...
This feature has been implemented in the release 2014.02 (not working with older releases)
Single value per line
Example
| No Format |
|---|
DATE_SMP;LOC_CODE;Eenheid;PARAMETER_ID;PAR_REF;PROD_CODE;ANAL_CODE;TYPE;SMP_CODE;COST_CODE;Groep;Waarde 01-01-81 00:00;MBP012;-;TansleyS_PTB;Nymphoides peltata;OW;PTB;gemeten;713;ECOLDOEL;ANGIO;4.0 01-01-81 00:00;MBP012;-;TansleyS_PTB;Phragmites australis;OW;PTB;gemeten;713;ECOLDOEL;ANGIO;8.0 01-01-81 00:00;MBP012;-;TansleyS_PTB;Polygonum amphibium;OW;PTB;gemeten;713;ECOLDOEL;ANGIO;4.0 01-01-81 00:00;MBP012;-;TansleyS_PTB;Polygonum persicaria;OW;PTB;gemeten;713;ECOLDOEL;ANGIO;1.0 01-01-81 00:00;MBP044;-;TansleyS_PTB;Nymphaea alba;OW;PTB;gemeten;712;ECOLDOEL;ANGIO;8.0 01-01-81 00:00;MBP044;-;TansleyS_PTB;Phragmites australis;OW;PTB;gemeten;712;ECOLDOEL;ANGIO;8.0 01-01-81 00:00;MBP044;-;TansleyS_PTB;Polygonum amphibium;OW;PTB;gemeten;712;ECOLDOEL;ANGIO;4.0 01-01-81 00:00;MBP044;-;TansleyS_PTB;Polygonum persicaria;OW;PTB;gemeten;712;ECOLDOEL;ANGIO;1.0 |
...
For more information of the table layout configuration see Table Layout
Multiple values per line
Since 2016.01 it will be possible to use multiple values per line by specifying a parameter or location by each value.
For 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>
<exportType>generalCsv</exportType>
<folder>$EXPORT_FOLDER$/Csv</folder>
<exportFileName>
<name>ExportGeneralCsv.csv</name>
</exportFileName>
<table>
<dateTimeColumn name="DATE_SMP" pattern="yyyyMMddHHmm"/>
<locationColumn name="LOC"/>
<valueColumn name="PAR_A" parameterId="A"/>
<valueColumn name="PAR_B" parameterId="B"/>
</table>
<idMapId>IdExport_HydroBiologie</idMapId>
<exportMissingValueString>-9999.0</exportMissingValueString>
<columnSeparator> </columnSeparator>
<decimalSeparator>.</decimalSeparator>
</general>
<timeSeriesSet>
...
</timeSeriesSet>
<timeSeriesSet>
...
</timeSeriesSet>
</export>
</timeSeriesExportRun>
|
| No Format |
|---|
yyyyMMddHHmm LOC PAR_A PAR_B
201604180110 loc 721.0 485.1
201604180210 loc 955.7 648.5
201604184210 loc 647.0 582.3
201604180310 loc 352.9 260.9
201604180410 loc 259.8 186.8
|
Defining column separator and decimal separator
Since 2016.01 it is possible to choose from multiple column separators: comma "," or semi-colon ";" or pipe "|" or tab "	" or space " "
When specifying a column separator it is compulsory to also specify the decimal separator as comma "," or point "."
| Code Block | ||||
|---|---|---|---|---|
| ||||
<general> <exportType>generalCsv</exportType> <folder>../junit_test_output/nl/wldelft/fews/system/plugin/dataExport/TimeSeriesExportTest/exportGeneralCsvColumnSeparator/export</folder> <exportFileName> <name>ExportGeneralCsvColumnSeparator.csv</name> </exportFileName> <table> <dateTimeColumn name="DateTime" pattern="yyyy-MM-dd HH:mm"/> <locationColumn name="Location"/> <parameterColumn name="Parameter"/> <qualifierColumn name="QualifierId" prefix="CAL_"/> <qualifierColumn name="QualifierId" prefix="IlC_"/> <attributeColumn name="QualifierName" id="qualifierName"/> <attributeColumn name="Type" id="type"/> <attributeColumn name="Groep" id="groep"/> <attributeColumn name="filter" id="filter"/> <propertyColumn name="StringProperty" key="stringKey"/> <propertyColumn name="SecondStringProperty" key="secondStringKey"/> <flagSourceColumn name="A" id="A"/> <flagSourceColumn name="B" id="B"/> <flagSourceColumn name="C" id="C"/> <flagSourceColumn name="D" id="D"/> <flagSourceColumn name="E" id="E"/> <valueColumn name="Value"/> <unitColumn name="Unit"/> </table> <idMapId>GeneralCsv</idMapId> <exportMissingValueString>-9999.0</exportMissingValueString> <columnSeparator>|</columnSeparator> <decimalSeparator>.</decimalSeparator> </general> |
This enables importing for example the format below:
| No Format |
|---|
DateTime|Location|Parameter|QualifierId|QualifierId|QualifierName|Type|Groep|filter|StringProperty|SecondStringProperty|A|B|C|D|E|Value|Unit 2003-02-22 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|0.0|m 2003-02-23 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|1.0|m 2003-02-24 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|2.0|m 2003-02-25 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|3.0|m 2003-02-26 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|4.0|m 2003-02-27 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|5.0|m 2003-02-28 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|6.0|m 2003-03-01 00:00|chj|mxgn|CALLPRAU|ILCOCIMC|Callicorixa praeusta|Macrofauna|INHET|1|StringValue|SecondStringValue|OK|OK|OK|OK|OK|7.0|m |