GeoAPI provides a set of interfaces in programming languages (currently Java and Python) for geospatial applications. The GeoAPI interfaces closely follow OGC specifications, adaptated to match the expectations of programmers.
ISO 19157 defines a DQM_Measure class, but there is no association to this class in any ISO 19157 object. Instead there is an association from DQ_Element to DQM_MeasureReference, then users need to look for that reference in a registry or catalogue (defined in another ISO standard) for getting the full DQM_Measure object.
The rational for above approach may be well relevant for documents encoded in formats such as XML, because it avoids inflating the document size with verbose quality measurement descriptions. But this size problem does not apply to interfaces in programming languages, where everything is basically just pointers. Even if the DQM_Measure was really consuming a lot of memory, implementations always have the possibility to fetch data from a database or do themselves the lookup in a registry under the hood when first needed.
For making easier to get data quality measures from a DQ_Element without forcing users to use a registry or catalogue, we propose to rename the DQ_Element.measure : DQM_MeasureReference property as measureReference, and use the measure property name for an association to a full DQM_Measure object. The latter is optional and implementers always have the possibility to specify only a DQM_MeasureReference is desired.
ISO 19157 defines a
DQM_Measureclass, but there is no association to this class in any ISO 19157 object. Instead there is an association fromDQ_ElementtoDQM_MeasureReference, then users need to look for that reference in a registry or catalogue (defined in another ISO standard) for getting the fullDQM_Measureobject.The rational for above approach may be well relevant for documents encoded in formats such as XML, because it avoids inflating the document size with verbose quality measurement descriptions. But this size problem does not apply to interfaces in programming languages, where everything is basically just pointers. Even if the
DQM_Measurewas really consuming a lot of memory, implementations always have the possibility to fetch data from a database or do themselves the lookup in a registry under the hood when first needed.For making easier to get data quality measures from a
DQ_Elementwithout forcing users to use a registry or catalogue, we propose to rename theDQ_Element.measure : DQM_MeasureReferenceproperty asmeasureReference, and use themeasureproperty name for an association to a fullDQM_Measureobject. The latter is optional and implementers always have the possibility to specify only aDQM_MeasureReferenceis desired.