...
In addition a workflow needs to scheduled to insert the data edits into the archive. More details can be found here 22-4 Merging edited data - DELFT-FEWS Documentation - Deltares Public Wiki
Custom export folders
Data is exported to the open archive according to fixed folder structure. In some cases this folder structure is customizable by using configuration options. From FEWS Release 202302 and higher it is possible to configure a custom export folder for each data type in the archive.
A configuration example is given below:
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<archives xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews https://fewsdocs.deltares.nl/schemas/version1.0/archives.xsd">
<catalogueUrl>https://fews-ut-ar-202301.avi.deltares.nl/deltares-archive-server/catalogue</catalogueUrl>
<elasticSearchUrl>https://fews-ut-ar-202301.avi.deltares.nl/deltares-archive-server/elastic</elasticSearchUrl>
<dataFolder>C:\fews\archive\data\</dataFolder>
<customExportFolders>
<products>yyyy/MM'/%areaId%/%sourceId%/'dd'/products/%productId%_%currentTime%'</products>
<config>yyyy/MM'/%areaId%/%revisionId%'</config>
<forecasterNotes>yyyy/MM'/%areaId%/test/'dd'/forecasterNotes'</forecasterNotes>
<logMessages>yyyy/MM/dd'%areaId%/logmessages'</logMessages>
<ratingCurves>yyyy/MM/dd'%areaId%/ratingcurves'</ratingCurves>
<snapShot>yyyy/MM/dd'%areaId%/snapshot'</snapShot>
<externalHistorical>yyyy/MM'/%areaId%/%sourceId%/'dd'/observed_%valueType%'</externalHistorical>
<externalForecast>yyyy/MM'/%areaId%/%sourceId%/'dd'/externalForecast/%sourceId%_'HHmmss</externalForecast>
<simulatedForecast>yyyy'/%taskRunId%/%areaId%/%sourceId%/%whatIfId%/%workflowId%_%forecastTime%_%currentTime%'</simulatedForecast>
<simulatedHistorical>yyyy/MM'/%areaId%/%sourceId%/'dd'/simulatedHistorical_%valueType%'</simulatedHistorical>
</customExportFolders>
</archives> |
It is possible to a use date/time pattern in the folders structure. The pattern will be parsed during export by using the time relevant for the export. The time which is used to parse the date/time pattern is depended of the type of export. Below an overview of the time used for each export type. Below an overview:
| Time used | |
| External historical | start time exported data |
| External forecast | external forecast time |
| Simulated forecast | time zero |
| Simulated historical | start time exported data |
| Snapshot | current time |
| Config | creation time latest revision |
| Products | time zero |
| Rating curves | current time |
| Log messages | start time exported data |
| Forecaster notes | start time exported data |
In addition it is possible to use plain text in the folder structure.
A set of tags like %areaId% are supported and will be parsed during the export. Note however that not all tags are supported for each type of export.
Below an overview of which tags are supported for which export type.
| areaId | sourceId | currentTime | valueType | taskRunId | whatIfId | workflowId | supplied attributes | revisionId | |
| External historical | x | x | x | ||||||
| External forecast | x | x | x | ||||||
| Simulated forecast | x | x | x | x | x | x | |||
| Simulated historical | x | ||||||||
| Snapshot | x | ||||||||
| Config | x | x | |||||||
| Products | x | x | x | x | |||||
| Rating curves | x | ||||||||
| Log messages | x | ||||||||
| Forecaster notes | x |