You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Overview

This export is available in DELFT-FEWS versions after 28-10-2009 (FEWS version 2009.02)

Exports data to NetCDF files which comply to the CF 1.4 standard.

To indicate that data values are missing , NetCDF-CF exports use float value 9.96921e+036 by default. It is possible to change it by entering a different missing value (NaN or other) in the configuration files. Use option <exportMissingValue> in TimeSeriesExport module, and <missVal> in GeneralAdapter
More information about the cf standards can be found at: http://cfconventions.org/

There are six types of NetCDF-CF exports which can be defined:

Configuring the export

An example of the NETCDF-CF_TIMESERIES export will be given here.

In FEWS, it is possible to couple time series with pre-configured properties. From 2021.02 the properties can be exported to the NETCDF file as NETCDF attributes. See a config example bellow. Using the example, the name of the NETCDF attribute will be systemid, the value will be the value of timeSeriesProperty with the name rivieren2, that belongs to the exported time series.


Since 2021.02 it is also possible to import NETCDF attributes into FEWS and save them as timeSeriesProperty. You can see a config example for that here: NETCDF-CF_GRID

ExportNetcdf_Timeseries 1.00 default.xml
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesExportRun 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/timeSeriesExportRun.xsd">
	<export>
		<general>
			<exportType>NETCDF-CF_TIMESERIES</exportType>
			<folder>%REGION_HOME%/Export/netcdf/0D</folder>
			<exportFileName>
				<name>.nc</name>
				<prefix>
					<timeZeroFormattingString>yyyyMMddHHmm</timeZeroFormattingString>
				</prefix>
			</exportFileName>
			<idMapId>IdExportNetCDF</idMapId>
			<exportMissingValueString>-999</exportMissingValueString>
			<exportTimeZone>
				<timeZoneName>GMT</timeZoneName>
			</exportTimeZone>
		</general>
		<properties>
			<string key="timeseriesproperty:rivieren1" value='netcdfattribute:discharge_forcing_id'/>
			<string key="timeseriesproperty:rivieren2" value='netcdfattribute:systemid '/>
		</properties>
		<timeSeriesSet>
			<moduleInstanceId>ExportNetcdf_Timeseries</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>Q.udm</parameterId>
			<locationSetId>DMFlowPoints</locationSetId>
			<timeSeriesType>simulated historical</timeSeriesType>
			<timeStep unit="nonequidistant"/>
			<relativeViewPeriod unit="day" start="-365" end="365"/>
			<readWriteMode>add originals</readWriteMode>
		</timeSeriesSet>
	</export>
</timeSeriesExportRun>

An example of the IdMapping used for the NETCDF-CF_TIMESERIES export will be given below. In this example, the mapped locations correspond to the locations of the locatiesSet as defined above in the ExportNetcdf_Timeseries.xml.
If the parameter has an entry in the standard name CF table, you can enter it in the externalQualifier1 attribute of the parameter. The value of this qualifier will be added as the standard_name attribute for this variable in the netcdf exported file.

IdExportNetCDF 1.00 default.xml
<?xml version="1.0" encoding="UTF-8"?>
<idMap version="1.1" 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/idMap.xsd">
	<parameter internal="Q.udm" external="discharge" externalQualifier1="discharge (not standardname, just for test)"/>

	<location internal="DMTak_1001" external="1001"/>
	<location internal="DMTak_1002" external="1002"/>
	<location internal="DMTak_1003" external="1003"/>
	<location internal="DMTak_1004" external="1004"/>
	...
	<location internal="DMTak_6115" external="6115"/>
</idMap>
  • No labels