I am working on a sameAs - mapping between LinkedGeoData and GeoNames.
It is very helpful that there is a public SPARQL endpoint for geonames, however spatial data is up to now only encoded via wgs84_pos:lat and wgs84_pos:long. While that describes that position perfectly, the matching approach and the tool I use uses metrics which depend on a pair of properties from each datasource and thus does not work with the position encoded in to different properties. Thus I would like to ask if in addition to wgs84_pos:lat and wgs84_pos:long the position could also be included in a single property using wgs84_pos:geometry.
An example from dbpedia for the city of Leipzig (http://dbpedia.org/resource/Leipzig):
wgs84:geometry * POINT(12.3833 51.3333)
wgs84:lat * 51.333332 (xsd:float)
wgs84:long * 12.383333 (xsd:float)
I don't really like the idea of having to encode the same values in tons of different formats. Can't you make your tools more intelligent to handle this situation more flexibly?
Thanks for the swift reply!
Well the tool is not developed by me but I wrote them an email too, asking them to add handling of values distributed over several properties. If that will not be possible I will probably install my own local SPARQL server and fill it with a geonames dump.