Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Example for specifying locations:

Code Block
xml
xml
<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"/>
				<parameterColumn name="PAR"/>
				<valueColumn name="LOC_A" locationId="A"/>
				<valueColumn name="LOC_B" locationId="B"/>
			</table>
			<idMapId>IdExport_HydroBiologie</idMapId>
			<exportMissingValueString>-9999.0</exportMissingValueString>
			<columnSeparator> </columnSeparator>
			<decimalSeparator>.</decimalSeparator>
		</general>
		<timeSeriesSet>
			...
		</timeSeriesSet>
		<timeSeriesSet>
			...
		</timeSeriesSet>
	</export>
</timeSeriesExportRun>


No Format
yyyyMMddHHmm PAR LOC_A LOC_B
201604180110 par 721.0 485.1
201604180210 par 955.7 648.5
201604184210 par 647.0 582.3
201604180310 par 352.9 260.9
201604180410 par 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 "&#009;" or space "&#x20;"

When specifying a column separator it is compulsory to also specify the decimal separator as comma ","  or point "."

 

Code Block
xml
xml
		<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 exporting 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

 

Separate alphanumeric and numeric values in two separate columns

Since 2017.01 it is possible to separate alphanumeric and numeric values in two separate columns

 

Code Block
xml
xml
<general>
	<exportType>generalCsv</exportType>
	<folder>$EXPORT_DIR$</folder>
	<exportFileName>
		<name>ExportGeneralCsv.csv</name>
	</exportFileName>
	<table>
		<dateTimeColumn name="DateTime" pattern="yyyy-MM-dd HH:mm"/>
		<locationColumn name="Location"/>
		<parameterColumn name="Parameter"/>
		<valueColumn name="ValueOnly" ignoreForEnumerationParameters="true"/>
		<valueColumn name="LabelOnly" ignoreForNumericalParameters="true"/>
		<unitColumn name="Unit" />
	</table>
	<idMapId>GeneralCsv</idMapId>
	<exportMissingValueString/>
	<convertValuesToEnumerationLabels>true</convertValuesToEnumerationLabels>
</general>

Columns not available for this export type

userColumn, yearColumn, monthColumn, dayColumn, hourColumn, minuteColumn, secondColumn

Exporting separate year, month, day, hour, minute and/or second columns


Ensemble  and ensemble member  columns

Since 2019.02 it is possible to export ensemble and ensemble member 

Code Block
xml
xml
<general>
      <exportType>generalCsv</exportType>
      <folder>$EXPORT_FOLDER$</folder>
      <exportFileName>
            <name>ExportGeneralCsv.csv</name>
      </exportFileName>
      <table>
          <dateTimeColumn name="DateTime" pattern="yyyy-MM-dd HH:mm"/>
          <locationColumn name="Location"/> 
          <parameterColumn name="Parameter"/> 
          <ensembleColumn name="Ensemble"/> 
          <ensembleMemberColumn name="Ensemble Member"/>
          <valueColumn name="Value"/> 
       </table>
 </general>

ents While the yearColumn, monthColumn etc. are not available for this export, it is possible to export a csv with separate columns for year, month, day etc. This can be achieved by configuring a <dateTimeColumn>, <dateColumn> or <timeColumn> with pattern="yyyy", or pattern="MM" etc. You can configure several of these column elements with different patterns. An example configuration can be found below.

Code Block
languagexml
	<table>
		<dateTimeColumn name="Year" pattern="yyyy"/>
		<dateTimeColumn name="Month" pattern="MM"/>
		<dateTimeColumn name="Day" pattern="dd"/>
		<dateTimeColumn name="Hour" pattern="HH"/>
		<dateTimeColumn name="Minute" pattern="mm"/>
		<dateTimeColumn name="Second" pattern="ss"/>
		<locationColumn name="Location"/>
		<parameterColumn name="Parameter"/>
		<valueColumn name="Value"/>
		<unitColumn name="Unit" />
	</table>