...
First two columns are the grid coordinates, third colomn is the value.
The name of the files which are to be imported should all follow this format:
ETAnn_pddMMyyaddmmyy.dat
Where:
nn - is a two digit number
dd - is a day of the month
MM - is the month
yy is the year.
The part between _p and "a" is the forecast time, after the "a" is the time of the timestap. Example:
As the files contain no time data the configuration should contain fileNameObservationDateTimePattern. More over the pattern here:
Import Module configuration options#fileNameObservationDateTimePatternETA40_p010119a020119.dat - a forecast made on January 01, 2019, predicting values for January 02, 2019.
Example configuration:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun 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/timeSeriesImportRun.xsd">
<import>
<general>
<importType>ONS-CPTEC_ETA</importType>
<folder>D:/fews/Import/ETA</folder>
<fileNameObservationDateTimePattern>'ETA40_p??????a'ddMMyy'.dat'</fileNameObservationDateTimePattern>
<fileNameForecastCreationDateTimePattern>'ETA40_p'ddMMyy'a??????.dat'</fileNameForecastCreationDateTimePattern>
<deleteImportedFiles>false</deleteImportedFiles>
<unitConversionsId>ImportUnitConversions</unitConversionsId>
<importTimeZone>
<timeZoneName>GMT+0</timeZoneName>
</importTimeZone>
<dataFeedId>ETA</dataFeedId>
</general>
<timeSeriesSet>
<moduleInstanceId>Import_ETA</moduleInstanceId>
<valueType>grid</valueType>
<parameterId>P.forecast</parameterId>
<locationId>ETA</locationId>
<timeSeriesType>external forecasting</timeSeriesType>
<timeStep id="day00"/>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
<externUnit parameterId="P.forecast" unit="mm"/>
</import>
</timeSeriesImportRun> |
...