Since 2018.01. Name of the OC connection. The user can choose between client config files of type OC Client type SINCE 2018.01. List of root config files that is used by this instance. Automatically downloaded on startup SINCE 2018.01. Option to tune the java virtual machine for an OC or FSS SINCE 2012.01/2015.01. Local cache size for downloaded time series from central database (when not using synchronization) or from the new archive server. Since 2015.01 downloaded blobs are stored in the temp dir and deleted on exit. SINCE 2012.02. Local datastore database format. Only applicable for SA or OC with synchronization Since 2014.01. Adds additional (system) logging. Since 2020.02. Directory that contains all cold states. In this case all the cold states that are in the database are ignored. In the import state activity for the general adapter there is an option to keep the zipped state outside the database and stored inside this directory. Since 2018.01. Module data set that is automatically exported on a FSS or OC. As soon the module data is changed the export dir is deleted and re-exported Since 2022.02. Dummy profile. Not using a local datastore. Configure this when you want to allow the user to select DDA besides a synch profile. Database blobs (e.g. time series) are downloaded on the fly. When the connection to the database is lost the user has to wait till the connection is reastablisched. With a local datastore synch profile the OC goes into read-only mode after the connection to the database is lost. SINCE 2017.02. Defines synchronization channels which control what exactly is synchronized to the Operator client when using synchronization (not using direct database access). Profile ids the user can choose from are listed with the connections earlier in this file. SINCE 2012.01. Parameters, Locations, Qualifiers and External Historical Time Series can by kept outside the MC database (without blobs or xml) Optional description of the profile. single fdb file, native driver, only works on Windows and Linux derby directory. Works on every platform HyperSQL. Only use for testing. Currently beta Since 2020.01. Stand alone with extra features not available in OC Since 2020.02. Client for Delft-FEWS Web Services. Since 2025.02. Course Leader for Delft-FEWS WaterCoach client-server. Since 2025.02. Participant for Delft-FEWS WaterCoach client-server. Name of the module data set exported dir relative to the region home Database when the external tables are not hosted by the MC database server. When local datastore is used the database is not optional By default (false) the open database has read write access by FEWS and others. Changes in the open database by others are visible in FEWS. When data is only stored in the open database clients needs direct access to the open database because data in the open database can not be synchronised to the local datastore. When true the data is the open database is not replacing the config and time series in the FEWS/MC database. The data is stored in the MC database AND in the open database. The open database is write only for FEWS and read only for others. Mirroring increases also the performance and reduces the network load and external time series are still synchronized to clients. Time series written with this synch level are written to the blobbed database and to the unblobbed external open database. When not specified all external historical time series are written to the external database and none of the external historical time series are written to the FEWS blobbed database Database schema of the table that contains parameter groups. This table is required. Items in this table are added to the region config when they are not in the xml configuration. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains parameter groups. This table is required. Items in this table are added to the region config when they are not in the xml configuration. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains parameters. This table is optional. Table is needed when the parameters are grouped into a tree. Items in this table are added to the the region config when they are not in the xml configuration. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that links parameters to parameter nodes. This table is optional. Items in this table are added to the the region config when they are not in the xml configuration. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains locations. This table is required. Items in this table are added to the the region config when they are not in the xml configuration. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu. Database schema of the table that contains qualifiers. This table is optional when you don't use qualifiers in your time series sets. This table replace can replace region configuration. Items in this table are added to the the region config when they are not in the configuration. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains qualifier sets. This table is optional when you don't use qualifiers in your time series sets. This table is dynamic and depends on qualifiers sets in your time series sets Database schema of the table that contains module instance. This table is optional when you ensure the parameter / location / qualifier combination is unique. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains time steps. This table is optional when you ensure the parameter / location / qualifier combination is unique. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains aggregation periods. This table is optional when you ensure the parameter / location / qualifier combination is unique. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains the users. This table is optional when you don't have a manual edit history table. Items are added to this table on the fly as soon they are referenced by written time series. All items from region config can be copied to this table at once with the F12 menu Database schema of the table that contains a key for every parameter/location/qualifier/moduleInstance/timeStep/aggregationPeriod/valueType combination. The qualifier, timeStep, moduleInstance, timeStep, aggregationPeriod and value type columns are optional. These columns are optional when you ensure the parameter / location / qualifier combination is unique. Database schema of the table that stores the values of external historical time series series. When specified the the external historical data is no longer stored in the FEWS database or read from the FEWS database. Database schema of the table that stores the comments of external historical time series series. When not specified comments are not saved. Database schema of the table that stores the manual edit history of external historical time series. When not specified the edit history is not available in the time series dialog Database schema of the table that stores the sample meta data. The sample data it self is stored in the timeSeriesValuesAndFlagsTable. Every sample provider should use it's own set of locations. When not specified the sample meta data is lost and sample data is shown as external historical data. Database schema of the table that stores the filters. A filter groups the times in the TimeSeriesKey table into a tree. This table defines the tree, the filterTimeSeriesKeys table links the time series to the leafs. This table is optional and only required if an external application wants to mirror the filter tree. It is not required for writing or reading time series. This table is only updated by FEWS and is a mirror of the Filters.xml. The time series in a filter can be controlled by changing the attributes of a location or sample parameter. In the Filters.xml the referenced locations sets are based on constraints on attributes. Sample parameters can be added to a filter based on parameter attributes Database schema of the table that links time series to filters. Contains filter key / time series key pairs Name of the table Auto generated unique integer by database instance. Used in foreign key relations Column for the ids of the parameters in the table. Name of the parameter group. When not specified the id is used as name Long (descriptive) name of location (tool tip) or description. integer column 0:instantaneous/1:accumulative/2:mean. The unit of the values internally stored in the data store. By specifying a display unit you can use another unit seen by the user Specify when the unit seen by the user is not the same as the unit of the values internally stored in the data store. Also specify displayUnitConversionsId above as first element in this config file. In this unit conversions the conversion from (internal) unit to display unit should be available Name of the table Auto generated unique integer by database instance. Used in foreign key relations Unique text identifier. Not generated by the database server. Since 2017.01. Column for the persistent ids. The persistent ids will never change. In the fews database and the archive the persistent ids will be used. The regular id is used in configuration and may change over time while the persistent id keeps the same. Short name of parameter for charts. When not available the id is used Short name of parameter for chart axes. When not specified the id is used Long (descriptive) name of location (tool tip) or description. Reference to a parameter group in the parameters groups table Default accuracy (smallest increment between two values) of the calculated or measured values for all parameters in this group. Value resolution can also be specified for a single parameter (since 2011.01). By default the resolution is dynamic and the values are stored as a 32 bit floating point with 6 significant digits. Floating points don't compress very well and are slow to decode. It is far more efficient to store a value as an integer with a scale factor (= value resolution). When a 8, 16 or 24 bit integer is not big enough to achieve the value resolution the default 32 bit floating point is used as fall back. E.g. When the accuracy of the water level is half a centimeter specify 0.005. When the accuracy of the discharge in 10 m3/s specify 10. Option to indicate if a time series of this parameter type is allowed to contain missing values when being used by a model or a transformation. When omitted this value will default to 'true'. If this is used for a transformation, then it is also required to set the option checkMissing in the inputVariable of the transformation to true. Standard name defined by the netcdf CF convention. Standard name is rejected when not in list version 57, see https://cfconventions.org/Data/cf-standard-names/57/build/cf-standard-name-table.html Standard name modifier defined by the netcdf CF convention Cell method as defined in the netcdf CF convention. See https://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#cell-methods SINCE 2016.02. Optional geospatial_vertical_positive attribute as defined in the netcdf DataDiscoveryAttConvention convention. This is currently only used for export to netcdf files when this parameter is used as domain parameter in a time series set. This attribute indicates which direction is positive (a value of "up" means that z increases up, like units of height, while a value of "down" means that z increases downward, like units of pressure or depth). The use of these further geospatial attributes is suggested. http://www.unidata.ucar.edu/software/thredds/current/netcdf-java/metadata/DataDiscoveryAttConvention.html Custom attribute that can be referenced from id maps, validation rules, thresholds, warning levels, transformations. Name of the table Auto generated unique integer by database instance. Used in foreign key relations Unique text identifier. Not generated by the database server. When not available the id is used Long (descriptive) name of location (tool tip) or description. Reference to a parameterNode is this table Name of the table reference to parameter nodes table reference to parameters table Coordinate reference system used for the x y columns Name of the table Auto generated unique integer by database instance. Used in foreign key relations Unique text identifier. Not generated by the database server. Since 2017.01. Column for the persistent ids. The persistent ids will never change. In the fews database and the archive the persistent ids will be used. The regular id is used in configuration and may change over time while the persistent id keeps the same. Short name of location for chart legend Short name of location for chart legend. Long (descriptive) name of location (tool tip) or description. Filename of an image file in the IconFiles config directory (including file extension). Tooltip to be displayed in the FewsExplorer. You can use use \n or CDATA or HTML when you need multiple lines. Besides the global properties and column names you can use the following virtual columns %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%] A tree is used in the locations list when parent/child relations are used. All the children of a location are automatically selected in the fews explorer 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. 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. X coordinate of the point (Easting). Y coordinate of the point (Northing) Z coordinate of the point (altitude). e.g. %Z%, put the actual dbase column name between %% The default z is 0 The area of the location/polygon. 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 Custom attribute that can be referenced from id maps, validation rules, thresholds, warning levels, transformations. Describes where and why this relation is used Reference to another location. This location relation id can be referenced from time series sets. Describes where and why this attribute is used Text that can be referenced from id maps, validation rules, thresholds, warning levels, transformations Number that can be referenced from id maps, validation rules, thresholds, warning levels, transformations Can be used in transformations. Integer column with 0 and 1 is allowed besides boolean column Since 2018.01. Timestamp column. Datetime that can be referenced from id maps, validation rules, thresholds, warning levels, transformations. Id of the attribute, this id can be referenced from id maps, validation rules, thresholds, warning levels. An attribute is referenced from other config files by quoting the attribute id with @s, e.g. @HARD_MAX@ Name of the table Auto increment integer column used in foreign key relations Unique text identifier. Not generated by the database server. Since 2017.01. Column for the persistent ids. The persistent ids will never change. In the fews database and the archive the persistent ids will be used. The regular id is used in configuration and may change over time while the persistent id keeps the same. Short name of parameter for charts Short name of parameter for chart axes Long (descriptive) name of location (tool tip) or description. Name of the table Auto increment integer column used in foreign key relations Unique text identifier. Not generated by the database server. Since 2017.01. Column for the persistent ids. The persistent ids will never change. In the fews database and the archive the persistent ids will be used. The regular id is used in configuration and may change over time while the persistent id keeps the same. Contains references to row in Qualifiers table Contains references to row in Qualifiers table Contains references to row in Qualifiers table Contains references to row in Qualifiers table Name of the table Auto increment integer column used in foreign key relations Unique text identifier. Not generated by the database server. Since 2017.01. Column for the persistent ids. The persistent ids will never change. In the fews database and the archive the persistent ids will be used. The regular id is used in configuration and may change over time while the persistent id keeps the same. Name Long (descriptive) name Name of the table Auto increment integer column used in foreign key relations Unique text identifier. Not generated by the database server. Name Name of the table Auto increment integer column used in foreign key relations Unique text identifier. Not generated by the database server. Name of the table Auto increment integer column used in foreign key relations Unique text identifier. Not generated by the database server. ids. Name of the table Auto generated unique integer by database instance. Used in foreign key relations reference to parameters table reference to location table Reference to qualifier table Column is optional when you don't use qualifiers. Reference to time step table Column is optional when parameter/location/qualifier combination is unique. Reference to aggregation period table Column is optional when parameter/location/qualifier combination is unique. Reference to module instance key column Column is optional when parameter/location/qualifier combination is unique. 0=scalar, 1=grid, 2=longitudinal profile, 3=polygon, 4=sample, 5=rating curve only scalar and sample are supported so far Every time a row is updated/added in the TimeSeriesValuesAndFlagsTable or TimeSeriesCommentsTable this time is updated Name of the table reference to time series keys table time of the measurement Float value column. Column should be nullable to store missing value Integer column, compound flags flags = flag + valueSource * 10 + loFlagSource * 100 + outOfDetectionRangeFlag * 1000 + state * 10000 + hiFlagSource * 100000; Name of the table reference to time series keys table time of the measurement Column with comment Name of the table reference to time series keys table time of the measurement time of the edit action 1970 JAN 1, 0:00 GMT is used for the backup of the original value before any edit NULL can not be used because it is part of the primary key contains reference to users table Column to store the user id NULL is used for the backup of the original value before any edit Float value column. Column should be nullable to store missing value Integer column, compound flags flags = flag + valueSource * 10 + flagSource * 100 + outOfDetectionRangeFlag * 1000 + state * 10000; Column to store the comment Name of the table reference to locations table. Location of the sample. All sample values in the TimeSeriesValuesAndFlagsTable for this location and time stamp belong to this sample time of the sample id delivered by the provided (sample parser). Uniqueness is not enforced Column that contains extra information about the sample Name of the table Auto generated unique integer by database instance. Used in foreign key relations Unique text identifier. Not generated by the database server. Short name of filter for chart legend Optional. Long (descriptive) name of filter (tool tip) or description. Optional, Used to show the filters in a tree Permission to control who can view this filter Permission to control who can edit time series enumerated in this filter (only editable time series can be edited) Name of the table Reference to filters table Reference to time series keys table e.g. com.microsoft.jdbc.sqlserver.SQLServerDriver or com.mysql.jdbc.Driver Connection string to database server. Test the connection string in db visualiser before using When specified the connection to the database is first tested before asking the jdbc driver to connect. Some jdbc drivers are using a very long time out. User name Password for user Encrypted password for user. Encrypt a password with the F12 menu Time zone used by the database for storing time stamps SINCE 2018.02, Enables debug logging SINCE 2018.02, Total size of the rolling files in megabytes When true every line in the log file logged from a workflow includes the task run id eg. 2019-09-12 15:37:19.246 INFO @MC01:000001 . The task run id is prefixed with @, the @ is always at position 30 when the line includes a task run id. The task run id is followed by a space. Lines that start with a tab (\t) are a continuation of the previous line Enables logging of errors to the windows event logger. False by default. Ignored under linux. Enables logging of errors to the linux syslog using the specified facility. Ignored under Windows. Name of the root config file that is downloaded from the database Since 2016.02. Use this when the PAC file is located on the intranet. for example. http://wpad.directory.intra/wpad.dat. SINCE 2017.01. see https://en.wikipedia.org/wiki/Proxy_auto-config Since 2016.02. Use this when you want to use your own WPAD script. Use a CDATA block around your script Local datastore free client (also known as Direct Datase Access). Allows the user to select the database to connect to when multiple connections are specified via a selection dialog. NB. When specified, the standard cache files are wiped, a subdirectory with the id attribute as directory name is used instead for the cache files. When for instance id=mc00, then the cache files for this connection are stored under localDataStore/mc00. SINCE 2012.01. Connection to central database required for FS/OC Deprecated and obsolete since 2017.02 SINCE 2017.02. When configured synchronization is used by this OC. The referenced profile id should be defined in this clientConfig.xml. Synchronization is only allowed for an OC. When multiple synch profile ids are listed the user can choose between different profiles at start up of this OC. When a synch profile is configured all connections in the client config should list at least one profile id. id of the connection Name of this connection in the selection dialog (defaults to above id).