Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DQ_Element and DQ_Result under Observation #6

Open
KathiSchleidt opened this issue Jan 28, 2019 · 0 comments
Open

DQ_Element and DQ_Result under Observation #6

KathiSchleidt opened this issue Jan 28, 2019 · 0 comments

Comments

@KathiSchleidt
Copy link
Collaborator

KathiSchleidt commented Jan 28, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant