/datasources

The Datasources endpoint can return the datasources that the provider offers. Filtering: uuid and name.

About Datasource

DataSource (“bronhouder” in Dutch) objects describe the source of the data. A node can have multiple data sources.

get

Request a specific datasource by its uuid.

get

/nodes

The Nodes endpoint can return the nodes that the provider offers. Filtering: uuid and name.

About Node

Node objects contain the properties of the data node. A node is an operational implementation of the Digital Delta specification.

get

Request a specific node by its uuid.

get

/observationtypes

The ObservationTypes endpoint can return the observationtypes that the provider offers. Filtering: list of parameters.

About ObservationType

The ObservationType objects describe all attributes to correctly interpret what has been measured, and in what way. It is essential to have the quantity field.

get

Request a specific observation type by its qualifier.
Since almost no specific ObservationTypes for biological entities exist in Aquo, AquaDesk is using uuids instead of the code. The type 'String' is used in both circumstances.

get

/locations

The Locations endpoint can return the locations that the provider offers. Filtering: bounding box, uuid, code, name and node.

About Locations

A location object contains all information required to describe a location. This version contains a node.

get
post

Request a specific location by its uuid.

get

/timeseries

The timeseries endpoint can return both the metadata and the data itself. If a start‐ and endtime is given in the request, the data is added to the response, for both the List and the Detail requests. Furthermore, it is possible to only retrieve the data (without the metadata) by querying the data endpoint: /timeseries/{uuid}/data/.
Optional: add start and end filter, returns metadata and data (values)
Filtering: value type, uuid, code, node, timeseries type, observation type, location name, start- and enddate.

About Timeseries

Timeseries objects contain all information needed to interpret timeseries.
There are references to other objects, such as Node, Location, DataSource, ObservationType and TimeseriesType.
The TimeseriesType should be added as a reference because it can indicate if a timeseries containts a RAW dataset or makes use of the current measurements. The Digital Delta specification of timeseries makes no assumptions on the nature of the series, timeseries may describe any series of data points of the same observation type and datasource in time on one location.
This includes both equidistant series (fixed time interval between data points) and non-equidistant series (with varying time interval).

Use case:

Imagine a data-source is providing several timeseries for a specific location and observation. For example:
Waterlevel is measured every 5 minutes for the location Lobith. This is the original timeseries from the datasource and we can call it the RAW timeseries or the original timeseries.
Within the same data-souce, again, waterlevel is measured every 5 minutes for the same location, but this timeseries is a manually or automatically validated timeseries. So in this case we have an original timeseries which is providing the raw data and another timeseries which has been validated. Both timeseries can be required for different purposes.
Now imagine that someone requires the validated timeseries instead of the original.
The users should be able to filter them based on this information and retreve data only for this type of timeseries. There are several more uses cases where more than two types are used. Think of timeseries that are recalculated based on validation, interval, aggregation, etc.

Using TimeseriesType is providing more flexibility in providing multiple timeseries for the same location and observation type provided by a single data-source.

get
post

Get the data of one timeseries, including metadata.

get

Get the detail data for the specified timeseries, excluding metadata.

get