...

Setting up the import module

Steps:

1. make the Configuration file for the import module and store in the ModuleConfigFiles directory. In this example it should be named Import 1.00 default.xml
2. register this new module in the ModuleInstanceDescriptors 1.00 default.xml file in the RegionConfigFiles directory
3. Add the new module at a workflow in order to run it.

h2 Step 1: Configure the import module
The first step is to configure an instance of the import module for the type of data you need to import. In this example we will import data in PI XML format for 4 locations. The file we want to import is shown below:

...

The timeSeriesSet element defines how the data will be sored stored in delft-Fews. If you later want to viewsview, use or export the data you will need the same timeseriesset to retrieve or view the data. IN In the timesereisset timeseriesset we have defined the following:

• moduleInstanceId – Name of this configuration instance, reflects the XML file name
• valueType – scalar, this is scalar data
• parameterId – H.obs – This is the parameterId in Delft-Fews. The parameter Id in the XML file is WaterLevel. The Id mapping (shown below) will map Waterlevel to H.obs
• locationSetId – In order to simplify configuration we have defined a list of locations (a locatioset) in the file LocationSets.xml (in the RegionConfigFiles directory). This set holds the following four locations: one, two, three, fours. As these are differenmt from the locations in the XML file we are importing the id mapping will need to map them.
• timeStep – the timestep defined here should map the timestep in the XML files to be imported.

Step 2: Register the new module – Add to the ModuleInstanceDescriptors 1.00 default.xml file

Step 3: Add the module to a workflow (ImportExternal)

Set up Id Mapping

...

Step 4: Make the idmap file

Step 5: register the idmap file

Setting up a (temporary) display to view the imported data

...