Extending GeoSPARQL by defining more vector literal types #16
Description
Official change request: OGC CR 585
OGC Change Request Vector Literal GeoSPARQL
GeoSPARQL currently offers WKT and GML literal types which can be used to encode vector geometries.
However, geospatial data formats are very heterogeneous and a variety of other data formats deserve to be encodable in GeoSPARQL in our opinion.
In the following we list the most likely candidates:
- GeoJSON: Very common throughout the Web (Done as Support GeoJSON literals in GeoSPARQL #1 )
- GeoHash: Common has representations of vector data (Doing as part Support GeoHash literals in GeoSPARQL #428)
- GPX: GPX Format used in GPS trackers
- KML Format by Google (Done as Support KML literals in GeoSPARQL #69 )
- (H)(E)WKB/TWKB: Binary serializations of WKT often used as an internal storage format in databases (Doing as part Support WKB literals in GeoSPARQL #427)
The following formats could be considered, but are in our opinion optional:
- LatLonText: Common format to display points in e.g. Wikidata or OSM
- GeoURI: Defacto standard for mobile phone geo urls
- Geobuf Format
- OSM Format: OSM XML
- Polyshape/EncodedPolyline: Format developed by Google to encode polylines/polyshapes
- SVG: Web standard for graphics in general
- X3D: Standard to visualize 3D geometries
Implementations of most of the described literals can be seen in an extension for rdf4j and an extension for Jena.
and in a proposed ontology here
Possibly, other literal implementations are useful and could be discussed.
The attached PDF provides links to all the dataformat specifications and proposes how literal representations could look like.