Versions Compared

Key

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

...

A complete import module configuration consists of an ID Mapping file and a Import Module Instance file. To convert the rainfall in a proper unit (from 0.1 mm per 6 hour to mm/hr for example) it is also required to configure a Unit Conversion file.

ModuleConfigFiles

...

The following example of an Import Module Instance will import the time series as equidistant series for timezone GMT with a time step of 6 hours.

Code Block
xml
xml
titleImportKNMI.xml
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun ......">
  <import>
    <general>
      <importType>KNMIEPS</importType>
      <folder>$IMPORT_FOLDER_KNMI_EPS$</folder>
      <failedFolder>$IMPORT_FAILED_FOLDER_KNMI_EPS$</failedFolder>
      <backupFolder>$IMPORT_BACKUP_FOLDER_KNMI_EPS$</backupFolder>
      <idMapId>IdImportEPS</idMapId>
      <unitConversionsId>ImportKNMIUnits</unitConversionsId>
      <importTimeZone>
        <!--EPS is in GMT-->
        <timeZoneOffset>+00:00</timeZoneOffset>
      </importTimeZone>
      <dataFeedId>KNMI-EPS</dataFeedId>
    </general>
    <timeSeriesSet>
      <moduleInstanceId>ImportKNMI</moduleInstanceId>
      <valueType>scalar</valueType>
      <parameterId>P.voorsp.ens</parameterId>
      <locationSetId>KNMI-EPS</locationSetId>
      <timeSeriesType>external forecasting</timeSeriesType>
      <timeStep unit="hour" multiplier="6"/>
      <readWriteMode>add originals</readWriteMode>
      <synchLevel>1</synchLevel>
      <ensembleId>EPS</ensembleId>
    </timeSeriesSet>
    <timeSeriesSet>
      <moduleInstanceId>ImportKNMI</moduleInstanceId>
      <valueType>scalar</valueType>
      <parameterId>P.voorsp.ctr</parameterId>
      <locationSetId>KNMI-EPS</locationSetId>
      <timeSeriesType>external forecasting</timeSeriesType>
      <timeStep unit="hour" multiplier="6"/>
      <readWriteMode>add originals</readWriteMode>
      <synchLevel>1</synchLevel>
    </timeSeriesSet>
    <timeSeriesSet>
      <moduleInstanceId>ImportKNMI</moduleInstanceId>
      <valueType>scalar</valueType>
      <parameterId>P.voorsp.det</parameterId>
      <locationSetId>KNMI-EPS</locationSetId>
      <timeSeriesType>external forecasting</timeSeriesType>
      <timeStep unit="hour" multiplier="6"/>
      <readWriteMode>add originals</readWriteMode>
      <synchLevel>1</synchLevel>
    </timeSeriesSet>

    <!--to let the import module know that the KNMI rainfall is an accumulative timeseries 
      in 0.1 mm/hr that should be disaggrated and converted to for example mm/hr-->
    <externUnit parameterId="P.voorsp.ens" unit="0.1 mm/6hr" cumulativeSum="true"/>
    <externUnit parameterId="P.voorsp.ctr" unit="0.1 mm/6hr" cumulativeSum="true"/>
    <externUnit parameterId="P.voorsp.det" unit="0.1 mm/6hr" cumulativeSum="true"/>
  </import>
</timeSeriesImportRun>

IdMapFiles

...

Info

Defines mappings between KNMI and FEWS parameters and locations.

...

Important in this configuration is the externalParameter is manipulated to identify the deterministic, control and ensemble forecasts. Therefore the import module generates automatically a suffix to the parameter ID in the import files. If the import file contains a parameter "13011" for rainfall, the import generates the next externalParameters: "13011_deterministic", "13011_control" and "13011_ensemble".

UnitConversionFile

...

Info

Defines the conversion of the units that should be applied.

...

Important in this configuration is the externalParameter is manipulated to identify the deterministic, control and ensemble forecasts. Therefore the import module generates automatically a suffix to the parameter ID in the import files. If the import file contains a parameter "13011" for rainfall, the import generates the next externalParameters: "13011_deterministic", "13011_control" and "13011_ensemble".

Example

...

Files

See attached files