-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to serialize coordinates for places #2
Comments
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
as eg the GND is using it: https://d-nb.info/gnd/4066009-6/about/lds.ttl |
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 ; http://www.intavia.eu/apis/spaceprimitive/3162 a crm:E94_Space_Primitive ; |
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.
The text was updated successfully, but these errors were encountered: