Versions Compared

Old Version 19

changes.mady.by.user Ivo Miltenburg

Saved on

compared with

New Version 20

changes.mady.by.user Ivo Miltenburg

Saved on

Key

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

...

In the FEWS client, it is possible to use the validation status as a condition for the interactive export. A specific flagSource Column can be selected which is used as a filter for the export. In the export, the The flagSource Columns are included for the PI-XML data type and will always be exported when available. The GeneralCSV datatype can be configured as an interactive export type as well. The flagSource columns that should be exported can be configured in the explorer.xml configuration file.

...

Import of flagSourceColumns

The flagSource Columns are included for the PI-XML data type and will be imported.

The GeneralCSV datatype can be configured as an import type as well. The flagSource columns that should be imported can be configured in the explorer.xml configuration file.

Below is given an example on how to configure a generalCSV import with flagSource columns.

Code Block
xml
xml
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun 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/timeSeriesImportRun.xsd">
	<import>
		<general>
			<importType>generalCSV</importType>
			<folder>../junit_test_output/nl/wldelft/fews/system/plugin/dataImport/TimeSeriesImportTestData/import/generalcsv</folder>
			<table>
				<dateTimeColumn name="DATE" pattern="dd-MM-yy HH:mm"/>
				<locationColumn name="LOC"/>
				<unitColumn name="UNIT"/>
				<parameterColumn name="PARAM"/>
				<flagSourceColumn id="A" name="FS_A"/>
				<!-- column with name fs a will be mapped to the flag source column with identifier A -->
				<flagSourceColumn id="B" name="FS_B"/>
				<flagSourceColumn id="C" name="FS_C"/>
				<flagSourceColumn id="D" name="FS_D"/>
				<flagSourceColumn id="E" name="FS_E"/>
				<valueColumn name="VALUE"/>
			</table>
			<logWarningsForUnmappableLocations>true</logWarningsForUnmappableLocations>
			<logWarningsForUnmappableParameters>true</logWarningsForUnmappableParameters>
			<logWarningsForUnmappableQualifiers>true</logWarningsForUnmappableQualifiers>
			<maxLogWarnings>1000</maxLogWarnings>
			<missingValue>-999</missingValue>
			<importTimeZone>
				<timeZoneOffset>+01:00</timeZoneOffset>
			</importTimeZone>
			<dataFeedId>generalCSV</dataFeedId>
		</general>
	</import>
</timeSeriesImportRun>

 

The CSV file for this example could look like this:

 

Code Block
none
none
DATE,LOC,VALUE,UNIT,PARAM,FS_A,FS_B,FS_C,FS_D,FS_E01-01-81 00:00,H-2001,2.3,m,P.m,OK,OK,OK,OK,OK3110040601;Spiegelplas 4;133054;475032;MEA;WP_CAS_ZUY;OW;Van Veenhapper;SPV7030;WP_CAS_ZUY;SBP130;06-04-10 00:00;Tubificidae;2;n;MACEV2010;AANTL_MEA;gemeten

Note that during import, the mapping goes from 'name' to 'id'. When importing the data, the flagSourceColumnId's should be configured in

...

the flagSourceColumns

...

 configuration file.

Copying of flagSource columns to other timeseries

It is possible to manually copy and paste the flagSources in the flagSource Columns to other flagSource Columns (from the same, or from other timeseries), when in edit mode.

It is not possible to copy flagSource columns in a transformation to another timeseriesThis is not possible with the current implementation.