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 Common Transport Elements application schema.

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

• Mappings:

  • Code list and enumeration values are mapped to skos:Concept.
  • The properties validFrom and validTo are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.
  • Properties with a geometry value type are aligned to locn:geometry and gsp:hasDefaultGeometry.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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 Network application schema.

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

• SimplePointReference.offset

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

• Mappings:

  • Code list values are mapped to skos:Concept.
  • The properties beginLifespanVersion and endLifespanVersion are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.
  • Property SimpleLinearReference.offset is mapped to the global property offset from this ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.
  • Properties with a geometry value type are aligned to locn:geometry and gsp:hasDefaultGeometry.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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 Hydro - Base application schema.

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

• Mappings: none

• Alignments (through subsumption):

  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.

• Omissions: none

Version: 1.0.0

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 Hydro - Physical Waters application schema.

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

• Mappings:

  • Code list and enumeration values are mapped to skos:Concept.
  • The properties beginLifespanVersion and endLifespanVersion are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.

• Alignments (through subsumption):

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

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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 Hydro - Network application schema.

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

• Mappings:

  • Code list values are mapped to skos:Concept.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.

• Omissions: none

Version: 1.0.0

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 Geographical Names application schema.

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

• Mappings:

  • Code list values are mapped to skos:Concept.
  • The properties beginLifespanVersion and endLifespanVersion are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Type GeographicalName is aligned with skos:Concept.
  • Property NamedPlace.geometry is aligned to property locn:geometry and gsp:hasDefaultGeometry.
  • Property NamedPlace.name is aligned to property locn:geographicName.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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 Cadastral Parcels application schema.

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

• CadastralParcel.referencePoint

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

• Mappings:

  • Code list values are mapped to skos:Concept.
  • The properties beginLifespanVersion, endLifespanVersion, validFrom, and validTo are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.
  • Property label is mapped to rdfs:label.
  • Property CadastralZoning.referencePoint is mapped to the global property referencePoint from this ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.
  • Properties CadastralParcel.geometry, CadastralBoundary.geometry, and CadastralZoning.geometry are aligned to locn:geometry and gsp:hasDefaultGeometry.
  • Property CadastralParcel.referencePoint is aligned to locn:geometry and gsp:hasGeometry.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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

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 2D application schema.

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

• Building.geometry2D

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

• Mappings:

  • Property BuildingPart.geometry2D is mapped to the global property geometry2D from this ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.

• Omissions: none

Version: 1.0.0

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 and endLifespanVersion are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.
  • Properties with a geometry value type are aligned to locn:geometry and gsp:hasDefaultGeometry.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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 Base Types & Base Types2 application schemas. Additional classes implement types from the INSPIRE foundation schemas for which no suitable ontology representation has been identified yet.

The following properties with global scope (see guidelines for further details) have been added to this ontology, for re-use by importing ontologies:

• beginLifespanVersion
• endLifespanVersion
• validFrom
• validTo

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

• Mappings:

  • Code list and enumeration values are mapped to skos:Concept.
  • Type Identifier is mapped to rdfs:Resource.
  • Type SpatialDataSet is mapped to dcat:Dataset.
  • Type PT_FreeText is mapped to rdf:langString.
  • Type TM_Position is mapped to time:TemporalPosition.

• Alignments (through subsumption):

  • Property Contact.address is aligned to property locn:address.

• Omissions:

  • The types Identifier and SpatialDataSet have not been converted. They are mapped as described before.
  • Property DocumentCitation.date has been omitted. A value for this property can be encoded using the DC-Terms properties ‘created’, ‘issued’, and ‘modified’. See the guidelines for further details.

Version: 1.0.0

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 Administrative Units application schema.

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

• AdministrativeBoundary.country

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

• Mappings:

  • Code list and enumeration values are mapped to skos:Concept.
  • The properties beginLifespanVersion and endLifespanVersion are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.
  • Property AdministrativeUnit.country is mapped to the global property country from this ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.
  • Properties with a geometry value type are aligned to locn:geometry and gsp:hasDefaultGeometry.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.

Version: 1.0.0

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 Addresses application schema.

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

• Mappings:

  • Code list values are mapped to skos:Concept.
  • The properties beginLifespanVersion, endLifespanVersion, validFrom, and validTo are mapped to the global properties defined by the base ontology.
  • Geometry types are mapped to classes from the Simple Feature ontology.

• Alignments (through subsumption):

  • Spatial object types are aligned with gsp:Feature.
  • Type Address is aligned with locn:Address.
  • Type ThoroughfareNameValue is aligned with gn:GeographicalName
  • Properties of spatial object types with value type GeographicalName are aligned to property locn:geographicName.
  • Properties with a geometry value type are aligned to locn:geometry and gsp:hasDefaultGeometry.

• Omissions:

  • Property inspireId is omitted. See the guidelines for further details.
  • Property ThoroughfareNameValue.name is omitted.
  • Type AddressRepresentation is omitted. Whenever this type is used as value type, then in the RDF encoding the RDF implementation of type Address is used. For further details, see the guidelines.

• Restructuring:

  • Property GeographicPosition.default is transformed into a new property defaultPosition on class Address.

Version: 1.0.0