...
- importType: MultiflexMeter
serverUrl: https://portal.multiflexmeter.net/api/v1/timeseries/{locationId}/?resolution=30sThe tag {locationId} will be replaced by FEWS with the configured locations in the timeSeriesSet.
The username and the password of the multiflexmeter api should be provided in the global.properties.
- A relative view period has to be configured that will determine the period for which the timeseries will be requested from the API.
- An id map idMap should be configured to map FEWS locations to the multiflex locations and FEWS parameters to Multiflex parameters.
- Missing values: the service returns values that probably should be interpreted as missing values. For example, the value 65535 is returned quite often and is probably a missing value.
Limitations
It is assumed that all timeseries responses are in the following format.
...
| 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>MultiflexMeter</importType>
<serverUrl>https://portal.multiflexmeter.net/api/v1/timeseries/{locationId}/?resolution=30s</serverUrl>
<user>$MULTIFLEX_METER_USER$</user>
<password>$MULTIFLEX_METER_PASSWORD$</password>
<relativeViewPeriod unit="hour" start="-24" end="0" startOverrulable="true"/>
<idMapId>IdImportMultiFlex</idMapId>
<missingValue>65535.0</missingValue>
<dataFeedId>Multiflex Meter</dataFeedId>
</general>
<timeSeriesSet>
<moduleInstanceId>ImportMultiflexMeter</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>T.obs</parameterId>
<locationSetId>MultiflexMeterLocations</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"></timeStep>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
</import>
</timeSeriesImportRun>
|
...