Page History

...

An example of the NETCDF-CF_GRID import will be given here.

From 2021.01 it is possible to import NETCDF attributes as timeSeriesProperties into FEWS. This can be configured in the properties (see example below). Using the example config, the value of the NETCDF attribute ‘systemid’ will be imported as a timeSeriesProperty ‘rivieren2’.

Since 2021.02 it is also possible to export timeSeriesProperties as NETCDF attributes. You can find a config example here:  https://publicwiki.deltares.nl/display/FEWSDOC/NETCDF-CF_GRID+Export

<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesImportRun.xsd">
	<import>
		<general>
			<importType>NETCDF-CF_GRID</importType>
			<folder>$IMPORT_FOLDER$/NETCDF</folder>
			<failedFolder>$IMPORT_FAILED_FOLDER$</failedFolder>
			<backupFolder>$IMPORT_BACKUP_FOLDER$</backupFolder>
			<idMapId>IdImportNetCDF</idMapId>
			<unitConversionsId>ImportUnitConversions</unitConversionsId>
		</general>
		<properties>
			<string key="netcdfattribute:taskrunid" value='timeseriesproperty:rivieren1'/>
			<string key="netcdfattribute:systemid" value='timeseriesproperty:rivieren2'/>
		</properties>   
		<timeSeriesSet>
			<moduleInstanceId>ImportNetcdf_Grid</moduleInstanceId>
			<valueType>grid</valueType>
			<parameterId>Snelheid.u.F0</parameterId>
			<locationId>hmcn_zeedelta</locationId>
			<timeSeriesType>external forecasting</timeSeriesType>
			<timeStep unit="minute" multiplier="30"/>
			<readWriteMode>add originals</readWriteMode>
			<synchLevel>6</synchLevel>
		</timeSeriesSet>
	</import>
</timeSeriesImportRun>

Import of metadata and (OpenDAP) grid references (since 2019.02)

It is possible to import gigabytes of grids in a fraction of a second. To achieve this only references to grid data in NetCDF files, OPeNDAP are imported. The grids are streamed from the OPenDAP service or NetCDF file to the wms service, oc, fss. The central database can be released of big gridded model results by exporting the model results directly to OPeNDAP and import the references back in the same workflow. This works even without any configuration changes in other areas as long the OPenDAP service is reachable. When a netcdf file is created in a workflow an external process is often moving this file to the final opendap location later on. This future file url can be configured (since 2021.01). The data becomes visible in the OC as soon the netcdf file is moved to the final location.

<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesImportRun.xsd">
   <import>
      <general>
			<importType>NETCDF-CF_GRID_REFERENCES</importType>
			<folder>$IMPORT_FOLDER$/NETCDF</folder>
			<idMapId>IdImportNetCDF</idMapId>
			<unitConversionsId>ImportUnitConversions</unitConversionsId>
      </general>
      <properties>
         <string key="futureFolderUrl" value="http..."/>
      </properties>
      <timeSeriesSet>
         <moduleInstanceId>GridImportNetcdf</moduleInstanceId>
         <valueType>grid</valueType>
         <parameterId>H.sim</parameterId>
         <locationId>locA</locationId>
         <timeSeriesType>simulated forecasting</timeSeriesType>
         <timeStep unit="nonequidistant"/>
                  <relativeViewPeriod unit="day" start="0" end="36524"/>
         <readWriteMode>add originals</readWriteMode>
      </timeSeriesSet>
   </import>
</timeSeriesImportRun>

Id Map Configuration

An example of the IdMapping used for the NETCDF-CF_GRID import is shown below.

...