Versions Compared

Old Version 72

changes.mady.by.user Andre Grijze

Saved on

compared with

New Version 73

changes.mady.by.user Andre Grijze

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagexml
<?xml version="1.0" encoding="UTF-8"?>
<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">
	<exportSimulated>
		<general>
			<archiveFolder>folder</archiveFolder>
			<areaId>area</areaId>
			<netcdfStorageExport>
				<matchingAttributeId>attribute1</matchingAttributeId>
				<matchingAttributeId>attribute2</matchingAttributeId>
			</netcdfStorageExport>
		</general>
		<activities>
			<netcdfExportActivities>
				<netcdfExportActivity>
					<fileName>test.nc</fileName>
					<timeSeriesSet>
						<moduleInstanceId>test</moduleInstanceId>
						<valueType>scalar</valueType>
						<parameterId>par</parameterId>
						<locationId>loc</locationId>
						<timeSeriesType>simulated forecasting</timeSeriesType>
						<timeStep unit="hour"></timeStep>
						<readWriteMode>add originals</readWriteMode>
					</timeSeriesSet>
				</netcdfExportActivity>
			</netcdfExportActivities>
		</activities>
	</exportSimulated>
</exportArchiveModule>


Because the time series and the meta data for the simulation are now stored separately it is important to know to which simulation a set of netcdf files belong. The meta data and the netcdf files are matched by using the task run id. In addition they are matched by the configured matchingAttributeId. The meta data of a simulation has the value of these attributes stored. They need to match with the values in the actual netcdf files. In netcdf storage you need to configure were the time series are stored so that they can be harvested by the harvester of the external netcdf storage. Below a configuration example is shown.

Code Block
languagexml
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2014 rel. 2 sp1 (http://www.altova.com) by Afdeling ICT (Stichting Deltares) -->
<externalStorage xsi:schemaLocation="http://www.wldelft.nl/fews/archive http://fews.wldelft.nl/schemas//version1.0/archive-schemas/externalStorage.xsd" xmlns="http://www.wldelft.nl/fews/archive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<simulatedForecastingNetcdfStorage id="rwsos.noordzee.matroos.maps">
		<dataFolder>c:\FEWS\archive\matroos\maps</dataFolder>
		<matchingAttributeId>source</matchingAttributeId>
		<matchingAttributeId>issue_time</matchingAttributeId>
	</simulatedForecastingNetcdfStorage>
</externalStorage>




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.
If no relativePeriod is specified the Current simulated forecast is exported

workflowIdstringThis 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

relatedWorkflowIdStringIf 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.
default=TRUE; if TRUE, a list of flags is stored, with each value pointing to the associated flag

includeComments

bool

only applied for scalar values.
default=TRUE; if TRUE, a list of comments is stored, with each value pointing to the associated comment

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

...