OSDU-Ontology
OSDU-Ontology copied to clipboard
use GeoSPARQL don't invent your own classes
You define a lot of your own classes following GeoJSON, eg
osdu:AnyCrsGeoJSONPoint
osdu:AnyCrsGeoJSONLineString
osdu:AnyCrsGeoJSONPolygon
osdu:AnyCrsGeoJSONMultiPoint
osdu:AnyCrsGeoJSONMultiLineString
osdu:AnyCrsGeoJSONMultiPolygon
osdu:AnyCrsGeoJSONGeometryCollection
osdu:AnyCrsGeoJSONFeature
osdu:AbstractAnyCrsFeatureCollection
osdu:GeoJSONPoint
osdu:GeoJSONLineString
osdu:GeoJSONPolygon
osdu:GeoJSONMultiPoint
osdu:GeoJSONMultiLineString
osdu:GeoJSONMultiPolygon
osdu:GeoJSONGeometryCollection
osdu:GeoJSONFeature
osdu:AbstractFeatureCollection
However, the OGC GeoSPARQL
standard defines how to represent all of this in RDF.
- Geometries are represented as opaque literals with datatypes
gmlLiteral
orwktLiteral
- Any OGC CRS (in the EPSG collection but not only) can be used
- Defines spatial relations such as
geo:ehContains
,geo:rcc8ntpp
(inside),geo:sfContains
- The standard is widely supported by semantic repositories. Upon seeing the special datatypes, they pass the geo data to special components for geospatial indexing.