Observation quality is to be provided via the DQ_Element type. However, it is unclear which DQ_Element is being referenced (the models are quite different!):
Additionally, DQ_Element requires provision of the result utilizing DQ_Result (both models). However, DQ_Result is only defined for
- DQ_ConformanceResult (just boolean pass/fail)
- DQ_QuantitativeResult (true quantity, requires UoM)
- DQ_DescriptiveResult (only 19157)
For our use case, we would require a DQ_CategoryResult, in order to provide verification and validity levels from a codelist (usually 3-4 options, i.e. raw data, preliminary validation, fully validated). Can we propose this here, or do we need to push this towards the DQ group?
Link to OGC STA GitHub: opengeospatial/sensorthings#68
Link to Fraunhofer GitHub: FraunhoferIOSB/FROST-Server#98
Observation quality is to be provided via the DQ_Element type. However, it is unclear which DQ_Element is being referenced (the models are quite different!):
Additionally, DQ_Element requires provision of the result utilizing DQ_Result (both models). However, DQ_Result is only defined for
For our use case, we would require a DQ_CategoryResult, in order to provide verification and validity levels from a codelist (usually 3-4 options, i.e. raw data, preliminary validation, fully validated). Can we propose this here, or do we need to push this towards the DQ group?
Link to OGC STA GitHub: opengeospatial/sensorthings#68
Link to Fraunhofer GitHub: FraunhoferIOSB/FROST-Server#98