Skip to content
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

Open
CarlaVS opened this issue Feb 22, 2022 · 5 comments
Open

How to serialize coordinates for places #2

CarlaVS opened this issue Feb 22, 2022 · 5 comments

Comments

@CarlaVS
Copy link
Collaborator

CarlaVS commented Feb 22, 2022

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:

<https://www.intavia.org/apis/place/3162> a crm:E53_Place ;
    crm:P168_place_is_defined_by "46.76667 23.6" ;

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.

@razz0
Copy link

razz0 commented Feb 22, 2022

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.

@sennierer
Copy link
Member

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

@sennierer
Copy link
Member

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)

@CarlaVS
Copy link
Collaborator Author

CarlaVS commented Aug 11, 2022

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).

@CarlaVS
Copy link
Collaborator Author

CarlaVS commented Aug 11, 2022

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 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants