What |
nameofinstance.xml |
---|---|
Required |
no |
Description |
Export data (timeseries) from Delft-Fews to several file formats |
schema location |
http://fews.wldelft.nl/schemas/version1.0/timeSeriesExportRun.xsd |
Entry in ModuleDescriptors |
<moduleDescriptor id="ExportRun"> |
Configuration
The export module can export timeseries for use in other systems. The configuration of the module is split into three sections:
- General: Specify file name, data type etc...
- metadata: Export specific settings
- timeseriesSets: actual data to export
In the sections below the different elements of the configuration are described
General
description
An optional description
exportTypeStandard
This type specifies which reader should be used to read the file. The type must be one from the enumeration. Presently (2007/02) only bfg and pi are included in this list.
exportType
This type specifies which reader should be used to read the file. It may be any string as long as this type is supported by the TimeSeriesExport module. The list of supported types is given below.
folder
Folder (directory) in which to store the exported files.
exportFileName
This elements describes how to construct the filename(s) of the exported file(s).
If only the name element is given a fixed name is used for each export. The prefix and suffix elements describe how to create a filename prefix and/or suffix. The temporaryPrefix is used to generate a prefix for the temporary file as it is being written. After that the fine is renamed.
validate
Optional element. Only applicable if the data are exported to the xml-file. This option activates the validation of the exported file against a XML schema.
idmapId
Id of IdMap to be used for parameterId and locationId mapping
unitConversionsId
Id of UnitConversions to be used for unit mapping
flagConversionsId
Id of flagConversions to be used for flag mapping
exportMissingValue/exportMissingValueString
Missing value definition for this time series. Either a string or a number. Defaults to NaN if not defined.
omitMissingValues
If set to true records with missing values are not exported
exportTimeZone
TimeZone in which to export the data. Can either be a string (timeZoneName) or an offset (timeZoneOffset).
convertDatum
Convert datum to local datum during import. The conversion will be done for all parameters which use datum (as configured in Parameters.xml) The local datum is defined in the z element in the locations.xml file.
metadata
TO BE COMPLETED
timeseriesSet
Define the timesereisset to be exported. Please make sure that no all exports support all timeseriestypes (e.g. csv only supports scalar type)
Supported export types
- csv
- bfg
- tsd
- fliwas
- pi
- shef
- grdc
- netcdf mapdphase
- netcdf alert
csv
Export scalar timeseries to csv type format (example config). The resulting csv files has three header rows. This first row contains the location name for each data column, the second row the location Id for each data column, the third row the parameter. Date/time is in yyy-mm-dd hh:mm:ss format. An example is shown below:
Location Name:,Bewdley,Saxons Lode Location Id:,EA_H-2001,EA_H-2032 Time,Rainfall,Rainfall 2003-03-01 01:00:00,-999,-999 2003-03-01 01:15:00,1.000,1.000 2003-03-01 01:30:00,2.000,2.000 2003-03-01 01:45:00,3.000,3.000 2003-03-01 02:00:00,4.000,4.000 2003-03-01 02:15:00,-999,5.000 2003-03-01 02:30:00,6.000,6.000 2003-03-01 02:45:00,7.000,7.000 2003-03-01 03:00:00,8.000,8.000 2003-03-01 03:15:00,9.000,9.000 2003-03-01 03:30:00,10.000,10.000 2003-03-01 03:45:00,11.000,11.000 2003-03-01 04:00:00,12.000,12.000 2003-03-01 04:15:00,13.000,13.000 2003-03-01 04:30:00,14.000,14.000 2003-03-01 04:45:00,15.000,15.000 2003-03-01 05:00:00,16.000,16.000 2003-03-01 05:15:00,17.000,17.000 2003-03-01 05:30:00,18.000,18.000 2003-03-01 05:45:00,19.000,19.000 2003-03-01 06:00:00,20.000,20.000
bfg
Export scalar timeseries to bfg type format (example config).
No example present.
tsd
Export scalar timeseries to tsd type format (example config). This is a tab delimited file with two header row. The first column contains the date/time. Date format is yyyy-MM-dd HH:mm:ss. The first header line contains the parameter and the T0. The second line the location above each column. As such, only one parameter can be exported per file.
fliwas
Export scalar timeseries to fliwas type format (example config).
An example is shown below:
<?xml version="1.0" encoding="UTF-8"?> <fliwas xsi:schemaLocation="http://www.wldelft.nl/fliwas/floriver/settings/fliwas.xsd" version="1.0" xmlns="http://www.wldelft.nl/fliwas" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <header gebied="fews" datum="2003-03-01" tijd="00:00:00" volgnummer="1.0"> <riviertak naam="EA_H-2001"> <voorspelling datum="2003-03-01" tijd="00:00:00"> <waterstand km="0" stand="2.11"/> <waterstand km="200" stand="2.11"/> <waterstand km="400" stand="2.11"/> <waterstand km="600" stand="2.11"/> </voorspelling> <voorspelling datum="2003-03-01" tijd="01:00:00"> <waterstand km="0" stand="3.11"/> <waterstand km="200" stand="3.11"/> <waterstand km="400" stand="3.11"/> <waterstand km="600" stand="3.11"/> </voorspelling> <voorspelling datum="2003-03-01" tijd="02:00:00"> <waterstand km="0" stand="4.11"/> <waterstand km="200" stand="4.11"/> <waterstand km="400" stand="4.11"/> <waterstand km="600" stand="4.11"/> </voorspelling> <maximum> <waterstand km="27" datum="2003-03-01" tijd="00:00:00" stand="1.31"/> <waterstand km="28" datum="2003-03-01" tijd="00:00:00" stand="1.41"/> </maximum> </riviertak> <riviertak naam="EA_H-2002"> <voorspelling datum="2003-03-01" tijd="00:00:00"> <waterstand km="0" stand="3.51"/> <waterstand km="100" stand="3.51"/> <waterstand km="300" stand="3.51"/> <waterstand km="500" stand="3.51"/> </voorspelling> <voorspelling datum="2003-03-01" tijd="01:00:00"> <waterstand km="0" stand="4.51"/> <waterstand km="100" stand="4.51"/> <waterstand km="300" stand="4.51"/> <waterstand km="500" stand="4.51"/> </voorspelling> <maximum> <waterstand km="29" datum="2003-03-01" tijd="00:00:00" stand="1.71"/> </maximum> </riviertak> <riviertak naam="EA_H-2032"> <voorspelling datum="2003-03-01" tijd="00:00:00"> <waterstand km="111" stand="1.91"/> <waterstand km="222" stand="1.91"/> </voorspelling> <voorspelling datum="2003-03-01" tijd="01:00:00"> <waterstand km="111" stand="2.91"/> <waterstand km="222" stand="2.91"/> </voorspelling> </riviertak> </header> </fliwas>
pi
Export scalar timeseries to PI type format (example config). This xml format is described in detail in the Delft-Fews published interface documentation. An example is shown below:
<?xml version="1.0" encoding="UTF-8"?> <TimeSeries xsi:schemaLocation="http://www.wldelft.nl/fews/PI http://fews.wldelft.nl/schemas/version1.0/pi-schemas/pi_timeseries.xsd" version="1.2" xmlns="http://www.wldelft.nl/fews/PI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <timeZone>0.0</timeZone> <series> <header> <type>accumulative</type> <locationId>EA_H-2001</locationId> <parameterId>Rainfall</parameterId> <timeStep unit="second" multiplier="900"/> <startDate date="2003-03-01" time="00:00:00"/> <endDate date="2003-03-01" time="05:00:00"/> <missVal>-999.0</missVal> <stationName>Bewdley</stationName> <units>m</units> </header> <event date="2003-03-01" time="00:00:00" value="-999.0" flag="88"/> <event date="2003-03-01" time="00:15:00" value="0.0010" flag="44"/> <event date="2003-03-01" time="00:30:00" value="0.0020" flag="44"/> <event date="2003-03-01" time="00:45:00" value="0.0030" flag="44"/> <event date="2003-03-01" time="01:00:00" value="0.0040" flag="44"/> <event date="2003-03-01" time="01:15:00" value="-999.0" flag="88"/> <event date="2003-03-01" time="01:30:00" value="0.0060" flag="44"/> <event date="2003-03-01" time="01:45:00" value="0.0070" flag="44"/> <event date="2003-03-01" time="02:00:00" value="0.0080" flag="44"/> <event date="2003-03-01" time="02:15:00" value="0.009000001" flag="44"/> <event date="2003-03-01" time="02:30:00" value="0.010000001" flag="44"/> <event date="2003-03-01" time="02:45:00" value="0.011000001" flag="44"/> <event date="2003-03-01" time="03:00:00" value="0.012" flag="44"/> <event date="2003-03-01" time="03:15:00" value="0.013" flag="44"/> <event date="2003-03-01" time="03:30:00" value="0.014" flag="44"/> <event date="2003-03-01" time="03:45:00" value="0.015000001" flag="44"/> <event date="2003-03-01" time="04:00:00" value="0.016" flag="44"/> <event date="2003-03-01" time="04:15:00" value="0.017" flag="44"/> <event date="2003-03-01" time="04:30:00" value="0.018000001" flag="44"/> <event date="2003-03-01" time="04:45:00" value="0.019000001" flag="44"/> <event date="2003-03-01" time="05:00:00" value="0.020000001" flag="44"/> </series> </TimeSeries>
shef
Export scalar timeseries to SHEF format (example config).
No example output at present.
grdc
Export scalar timeseries to GRDC type format (example config). GRDC-NRT-Format - for the exchange of near real-time hydrological data.
Example:
# GRDC-NRT-Format - for the exchange of near real-time hydrological data # # National Station ID;Timestamp;Water level;Discharge;is missing value water level;is missing value discharge;is directly determined water level?;is directly determined discharge?;is data reliable water level?;is data reliable discharge?;aggregation interval water level&discharge;aggregation offset water level&discharge;is ice cover?;is ice jam?;is weedage?;is influenced by backwater? EA_H-2032;2003-03-01 01:00:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 01:15:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 01:30:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 01:45:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 02:00:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 02:15:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 02:30:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 02:45:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 03:00:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 03:15:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 03:30:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 03:45:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 04:00:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 04:15:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 04:30:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 04:45:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 05:00:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 05:15:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 05:30:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 05:45:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2032;2003-03-01 06:00:00;-999;-999;1;1;0;0;0;0;0;;;;; EA_H-2001;2003-03-01 01:00:00;0.35;1.35;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 01:15:00;0.35;2.35;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 01:30:00;0.34;3.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 01:45:00;0.34;0.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 02:00:00;0.34;0.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 02:15:00;0.34;0.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 02:30:00;0.34;0.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 02:45:00;0.34;0.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 03:00:00;0.34;0.34;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 03:15:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 03:30:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 03:45:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 04:00:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 04:15:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 04:30:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 04:45:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 05:00:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 05:15:00;0.33;0.33;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 05:30:00;0.32;0.32;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 05:45:00;0.32;0.32;0;0;0;0;1;1;0;;;;; EA_H-2001;2003-03-01 06:00:00;0.32;0.32;0;0;0;0;1;1;0;;;;;
netcdf mapdphase
TO BE COMPLETED
netcdf alert
TO BE COMPLETED