Model documentation simon #1
Conversation
| Sites, site visits, samplings and observations can use the TERN Location Alignment vocabulary, which is a minimal ontology to tie together the GeoSPARQL vocabulary and the W3C Basic Geo WGS84 vocabulary. | ||
| TERN Location Alignment also defines a specialised Point class with properties to express the depth and elevation. | ||
| LineString and Polygon are also specialised to denote that a WKT literal is required. | ||
| Sites, site visits, samplings and observations can use the TERN Location Alignment vocabulary, which is a minimal ontology to tie together the GeoSPARQL vocabulary and the W3C Basic Geo WGS84 vocabulary. See https://w3id.org/tern/ontologies/loc. |
There was a problem hiding this comment.
My general recommendation is to use GeoSPARQL and WKT as much as possible. LOC gives the alternative of addresses or locations denoted by some text string, but in practice I think we will usually have coordinate-based geometries?
There was a problem hiding this comment.
LOC gives the alternative of addresses or locations denoted by some text string
tern-loc:Point basically defines a few constraints to require wgs:lat, wgs:long and geosparql:asWKT.
Not sure if we are looking at the same thing. I don't see any references to addresses or locations denoted by text string.
These are the current geometries defined in tern-loc for use with the TERN Ontology.
but in practice I think we will usually have coordinate-based geometries?
Currently the 3 geometries defined in tern-loc all require a wktLiteral to represent the geometry.
There was a problem hiding this comment.
I was incorrect. I had not looked property at tern-loc - I had conflated it with https://www.w3.org/ns/locn
|
Thanks @dr-shorthair, I've resolved the comment relating to |
@dr-shorthair I've made some updates to address your PR in ternaustralia#13.