...
The TAHMO import will take the serverUrl and append it with "stations" to obtain information about the available locations. It will then use the location id's to construct the query url's for the timeseries as such: "<serverUrl>/timeseries/<locationId>/hourly?startDate=...&endDate=...". Note that specifying a relativeViewPeriod is required.
Example Import configuration file:
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 Observations and Measurements data from a service --> <import> <general> <importType>TAHMO</importType> <serverUrl>https://tahmoapi.host.net/v1/</serverUrl> <user>XXXXX<<user>dummy_username</user> <password>XXXXX<<password>dummy_password</password> <relativeViewPeriod unit="hour" start="-5" end="0" startOverrulable="true" endOverrulable="true"/> <idMapId>IdImportTahmo</idMapId> </general> <timeSeriesSet> <moduleInstanceId>ImportDD<<moduleInstanceId>ImportTahmo</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> |
...