...
Validation of the values in the UmAquo import files is done against the Aquo schemas . Instead of validating over the web, validation is done locally by validating against the schemas present in the resource file ^UmAquoUmAquo_schemas.jar||\. This archive contains a subset of schemas from the Aquo schemas site. If the Aquo schemas are updated then a new version of the schemas jar must be distributed.
...
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"> <!-- This is an example import configuration file for importing UmAquo CSV data from an import directory --> <import> <general> <!-- Class name of UmAquo CSV parser --> <parserClassName>nl.deltareswldelft.webservice.umaquo.timeseriesparsers.UmAquoXmlTimeSeriesParser</parserClassName> <!-- Path to directory containing UmAquo libraries and schemas. If omitted then the content of the umaquo-bin can be placed in the FEWS-bin dir --> <binDir>%REGION_HOME%/Modules/umaquo-bin</binDir> <!-- Directory from which CSV files are to be imported --> <folder>$IMPORT_FOLDER$/UmAquo/XML</folder> <failedFolder>$IMPORT_FAILED_FOLDER$/UmAquo/XML</failedFolder> <backupFolder>$IMPORT_BACKUP_FOLDER$/UmAquo/XML</backupFolder> <idMapId>IdImportUmAquo</idMapId> <importTimeZone> <timeZoneOffset>+00:00</timeZoneOffset> </importTimeZone> </general> <properties> <!-- Optional: select UmAquo schema version 2009 or 2011. Default = 2009 --> <int key="SCHEMA_VERSION" value="2009"/> </properties> <timeSeriesSet> <moduleInstanceId>ImportUmAquo</moduleInstanceId> <valueType>scalar</valueType> <parameterId>MyPar</parameterId> <locationSetId>MyLocSet</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>add originals</readWriteMode> <synchLevel>1</synchLevel> </timeSeriesSet> </import> </timeSeriesImportRun> |
Here is an example id-map file:
Code Block |
---|
<?xml version="1.0" encoding="UTF-8"?> <idMap 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/idMap.xsd" version="1.1"> <!-- internalLocation: FEWS location internalParameter: FEWS parameter internalLocation: UM Aquo location externalParameter: UM Aquo parameter externalQualifier : eenheid externalQualifier1 : hoedanigheid externalQualifier2 : compartiment <!-- Optional: allow lenient validation. Default = false --> <map internalLocation="LOC-001" internalParameter="Q.obs" externalLocation="LOC-001.external" externalParameter="Q.obs.external" externalQualifier="m3/s;kubieke meter per seconde" externalQualifier1="NVT;Niet van toepassing" externalQualifier2="NT;Niet van toepassing"/> </idMap> |
Id-Mapping goes as follows:
Internal timeseries location and parameter combinations are mapped to external location, parameter and qualifier sets as follows:
- externalLocation values are read from the Meetpunt column
- externalParameter values are read from the Parameter column
- 1st externalQualifier values are read from the Eenheid column
- 2nd externalQualifier values are read from the Hoedanigheid column
- 3rd externalQualifier values are read from the Compartiement column
Here is an example flag conversion file:
...
<bool key="LENIENT" value="true"/>
</properties>
<timeSeriesSet>
<moduleInstanceId>ImportUmAquo</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>MyPar</parameterId>
<locationSetId>MyLocSet</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<readWriteMode>add originals</readWriteMode>
<synchLevel>1</synchLevel>
</timeSeriesSet>
</import>
</timeSeriesImportRun>
|
Here is an example id-map file:
Here is an example flag conversion file: