...
A NetCDF file can contain multiple variables. By default the external parameter id is matched to the names of the variables in the NetCDF file to find the required variable to import. There also is an option to use the standard_name attribute or long_name attribute of the variable in the NetCDF file. To use this option add the variable_identification_method property to the import configuration. This can be done by adding the following lines to the import configuration file, just above the time series sets:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<properties> <string key="variable_identification_method" value="standard_name"/> </properties> |
The value can be "standard_name", "long_name" or "variable_name" (default). If value is e.g. "standard_name", then the external parameter id from the id map configuration file is matched to the standard_name attributes of the variables in the NetCDF file to find the required variable to import. If the variable_identification_method property is not present, then "variable_name" is used by default. The variable_identification_method property currently only works for import types "NETCDF-CF_GRID", "NETCDF-CF_TIMESERIES" and "NETCDF-CF_PROFILE".
...
A catalog file is usually called catalog.xml. The URL of a catalog file can be obtained in the following way.
For a THREDDS opendap server: | First browse to a folder on the server. Then copy the current URL from the address line and replace "catalog.html" at the end of the url by "catalog.xml". |
|---|---|
For a HYRAX opendap server: | First browse to a folder on the server. Then click on the link "THREDDS Catalog XML" on the bottom of the page. Then copy the current URL from the address line. |
Example: to import data from the folder TODO use the following line in the import configuration:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<serverUrl>TODO</serverUrl>
|
Import data for a given period of time
...
This can be used to import only the relevant data if only data for a given period is needed, which can save a lot of time. However, for this to work the import still needs to search through all the metadata of the file(s) to be imported. So for large catalogs that contain a lot of files, it can still take a lot of time for the import to download all the required metadata from the OPeNDAP server.
Example: to import only data within the period from 2007-07-01 00:00:00 to 2008-01-01 00:00:00, add the following lines to the import configuration:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<startDateTime date="2007-07-01" time="00:00:00"/>
<endDateTime date="2008-01-01" time="00:00:00"/>
|
Import data for a given sub grid
...