Configuration for a single run of the General Adapter. Exactly one such configuration is necessary for each module instance run. General - i.e. activity independent - settings for this General Adapter run. Burn-in periods for cold state starts. Activities that will be performed within this General Adapter run. Optional description of the General Adapter run. Version of the PI specification that is supported by the pre and post adapter Since 2022.02. When true all exported and imported files are transferred in memory between FEWS and execute activities. An execute activity can read the file content from var input = (InputStream) System.getProperties().get(file) and write to var output = (BufferedOutputStream) System.getProperties().get(file). All execute activities that transfer files to and from FEWS should be java activities that don't use a custom jre and check the System.getProperties().get(file) before they fall back to read/write the file on disk. Only NetCDF3 files can be transferred in memory. For NetCDF files the System.getProperties().get(file) contains a chunked byte array (byte[][]). An empty byte[][] array is set to tell an execute activity to save the nc file to memory as chunked byte array. The diagnostic file is also transferred in memory. Execute activities should always fall back on the files on disk when the System.getProperties().get(file) == null Root directory of the module instance. This may be either a relative or absolute path. Working directory for several activities. Best to use %TEMP_DIR% as value. The OS location of the temp dir can be overruled with global property tempDir. When running the GA in debug mode using the manual forecast dialog (ctrl+R) the temp dir is preserved till FEWS exits Directory to which the General Adapter will export data. Directory to which the General Adapter will export data sets. Check all export dataset activities for changes before updating. If no change detected skip update. If change detected dataset is updated Option to purge content of export module dataset dir before updating. Default 'false' will result in overwriting of existing contents Id of a file that contains mapping from internal to external location and parameter ID's. Id of UnitConversions to be used for export unit mapping Directory the General Adapter will import data from. Id of a file that contains mapping from external to internal location and parameter ID's. Id of UnitConversions to be used for import unit mapping Directory of the dump file. List of directories that the General Adapter will dump in case of a module failure. The binary dump will include all sub directories. File containing diagnostic information about the module instance run. This file always is located in the importDir. Missing value definition for this TimeSeries. Defaults to -999 if not defined. An exception applies to NetCdf files: if exportMissingValue is not configured, then 9.96921e+036f is used Convert datum from Ordnance level during Import. Convert datum to Ordnance level during Export. Import data is converted from this timezone to GMT. Export data is converted from GMT to this timezone. The date time format of the %TIME0% variable. This date time format is only used if there is no date time format specified in the arguments for the variable. yyyy = Year, MM = Month in year, dd = Day in month, HH = Hour in day (0-23), mm = Minute in hour, ss = Second in minute. The date time format of the %START_DATE_TIME% variable. This date time format is only used if there is no date time format specified in the arguments for the variable. yyyy = Year, MM = Month in year, dd = Day in month, HH = Hour in day (0-23), mm = Minute in hour, ss = Second in minute. The %START_DATE_TIME% variable only works in an importStateActivity (since 2014.02) and inside a template file for an exportCustomFormatRunFileActivity (since 2013.02). The date time format of the %END_DATE_TIME% variable. This date time format is only used if there is no date time format specified in the arguments for the variable. yyyy = Year, MM = Month in year, dd = Day in month, HH = Hour in day (0-23), mm = Minute in hour, ss = Second in minute. The %END_DATE_TIME% variable only works in an importStateActivity (since 2014.02) and inside a template file for an exportCustomFormatRunFileActivity (since 2013.02). Since stable build 2015.01. Definitions of date time formats that can be used as arguments for the %TIME0%, %START_DATE_TIME% and %END_DATE_TIME% variables, e.g.: %START_DATE_TIME(idOfADateFormat)% %END_DATE_TIME(idOfAnotherDateFormat)%. Date time formats specified as arguments overrule the startDateTimeFormat and endDateTimeFormat specified above. The %START_DATE_TIME% and %END_DATE_TIME% variables only work in an importStateActivity (since 2014.02) and inside a template file for an exportCustomFormatRunFileActivity (since 2013.02). Deprecated and obsolete since 2009.01. Specify the member range in the workflow. The model time step adjusts the end time when necessary of the run period for this model and for all models/modules that will run after this model in the same task run Activities to start up a General Adapter run. Activities to export data through the Published Interface format. Since 2018.01 Activities to wait for event Activities to execute the module or its adapters. Activities to import data through the Published Interface format. Activities to shut down a General Adapter run. Purges a single file or a set of files within a directory. Creates directories and, if necessary, any parent directories. Use this task for directories expected by the adapter but not used as input or output directory. Input and output directories are automatically created Unzip a single file or a set of files within a directory. Zip a single file or a set of files within a directory. Exports a module instance state. Exports time series. Exports a data set. Triggers export of data set for active module instance. Since 2013.01 it is possible to export multiple data sets Exports map stacks. Exports longitudinal profiles. Since 2013.01. Calls a third party serializer that directly writes to a native model time series format. The serializer is not part of FEWS but is located in one of the jar files in the specified binDir Exports rating curve for the configured locations. All rating curves within the run period and the last rating curve before or at the start of the run period are exported Since 2016.01 Export time series with a single shared domainParameter at once to pi_tables.xml. All tables within the run period and the last table before or at the start of the run period are exported Exports a module parameter set. Triggers export of parameter set for active module instance. Exports a rating curve or other table for one or more locations Since 2020.01 Exports a csv file with attribute values for locations Exports scalar, grid or 1d/2d spectra time series to a NetCDF file. All time series specified inside one exportNetcdfActivity must have the same value type (grid, scalar, 1d spectra or 2d spectra). For this export it is required that all ensembles have exactly the same ensemble member indices. The usage of ensemble member id's (strings) is not supported yet. Exports a pi run file in xml format. The run file contains general information about the run executed by the general adapter that is used by the pre and post adapter. Since 2014.01. FEWS-10385. Exports a run file in netcdf format. The netcdf run file contains general information about the run executed by the general adapter that can be used by the pre and post adapter. Activity to create a custom run info file. This activity replaces tags in a template file with actual (modified) values. The template file can contain location attribute tags between '@' signs, general adapter tags between '%' signs and global properties between '$' signs. The specified template file will be copied to the specified export file before the tags are replaced. So the template file itself is not changed. If the export file already exists, then it will be overwritten. Exports an area selection mask as shape file or as PiMapStack. This activity requires an embedded polygon to be specified within the areaSelectionShapeFileBase64 field of the TaskProperties. This file is then available to be used by the pre and post adapter. Exports an area selection mask in the form of a PiMapStack (currently NGMS only). This activity requires selectedLocationIds to be specified within the TaskProperties. This selection is then available to be used by the pre and post adapter. Since 2015.01. Exports csv files as module run tables. Exports configured coefficient set for the configured location or location set. SINCE 2018.01. Used in combination with the parallel run option in the workflow. Wait until the specified file exits before starting the execute activities SINCE 2018.01. Used in combination with the parallel run option in the workflow. Wait until the specified file exits before starting the execute activities Executes a module or its adapters. Since 2014.03. FEWS-12495. Execute import activities after error occurred, activity with error still fails. Optional description of the execute activity. File that should exist before continue Timeout to wait in milliseconds. Imports a module instance state. Imports time series. Import map stacks. Imports scalar, grid or 1d/2d spectra time series from a NetCDF file resulting from the run of the external modules. All time series specified inside one importNetcdfActivity must have the same value type (grid, scalar, 1d spectra or 2d spectra). For this activity the exportPlaceholderFile option only works for scalar and grid data, not for spectra data. Note: this activity is exactly the same as importPiNetcdfActivity, only the name is better, since the NetCDF format has nothing to do with the PI format. Deprecated, do not use. Please use importNetcdfActivity instead. Imports scalar, grid or 1d/2d spectra time series from a NetCDF file resulting from the run of the external modules. All time series specified inside one importPiNetcdfActivity must have the same value type (grid, scalar, 1d spectra or 2d spectra). For this activity the exportPlaceholderFile option only works for scalar and grid data, not for spectra data. Import longitudinal profiles. Since 2017.02. Import shape file Since 2024.02. Imports GeoJson files Imports time series using a dedicated custom time series parser. Since 2015.01. Imports csv files as module run tables. Unzip a single file or a set of files within a directory. Zip a single file or a set of files within a directory. Purges a single file or a set of files within a directory. Optional description for the activity. Optional, set this to true to allow deletion of nested subdirectories when using a wild card. File or files to be deleted. Use * and ? as wild cards. Since 2023.02. Files older than this age are to be purged. Optional description for the activity. Directory to be created. Optional description for the activity. Zip File that is to be unpacked. Destination directory to which source is unpacked. Optional description for the activity. Source directory that has to be packed. Wildcards are NOT allowed. Since 2019.02 eSource file pattern to select a subset of files to be packed, relative to the source directory specified in the sourceDir element. Wildcards are allowed. Tags between %% are allowed since 2022.01 Since 2024.02 Pattern to parse the date/time from the file name. e.g.'BXD0521000005_???????'yyyyMMdd_HHmmss'.nc' Since 2024.02 Only files with file name in this period are allowed in this period Zip file that to be created. Optional description for the activity. File to which the general run information is exported. This should be either an absolute path or a path relative to the exportDir defined in the general section. Kind of environment variables for the pre and post adapters. These properties are copied to the run file. This is also a convenient way way to pass global properties to a pre or post adapter. An adapter is not allowed to access the FEWS global.properties directly. Global properties (between $) are replace by there literal values before copied to the run file. These extra options makes an additional pre or post adapter configuration file unnecessary. Optional description for this activity. Netcdf run file to which the general run information will be exported. This should be either an absolute path or a path relative to the exportDir defined in the general section. Optional. Properties in the form of key-value pairs that can be used to pass information to the pre and post adapter. These properties will be copied to the netcdf run file. These properties can be used as configuration for the pre and post adapter, so it is not needed to have a separate configuration file for the pre and post adapter. This is also a convenient way to pass global properties from FEWS to a pre or post adapter, since an adapter is not allowed to access the FEWS global.properties file directly. Global properties (between '$' signs) in these key-value pairs will be replaced by their literal values before they are copied to the netcdf run file. Optional description for the activity. File to which the data will be exported. This file is always placed in exportDir. When true the events in the PI time series file are written to a binary file instead of the xml file. The written xml file will only contain the time series headers and optionally a time zone. The binary file has the same name as the xml file only the extension is "bin" instead of "xml" During PI time series import the bin file is automatically read when available. The byte order in the bin file is always Intel x86. When true the run period, written in the pi run file, will not be extended. When false the relative view period specified is used to extend the period. For "read complete forecast" the period of actual available data is used. When true any thresholds for a time series will be written in its header When true, the location selection will be applied. Otherwise all available locations will be exported. By default the ensemble member index is written. Since FEWS 2012.01 it is also possible to use non integer ensemble member ids. Configure in the general section piVersion = 1.10 TimeSeriesSet that defines what data is to be exported with the possibility to define constraints. When "read complete forecast" is specified this also affects the run period. The time series is not exported when the time series is empty or when omitMissingValues = true and the time series is empty after removing the missing values. File is not written when file is empty (after omitMissingValues and omitEmptyTimeSeries) use this period to select all approved forecasts with forecast start time lying within this period Option to check the timeseries for missing values. This option works in combination with the Parameter flag 'allowMissing'. When omitted defaults to 'false'. Since 2017.02. Option to skip time series sets if the location set does not exist. Useful when module or workflow is run in loop with tags being translated. When omitted defaults to 'false'. Optional description for the activity. File to which the data will be exported. This file is always placed in exportDir. Fully qualifying name of a Java class that implements a time series serializer interface. Directory with jar files and optionally native dlls. When not specified the bin dir and class loader of FEWS is used. When specified the java class is executed in a private class loader, it will not use any jar in the FEWS bin dir except the Delft_Utils.jar. Only one class loader is created per binDir , serializers should still not use static variables Name of dataset file containing the binaries located in the 'binDir'. Use this to update 'binDir' through configuration changes. This will delete the 'binDir' for an update, therefore this will be limited to a 'binDir' that is a sub directory of region home. When true the run period, written in the pi run file, will not be extended. When false the relative view period specified is used to extend the period. For "read complete forecast" the period of actual available data is used. When true, the location selection will be applied. Otherwise all available locations will be exported. TimeSeriesSet that defines what data is to be exported with the possibility to define constraints. When "read complete forecast" is specified this also affects the run period. The time series is not exported when the time series is empty or when omitMissingValues = true and the time series is empty after removing the missing values. File is not written when file is empty (after omitMissingValues and omitEmptyTimeSeries) use this period to select all approved forecasts with forecast start time lying within this period Option to check the time series for missing values. This option works in combination with the Parameter flag 'allowMissing'. When omitted defaults to 'false'. Optional description for the activity. ID of the module instance for which the state will be exported. Export state exported by this ensemble Use a sub string of the active ensemble member id as member id when resolving the state. Fore example use (...) to use the first three characters of the active ensemble member id Use ensemble member id when resolving the state. Directory to which the module instance state is to be exported. This should be the path where the model expects to find the state file(s). This should be either an absolute path or a path relative to the exportDir defined in the general section. All contents of the stored state are exported to this directory. Only use this option in combination with a PI state description xml file. Fully qualified name of the XML file containing the state export configuration. This should be either an absolute path or a path relative to the exportDir defined in the general section. This option writes the input state file paths to a pi state description xml file. Only use this option in combination with a PI state description xml file. The locations of the state. In case the state consists of a whole directory only one stateLocation is allowed. This option writes the input state file paths to a pi state description xml file. State specific settings. They can be overruled by the TaskProperties. When not specified the state selection in the workflow descriptor is used. Time settings are relative to time0. Adjusts the start time of time series to the exported state time within this general adapter run when start is overrulable or not specified. Default is true. When specified all activities are run in a loop to ensure on every cardinal time a state is produced. This has two advantages. States are equally and frequently distributed over time so it possible to start a update run from every point, also half way a cold update run that spans several days. The other advantage is the restriction on memory consumption, you can can run over months without going out of RAM. States will be produced on every cardinal time between the exported state time and time0. After finishing all activities, all the activities are run again until all states have been produced until time0. Do not specify a relative view period for the time series sets in the export activities when you need time series from input to output state time. Write an extra state at end of the state search period that can be used in the next state run. Some (HBV) models need a minimum run length to perform corrections at the end of the run. Optional description for the activity. ID of the module instance for which the state will be exported. Since 2021.01. Name of the module data set file that will be exported Since 2014.02. FEWS-11097. Map a time series vale at time0 to a module data set name Since 2015.02 FEWS-13044 Overruling dataset name when cold state was exported Optional description for the activity. File to which the rating curve will be exported. This file is always placed in exportDir SINCE 2019.02 If configured, then only the latest available rating curve in the run period will be exported Stage resolution. Use unit configured with 'displayUnit' in stage parameter group. If there is no 'displayUnit' , m are used. Every resolution 'step' (e.g. 0.5 ft) stage/flow pair are exported. The exporting stage/value pairs starts at rating curve minStage and goes up to the ratingCurve maxStage, if any available, otherwise up to the last rating curve stage value. Background info: the logarithmic interpolation in a rating curve needs a complex algorithm. For this reason it's it is convenient when we can convert to a more detailed table where we can use linear interpolation ID of the location(s) for which the rating curve will be exported. Optional description for the activity File to which the 1D spectra time series will be exported. This file is always placed in exportDir TimeSeriesSet that defines what 1D spectra time series should be exported to pi_tables.xml Since 2015.01. FEWS-11031 Restriction for the locations in the specified time series sets. this tag can used to generate a group for each location in the locationSet for the defined model this tag can used to used to generate table from a template defined for a certain parameter Optional description for the activity. Module name for parameter file being exported (Do not add file extension). This tag can be used to generate a parameter-xml based on a template-xml. For each location in the locationset a group will be added to the parameter xml ID of the module instance for which the state will be exported. Optional description for the activity. File to which the data will be exported. This file is always placed in exportDir. When true an empty or non existing location set results in an empty header file, when false nothing will be exported. Default is false Id of the location set for which the attributes will be exported Id of the location for which the attributes will be exported First column which specifies the id of the location, can be overruled with an attribute Column for exported location attribute values Format of the exported grids Optional description for the activity. File to which the map stack will be exported. This file is always placed in exportDir. Name of exported grids. The number of names must coincide with the number of locations being exported. Fews Location id to which the gridName is linked. For USGS BIL files this represents the file name. For ASCII/PCRASTER files this represents a file prefix used to store the separate time steps. Format of the exported grids When true the run period, written in the pi run file, will not be extended. Time series set information. ValueType must be equal to 'grid'. Optional list of properties that can be used for configuring the export grids. USGS-properties: - nrBits (int) - nrDecimals (int) Optional description for the activity. File to which the area selection will be exported. This file is always placed in exportDir. The specified file can have the extension shp for shape file or xml for a map stack in the case the grid location and gridFormat should also be specified By default the shape file is exported with WGS 1984 coordinates Fews Location id to which the gridName is linked. When not specified a shape file is exported. Format of the exported grids. When not specified a shape file is exported. Optional description for the activity. File to which the area selection will be exported. This file is always placed in exportDir. Fews Location id to which the gridName is linked. Identifier for locationset for which to generate grid files for each. The locations should have polygons associated with them. Format of the exported grids Optional description for the activity. File to which the data will be exported. This file is always placed in exportDir. Default value is netcdf3. Configure a GeoDatum conversion during export - applicable only to scalar data Since 2017.02 Applicable only to scalar time series. When true then the scalar time series at the same geo point X,Y but different Z are considered to be Z-layers. Z values are used to create a z-dimension in the NetCdf file, and the time series values are written to the associated z element. Per parameter only one z-dimension is allowed. Different parameters may have different z-dimensions Since 2021.02 Applicable only to scalar and gridded time series with exactly one ensemble member. When false then this ensemble member is not written to the file and parameter in the file does not have realization dimension. A config error will be given when set to false and more ensemble members are found in the timeseries When true the run period, written in the pi run file, will not be extended. TimeSeriesSet that defines what data is to be exported with the possibility to define constraints. Are missing values to be written to the export file or should they be left out. The time series is not exported when the time series is empty or when omitMissingValues = true and the time series is empty after removing the missing values. File is not written when file is empty (after omitMissingValues and omitEmptyTimeSeries) When true, the location selection will be applied. Otherwise all available locations will be exported. Since 2017.02. Option to skip time series sets if the location set does not exist. Useful when module or workflow is run in loop with tags being translated. When omitted defaults to 'false'. Option to check the time series for missing values. This option works in combination with the Parameter flag 'allowMissing'. When omitted defaults to 'false'. Optional description for the activity. File to which the table will be exported. This file is always placed in exportDir. Type of table to be exported. ID of the table to be exported. Parameters for the convertEquation operation. location id to select the rating curve Location set id of time series. Optional description for the parameters. In case the state consists of a list of files the location can only be a file name without a path. Type of location: this is either file or directory This should be either an absolute path or a path relative to the stateExportDir defined in this activity. This should be an absolute path. Optional description for the activity. Deprecated, do not use this if a pi state description xml file is not needed. Fully qualified name of the XML file containing the state import configuration. This should be either an absolute path or a path relative to the importDir defined in the general section. This option reads the output state file paths from a pi state description xml file. By default the warm state is zipped and stored as a blob in the database. For large states (>50MB) it is recommended to store the data outside the database in a directory. This directory is configured in the clientConfig.xml (optional element warmStatesDirectory). When using a stand alone system or using oracle and a single MC system it is possible to store larger grids inside the database. Expired states are removed automatically from this directory by the CompactCacheFiles workflow. The state description is still written to the database, the blob field will be empty By default the expiry time is the same as the original expiry tme of the forecast. Optional Synch level for state. Defaults to 0 if not specified. Configure synch level 20 when this state should be downloaded to the OC for use in IFD Optional description for the activity. if TRUE, at GA export the importFile will be exported with headers only, without any data. Usage : lets models know which data are expected at GA import. Note: this option is not supported for spectra data. File the data will be imported from. This file is always placed in the importDir. FEWS-11360. Folder in which import files are located, only available for Netcdf Import Activities FEWS-11360. e.g *.xml to skip non xml files. Only the * and ? wild cards are recognized. Only available for Netcdf Import Activities Since 2023.02. Regular Expression. When a match of the pattern in the filename is found, this will overrule the exernal grid location Id for the time series being imported. A simple pattern is (without quotations) '(.*)' which matches the whole filename. (.*)\.nc extracts the fle name without the .nc extension An other simple pattern is .{2}(.*).{4} that removes the first 2 and last 4 character of the filename to get the id More complicated expressions can be found at http://en.wikipedia.org/wiki/Regular_expression TimeSeriesSet that defines what data is to be exported with the possibility to define constraints. Since 2019.01. Option to skip import when location set does not exist. Since 2014.02. FEWS-11446 .TimeSeriesSet to take over property from. Since 2015.01. Import csv files that can be viewed by the ModuleDataViewer. Since 2015.01. Character set of the text in the csv file. Specify only when the csv file contains non western characters. Since 2015.01. Optional description for the import. Since 2015.01. File the data will be imported from. Since 2015.01. Display name of the csv file that is imported. Since 2015.01. Configure a mapping of the CSV columns to different database types. If no mapping is specified for a column, the column will be mapped to a string. Since 2019.02. By design the activity will fail if the configured importFile is not found. To overrule this behaviour a warning will be logged but the activity won't fail. Since 2020.02. Export csv files for ModuleRunTables. ID of the module instance for which the current ModuleRunTable will be exported. Since 2020.02. Character set of the text in the csv file. Specify only when the data contains non western characters. Since 2015.01. Optional description for the export activity. Since 2020.02. File the data will be exported to. Since 2020.02. Display name of the Module Run Table file that is to be exported. Since 2020.02. By design the activity will fail if a moduleRunTable with the requested ModuleInstanceId and display name is not found. To overrule this behaviour a warning will be logged but the activity won't fail. Optional description for the activity. File to which the coefficient set will be exported. This file is always placed in exportDir. Identifier of a coefficientSet to export. Name of the file that contains the coefficientSet to use. This name should not include the file extension. ID of the location(s) for which the coefficient set will be exported. Since 2015.01. CSV columns will be mapped to database types so they can be viewed with the Module Data Viewer. Since 2015.01. Column that contains string values Since 2015.01. Column that contains integer values Since 2015.01. Column that contains double values Since 2015.01. Column that contains boolean values. Should be set to either true or false. Since 2015.01. Column that contains the date and time values Since 2015.01. Only required when the type of the column is text instead of timestamp Since 2015.01. Name of the column in the CSV file. Since 2015.01. Name of the column to be stored in FEWS. If not specified the name of the imported csv will be used. Optional description for the activity. File the data will be imported from. This file is always placed in the importDir. Fully qualifying name of a Java class that implements a time series parser interface. Directory with jar files and optionally native dlls. When not specified the bin dir and class loader of FEWS is used. When specified the java class is executed in a private class loader, it will not use any jar in the FEWS bin dir except the Delft_Utils.jar. Only one class loader is created per binDir , parsers should still not use static variables Name of dataset file containing the binaries located in the 'binDir'. Use this to update 'binDir' through configuration changes. TimeSeriesSet that defines what data is to be exported with the possibility to define constraints. Since 2019.01. Option to skip import when location set does not exist. Since 2014.01. FEWS-10771. Optional maximum horizontal snap distance in meters. When the parser provides horizontal location coordinates (x,y) and no locationIds, then the location mapping will be done by matching the horizontal coordinates. The horizontal snap distance is the tolerance used to detect which internal and external horizontal coordinates are the same. This only works when the input format provides the coordinate system for the coordinates of the locations. When the parser does not provide the coordinates for a time series an error is logged. Note: this option has no effect for grid data. Note 2: it is not possible to import data using horizontal coordinates and using locationIds in the same importNetcdfActivity, need to define separate import activities for that (one with maximumSnapDistance and one without maximumSnapDistance). Since 2014.02. Optional maximum vertical snap distance in meters. When the parser provides vertical location coordinates (z) and no locationIds, then the location mapping will be done by matching the vertical coordinates. The vertical snap distance is the tolerance used to detect which internal and external vertical coordinates are the same. This only works when the input format provides the coordinates of the locations. When the parser does not provide the vertical coordinates for a time series an error is logged. Note: this option currently only works for importing horizontal layers from netcdf 3D grid data. Note 2: it is not possible to import data with z-coordinates (layers from 3D grids) and data without z-coordinates (2D grids) in the same importNetcdfActivity, need to define separate import activities for that (one with maximumVerticalSnapDistance and one without maximumVerticalSnapDistance). Since 2017.02. When true the location is resolved by the layer sigma coordinate Default is false. If this is true, then this importActivity will run continuously during the configured execute activities. Additionally this importActivity will also run as part of the configured import activities as normal. This way it is possible to import data that is produced by an execute activity, while it is being produced. For instance if a model run writes new output data to an existing file after each timeStep, then the continuously running importActivity will immediately import the file, including the new data. This way the new data can be viewed in FEWS as soon as it becomes available, i.e. already during the model run. Currently the data that is imported during the execute activities can only be viewed after selecting "open most recent running forecast and adjust system time" from the debug menu in the FEWS Explorer window. If the running forecast is opened and selected in the data viewer, then the displays are updated each time when new data becomes available during the run. This feature only has effect for stand alone FEWS systems and for FEWS systems that use direct database access. Burn-in profile for cold state starts. Used to replace first part of a time series. For time series with matching parameter-location ids, the first value is replaced by the initialValue. Element length defines the length of time series beginning that is to be replaced using linear interpolation. Length of time series beginning that is to be replaced. Since 2019.01. Option to skip export when location set does not exist. Parameter id of time series. List of location ids of time series. Location set id of time series. New start value for the time series. Since 2017.02. Start value for the time series using location attributes Since 2017.02. Id of the location attribute that contains the new start value for the time series. Since 2019.01. Required when the attribute referenced by the initialValueAttributeId contains multiple values for a single location. When the look-up value is the nth value in the lookup attribute the nth initial value will be used. Since 2019.01. Required when the attribute referenced by the initialValueAttributeId contains multiple values for a single location. When the lookup text is the nth value in the lookup attribute the nth initial value will be used. Optional description for the activity. The pathname of the template file relative to the rootDir (or absolute path). This file can contain location attribute tags between '@' signs, general adapter tags between '%' signs and global properties between '$' signs. The pathname of the export file relative to the exportDir (or absolute path). This file is created during the workflow run and will be a copy of the template file in which the tags are replaced with actual (modified) values. If this file already exists, then it will be overwritten. Optional. Location attribute tags in the template file will be replaced with the corresponding (modified) attribute values of the location with this locationId. If this is not specified, then location attribute tags will not be replaced. Since 2017.02, optional. All tags will be replaced with a fixed number of characters, spaces are inserted in front of the value where necessary. Note that when tags are replaced with text, the replacement text must be small enough to fit in the fixed width, otherwise the replacement text is used as is and the outputted value will therefore not conform to the fixed width. A warning is logged in this case. Since 2017.02, optional. When replacing a tag with a number value, the specified number of decimals is used. Note that if configured, the fixedWidth must be large enough to fit all number values with the given number of decimals. Since 2023.02, optional. When replacing a tag with a number value, the specified minimum number of decimals is used. Note that if configured, the fixedWidth must be large enough to fit all number values with the given number of decimals. Since 2023.02, optional. When replacing a tag with a number value, the specified maximum number of decimals is used. Note that if configured, the fixedWidth must be large enough to fit all number values with the given number of decimals. Since 2014.01. Optional state import directory. This should be either an absolute path or a path relative to the importDir defined in the general section. If this stateImportDir is specified, then the importFile paths in this activity can be paths relative to this stateImportDir instead of absolute paths. This stateImportDir is only needed when you want to use relative importFile paths. If all importFile paths in this activity are absolute, then this stateImportDir is not needed and will not be used. This option does not use a pi state description xml file. Since 2014.01. One or more output state files from the model. The specified files will be imported. This option does not use a pi state description xml file. Since 2017.02. eg. 'State_'yyyyMMdd_HHmmss'.bin' Imports all files from the state import dir that matches this pattern. To get the state time the pattern is used. The work dir is used when the state import dir is not specified. This option does not use a pi state description xml file. Since 2017.02. This relative path and name are used to store the imported file in FEWS. This path should be relative to the stateExportDir in the exportStateActivity that will be used to export this state file again for a future model run. If the imported output state file needs to be renamed before it can be used as input state file for a future model run, then the name of the relativeExportFile can be different from the name of the importFile. Since the 2023.02 is it possible to use question marks. The ? chars are copied from the input file name Path and name of an output state file from the model. This file will be imported. This should be either an absolute path or a path relative to the stateImportDir defined in this activity. The %END_DATE_TIME% tag can be used here (since 2014.02), in case the state file name contains a timestamp of the end time of the run. This relative path and name are used to store the imported file in FEWS. This path should be relative to the stateExportDir in the exportStateActivity that will be used to export this state file again for a future model run. If the imported output state file needs to be renamed before it can be used as input state file for a future model run, then the name of the relativeExportFile can be different from the name of the importFile. The %END_DATE_TIME% tag can be used here (since 2014.02), in case the state file name contains a timestamp of the end time of the run. Since 2014.02. FEWS-11097. Time series set that determines the time serie for the value at T0 to pick the correct entry from the module data set map Since 2014.02. FEWS-11097. Map with different value-moduleDataSetName pairs, the value at T0 at the time serie from configured time series set will be used to pick the correct entry from the map Pattern for this date time format. This can be e.g. "yyyy-MM-dd HH:mm:ss". yyyy = Year, MM = Month in year, dd = Day in month, HH = Hour in day (0-23), mm = Minute in hour, ss = Second in minute. Identifier for this date time format. Use this identifier to refer to this date time format in the argument of a variable. Since 2020.01. Z layer parameter Since 2015.01. FEWS-11031 Restriction for the locations in the specified time series sets. Since 2020.01. Z layer parameter Since 2015.01. FEWS-11031 Restriction for the locations in the specified time series sets. Indication of the coordinate system used - defaults to WGS-1984 Since 2023.01. Character set of the dbf file. File to import. The file will be imported at time 0 Directory (relative to work dir or absolute) to import the files from eg. 'Shape_'yyyyMMdd_HHmmss'.shp' or 'provincies_'ddMMMyyyyHHmmss'.geojson'. Imports all files from the import dir that matches this pattern. To get the time the pattern is used. The work dir is used when the import dir is not specified. When not specified time0 is used. In this case a single file is expected in the import dir Attribute to import from the file Id of the dbf file column. The values from this column are use to fill the polygons Attribute Id to import. This Id is associatedwith dbf column. Note: geojson file is first converted to the shp file Time series property key used to store the property value. By default, the key equals the attribute id Name / header of the column used for the location id Name / header of the column used for the values of this attibute Attribute that should be used to overrule the id of the location, useful if a different external id is desired for the location Optional description (this is never used in the code). Optional. Since 2021.02, it is possible to include location attributes as properties.