Versions Compared

Key

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

...

  • 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 locationset) in the file LocationSets.xml (in the RegionConfigFiles directory). This set holds the following four locations: one, two, three, fours. As these are different from the locations in the XML file we are importing the to be imported id mapping will need to map thembe set up.
  • timeStep - the timestep defined here should map the timestep in the XML files to be imported.

...

All moduleInstances must be registered in Delft-Fews. This is done by adding en entry in the moduleInstancseDescriptors moduleInstanceDescriptors file in the RegionConfigDiles RegionConfigFiles section of the configuration. To register this module we will need to a the following to the moduleInstancedescriptorsThe moduleInstancedescriptors file shown below includes this appropriate entry:

Info

In this example only one moduleInstance is present. Usually you will need to ad your module to an existing list.

...

In order to refer to all four locations in one go (Instead of having to create four different timeseriesset) a locationset is defined in the file LocationSets 1.00 Default.xml in the RegionConfigFiles directory:

Set up Id Mapping

Step 4: Make the idmap file

No Format

<?xml version="1.0" encoding="UTF-8"?>
<locationSets 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/locationSets.xsd">
	<locationSet id="LevelGauges" name="LevelGauges">
		<locationId>one</locationId>
		<locationId>two</locationId>
		<locationId>three</locationId>
		<locationId>four</locationId>
	</locationSet>

</locationSets>

Set up Id Mapping

Step 5: Make the idmap file

 The format of the IdMap files is described in the  The format of the IdMap files is described in the DELFT-FEWS configuration guid and also in the .xsd scheme. All idMaps are stores in the IdMapFiles directory.  The Idmap needed for this example (IdImport 1.00 Default.xml) should match the parameter WaterLevel to H.obs and should also map the four locations. The files is shown below:

No Format
<?xml version="1.0" encoding="UTF-8"?>
<idMap 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" version="1.1">
	<parameter internal="H.obs" external="WaterLevel"/>
	<location internal="one" external="LocA"/>
	<location internal="two" external="LocB"/>
	<location internal="three" external="LocC"/>
	<location internal="four" external="LocD"/>
</idMap>

Step

...

6: register the idmap file

Similar to ModuleInstances IdMap should also be registered. In this case we need to register the IdImport file in the file IdMapDescriptors in the RegionConfigFiles directory:

...