...
Parser for importing track data from a NetCDF file. This can be used for importing data that is valid according to the CF-1.6 conventions with featureType "trajectory" or "point". More information about the CF conventions can be found at http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html.
For featureType "point" all points in the file are imported together to form a single track. For featureType "trajectory" this parser supports only a single track per file, i.e. variables in the NetCDF file must be one dimensional and only have a time dimension. For an example of the format that can be imported with this import type, see http://cfconventions.org/cf-conventions/cf-conventions.html#_single_trajectory
Track x,y coordinates are imported as normal timeSeries, i.e. they do not get any special treatment in this parser and are handled like other data variables. In fact this parser does not know about tracks at all. Tracks are constructed in other places in Delft-FEWS (e.g. trackLayer in GridDisplay) where it is possible to combine a data timeSeries with two timeSeries with x and y coordinates in the configuration to create a track.
For details about other formats of NetCDF files that can be imported in Delft-FEWS, see NetCDF formats that can be imported in Delft-FEWS.
Also see:
...
.
...
Consequences for coordinates
The values of coordinate timeSeries are imported as normal timeSeries. Therefore for the coordinate timeSeries there must be timeSeriesSets configured in the import run and parameters configured in the id map. Furthermore the imported coordinates are rounded to floats. For global lat,lon coordinates in degrees this corresponds to a spatial accuracy of about 4 meters.
Supported properties
- connection_retry_count (only used for importing data from an OPeNDAP server)
- connection_retry_interval_in_milliseconds (only used for importing data from an OPeNDAP server)
...