...
Those parts will be filled as follows:
- <part A> will be filled according to externalAttribute "LOCATION_ATTRIBUTE_PART_A" of the location, if not configured part A will remain empty
- <part B> will be location id (HecDss always writes this in capitol letters)
- <part C> will be parameter id
- <part D> will be the start date (see Time Steps and start dates)
- <part E> will be the time step (see Time Steps and start dates)
- <part F> will be the first qualifier id
...
| View file | ||||
|---|---|---|---|---|
|
Here is a very simple import export configuration example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesExportRun 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/timeSeriesExportRun.xsd">
<export>
<general>
<exportType>HecDss</exportType>
<folder>$EXPORT_FOLDER$</folder>
<exportFileName>
<name>output.dss</name>
</exportFileName>
</general>
<exportAttribute internalAttributeId="REGION" externalAttributeId="LOCATION_ATTRIBUTE_PART_A"/>
<timeSeriesSet>
<moduleInstanceId>Run_XBeach</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Flow</parameterId>
<locationId>FarWest</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<relativeViewPeriod unit="week" start="-1" end="0"/>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
</export>
</timeSeriesExportRun>
|
...