
INSPIRE Building Base
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 Base application schema.
The following properties have been encoded with global scope (see guidelines for further details):
BuildingGeometry2D.horizontalGeometryReference
BuildingGeometry2D.horizontalGeometryEstimatedAccuracy
BuildingGeometry2D.verticalGeometryEstimatedAccuracy
During the derivation, the following mappings, alignments, and omissions have been applied:
-
Mappings:
- Code list values are mapped to
skos:Concept
. - The properties
beginLifespanVersion
andendLifespanVersion
are mapped to the global properties defined by the base ontology. - Geometry types are mapped to classes from the Simple Feature ontology.
- Code list values are mapped to
-
Alignments (through subsumption):
- Spatial object types are aligned with
gsp:Feature
. - Properties of spatial object types with value type
GeographicalName
are aligned to propertylocn:geographicName
. - Properties with a geometry value type are aligned to
locn:geometry
andgsp:hasDefaultGeometry
.
- Spatial object types are aligned with
-
Omissions:
- Property
inspireId
is omitted. See the guidelines for further details.
- Property
Version: 1.0.0