INSPIRE Building 3D

by

Infrastructure for Spatial Information in Europe (INSPIRE)

Created 3 years ago
70 statements

This is a draft RDF vocabulary for representing spatial data sets in INSPIRE as RDF. This vocabulary has been created using the “Guidelines for the RDF encoding of spatial data”.

The use of RDF is optional and does not supersede or replace the requirements regarding encoding specified in Clause 9 of the INSPIRE Data Specifications. This optional encoding is intended to support the e-government and open data community in Europe, which is increasingly looking at RDF to represent data.

This is a draft version. It has limitations and is expected to contain errors. Please report any issues or concerns in GitHub.

This ontology contains classes and properties that have been derived from the INSPIRE Buildings 3D application schema.

The following properties have been encoded with global scope (see guidelines for further details):

  • Building.geometry3DLoD1
  • Building.geometry3DLoD2
  • Building.geometry3DLoD3
  • Building.geometry3DLoD4

During the derivation, the following mappings, alignments, and omissions have been applied:

  • Mappings:

    • GM_MultiCurve and GM_MultiSurface are mapped to the according classes from the Simple Feature ontology.
    • GM_Solid is mapped to the according class from the GML ontology.
    • Properties geometry2D are mapped to the global property geometry2D from the buildings 2D ontology.
    • Properties horizontalGeometryReference, verticalGeometryEstimatedAccuracy, and horizontalGeometryReference are mapped to the according global properties from the buildings base ontology.
    • Properties BuildingPart.geometry3DLoDX (with X=1,2,3,4) are mapped to the global properties geometry3DLoDX (with X=1,2,3,4) from this ontology.

  • Alignments (through subsumption):

    • Spatial object types are aligned with gsp:Feature.
    • Properties with a geometry value type are aligned to locn:geometry and gsp:hasGeometry.

  • Omissions: none

Version: 1.0.0

Graphs