This page is currently a guideline for what a DD API 3.0 service should confirm to in order to be able to let Delft FEWS clients connect to it.
Delft-FEWS will construct request url's as follows:
<serverUrl>?$filter=parameter/quantity eq '<parameterId>' and parameter/parameter eq '<qualifierId>' and foi/code eq '<locationId>' and phenomenontime/beginposition ge <startTime> and phenomenontime/endposition le <endTime>
Where
- <serverUrl> will be replaced by the server url configured in the FEWS import configuration
- <parameterId> will be replaced by external parameter id, this will always be supplied
- <qualifierId> will be replaced by external qualifier id, this is optional, when there is no external qualifier the and parameter/parameter eq '<qualifierId>' part of the url request will be left out
- <locationId> will be replaced by external location id, this will always be supplied
- <startTime> will be replaced by the start of the requested period according to the format: yyyy-MM-ddTHH:mm:ssZ this will always be supplied
- <endTime> will be replaced by the end of the requested period according to the format: yyyy-MM-ddTHH:mm:ssZ this will always be supplied
There will not be a part in the url request to specify the desired time step of the data. In case the data returned will not be according to a consistent time step, a non-equidistant time step should be used within FEWS from which later on equidistant time series can be constructed if desired.
