Skip to content

DQ_Element and DQ_Result under Observation #6

@KathiSchleidt

Description

@KathiSchleidt

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!):

  • ISO 19115
  • ISO 19157

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions