Since 2023.01. If this option is set to true then the harvester will run directly after the export to the archive to update the open archive catalogue. Since 2023.01. If this option is set to true then the harvester will run directly after the export to the archive to update the netcdf storage catalogue. data folder of the archive (the folder which contains the catalogue folder) By default this is the %REGION_HOME%/temp dir. When the available disk space in this dir is too small you can configure directory with more disk space. This temp dir is used by the snapshot export. The temp dir should be a local disk when using windows. For linux this is not required although the export will be slower. The temp file is moved to the archive folder when the snapshot is completely finished. This this is much faster when the archiveFolder and tempFolder are on the same volume. Properties can be used to add custom keywords to the catalogue (Geonetwork only) With this option it is possible to define the name of the dataset (Geonetwork only) Since 2023.02. Optional choice for storing export status in the database (table ExportStatus). If this choice is omitted, export status will be stored in database using the export folder name as dataFeedId. Id for data feed. Export status will be stored in database using this id Option disableDataFeedInfo indicates that no export status should be stored in database Since 2022.01. By default it is not allowed to export products to the archive in IFD mode. With this option the exporting of the products also in IFD mode can be enabled Since 2024.01. If it's configured, te export will loop through the location ids, replacing all %LOCATIONID% and %LOCATIONNAME% tags in the source file name and attributes with the respective ids/names. Since 2024.01. If it's configured, there will be no warning / error logged is the source file that is to be exported does not exist. Each product can be labelled with an area id, this is used to easily search for data in the catalogue Each product can be labelled with an source id, this is used to faciliate the searching for products in the catalogue Since 2022.02. An attribute which can be used to identify the product in the archive. Since 2022.02. Adds an extra subfolder to the archive structure if configured. Example: year/month/areaid/day/productid/subFolderName/metaData.xml Since 2022.02. Adds an extra subfolder with the date and time of the workflow's Time0. to the archive structure if configured. Example: year/month/areaid/day/productid/2022_01_19_T_ 20_00/metaData.xml Indicate if the set of files (products) should be zipped after archiving Location of the files which should be send to the archive. This element allows the use of wildcards in the file and the filepath This element can used to define a subfolder in the main folder in which the product in stored. All the files defined in this section will be stored in this subfolder Name of the zipfile To archive products by using wildcards this section can be used. It also allows to zip the content after archiving Location of the file which should be send to the archive Since 2019.02 Move the files to the archive instead of copying them The import folder from which the products should archived The pattern which will be used to determine the creation time of the file. Only files which comply to the configured date time pattern will be archived. The file name (without extension will have postfix from which the creation time of the file will be derived. option to label the snapshot with an area Since 2017.02. Option to filter the data in the snapshots Label the config export with an area id zip the snapshot of the database. By default the snapshot is zipped Since 2024.01. Use the last exported snapshot as a base to speed up the export and reduce the load on the central database. A copy of the last exported snapshot is made, the rows that no longer exist in the central database are deleted from the copy, the new rows are added and the modified ones are updated. Default is true One daily export by default Since 2022.01. By default it is not allowed to export snapshot to the archive in IFD mode. With this option the exporting of the snapshot also in IFD mode can be enabled Since 2018.01. If this option is "false" then only 1 daily export is allowed. If there are multiple exports during the day, the previous export will be overwritten. If this option is "true" the snapshort will stored in a directory which has the pattern hhmmss otherwise the folder will have the pattern dd (which will cause that only one export is allowed during the day) Since 2018.01 If this option is available , the previously exported snapshot will be always overwritten with the new one. The snapshot will be exported directly to the configured archiveFolder (no subfolders are created) Since 2022.01. By default it is not allowed to export config to the archive in IFD mode. With this option the exporting of the config also in IFD mode can be enabled data folder of the archive The name of the nc file is by default composed as follows: timeSeriesType_valueType_timeStep.nc, for example observed_scalar_15_minutes.nc. Optional fileNamePrefix replaces the timeSeriesType, for example reservoirs_scalar_15_minutes.nc Properties can be used to add custom keywords to the catalogue (Geonetwork only) Exported data sets are labeld with areaId Forecasts can be labelled with a source id, to facilitate searching in the archive Id of a file that contains mapping from internal to external location and parameter ID's dataSetPeriod specifies if the observed time series should be archived in daily netcdf files or in monthly netcdf files. Daily is default The relative period for which the observed time series and external forecasts should be archived. This element is required if the observed time series are archived. If this element is omitted, external forecast are completely archived Defines additional metadat to the netcdf file The comments added to the time series are by default also stored in the netcdf-file. With the option this can be disabled The flags of the values of the time series are by default also stored in the netcdf-file, with the option this can be disabled The properties added to the time series are by default also stored in the netcdf-file, with the option this can be disabled If this option is set to true, the data export will verify after the export that the exported time series in the netcdf files are the same as the time series in FEWS. Id of the workflow the time series should be archived Filter defines the time series to be archived. If no filter is configured, then all time series created and/or modified by this workflow will be archived this option should not be used in production! Only when migrating from an old archive to the fews archive this option is useful. It allows that you export to monthly sets to a certain date from an sa and start exporting to daily files from fews at the same date. When the month is finished these files can be merged into a single montly data set Since 2022.01. By default it is not allowed to run amalgamateObserved in IFD mode. With this option the running amalgamate also in IFD mode can be enabled Since 2022.01. By default it is not allowed to export external historical series to the archive in IFD mode. With this option the exporting of the external historical series also in IFD mode can be enabled Period of data which will be exported to the open database Since 2022.01. By default it is not allowed to simulated time series to the archive in IFD mode. With this option the exporting of the simulated series also in IFD mode can be enabled if this option is set to true previous archived forecast for the same workflow time zero combination will be overwritten The relative period for which external forecasts should be archived. Since 2022.01. By default it is not allowed to export time series to the archive in IFD mode. With this option the exporting of the time series also in IFD mode can be enabled URL of the archive database total amount of threads to insert data into the database total amount of threads to read data from the netcdf files Id of UnitConversions to be used for export unit mapping It is possible to provide the export plugin a time zone to convert the provided times to a local time. the options group can be used to pass configuration options to the plugin class FEWS can export observed data in daily netcdf files or in monthly netcdf files. Period of data which will be archived Id of a file that contains mapping from internal to external location and parameter ID's. If this option is set to true FEWS will not log an error when an location set is not configured Since 2022.01. By default it is not allowed to export observed time series to the archive in IFD mode. With this option the exporting of the observed series also in IFD mode can be enabled Id of UnitConversions to be used for unit mapping. Available since 2022.02 Available since 2022.02 Deprecated since 2024.01. Period of data which will be archived Id of a file that contains mapping from internal to external location and parameter ID's. If this option is set to true FEWS will not log an error when an location set is not configured Since 2017.02. By default it is not allowed to export to the archive in IFD mode. With this option the exporting of the forecasts also in IFD mode can be enabled Forecasts can be labelled with an area id a simulated dataset can be labelled with an source id , to facilitate searching in the archive By default the workflow id is used as an prefix for the folder in which the forecast is stored, this can be overruled by using this setting Id of a file that contains mapping from internal to external location and parameter ID's. If this option is set to true FEWS will not log an error when an location set is not configured The modifiers, states of related workflows will also be archived if this option is set to true previous archived forecast for the same workflow time zero combination will be overwritten By default the task dispatch time is used to create output folder path. With this option the dispatch time can be replaced by the taskRunId. This option only has effect when overwritePreviousForecast is set to false Since 2021.01. The output directory to which the forecast will be exported will be according to the following path:whatIfTemplateId/whatIfId/timezero-dispatchtime Since 2017.02. By default it is not allowed to export forecasts to the archive in IFD mode. With this option the exporting of the forecasts also in IFD mode can be enabled Available since 2022.02. Id of UnitConversions to be used for unit mapping. Available since 2022.02. If set to true, missing values won't be written to the export file. Available since 2022.02. Optional. If this is specified, then the period for which data is exported will be truncated for simulated data that was created in a run that started with a cold state. In other words for this type of data, any data before the specified start time will not be exported. This start time is relative to the time zero of the run in which the data was created. This can be used to avoid exporting data that was created during the warm-up period of a model run after a cold start. Note: this option only works when the default state selection was configured to be cold state for the run in which the data was created. Deprecated since 2024.01. If this option is set to true, only the export metadata will be verified, not the timeseries. Since 2022.01. The netcdf files will not be exported to the open archive but to an external data storage Since 2022.02. This attribute will be used to identify the file in the netcdf storage in addition to the taskrun id and the file name Since 2017.02 If this period is configured all forecasts in this period will be exported Since 2017.02 the workflow id of the forecast which should be exported The relative period for which external forecasts should be archived. Id of a file that contains mapping from internal to external location and parameter ID's. If this option is set to true FEWS will not log an error when an location set is not configured Since 2022.01. By default it is not allowed to export external forecast to the archive in IFD mode. With this option the exporting of the external forecast also in IFD mode can be enabled Deprecated since 2024.01. Available since 2022.02. Id of UnitConversions to be used for unit mapping. Available since 2022.02. If set to true, missing values won't be written to the export file. The period for which log messages will be archived. The period for which messages (forecaster notes) will be archived. The creation time of the messages should be in this period Since 2022.01. By default it is not allowed to export messages to the archive in IFD mode. With this option the exporting of the messages also in IFD mode can be enabled Optional relative view period exporting rating curves. When used all rating curves that where added or updated within this period will be exported. If omitted all rating curves will be exported to file. Optional prefix to be used in combination with the 'relativePeriod' element. When using the relativePeriod it is advised to include the T0 timestamp in the export file name. 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 Option to export ratingcurves with modifiers applied. If omitted then un-modified rating curves will be exported Since 2022.01. By default it is not allowed to export ratings to the archive in IFD mode. With this option the exporting of the ratings also in IFD mode can be enabled a dataset containing observed data can be labelled with an areaid, to facilitate searching in the archive an observed dataset can be labelled with an source id , to facilitate searching in the archive Define the time series which should be exported to the archive Since 2021.01 A selection of time series from a workflow. If the workflow is not configured the time series filter will be applied on the time series from the curent workflow. a dataset containing observed data can be labelled with an areaid, to facilitate searching in the archive an observed dataset can be labelled with an source id , to facilitate searching in the archive Define the time series which should be exported to the archive Since 2021.01 A selection of time series from a workflow. If the workflow is not configured the time series filter will be applied on the time series from the curent workflow. a dataset can be labelled with an areaid, to facilitate searching in the archive an dataset can be labelled with an source id , to facilitate searching in the archive a dataset containing observed data can be labelled with an areaid, to facilitate searching in the archive an observed dataset can be labelled with an source id , to facilitate searching in the archive Define the time series which should be exported to the archive Since 2021.01 A selection of time series from a workflow. If the workflow is not configured the time series filter will be applied on the time series from the curent workflow. name of the netcdf file in which the external forecast should be archived prefix for the generated file (only used when exporting with a workflow selection) a dataset containing observed data can be labelled with an areaid, to facilitate searching in the archive an observed dataset can be labelled with an source id , to facilitate searching in the archive use this section to enhance the meta data which is going to be stored in the netcdf file the comments added to the time series are by default also stored in the netcdf-file, with the option this can be disabled the flags of the values of the time series are by default also stored in the netcdf-file, with the option this can be disabled the flags added to the time series are by default also stored in the netcdf-file, with the option this can be disabled use the module instance id (if unique in a file) as the source store in the metadata file at which times these thresholds are passed Since 2021.01. Adds a new variable to the NetCdf export for locations. The value of the attributes is a location attribute. Define the time series which should be exported to the archive Since 2021.01 A selection of time series from a workflow. If the workflow is not configured the time series filter will be applied on the time series from the curent workflow. Since 2024.01. The time series filter which will be used to determine which time series should be archived. Since 2024.01. If this workflow id is defined then the time series which are generated in this workflow will be used to determine which time series should be archived. If this option is not used then time series of the current workflow will be used. name of the netcdf file in which the external forecast should be archived prefix for the generated file (only used when exporting with a workflow selection) Forecasts can be labelled with an area id a simulated dataset can be labelled with an source id , to facilitate searching in the archive Define additional metadata to the netcdf file the comments added to the time series are by default also stored in the netcdf-file, with the option this can be disabled If this option is set to true the flags of the time series will also be archived. By default this option is true. If this option is set to true the properties of the time series will also be archived. By default thiss option is true. use the module instance id (if unique in a file) as the source name of the netcdf file in which the forecasts should be archived file name to pattern to define the name of the file. The time zero of the forecast will be used to determine the file name. a forecast can be labelled with a sourceid to facilitate searching Define additional metadata to the netcdf file the comments added to the time series are by default also stored in the netcdf-file, with the option this can be disabled If this option is set to true the flags of the time series will also be archived. By default this option is true. Available since 2022.02. If set to true, missing values won't be written to the export file. Available since 2022.02. Optional. If this is specified, then the period for which data is exported will be truncated for simulated data that was created in a run that started with a cold state. In other words for this type of data, any data before the specified start time will not be exported. This start time is relative to the time zero of the run in which the data was created. This can be used to avoid exporting data that was created during the warm-up period of a model run after a cold start. Note: this option only works when the default state selection was configured to be cold state for the run in which the data was created. If this option is set to true the properties of the time series will also be archived. By default thiss option is true. time ranges added to the time series are by default NOT stored in the netcdf-file, with the option this can be disabled. Not supported for ensembles. value ranges added to the time series are by default stored in the netcdf-file, with the option this can be disabled. Not supported for ensembles. name of the netcdf file in which the external forecast should be archived prefix for the generated file (only used when exporting with a workflow selection) an external forecast can be labelled with a areaid to facilitate searching an external forecast can be labelled with a sourceid to facilitate searching Define additional metadata to the netcdf file the comments added to the time series are by default also stored in the netcdf-file, with the option this can be disabled If this option is set to true the flags of the time series will also be archived. By default this option is true. If this option is set to true the properties of the time series will also be archived. By default thiss option is true. time ranges added to the time series are by default NOT stored in the netcdf-file, with the option this can be disabled. Only supported for scalar non equidistant timeSeries. Not supported for ensembles. value ranges added to the time series are by default stored in the netcdf-file, with the option this can be disabled. Only supported for scalar non equidistant timeSeries. Not supported for ensembles. use the module instance id (if unique in a file) as the source Each forecaster note can be labelled with an area id to faciltate searching in the archive id of the area to which the log messages should be archived The (minimum) loglevel of the exported log messages A filter for the event code define additional metadata which will be added to the netcdf file define a subfolder for the reports which are going to be exported in this section if this element is omitted all reports will be exported which are created in the forecast run. However it can be used to filter by module instance id This section can be used to define an export for the states which are produced in this run. Use ModuleInstanceIdsChoice to filter for module instances. If no ModuleInstanceIdsChoice is configured, all states are exported. If a relative view period is configured, only states within this relative view period are exported. Name of file to which the rating curve will be exported. This file is always placed in exportDir. A rating curve export can be labelled with an area id, to facilitate searching in the archive 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. Use timeZero of the task-run as prefix/suffix. Format it as specified with this element.