Geoera HOVER WP3 – Task 3-5c product for thermal and natural mineral waters – vocabularies and codelists about project-support-wp8 HOT 8 CLOSED

We have assigned Martin Schiegl to look at the vocabulary issue but, if I understand your question correctly, you will want to use the Observations and Measurements schema suggested by @CipoCar to put qualifiers on the values so we are asking Carlo to comment on that aspect.

from project-support-wp8.

No issues with a vocabulary "hydrochemical compounds". It is more of a problem how to implement O&M, GeoSciML or INSPIRE standards.

from project-support-wp8.

Thank you for your replies! I think we solved the issue with the vocabulary of "hydrochemical compounds".

Basically we show point data with hydrochemical measurements in this product,
For example "Arsenic" is now considered in the new vocabulary "hydrochemical compounds".
However, we also need a "value = concentration of the hydrochemical compound" and the "unit". So far we suggest to use https://ucum.org/ucum.html for the units, but we also need to consider values below the detection limit and we are not sure how to solve this.
Examples:
Arsenic = 0,1 mg/l
Arsenic = <0,1 mg/l

Many thanks!

from project-support-wp8.

@elsdan Have you discussed using the O&M model for this with @soreslaszlo ?

from project-support-wp8.

no, could you provide me with his contact, I think he is not active on this platform.

from project-support-wp8.

Including response sent by @soreslaszlo by email here for reference:

Dear Daniel,

In the FROST propotype service for HOVER test data I used the following solution for the detection limit problem:

In principle it is not appropriate to mix numeric and textual values for the same property. When we tend to do this we are mixing different things: quantities and categories.
Following the practice of HIKE I created a dictionary for a few hydrochemical categories.

These Concept names are used to define the name of properties (ObeservedProperties) and the category values for Observed data .

You can find more about the FROST prototype on GitHub #299

Best regards,
Laszlo

from project-support-wp8.

Status update

This project prefers to use numerical values rather than categorical ranges as in the above FROST example for some of the properties they are reporting. They are currently intending to put values of half detection limit in cases where the value is below detection limit.

They are intending to include the measurement units in the field name.

Potential codelists have been drafted in HOVER deliverable D3.5a and are undergoing refinement/approval with GIP-P WP4.

from project-support-wp8.

Have confirmed by email that remaining details are being handled by direct communications with EGDI and WP4.

from project-support-wp8.