02 LocationSets

Location sets may be used to define logical groups of locations. Often an action may need to be taken on a whole set of locations (e.g. validation). By creating a LocationSet the action need only be defined once.

Any location may appear in more than one location sets. Internally a location set is simply evaluated as a list of locations.

When available on the file system, the name of the XML file is for example:

LocationSets 1.00 default.xml

LocationSets                              Fixed file name for the locationSets configuration

1.00                                            Version number

default                                       Flag to indicate the version is the default configuration (otherwise omitted).

Figure 24 Elements in the LocationSets configuration

locationSet

Root element for the definition of a location set. Multiple entries may exist.

Attributes;

•         id: Id of the location set. This must be unique

sortingLocationAttributeId

You can specify an attribute that should be used for sorting the locations (in this very particular locationSet only!) in the user interface. This is useful for list locations in for example a logical river order (upstream to downstream). The attribute should then contain a numbering. Note that the attributes are ordered as strings, so use 00001 instead of 1.
Option is available since 2014.01

description

Optional description of the location set. Used for reference purposes only.

locationId

Location ID configured to be a member of the locationSet. Multiple entries may exist.

locationSetId

LocationSet ID configured to be a member of the locationSet. Multiple entries may exist. This is useful to group locationSets together.

esriShapeFile and CSV file

It is possible to define locationSets with locations that are automatically generated (so NOT defined in the locations.xml) from an ESRI Shape file or from a CSV table. See all detailed information at the next page

table

It is also possible to define locationSets with locations that are read directly from a database. The contents of the database table are on the fly read and converted to a DBZ file. This DBZ file will be used by FEWS. This is for backup purpose in case the database is not available any more, like in stand-alone test environments.

See all detailed information at the next page

Label

It is possible to define a label that is presented in the map. For more information, see Explorer.