Versions Compared

Key

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

...

Optional element available since 2018.01. By default this element is set to true and FEWS will log a debug message when an empty locationSet is created. If set to false, FEWS will log a config error instead. When separate locationSets xml-files are used, each file can have its own <allowEmptyLocationSets> element, which will only apply for the location sets listed in that file.

sortByName

Sorts the locations in this set by name. When false the order  of the specified location ids or the order in the esri shape file is used. Note that this only applies to the sorting of locations within a locationSets. This will have effect on e.g. sorting of locations in export files, or within a plot. Sorting of locations in filters and displaygroups is configured in their respective configuration files.Deprecated. Sorting by name has become default, a sorting attribute can be defined in the location set <sortingLocationAttributeId>

sortingLocationAttributeId

...

  • Give the main locationSet based on the csvFile a sortingLocationAttributeId that makes sense (e.g. Name or logical river order). This will be the first locationSet found by FEWS, and therefore will dictate the sorting order used in the Filter (aka DataViewer, configured in Filters.xml). This is because by default locations sets use the sorting of the parent location set.
  • Give all locationSets derived from the main locationSet a sortingOrder to overrule the default by name sorting order defined in the main locationSet (based on the csvFile).
  • Create separate locationSets for displaysGroups and Exports when the order in these two is different.
  • Don't define numeric attributes as text attributes in your configuration. Don't use leading zeros for numeric attributes in your csv. Leading zeros and/or text attributes will significantly increase the memory usage and start-up time of FEWS.

  • (General recommendation) After making these kind of changes to config, if you experience unexpected behaviour in Delft-FEWS after a refresh, restart Delft-FEWS to see if this behaviour is persistent.

...