...
- Only .csv or .dbf files that are used in the configuration can be displayed.
If locations are configured in *.xml, *.Json or database, these file will not be shown. - Files are sorted alphabetically.
The meta data files are not grouped in sub-folders, this information is ignored.- Content of the first file is shown by default in the bottom panel. Selecting another file will display its content.
...
By default the column headers of the meta data table use the column name in the CSV or DBF file.
They can be overruled in LocationSets.xml with two name elements:
- <columnDisplayName> for standard location elements (like id, name, x, y)
- <name> for location attribute names (like HYFS_STATIONID in the example below)
Note: Do not use the same <name> twice within a single meta data file. This will throw a Config ERROR when Delft-FEWS is started.
...
Meta data rules to check the meta data <text> for errors can be configured in LocationSets.xml.
There are rules available to check the text value on format, against enumerationValues and against a regularExpression.
...
Often, locations will be defined in a single main location file, while the meta data is spread over several attributeFiles.
To make it easier to add new locations (and their required meta data), you can configure LocationSets.xml to automatically complete attributeFiles (since 2023.01).
...
Note: When you configure the <required> element for an attribute, Delft-FEWS will log an ERROR if they are not filled.
Using this option can help you identify missing required meta data more easily.
| Code Block |
|---|
<constraints> <attributeTextEquals id="ACCEPTANCE" equals="ACCEPTED"/> </constraints> |
Automatically accept or reject locations in locationSet
<To be documented>