Open CarlaVS opened 2 years ago
An issue with this is that it's not clear from the data that ISO 6709 is used. For machine readability this information would need to be conveyed somewhere.
One simple alternative solution would be to use the Basic Geo Vocabulary which is already in use in BiographySampo. But this is of course not directly compatible with CIDOC CRM.
What about geosparql from OGC? https://en.wikipedia.org/wiki/OGC_GeoSPARQL
geo:hasGeometry _:node1g02elp9ox8232762 .
_:node1g02elp9ox8232762 geo:asWKT "Point ( +016.371690 +048.208199 )"^^geo:wktLiteral;
a sf:Point .
as eg the GND is using it: https://d-nb.info/gnd/4066009-6/about/lds.ttl
Just to note that here: ISO 6709 as mentioned by @CarlaVS and WKT have a different sequence of coordinates. lat long
(ISO 6709) vs long lat
(WKT)
Update: Decided to use Cidoc CRM/ wkt Literal solution. See: https://github.com/InTaVia/source-dataset-conversion/blob/67f2639095225e946388bf3c384758f90814032b/APIS_dataset/apis_conversion_cidoc7.1.1.py .
The order of coordinates is "POINT Longitude Latitude". Be careful and check twice in you code (see comment above).
Example from the current solution:
http://www.intavia.eu/apis/place/3162 a crm:E53_Place ; crm:P168_place_is_defined_by http://www.intavia.eu/apis/spaceprimitive/3162 ; crm:P1_is_identified_by http://www.intavia.eu/apis/placeappellation/3162/Klausenburg, http://www.intavia.eu/apis/placeidentifier/3162 ; owl:sameAs https://apis.acdh.oeaw.ac.at/apis/api/entities/place/3162/, https://sws.geonames.org/681290/ .
http://www.intavia.eu/apis/spaceprimitive/3162 a crm:E94_Space_Primitive ; crm:P168_place_is_defined_by "POINT 23.6 46.76667"^^geo:wktLiteral .
We have coordinates for places in different InTaVia datasets.
My suggestion to serialize them (according to ISO 6709) with the P168 place is defined by property is:
We could also split the lat and long in two values or add the information which one is latitude and longitude. I think in this case the most simple solution is the best one.