...
Overview
To be able to have only on one file that manages all the regional information, Delft-FEWS offers the functionality to use a DBF or shape files that can be linked to the configuration. Locations and locationSets can be automatically generated and useful information as idMaps, thresholdvalues or validation values can be derived from these tables. It is also possible to link to one or more DBF files that contain time-dependent attributes. This can be used to define time-dependent coefficients that can be used by the new transformation module.
Finally you have a configuration that has many links to the DBF / shape files, but that will be managed only in these files. The advantage is that these files can simply be updated by automatic updating processes.
...
- you generate locations in a locationSet and define attributes to these locations that store additional information like idMapping or validation limits.
- locationSets can be generated from the DBF or from another locationSet by using conditions.
- idMaps can be linked to the location text attributes.
- all values in validationRuleSets can be linked to location number attributes
- all threshold values can be linked to location number attributes
- displayGroups can be generated automatically from locationSets
- it works both for regular point locations as for grids
- values in coefficientSetFunctions in a transformation config file can be linked to location number attributes
Configuration
locationSets
...
| No Format |
|---|
<locationSet id="ST_K.meting" editable="false">
<locationSetId>gegevensdump</locationSetId>
<constraints>
<not>
<attributeTextEquals equals="" id="IDMAP_KLEP"/>
</not>
<attributeTextEquals equals="Stuwen" id="TYPE"/>
</constraints>
</locationSet>
|
It is also possible in a locationSet to link to time-dependent attributes in a DBF file. This is very useful to define attributes that are used as coefficients in a coefficientSetFunction in a transformation config file. In that case the coefficientSetFunction needs to be defined only once with a link to the correct attributes. Then a transformation run will use the coefficientSetFunction to create coefficientSets for each location and time-period by taking the required values from the attributes from the DBF file automatically.
Time-dependent attributes need to be defined in a separate DBF file. In the locationSet use the attributeFile tag to make a reference to such a file. The following xml example has a reference to the file PumpStationsAttributes.dbf, which contains attributes that have different values for different periods in time, as well as different values for different locations. In this case the startDateTime and endDateTime tags refer to the columns in the DBF file that contain the start and end dates and times for each row. A given row in the DBF file contains values that are only valid between the optional startDateTime and endDateTime for that row. If a row has no startDateTime, then it is valid always before the endDateTime. If a row has no endDateTime, then it is valid always after the startDateTime. If a row has no startDateTime and no endDateTime, then it is always valid.
| No Format |
|---|
<locationSet id="PumpStations">
<esriShapeFile>
<file>PumpStations</file>
<geoDatum>WGS 1984</geoDatum>
<id>%ID%</id>
<name>%ID%</name>
<x>%X%</x>
<y>%Y%</y>
<z>0</z>
<attributeFile>
<dbfFile>PumpStationsAttributes</dbfFile>
<id>%ID%</id>
<timeZoneOffset>+05:00</timeZoneOffset>
<dateTimePattern>dd-MM-yyyy HH:mm</dateTimePattern>
<startDateTime>%START%</startDateTime>
<endDateTime>%EIND%</endDateTime>
<attribute id="speed">
<number>%FREQ%</number>
</attribute>
<attribute id="discharge">
<number>%POMPCAP%</number>
</attribute>
</attributeFile>
</esriShapeFile>
</locationSet>
|
locations
The regional configuration file Locations is not needed any more, except for other locations that are not supplied in a DBF file.
...