Open
Description
I just used this notebook to remind myself how to get data from a THREDDS server, and managed to confuse myself when using catalog.datasets, as documented in siphon#361. I proposed a documentation fix to the DatasetCollection
class, but also wanted to propose some changes to this notebook.
Specifically,
- In section 1, cell 4: cat.datasets, when printed, looks like a list. I recommend adding "Here,
cat.datasets
is a dictionary, and what you see above is a list of its keys, which are also the filenames of the datasets. Accessingcat.datasets
with one of these keys will return theDataset
that can be used to download the data, as you'll see below." - In section 3, above cell 10: "As noted above, the dataset name can be used to access each
Dataset
, but we can also index by position. - and below cell 11: "As you might have noticed,
datasets
is a special kind of dictionary that can be indexed in two ways, but it doesn't work like a list when you loop over it. Instead, sincedatasets
is a dictionary, if you loop through it you will get a sequence of keys: the filenames. So, to loop through eachDataset
and download it, you would writefor ds_name in datasets: datasets[ds_name].download()
. That could be useful if you want to further filter out datasets based on the dataset name."
That might not be the best / shortest wording for a workshop setting, so suggestions welcome.
Metadata
Metadata
Assignees
Labels
No labels