Skip to content

v2.0.0 — Zones carry a GeoSPARQL geometry

Choose a tag to compare

@Miguel2617 Miguel2617 released this 11 Nov 11:59
· 1 commit to master since this release

Zones carry a GeoSPARQL geometry.

A zone and its spatial extent are now two different things. caskbot:Zone is a geo:Feature with caskbot:RestrictedZone and the new caskbot:OperatingZone below it, the extent hangs on the zone through geo:hasGeometry and is a POS:PositionRegion, which the new bridge axiom POS:PositionRegion rdfs:subClassOf geo:Geometry also makes a geo:Geometry. The shape is a WKT literal and carries its coordinate reference system inside the literal. caskbot:zoneAppliesTo states whether a zone holds for a kind of platform or for an individual robot, and caskbot:hasOperatingZone is the counterpart of caskbot:hasRestrictedZone.

Breaking change. Up to 1.25.2 caskbot:RestrictedZone was a subclass of POS:PositionRegion and therefore, through POS:PositionMeasure, a physical quantity. GeoSPARQL declares geo:Feature and geo:Geometry disjoint, so that modelling would have made the import closure inconsistent. Data that typed a zone as a position region has to move the extent into a geo:hasGeometry of its own.

GeoSPARQL 1.1 (OGC 22-047r1) is imported from the OGC repository pinned to commit 0198218, because the version IRI the ontology declares for itself, http://www.opengis.net/ont/geosparql/1.1, does not resolve, and the unversioned IRI serves a catalogue page rather than the axioms.

Verified with HermiT over the full import closure: consistent, no new unsatisfiable classes.