Anomalie #22629
discrepancy between elevation accuracy and borehole collar accuracy
| Statut: | Nouveau | Début: | 04/03/2019 | |
|---|---|---|---|---|
| Priorité: | Normal | Echéance: | ||
| Assigné à: | - | % réalisé: | 0% | |
| Catégorie: | - | |||
| Version cible: | - |
Description
eposb:boreCollarPositionalAccuracy is a simple value with a unit definition in one element.
eposb:elevationAccuracy triggers gmd:DQ
- The latter is quite complicated (and I can't get all of it to work properly in geoserver, which however is a side-issue and marked in the mapping file in the svn).
- Is it reasonable to request a much higher level of documentation for the data quality of the elevation than for the entire location? Why? How did we think?
- If we can't find a reason for the difference, then we should aim at aligning the two properties to one of the two approaches.
Any thoughts on this issue? Please comment below.
Maybe Sylvain can check his freeplane notes on this issue that we remember better the reason for the decisions on how to treat data quality.