-
Am I missing something or is the DataInterface gone as an output type of a system?
What would be the appropriate way to point to an external, not OGC-API compatible service holding the outputs of a…
-
The current Datastream model only allows for scalar results (a single observed property) and creating a separate collection for the MultiDatastream case feels a little hacky. Can we consider using SWE…
-
It seems that only WaterML is supported in SOS component. Are you planning to implement SensorML as well? (https://www.opengeospatial.org/standards/sensorml)
Thank you
-
```
Incorporate SensorML records in a NetCDF global attribute via the toolbox.
```
Original issue reported on code.google.com by `guillaum...@gmail.com` on 8 Jun 2011 at 4:08
-
Currently, the `Sensor` is considered to be a "Citizen Scientist" always (ideas exist to have different roles later on). However, the STA only supports SensorML and PDF types as sensor descriptions. F…
ridoo updated
3 years ago
-
Given the new flexible extra endpoint, for some applications it could be useful to offer more detailed and standardized information about stations/sensors, by providing a full URL to the original Sens…
nuest updated
7 years ago
-
Related to #12
See "SensorML 2.0 Test" in `test_describesensor.R`
nuest updated
2 years ago
-
The Foreword states:
> This release is not fully backward compatible with version 2.0 even though changes were kept to a minimum.
It would be really helpful to have a table of (at least) the bre…
-
Recently, the models for SWE Common Data and SensorML were used to create a JSON encoding for these standards. These JSON encodings are currently being used to support
- tasking parameters in STA
…
-
The SensorML standard states that the Unique Identifier must be a gml:identifier with the codespace "uniqueID" (pg 81). However, there is inconsistency primarily in SensorML examples. For example:
…