scrollbar |
---|
Anchor | ||||
---|---|---|---|---|
|
Within Delft-FEWS, the datasets are exported to the archive in a workflow using the ExportArchiveModule. This workflow needs to be scheduled on a regular interval to archive all relevant data.Simulated data sets are preferably exported to archive from the workflow which created the simulation. This is especially the case when modifiers are used in the simulation. When a simulation is not exported to the archive directly it might be that some modifiers which are used in the simulation are deleted are changed in between. This will cause that it won't be possible to archived all the used modifiers correctly.
...
The schema of the associated configuration file (Figure 4.1) is defined at:
http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd.
Figure 4.1 Top level of Delft-FEWS exportArchiveModule.xsd
Table of Contents | ||||
---|---|---|---|---|
|
Observations archiving by Delft-FEWS
...
With daily exports of observed data per area, the number of small datasets on the file system may increases quickly. This has several disadvantages as the harvesting process will take longer processing many small datasets, while the performance of seamless integration (and webservices) will also drop. Therefore, an amalgamate process is developed which merges the daily observation files into one observation file per month. Currently, this amalgamate process is executed from the Fews-application side by an FSS by using the following configuration.
...
Element
...
Format
...
Description
...
GeneralAmalgamateObservedSection ComplexType
...
...
...
archiveFolder
...
string
...
Export destination folder, assumes that the account running the FEWS (FSS) application has write access
...
relativePeriod
...
...
period experiencing changed data that should be amalgamted
...
AmalgamateActivities ComplexType
...
...
...
amalgamateObservedData
...
AmalgamateActivity
...
indicator that observed data will be amalgamated
...
areaId
...
string
...
area for which amalgamation takes place
In future, the amalgamate process will be executed on the archive serverside via the ArchiveAdminConsole.
...
Element
...
Format
...
Description
...
general ComplexType
...
...
...
archiveFolder
...
string
...
Export destination folder, assumes that the account running the FEWS (FSS) application has write access
...
relativePeriod
...
...
Exports entire dataset by day, for any day where a database change (blob creation time) is detected within the relativePeriod (relative to T0). Existing files are overwritten*
...
MessagesActivities ComplexType
...
...
...
forecasterNotesExportActivity ComplexType*
...
...
...
areaId
...
string
...
area for which messages need to be archived
Specify the relativePeriod in such way that the observed datafiles are stable and are not updated anymore. E.g. use one or two months of delay
Code Block | ||||
---|---|---|---|---|
| ||||
<exportArchiveModule xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd">
<amalgamateObserved>
<general>
<archiveFolder>$ARCHIVE_FOLDER$</archiveFolder>
<relativePeriod unit="day" start="-62" end="-31"></relativePeriod>
</general>
<activities>
<amalgamateObservedData>
<areaId>$BASIN$</areaId>
</amalgamateObservedData>
</activities>
</amalgamateObserved>
</exportArchiveModule>
|
Element | Format | Description |
GeneralAmalgamateObservedSection ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| period experiencing changed data that should be amalgamted |
AmalgamateActivities ComplexType |
|
|
amalgamateObservedData | AmalgamateActivity | indicator that observed data will be amalgamated |
areaId | string | area for which amalgamation takes place |
In future, the amalgamate process will be executed on the archive serverside via the ArchiveAdminConsole.
Anchor | ||||
---|---|---|---|---|
|
*When an existing file is locked while it needs to be overwritten, the export function writes a new temporary file. The FileSweeper, a scheduled process, renames this file when the lock is removed from the original file.
Figure 4.3 Delft-FEWS export configuration for archiving messages
...
archiving by Delft-FEWS
Delft-FEWS can export external forecast time series messages to the archive via the ArchiveExportModule (exportExternalForecast exportMessages activity).
For external forecasts messages a dataset is generated for every area for every source for every forecaston a daily basis. The associated directory structure of the Delft-FEWS export for this type of dataset is as follows:.
<archiveRoot>/<yyyy>/<MM>/<areaId>/<dd>/external_forecasts/<sourceId>_<ExtForecastTime>
The exportArchiveModule.xsd has a dedicated exportExternalForecast section to configure the time series that need to be archived (see Figure 4.4). Table 4.3 documents the associated elements:
messages/
Note: The date associated with a message is the creation time, not the T0 at which the forecaster note was created or the Event Time. This means that the relative period as configured in exportMessages (which is relative to T0), for exporting the forecaster Notes to the Archive should cover the creation time. This is not so mch an issue in a live system, as it is in a Stand Alone, where T0 and System Time might be far apart.
The exportArchiveModule.xsd has a dedicated exportMessages section to configure the messages that need to be archived (see Figure 4.3). Currently only ForecasterNotes can be archived. Table 4.2 documents the associated elements:
Table 4.2 Figure 4.4 Delft-FEWS export configuration for archiving external forecasts
Table 4.3 Delft-FEWS export configuration for archiving external forecastsmessages
Element | Format | Description |
GeneralExportForecastSection general ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| Exports entire external forecast dataset by source and forecast timeday, for any forecast day where a database change (blob creation time) is detected within the relativePeriod (relative to T0). Existing timeseries files are overwritten* |
MessagesActivities ComplexType |
|
|
forecasterNotesExportActivity ComplexType* | ||
idMap | string | idMap applied to translate internal FEWS identifiers to identifiers that meet NetCDF-CF criteria.E.g. netcdf does not allow a full stop ('.') in the variable name |
ExternalForecastActivities ComplexType |
|
|
NetcdfExternalForecast ExportActivities ComplexType |
|
|
NetcdfExternalForecast ExportActivity ComplexType* |
|
|
fileName | string | without nc extension, preferably no spaces |
areaId | string | area to which the dataset belongs |
sourceId |
| identifies underlying source e.g. NWP product |
ncMetaData | string elem. | optional metadata tags within NetCDF file following CF convention. Supported by the internal catalogue of the THREDDS Data Server |
includeFlags | bool | only applied for scalar values. |
includeComments | bool | only applied for scalar values. |
includeTimeSeriesProperties | bool | only applied for scalar values. default=TRUE; if TRUE, a list of properties is stored, with each value pointing to the associated property |
includeTimeRanges | bool | only applied for nonequidistant scalar values. Not valid for ensembles. default = TRUE; if TRUE, time-start and time-end properties will be stored if available. |
includeValueRanges | bool | only applied for nonequidistant scalar values. Not valid for ensembles. default = TRUE; if TRUE, value-start and value-end properties will be stored if available. |
timeSeriesSets |
| FEWS timeseries sets |
*When an existing file is locked while it needs to be overwritten, the export function writes a new temporary file. The FileSweeper, a scheduled process, renames this file when the lock is removed from the original file.
...
Exporting forecasts can be done in three ways:
Exporting forecasts in the workflow which computed the forecast
The preferred way of archiving forecasts is at the end of the workflow which computed the forecast. Especially when you have using modifiers in your workflow. If you export the data in another workflow after the forecast is computed it is not guaranteed that the applied modifiers are still available in FEWS.
Exporting all forecasts in a relative period
It is also possible to archive a simulation from a scheduled workflow. In this case a relative period (relativePeriod in schema) should be configured to indicate which time period should be archived. In addition the workflow id (workflowId in schema) should be configured which should be archived.
Exporting the current forecast in a workflow which didn't computed the forecast
It is also possible to archive the current forecast to the archive from another workflow that computed the forecast.
If the export is done without an relative period but not in the workflow which created the forecast the current forecast will be exported. If you have used modifiers in this workflow you should also configure the relatedWorkflowId to indicate which workflow was run to compute the forecast, this will ensure that the modifiers used in this workflow will also be exported to the archive.
...
Element | Format | Description |
GeneralExportForecastSection ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| Exports entire simulated timeseries by workflow. |
workflowId | string | This option should be in combination with the relativePeriod. Al the forecasts of the workflowId which exists in the relative period will be exported |
idMap | string | idMap applied to translate internal FEWS identifiers to identifiers that meet NetCDF-CF criteria.E.g. netcdf does not allow a full stop ('.') in the variable name |
relatedWorkflowId | String | If the export is done without the relativePeriod and workflowId option but not in the workflow which created the forecasts the workflow id of the forecast you are trying to export should be configured to make sure that the modifiers which are used in this forecast will be exported. |
ForecastActivities ComplexType |
|
|
NetcdfForecastExportActivities ComplexType |
|
|
NetcdfForecastExportActivity ComplexType* |
|
|
fileName | string | without nc extension, preferably no spaces |
areaId | string | area to which the dataset belongs |
ncMetaData | string elem. | optional metadata tags within NetCDF file following CF convention. Supported by the internal catalogue of the THREDDS Data Server |
includeFlags | bool | only applied for scalar values. |
includeComments | bool | only applied for scalar values. |
timeSeriesSets |
| FEWS timeseries sets |
ReportsExportActivity ComplexType* |
|
|
subfolder | string | Subdirectory within the 'reports' directory |
moduleInstanceId | string | moduleInstanceId which created the report |
ModuleStatesExportActivity ComplexType* |
|
|
moduleInstanceId | string | moduleInstanceId which created the state |
*When an existing file is locked while it needs to be overwritten, the export function writes a new temporary file. The FileSweeper, a scheduled process, renames this file when the lock is removed from the original file.
Figure 4.5 Delft-FEWS export configuration for archiving simulations
...
Element | Format | Description |
GeneralExportConfig ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod (TO DO) |
| Exports entire configuration when database change (config revision) has been detected within the relativePeriod (relative to T0). Existing files are overwritten* |
ExportConfigActivities ComplexType |
|
|
ExportConfigActivity ComplexType* |
|
|
areaId | string | area to which the dataset belongs |
...
|
| |
areaId | string | area for which messages need to be archived |
*When an existing file is locked while it needs to be overwritten, the export function writes a new temporary file. The FileSweeper, a scheduled process, renames this file when the lock is removed from the original file.
Figure 4.3 Delft-FEWS export configuration for archiving messages
Anchor | ||||
---|---|---|---|---|
|
Delft-FEWS can export external forecast time series to the archive via the ArchiveExportModule (exportExternalForecast activity).
For external forecasts a dataset is generated for every area for every source for every forecast. The associated directory structure of the Delft-FEWS export for this type of dataset is as follows:
<archiveRoot>/<yyyy>/<MM>/<areaId>/<dd> /external_forecasts/<sourceId>_<ExtForecastTime>
The exportArchiveModule.xsd has a dedicated exportExternalForecast section to configure the time series that need to be archived (see Figure 4.4). Table 4.3 documents the associated elements:
Figure 4.4 Delft-FEWS export configuration for archiving external forecasts
Table 4.3 Delft-FEWS export configuration for archiving external forecasts
Element | Format | Description |
GeneralExportForecastSection ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| Exports entire external forecast dataset by source and forecast time, for any forecast where a database change (blob creation time) is detected within the relativePeriod (relative to T0). Existing timeseries files are overwritten* |
idMap | string | idMap applied to translate internal FEWS identifiers to identifiers that meet NetCDF-CF criteria.E.g. netcdf does not allow a full stop ('.') in the variable name |
ExternalForecastActivities ComplexType |
|
|
NetcdfExternalForecast ExportActivities ComplexType |
|
|
NetcdfExternalForecast ExportActivity ComplexType* |
|
|
fileName | string | without nc extension, preferably no spaces |
areaId | string | area to which the dataset belongs |
sourceId |
| identifies underlying source e.g. NWP product |
ncMetaData | string elem. | optional metadata tags within NetCDF file following CF convention. Supported by the internal catalogue of the THREDDS Data Server |
includeFlags | bool | only applied for scalar values. |
includeComments | bool | only applied for scalar values. |
includeTimeSeriesProperties | bool | only applied for scalar values. default=TRUE; if TRUE, a list of properties is stored, with each value pointing to the associated property |
includeTimeRanges | bool | only applied for nonequidistant scalar values. Not valid for ensembles. default = TRUE; if TRUE, time-start and time-end properties will be stored if available. |
includeValueRanges | bool | only applied for nonequidistant scalar values. Not valid for ensembles. default = TRUE; if TRUE, value-start and value-end properties will be stored if available. |
timeSeriesSets |
| FEWS timeseries sets |
*When an existing file is locked while it needs to be overwritten, the export function writes a new temporary file. The FileSweeper, a scheduled process, renames this file when the lock is removed from the original file.
Anchor | ||||
---|---|---|---|---|
|
Delft-FEWS can export simulations to the archive via the ArchiveExportModule (exportSimulations activity).
Exporting forecasts can be done in three ways:
Exporting forecasts in the workflow which computed the forecast
The preferred way of archiving forecasts is at the end of the workflow which computed the forecast. Especially when you have using modifiers in your workflow. If you export the data in another workflow after the forecast is computed it is not guaranteed that the applied modifiers are still available in FEWS.
Exporting all forecasts in a relative period
It is also possible to archive a simulation from a scheduled workflow. In this case a relative period (relativePeriod in schema) should be configured to indicate which time period should be archived. In addition the workflow id (workflowId in schema) should be configured which should be archived.
Exporting the current forecast in a workflow which didn't computed the forecast
It is also possible to archive the current forecast to the archive from another workflow that computed the forecast.
If the export is done without an relative period but not in the workflow which created the forecast the current forecast will be exported. If you have used modifiers in this workflow you should also configure the relatedWorkflowId to indicate which workflow was run to compute the forecast, this will ensure that the modifiers used in this workflow will also be exported to the archive.
The associated root directory structure of the Delft-FEWS export for this type of dataset is as follows:
<archiveRoot>/<yyyy>/<MM>/<areaId>/<dd>/simulated/<workflowId><TimeZero><DispatchTime>
Where <dd> refers to the date of the forecast time T0.
This directory holds the metaData.xml as well as runInfo.xml file with the FEWS taskrun properties (see Figure 3.8). Within this directory the following sub-folders may exist:
/timeseries, /reports, /modifiers, /states
The exportArchiveModule.xsd has a dedicated exportSimulated section to configure the messages that need to be archived (see Figure 3.7). The associated specification is given in Table 4.4.
Table 4.4 Delft-FEWS export configuration for archiving simulations
Element | Format | Description |
GeneralExportForecastSection ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| Exports entire simulated timeseries by workflow. |
workflowId | string | This option should be in combination with the relativePeriod. Al the forecasts of the workflowId which exists in the relative period will be exported |
idMap | string | idMap applied to translate internal FEWS identifiers to identifiers that meet NetCDF-CF criteria.E.g. netcdf does not allow a full stop ('.') in the variable name |
relatedWorkflowId | String | If the export is done without the relativePeriod and workflowId option but not in the workflow which created the forecasts the workflow id of the forecast you are trying to export should be configured to make sure that the modifiers which are used in this forecast will be exported. |
ForecastActivities ComplexType |
|
|
NetcdfForecastExportActivities ComplexType |
|
|
NetcdfForecastExportActivity ComplexType* |
|
|
fileName | string | without nc extension, preferably no spaces |
areaId | string | area to which the dataset belongs |
ncMetaData | string elem. | optional metadata tags within NetCDF file following CF convention. Supported by the internal catalogue of the THREDDS Data Server |
includeFlags | bool | only applied for scalar values. |
includeComments | bool | only applied for scalar values. |
timeSeriesSets |
| FEWS timeseries sets |
ReportsExportActivity ComplexType* |
|
|
subfolder | string | Subdirectory within the 'reports' directory |
moduleInstanceId | string | moduleInstanceId which created the report |
ModuleStatesExportActivity ComplexType* |
|
|
moduleInstanceId | string | moduleInstanceId which created the state |
*When an existing file is locked while it needs to be overwritten, the export function writes a new temporary file. The FileSweeper, a scheduled process, renames this file when the lock is removed from the original file.
Figure 4.5 Delft-FEWS export configuration for archiving simulations
Anchor | ||||
---|---|---|---|---|
|
Delft-FEWS can export the current configuration to the archive via the ArchiveExportModule (exportConfig activity). The configuration thus is exported as part of the workflow. The associated root directory structure of the Delft-FEWS export for this type of dataset is as follows:
<archiveRoot>/<config>/<areaId>/<yyyymmdd>/
The date refers to the revision date of the configuration. The file name typically holds the revisionId.
The exportArchiveModule.xsd has a dedicated exportConfig section to setup the export of the Configuration (see Figure 4.6). This is due to be revised as the same relativePeriod based export mechanism should be adopted for checking what to export (see Table 4.5).
Figure 4.6 Delft-FEWS export configuration for archiving configurations
Table 4.5 Delft-FEWS export configuration for archiving a configuration
Element | Format | Description |
GeneralExportConfig ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod (TO DO) |
| Exports entire configuration when database change (config revision) has been detected within the relativePeriod (relative to T0). Existing files are overwritten* |
ExportConfigActivities ComplexType |
|
|
ExportConfigActivity ComplexType* |
|
|
areaId | string | area to which the dataset belongs |
Anchor | ||||
---|---|---|---|---|
|
Delft-FEWS can export rating curves to the archive via the ArchiveExportModule (exportRatingCurves activity). The entire history of the rating curves is exported and the export format is PI-XML (not NetCDF!). The associated root
...
Element | Format | Description |
GeneralExportRatingCurves ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| If defined, only rating curves which have database changes during the relativePeriod (relative to T0) are exported. If no relativePeriod is specified all available rating curves are exported |
Prefix-timeZeroFormattingString | string | Adds T0 stamp as prefix to file name E.g.yyyymmdd_hhmm |
idMap | string | idMap applied to translate internal FEWS identifiers to external identifiers |
unitConversionsId | string | Allows conversion of rating table units |
includeModifiers | bool | Default=FALSE; If TRUE, rating curve modifiers should be included in the export |
...
Table 4.7 Delft-FEWS export configuration for archiving rating curves (activities section)
Element | Format | Description |
RatingCurvesActivities ComplexType |
|
|
RatingCurvesExportActivity ComplexType |
|
|
fileName | string | without nc extension, preferably no spaces |
areaId | string | area to which the dataset belongs |
linearTableStageresolution | string | Stage increment between the rows in a rating table |
locationId/locationSetId | string | Locations for which rating curves should be exported to this file |
...
Snap shots of the Delft-FEWS database can be archived via the archiveExportModule (exportSnapShot activity).
For snapshots a dataset is generated and stored under the configured area at the memoment of workflow execution. The associated directory structure of the Delft-FEWS export for this type of dataset is as follows FEWS-10198: update directory structure to above setup:
<archiveRoot>/<yyyy>/<MM>/<areaId/<snapshot>/
Figure 4.9 and Table 4.8 documents the associated elements in the exportSnapShot activity:
Since 2019.02 the archive snapshot export is incremental. A copy of the last exported snapshot is made to use as base for the new export. The modified and new rows are copied. Rows that are no longer in the specified profile or central database are deleted from the copy. The snapshot is compacted afterwards . Whether or not a previous snapshot is used as base, the created snapshot contains the same rows and has the same size.
Table 4.8 Delft-FEWS export configuration for archiving database snap shots
...
Element
...
Format
...
Description
...
general ComplexType
...
...
...
archiveFolder
...
string
...
Export destination folder, assumes that the account running the FEWS (FSS) application has write access
...
ExportSnapShotActivity ComplexType
...
...
...
areaId
...
string
...
area (folder) where snapshot is archived
ratingcurves/<areaId>
The configurator can choose between exporting the full set or just the rating curves that have changed, with or without modifier changes.
The exportArchiveModule.xsd has a dedicated exportRatingCurve section to setup the export of the Configuration. Table 4.6 and Figure 4.7 discuss the general section.
Table 4.6 Delft-FEWS export configuration for archiving rating curves (general section)
Element | Format | Description |
GeneralExportRatingCurves ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
relativePeriod |
| If defined, only rating curves which have database changes during the relativePeriod (relative to T0) are exported. If no relativePeriod is specified all available rating curves are exported |
Prefix-timeZeroFormattingString | string | Adds T0 stamp as prefix to file name E.g.yyyymmdd_hhmm |
idMap | string | idMap applied to translate internal FEWS identifiers to external identifiers |
unitConversionsId | string | Allows conversion of rating table units |
includeModifiers | bool | Default=FALSE; If TRUE, rating curve modifiers should be included in the export |
Figure 4.7 Delft-FEWS export configuration for archiving rating curves, general section
Table 4.7and Figure 4.8 discuss the activities section of for exporting rating curves.
Table 4.7 Delft-FEWS export configuration for archiving rating curves (activities section)
Element | Format | Description |
RatingCurvesActivities ComplexType |
|
|
RatingCurvesExportActivity ComplexType |
|
|
fileName | string | without extension, preferably no spaces |
areaId | string | area to which the dataset belongs |
linearTableStageresolution | string | Stage increment between the rows in a rating table |
locationId/locationSetId | string | Locations for which rating curves should be exported to this file |
Figure 4.8 Delft-FEWS export configuration for archiving rating curves, activities section
Anchor | ||||
---|---|---|---|---|
|
Location of the snapshot
Snap shots of the Delft-FEWS database can be archived via the archiveExportModule (exportSnapShot activity).
For snapshots a dataset is generated and stored under the configured area at the moment of workflow execution. The associated directory structure of the Delft-FEWS export for this type of dataset is as follows:
<archiveRoot>/<yyyy>/<MM>/<areaId/<snapshot>/
Figure 4.9 and Table 4.8 documents the associated elements in the exportSnapShot activity.
Incremental export
Since 2019.02 the archive snapshot export is incremental. A copy of the last exported snapshot is made to use as base for the new export. The modified and new rows are copied. Rows that are no longer in the specified profile or central database are deleted from the copy. The snapshot is compacted afterwards . Whether or not a previous snapshot is used as base, the created snapshot contains the same rows and has the same size.
Delft-FEWS stores the location of the last snapshot in a text file: $ARCHIVE_FOLDER$\lastExportedSnapshotPath_$AREA$.txt, If this file does not exist, Delft-FEWS will export a complete snapshot.
Table 4.8 Delft-FEWS export configuration for archiving database snap shots
Element | Format | Description |
general ComplexType |
|
|
archiveFolder | string | Export destination folder, assumes that the account running the FEWS (FSS) application has write access |
zipExportedSnapShot | boolean | Place local datastore in zip file. Default true |
singularExport | The archive folder structure will be ignored and the snapshot will be written directly in the archiveFolder | |
ExportSnapShotActivity ComplexType |
|
|
areaId | string | area (folder) where snapshot is archived |
Figure 4.9 Delft-FEWS export configuration for archiving database snap shots
Code Block | ||
---|---|---|
| ||
<exportArchiveModule xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews">
<exportSnapShot>
<general>
<archiveFolder>$ARCHIVE_DIR$</archiveFolder>
</general>
<activities>
<exportSnapShot>
<areaId>area</areaId>
<filter id="only time series">
<xmlConfig enabled="false" name="Default xml config" synchLevel="11"/>
<coldStates enabled="false" name="Default cold states" synchLevel="11"/>
<moduleDataSets enabled="false" name="Default module data sets" synchLevel="11"/>
<mapLayers enabled="false" name="Default map layers" synchLevel="11"/>
<icons enabled="false" name="Default icons" synchLevel="11"/>
<reportTemplates enabled="false" name="Default report templates" synchLevel="11"/>
<reportImages enabled="false" name="Default report images" synchLevel="11"/>
<continuousTimeSeries enabled="true" name="Simulated" synchLevel="0" maxAge="1000" unit="week"/>
<continuousTimeSeries enabled="true" name="Telemetry" synchLevel="1" maxAge="1000" unit="week"/>
<continuousTimeSeries enabled="true" name="Manual" synchLevel="5" maxAge="1000" unit="week"/>
<continuousTimeSeries enabled="true" name="Astronomical and climatological" synchLevel="4" maxAge="1000" unit="week"/>
<continuousTimeSeries enabled="true" name="Small external forecast grids" synchLevel="6" maxAge="1000" unit="week"/>
<continuousTimeSeries enabled="true" name="Large external forecast grids" synchLevel="16" maxAge="10000" unit="week"/>
<warmStates enabled="false" name="Warm states" maxAge="10" unit="week"/>
<logEntries enabled="false" name="Log Entries" maxAge="1" unit="week"/>
<thresholdEvents enabled="false" name="Threshold Events" maxAge="1" unit="week"/>
</filter>
</exportSnapShot>
</activities>
</exportSnapShot>
</exportArchiveModule>
|
...
Archiving Delft-FEWS products
The Open Archive offers the possibility to archive products. A product is a collections of files which are stored in the archive. This option can be used to archive for example state files, reports or any other kind of file.
...
An configuration example is given below.
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<exportArchiveModule
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews">
<exportProducts>
<general>
<archiveFolder>$ARCHIVE_DIR$</archiveFolder>
</general>
<activities>
<exportProduct>
<areaId>area</areaId>
<sourceId>source</sourceId>
<sourceFile>$INPUT_FOLDER$/sourceA</sourceFile>
<sourceFile>$INPUT_FOLDER$/sourceB</sourceFile>
<moveFile>true</moveFile>
</exportProduct>
</activities>
</exportProducts>
</exportArchiveModule> |
...
An configuration example is given below.
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<exportArchiveModule
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews">
<exportProducts>
<general>
<archiveFolder>$ARCHIVE_DIR$</archiveFolder>
</general>
<activities>
<exportProduct>
<areaId>areaTest</areaId>
<sourceId>sourceTest</sourceId>
<sources>
<zipProduct>true</zipProduct>
<sourceFiles>$INPUT_FOLDER$/testdata/exportandmoveandzip/source?</sourceFiles>
<relativePath>aa</relativePath>
</sources>
<moveFile>true</moveFile>
</exportProduct>
</activities>
</exportProducts>
</exportArchiveModule> |
...
An configuration example is given below
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<exportArchiveModule
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/exportArchiveModule.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews">
<exportProducts>
<general>
<archiveFolder>$ARCHIVE_DIR$</archiveFolder>
</general>
<activities>
<exportProduct>
<areaId>areaTest</areaId>
<sourceId>sourceTest</sourceId>
<importFolder>$IMPORT_DIR$</importFolder>
<fileNameProductDateTimePattern>yyyyMMdd'.nc'</fileNameProductDateTimePattern>
</exportProduct>
</activities>
</exportProducts>
</exportArchiveModule> |
...