Since FEWS 2026.01. If this option is set to true the rows with duplicate location ids are skipped in the listed main files (not the attribute files). e.g. @catchment@. Generate a sub location set id for every unique location set id generated by the function. e.g. @catchment@. Names of the generated location sets. First location in the generated location set is used to generate the name. Effects the order of legend items, lists and columns in displays and reports. A collection of locations. Can be build from other location sets, shape files or listing locations explicit or by only specifying constraints Add all the locations in the specified location set to this location set. When were constraints are specified only the locations that matching all the constraints are added Loads locations from a shape file and adds these locations to the location set. When constraints are specified only locations that matching all the constraints are loaded. Use a different excluding constraints when locations from one shape file are loaded by different location sets For locationId, name, description, shortName, tooltip, parentLocationId and custom attributes you can reference the dbase file columns by putting the dbase column name between name) between % Loads locations from a geojson file and adds these locations to the location set. When constraints are specified only locations that matching all the constraints are loaded. Use a different excluding constraints when locations from one shape file are loaded by different location sets For locationId, name, description, shortName, tooltip, parentLocationId and custom attributes you can reference the attributes by putting the dbase column name between name) between % Loads locations from a gpkg file and adds these locations to the location set. When constraints are specified only locations that matching all the constraints are loaded. Use a different excluding constraints when locations from one shape file are loaded by different location sets For locationId, name, description, shortName, tooltip, parentLocationId and custom attributes you can reference the attributes by putting the dbase column name between name) between % Since 2013.01, FEWS-8714. Loads locations from a csv file and adds these locations to the location set. When constraints are specified only locations that matching all the constraints are loaded. Use a different excluding constraints when locations from one csv file are loaded by different location sets For locationId, name, description, shortName, tooltip, parentLocationId and custom attributes you can reference the dbase file columns by putting the csv column name between name) between % Loads locations from a database table and adds these locations to the location set. When constraints are specified only locations that matching all the constraints are loaded. Use a different excluding constraints when locations from one shape file are loaded by different location sets For locationId, name, description, shortName, tooltip, parentLocationId and custom attributes you can reference the dbase file columns by putting the dbase column name between name) between % Restriction for the locations in this location set. Only locations where for all the constraint is valid are included in this location set. It is a filter for the location sets and shape files specified above. Links an extra attribute file to multiple parent tabular files. Useful for id maps and thresholds. These attributes can not be used in for constraints configured in this location set. Location set ids can not be listed when using this locationSet wide attribute file Set editable="true" to enable adding/removing locations to this locationSet in the ConfigEditor UI. Since 2018.01. If this element is set to false, an error will be logged if an empty location set is configured. By default FEWS will allow empty location sets and will only log a debug message. name of layer in the map layer files or a full absolute path to the shape file (*.shp). Character set of the text in the dbf file. Specify only when the dbf file contains non western characters. When x and y are specified the shape file is optional and only the dbf is required. When x and y are not specified the coordinates are read from the shape file. When the shape file contains polygons the x and y are required Links an extra csv or dbf file to the current shape file to import extra attributes. Optionally allows defining different values for different periods and multiple values (tables) per attribute Geo datum of the coordinates, default is lat long, WGS 1984 A projection file has the same name as the shp file, only the with extension .prj instead of .shp. A prj file can be used instead of specifying the geo datum. When false lat long, WGS 1984 will be used name of layer in the map layer files to the geojson file (*.geojson). When the geojson file contains multiple shape types you can add the layer multiple times for each shape type When x and y are specified the shape file is optional and only the dbf is required. When x and y are not specified the coordinates are read from the shape file. When the shape file contains polygons the x and y are required Links an extra csv or dbf file to the current shape file to import extra attributes. Optionally allows defining different values for different periods and multiple values (tables) per attribute name of layer in the map layer files to the geojson file (*.geojson). When the geojson file contains multiple layer you can can specify the layer name When x and y are specified the shape file is optional and only the dbf is required. When x and y are not specified the coordinates are read from the shape file. When the shape file contains polygons the x and y are required Links an extra csv or dbf file to the current shape file to import extra attributes. Optionally allows defining different values for different periods and multiple values (tables) per attribute name of layer in the map layer files or a full absolute path to the csv file (*.csv). When the file is automatically overwritten by an external source Character set of the text in the csv file. Specify only when the csv file contains non western characters. Links an extra csv file to the current shape file to import extra attributes. Optionally allows defining different values for different periods and multiple values (tables) per attribute Database with the locations table Loads locations from this database table and adds these locations to the location set. When constraints are specified only locations that matching all the constraints are loaded. Use a different excluding constraints when locations from one shape file are loaded by different location sets For locationId, name, description, shortName, tooltip, parentLocationId and custom attributes you can reference the dbase file columns by putting the dbase column name between name) between % Geo datum of the coordinates Links an table to the current table to import extra attributes. Optionally allows defining different values for different periods and multiple values (tables) per attribute Since 2021.01. Links an csv or dbf file to the current database table to import extra attributes. Optionally allows defining different values for different periods and multiple values (tables) per attribute. ids of the locations in the shape file. e.g. "H_%ID%", put the actual column name between %%. Names of the locations e.g. %NAME%, put the actual column name between %% Long (descriptive) name of location (tool tip) or description. e.g. "Meteo station %NAME%, put the actual column name between %% Short name of location for chart legend. e.g. %SHORT_NAME%, put the actual column name between %% Filename of an image file in the IconFiles config directory (including file extension). Label to be displayed on the map in FewsExplorer. Besides the global properties and column names you can use the virtual columns %LAST_VALUE%, %LAST_VALUE_TIME%, et cetera (similar to toolTip) Tooltip to be displayed in the FewsExplorer. You can reference location attributes with @ATTRIBUTE_ID@ (Since 2013.02) You can reference csv/dbf columns without defining an attribute with %COLUMN_NAME% You can use use \n or CDATA or HTML when you need multiple lines. You can use the following variables %LAST_VALUE%, %LAST_VALUE_TIME%, %FORECAST_START_TIME%, %MAXIMUM_VALUE%, %MAXIMUM_VALUE_TIME% The tooltip supports html including images and hyperlinks. The url in the hyper link can be an internet url, an executable file, a document file, or a folder. Use the CDATA xml tag to include html in a xml file. By default the following tool tip is used. ID: id\n Name: name\n Desc: description Last value [%LAST_VALUE%] Time [%LAST_VALUE_TIME%]\n Forecast Start Time [%FORECAST_START_TIME%]\n Maximum [%MAXIMUM_VALUE%] Time [%MAXIMUM_VALUE_TIME%] When a location has a parent id it is an invisible child location. All the children of a location are automatically selected in the fews explorer e.g. H_%PARENT_ID%, put the actual column name between %% This offset is always relative to GMT. For example "+02:00" means GMT+02:00. If no offset specified, then time zone GMT is used by default. Optional pattern for the dateTimes in the character column. Default is yyyyMMdd, this is the internal format a dbf file is using when the column is of type 'D'. Since 2014.01. e.g. %START_TIME%, put the actual column name between %%. When specified multiple rows with the same location id are allowed. The row is used for the specified period. The location is invisible for times when no row is applicable Since 2014.01. e.g. %END_TIME%, put the actual column name between %%. When specified multiple rows with the same location id are allowed. The row is used for the specified period. The location is invisible for times when no row is applicable Since 2016.01. When true (default) errors will be logged for locations with time dependent attributes that have overlapping periods or gaps between periods Deprecated and obsolete since 2014.01, use startDateTime. Optional start time of the period for which a location is visible in the user interface. The start time is inclusive. If not defined, then a location is visible for all times before end time. Possible to refer to a column. Use e.g. "%START_DATE% %START_TIME%", put the actual dbase column name between %%. When all the locations in the csv/dbf file are visible for the same period, specify a literal date time eg "2000/1/1". Deprecated and obsolete since 2014.01, use endDateTime. Optional end time of the period for which a location is visible in the user interface. The end time is inclusive. If not defined, then a location is visible for all times after start time. Possible to refer to a column. Use e.g. "%END_DATE% %END_TIME%", put the actual column name between %%. When all the locations in the csv/dbf file are visible for the same period, specify a literal date time eg "2002/1/1". X coordinate of the point (Easting). e.g. %X%, put the actual column name between %%. Y coordinate of the point (Northing) e.g. %Y%, put the actual column name between %%. Z coordinate of the point (altitude). e.g. %Z%, put the actual column name between %% The default z is 0 Since 2022.02. %Bed_level%, put the actual column name between %% Since 2017.02. Sigma coordinate of the layer. e.g. %Sigma%, put the actual column name between %% The area of the location/polygon. e.g. %AREA%, put the actual column name between %% Relation that can be used in time series sets. When a location relation is specified in a time series set the time series set locations are mapped to the related locations and these related locations are used to read/write the time series. e.g. "H_%UPSTREAM_ID%, put the actual column name between %% Description name of csv file in the map layer files or a full absolute path to the csv file . When the file is automatically overwritten by an external source name of shp file in the map layer files name of geojson file in the map layer files When the geojson file contains multiple shape types you can add the layer multiple times for each shape type When true, no geometry needs to be read. This can be useful when the geojson file is used in multiple places for different attributes. name of geojson file in the map layer files When true, no geometry needs to be read. This can be useful when the geopackage file is used in multiple places for different attributes. When the file contains multiple layers the layer name should be specified name of dfb file in the map layer files or a full absolute path to the dbf file . Character set of the text in the dbf file or csv file. Specify only when the csv file contains non- latin characters. Don't configure for geojson/gpkg files ids of the locations in the dbf file. e.g. "H_%ID%", put the actual dbase column name between %%. Since 2021.02. When false (default) a config warning is logged for each location id not in the locations set Since 2023.01. When true a config error is logged when not all locations are listed that exist in the location set. Missing rows can be added automatically in the tabular config viewer Since 2023.01. When true a config error is logged when not all locations are listed that exist in the parent csv/shp file. The location set can contain fewer ids that the csv due a constraint defined in the location set. Missing rows can be added automatically in the tabular config viewer This offset is always relative to GMT. For example "+02:00" means GMT+02:00. If no offset specified, then time zone GMT is used by default. default is yyyyMMdd, this is the internal format a dbf file is using when the column is of type 'D' Description Table name ids of the locations in the dbf file. e.g. "H_%ID%", put the actual dbase column name between %%. Since 2021.02. When false (default) a config warning is logged for each location not in the locations set start time of the period the values in the row should be used eg "%START_DATE% %START_TIME%", put the actual dbase column name between %%. When the values are always valid do not specify a period. When the all the values in the dbf file are valid for a constant period specify a literal date time eg "2000/1/1" Default is the beginning of time see start date time Set the visibilty period of the location when not defined in the main location see visibility start date time Short name of location for chart legend. e.g. %SHORT_NAME%, put the actual column name between %% Z coordinate of the point (altitude). e.g. %Z%, put the actual column name between %% The default z is 0. Z coordinate of the point (altitude). e.g. %Z%, put the actual column name between %% The default z is 0 Since 2016.01. When true (default) errors will be logged for locations with time dependent attributes that have overlapping periods or gaps between periods Relation that can be used in time series sets and constraints and functions. When a location relation is specified in a time series set the time series set locations are mapped to the related locations and these related locations are used to read/write the time series. e.g. "H_%UPSTREAM_ID%, put the actual shape/dbase column name between %%. Can not be used in combination with startDateTime and endDateTime SINCE 2019.01. Relation that allows map to multiple locations. A one to many relation that can be only be used in time series sets and not in constraints or functions. When a location relation is specified in a time series set the time series set locations are mapped to the related locations and these related locations are used to read/write the time series. e.g. "H_%UPSTREAM_ID%, put the actual shape/dbase column name between %% Can not be used in combination with startDateTime and endDateTime Makes it possible to ignore the lines that are not in use. It will skip all rows that have a certain column value Name of the column that should be checked Value of the column Ignore the case of the value Describes where and why this relation is used Reference to another location. e.g. H_%UPSTREAM_ID%, put the actual column name between %% When there is no value for the referenced column are config error is logged This location relation id can be referenced from time series sets. Name used in the tabular config file display 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 and will not influence the location order in, for instance, the data viewer Since 2014.01 Location attribute Id the locations should be sorted by in this set. Each location can only have 1 attribute which defines the sorting, this will automatically be the first defined. Sorting of locations with different sorting attributes will result in grouping locations with the same sorting attribute together. Id of location attribute, each location that has a value for this attribute belongs to the chainage. The value of this attribute determines the position in the chainage. Optional field. If configured, this location attribute will be used as the label of vertical station lines in longitudinal plot If a location does not have this attribute, there will be no vertical station line drawn. This should be a text attribute.