MIM7: Geospatial Data
OASC MIM7: Geospial Data
Description
MIM7 aims to provide Minimal Interoperability Mechanisms related to geospatial data, to tackle the challenge faced by cities and communities of being able to integrate and transfer data between internal and external IT systems. It also takes into account the fact that spatial assets need to be accessed as linked data by many IT- and IoT-systems, and over a long period of time, and thus the vital role of the use of persistent identifiers.
Objectives
To enable cities and communities to easily integrate data about spatial assets such as streetlights, buildings, and streets with spatio-temporal data from sensors, along with other data sources that can provide helpful context information to the geospatial data, and make the data interoperable within, and between cities and communities.
This integration should be made possible across technologies and vendors.
Capabilities and Requirements
C1: Cities and communities can easily transfer geospatial data between internal and external IT systems.
R1: Geospatial data shall be exposed through a standards-based web service interface.
C2: Cities and communities can integrate 2D and 3D geospatial data coming from a variety of sources, for example geodata and building information models, and share that data within, and between them in an interoperable way.
R2: Geospatial data shall be encoded using open standards. It is recommended to use relevant standards from OGC and Building Smart International.
C3: Cities and communities can integrate geospatial data with other data that can provide further information about the context.
R3: All data sets used to provide further information about the context covered by geospatial data shall comply with MIM1 and MIM2.
C4: Cities and communities have a consistent and persistent way of describing individual instances of all features, things or entities included in the geospatial data sources.
R4: Unique and persistent identifiers shall be used to identify particular instances of any entity used in data sets (see MIM1: Interlinking Data).
C5: Coordinate Reference Systems (CRS) used in data sharing, are easily transformable into a common CRS.
R5: Coordinate Reference Systems (CRS) shall comply with standards, and information shall be provided regarding which standard (e.g., EPSG:4326, EPSG:3857 etc.,) is being used. This will include the EPSG number or WGS number, along with information about any variation based on national systems such as the Latvian LKS-92, so that data could be transformed to a common CRS. Note: Within the EU, for geospatial data it is required to use metadata compliant with the INSPIRE Directive. This includes the metadata needed to describe the CRS information.
Mechanisms
M1: Legacy Web based Mechanisms
R1: Geospatial data shall be exposed through a standards-based web service interface.
Data is made accessible through OGC WFS
R2: Geospatial data shall be encoded using open standards. It is recommended to use relevant standards from OGC and Building Smart International.
GML and CityGML should be used for Geospatial encoding
M2: API Web based Mechanisms
R1: Geospatial data shall be exposed through a standards-based web service interface.
Data is made accessible through OGC API Features and OGC SensorThings API.
R2: Geospatial data shall be encoded using open standards. It is recommended to use relevant standards from OGC and Building Smart International.
GeoJSON including JSON feature geometry and CityJSON are preferred for geospatial encoding in API-based mechanisms, with, GeoPackage, and CityGML as alternatives.
Interoperability Guidance
For Standards-based geospatial encoding such as GML, and CityGML shared through OGC WFS, A proxy OGC API could be considered on top of the OGC WFS service
Last updated