-
SensorThings currently has name, symbol and definition.
Is the UOM in SWE-Common allowed to have both a UCUM Code (symbol) and a href (definition) at the same time? Given the `oneOf` I guess not.
…
-
We are discussing about creating a native QGIS data provider for STA, see
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/257
One use-case that I'm personally interested in is retrieving…
-
### What is the bug or the crash?
When adding geospatial layers, the SensorThings Data Provider only name the layer using its geometry type (Point, Line, etc...).
If you add Locations, and Feature…
-
**Description / Describe**
SensorThings a un standard OGC https://www.ogc.org/standards/sensorthings
Ce standard permet d'avoir une interopérabilité avec tous les données de capteurs.
L'Agrocamp…
-
Just for the record, and related to https://github.com/w3c/sdw-sosa-ssn/issues/29#issuecomment-1779470219
The OMS definition of Feature of Interest is: "subject of the observation".
This is more…
-
Source: http://ogc.standardstracker.org/show_request.cgi?id=575
In various contexts, we've identified a requirement for a description of a potential observation; this is in close alignment with the O…
-
It would be great to clarify / provide examples of what URIs should be used for properties / field definitions (`x-ogc-definition`).
I imagine we might want to support both OGC and non-OGC definiti…
-
### Steps to Reproduce
Add the select query parameter to a request with ID selected.
### Expected Behavior
The response should only include the IDs of the resources returned.
### Actual Behavior
…
-
### Feature description
Sensorthings adds to each type (sensor, location, datastream) a set of navigationlinks which enable linkage between the types, actually one needs to follow the link to retri…
-
Code lists has the following values initially:
* **homogenousObservationCollection**: if an attribute value is provided within the ObservationCharacteristics, this value applies to all contained ob…