Overview
| Excerpt | ||
|---|---|---|
| ||
Import for IJsselmeer Klepstanden |
Import IJsselmeer Klepstanden from ASCII formatted file.
Input file structure
The input file is of ASCII type.
The following snippet illustrates a sample data file :
| No Format |
|---|
Stevinsluis Tue Jun 1 2010 02:47:54,Kolk1,Zuid,Stand:0 Stevinsluis Tue Jun 1 2010 02:47:54,Kolk2,Zuid,Stand:3 Stevinsluis Tue Jun 1 2010 02:47:54,Kolk3,Zuid,Stand:1 Stevinsluis Tue Jun 1 2010 02:48:54,Kolk1,Zuid,Stand:2 |
Each row contains in fact 6 columns, however column seperation is not consistent.
Seperation characters in use are white space, comma, colon.
Data contained in each row are described as (first row from snippet above as example):
column | Description | Value |
|---|---|---|
1 | Location | Stevinsluis |
2 | Time stamp | Tue Jun 1 2010 02:47:54 |
3 | External qualifier 1 | Kolk1 |
4 | External qualifier 2 | Zuid |
5 | Parameter ID | Stand |
6 | Parameter value | 0 |
The location , External qualifier 1 and External qualifier2 are concatenated during the import to form the LocationID used by the import to store the time series.
For the first row in the data example above, the LocationID becomes Stevinsluis_Kolk1_Zuid
Configuration
In order to import IJGKlepstanden configure a module like this:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?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>IJGKlepstanden</importType>
<folder>$IMPORT_FOLDER_IJGKlepstanden$</folder>
<failedFolder>$IMPORT_FOLDER_IJGKlepstanden$</failedFolder>
<backupFolder>$IMPORT_FOLDER_IJGKlepstanden$</backupFolder>
<importTimeZone>
<timeZoneOffset>+01:00</timeZoneOffset>
</importTimeZone>
<dataFeedId>IJGKS-DF</dataFeedId>
<reportChangedValues>true</reportChangedValues>
</general>
<timeSeriesSet>
<moduleInstanceId>ImportIJGKS</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Klepstand</parameterId>
<locationSetId>IJGKS_Locs</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant" />
<readWriteMode>add originals</readWriteMode>
<ensembleId>IJGKS</ensembleId>
</timeSeriesSet>
.
.
.
</import>
</timeSeriesImportRun>
|
idMapping
Non matching LocationID and ParameterID assigned during import can be mapped to the ones in use by the FEWS system by defining an ID Mapping.
For example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?> <idMap version="1.1" 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/idMap.xsd"> <parameter external="Stand" internal="Klepstand"/> <location external="Stevinsluis_Kolk1_Zuid" internal="STS_01_S"/> </idMap> |