...
| No Format |
|---|
,Bewdley,Saxons Lode ,Rainfall,Rainfall ,0,1 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 |
...
Additional Header Information
Additional data can be added to the header of an export. These data are supplied in the configuration as a sequence of key value pairs, with the key having the prefix "additional-". The additional header information is formatted as a '#' then up to 20 characters of the key (padded with spaces) then '| ' and finally the value.
Example
| Code Block | ||||
|---|---|---|---|---|
| ||||
<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>
...
</general>
<properties>
<string key="additional-key-name" value="VALUE_NAME"/>
<string key="additional-units" value="XYUNITS"/>
</properties>
<meta-data>
... |
| Code Block | ||||
|---|---|---|---|---|
| ||||
#key-name | VALUE_NAME
#units | XYUNITS
,Bewdley,Saxons Lode
,Rainfall,Rainfall
,0,1
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 |