Requirements identified after the first release of LOCN about core-location-vocabulary

[makxdekkers]

Issues to be considered in the context of the next major semantic release.

[GeertThijs]

@andrea-perego Specifying spatial / temporal reference systems: That kind of info is explicitly embedded in geometry serialisations like gml or wkt and mplicitly in serialisations like geojson (where the spatial reference system is always WGS84). Example of gml with reference system info on the serialisation: <gml:Point srsName=<"http://www.opengis.net/def/crs/EPSG/0/31370"> \n gml:coordinates159555.00,166155.00</gml:coordinates> \n </gml:Point>. The reference system here is Lambert 72, often used in Belgium.

[GeertThijs]

@andrea-perego Specifying spatial coverage with a bbox: This is implicitly covered by locn:Geometry. A bounding box would be a polygon, a centroid a point. So this is only necessary when in a data exchange it is important to single out bounding boxes or centroids from a bunch of generic geometries. Both can be derived ad hoc from any geometry and the use case is more as a query parameter than something that is actually exchanged between two parties.

[EmidioStani]

In agreement with the observations of @GeertThijs, this can be closed