...
| 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>
<!--Bayern-->
<general>
<importType>IFKIS</importType>
<folder>$IMPORT_FOLDER_IFKIS$</folder>
<failedFolder>$IMPORT_FOLDER_IFKIS$</failedFolder>
<backupFolder>$IMPORT_FOLDER_IFKIS$</backupFolder>
<idMapId>IdImportIFKIS</idMapId>
<importTimeZone>
<timeZoneOffset>+01:00</timeZoneOffset>
</importTimeZone>
<dataFeedId>IFKIS-DF</dataFeedId>
<reportChangedValues>true</reportChangedValues>
</general>
<timeSeriesSet>
<moduleInstanceId>ImportIFKIS</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>P</parameterId>
<locationSetId>IFKIS-LOCS</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour" multiplier="1"/>
<readWriteMode>add originals</readWriteMode>
<synchLevel>1</synchLevel>
</timeSeriesSet>
.
.
.
</import>
</timeSeriesImportRun>
|
...
The parser assigns the numerical ID found in the header to LocationID as well as ParameterIDon each row to LocationID.
Parameters are named by the parser according to the table above.
To map these to current FEWS location and parameter an idMapping can be configured.
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="24095302precipitation" internal="P.voorsp.ens"/>
<location external="24095302810" internal="KNMIThe_FEWS_NL001location1"/>
</idMap>
|