Extend hasGeometry to allow for GeometryCollections

opengeospatial / ogc-geosparql

Public Repository for the OGC GeoSPARQL Standards Working Group

71 stars 19 forks source link

Extend hasGeometry to allow for GeometryCollections #525

Open nicholascar opened 3 weeks ago

nicholascar commented 3 weeks ago

This PR extends the range of hasGeometry to allow for the union of Geometry and GeometryCollection. This change is requested to allow for more sophisticated representations of the spatiality ofFeatures. Ultimately, this change will allow for a form of fuzzy (uncertain) spatiality by usingGeometry Collectionsof relatedGeometry` objects.

This PR also:

updates the version numbers of GeoSPARQL in this branch from 1.1 to 1.3
fixes some small ASCIIDOC formatting and referencing issues

situx commented 3 days ago

GeoSPARQL Meeting 26th June:

Leave the range of geo:hasGeometry unchanged
Make geo:SpatialObjectCollection subClassOf geo:SpatialObject
Make geo:FeatureCollection subClassOf geo:Feature
Make geo:GeometryCollection subClassOf geo:Geometry

Obversation:

geo.ttl already includes the following statements: geo:SpatialObjectCollection rdfs:subClassOf [ rdf:type owl:Restriction ; owl:allValuesFrom :SpatialObject ; owl:onProperty rdfs:member ; ] ; Similar ones exist for FeatureCollection and GeometryCollection, respectively.

Does that not already solve the problem attempted to be solved by this pull request?