8 Matching Annotations
  1. Jan 2022
    1. Best practice for developing GML encodings is to develop a XML schema (XSD) using the GML schema, derived from a UML model based on ISO 19107.
      • would this require enterprise architect expertise? And who would responsibility lay with?
      • we do not use GML internally
    2. ConceptScheme (SKOS).
      • what would be the benefit of using SKOS over utilising a codelist option from ISO 19103. Is it because it helps with compliance of web application encoding?
    3. To be completed. It is noted CityGML does not support survey observation nor explicit topological concerns, however it is expected that the proposed 3D Solid Geometry profile would support the implicit profile of ISO19107 used in CityGML.
      • CityGML models building forms in various LoD’s. These are primarily from building footprints and shells I believe. CityGML may be too verbose and large a language for cadastral features. However simple referencing/mapping to CityGML as a subset would useful.
    4. A Canonical Logical Model for ISO 19156 is available in the OWL language: SOSA (Sensor, Observation, Sample and Actuator). This forms part of a larger model that supports description of observation equipment, sampling strategies etc.
      • Will SOSA be able to represent the majoring of concepts and classes that surveyors currently collect?

      • Is there a gap in translation across 19156 and SOSA. Are all types of surveying observation transposable to a SOSA element?

      • Does SOSA help future proof the model due to it inclusion of sensor elements that is generated by modern survey field equipment?