Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Alternatively you can use the relativeViewPeriod element so set a period to import relative to the T0. If you do this you can use the manual forecast dialog to set the period to import data from using the Cold/Warm state selection options.

Import data for a given forecast time

It often happens that on an OPeNDAP server there is data available for multiple forecasts with different forecast times. If the time periods of the forecasts overlap, then only one of the forecasts can be imported at a time. If there is a separate file for each forecast, then this can be done by specifying the URL of the required file in the import configuration. However, when such data is imported in an operational system, then the import URL should be changed each time a new forecast becomes available on the OPeNDAP server. If the URLs for the different forecasts contain the forecast time and only differ in forecast time, then the TIME_ZERO tag can be used to solve this problem. The import will replace the TIME_ZERO tag in the URL with the time zero (forecast time) of the current import run. This way different forecast data is imported each time the import runs for a different time zero.

Note

If the import runs for a time zero for which there is no forecast data available on the OPeNDAP server, then the import will fail with an error message. Therefore make sure that the import only runs at the specific forecast times for which there is data available on the OPeNDAP server.

For information on how to use the TIME_ZERO tag see serverUrl. Example of an import URL with TIME_ZERO tags:

Code Block
xml
xml

<serverUrl>http://nomads.ncep.noaa.gov:9090/dods/gfs/gfs%TIME_ZERO(yyyyMMdd)%/gfs_%TIME_ZERO(HH)%z</serverUrl>

Import data for a given subgrid

Note

Importing data for a subgrid currently only works for regular grids.

...