Closed hylkevds closed 2 years ago
6: When posting Observations using DataArrays, you can specify the FeatureOfInterest by adding the component FeatureOfInterest/id. However when getting Observations using DataArrays this is not specified. Is this intentional, or should it also be possible to specify that you want to fetch the ids of the FeatureOfInterest of the Observations?
Some simple solutions:
dataArray@iot.count
elements from the examples.@iot.nextLink
and @iot.count
to the examples.It would be good to have a bit more text explaining how the dataArray extension relates to query parameters. Something like:
$select
, $top
, $skip
, $count
and $orderby
work the same as they would with a non-dataArray request, only the formatting of the result is different, as the Observations are grouped by (Multi)Datastream. The result can contain @iot.count
and @iot.nextLink
fields just like with normal requests for Observations. The $expand
query parameter is not allowed for dataArray requests.
Fixed with the publication of Sensing v1.1.
DataArrays are grouped by (Multi)Datastream:
So when I do a get on http://example.org/v1.0/Observations?$resultFormat=dataArray the "value" array in the response might contain one or more objects, depending on the number of Datastreams that the resulting Observations belong to.
The questions: 1: The example shows a "dataArray@iot.count" element for each value object that is not further defined. Is this:
2: OrderBy: Since the Observations are grouped per Datastream, when I request an orderby=id I could end up with the following, which means the ordering is partly un-done:
3: The test section "A.6 SensorThings API Data Array Extension" states:
Since the Data Array is only specified for Observations, you can not create Datastreams using it. So I suppose this should be "Create at least two Observations ..." or "Create Observations for at least two Datastreams ..."
4: Should the data array response contain a global @iot.nextLink and @iot.count?
5: The navigation link to the Datastream is incorrect in the example:
Since the page url is
/v1.0/Datastreams(1)/Observations
, this would link to/v1.0/Datastreams(1)/Datastreams(1)
, so the navigation link should be to../Datastreams(1)