...
This information is needed to configure the TimeseriesSet in the import module. A quick look at the files shows that there are four locations: LocA, LocB, LocC and LocD. Only one parameter is present (WaterLevel) and the data comes in hourly timesteps.
Another type of information that we will need is the location at which Delft-Fews can find to files to be imported. For this example we assume the files will be located in c:/Import/PI .
Below the configuration XML file for the import module that will read the files is shown:
| No Format |
|---|
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2006 rel. 3 sp1 (http://www.altova.com) by Jaap S (WL | Delft Hydraulics) -->
<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>PI</importType> <!-- Indicated we will read PI Files -->
<folder>c:/Import/PI</folder> <!-- read the files from here -->
<!-- Files WILL BE DELETED after import -->
<failedFolder>c:/Backup/PI</failedFolder>
<!-- If specified the imported files will be copied to this location -->
<idMapId>IdImport</idMapId> <!-- The IdMap for this import -->
<importTimeZone>
<timeZoneOffset>+00:00</timeZoneOffset>
</importTimeZone>
</general>
<timeSeriesSet>
<moduleInstanceId>Import/moduleInstanceId> <!-- The name of this moduleinstance -->
<valueType>scalar</valueType>
<parameterId>H.obs</parameterId>
<locationSetId>LevelGauges</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour" multiplier="1"/>
<readWriteMode>add originals</readWriteMode>
<synchLevel>1</synchLevel>
</timeSeriesSet>
</import>
</timeSeriesImportRun>
|
Set up Id Mapping
Adding the new import to a workflow
...