Thank you Alexandru,
 
So please allow me one more question:
I see the use of dbpprop:longDeg, dbpprop:lonDeg, dbpprop:longD, ....and 
certainly more typos
 
So I understand that this is coming from what you say "people not respecting 
the correct formatting in wikipedia ", si that right ?
 
As it would be useful to know all the typos, is there a place to see all of 
those properties ?
I tried to look for them in the ontologies files available here [1], but with 
no success
 
I bet that SPARQLing the end-point and doing string match to properties 
starting with "dbpprop:lon" is maybe my best chance ?
 
Thank you
Fabian
 
[1] http://wiki.dbpedia.org/Ontology?v=194q

>>> Alexandru Todor <to...@inf.fu-berlin.de> 28.04.2015 16:30 >>>
Hi Fabian,

The dbpprop properties come directly from the infoboxes and are 1:1 
extractions. The geo properties are the results of the infobox mappings to the 
geo ontology. In many cases the mappings don't work right due to people not 
respecting the correct formatting in wikipedia or the mappings not being 
created yet, that's why we keep the dbpprop properties too.

So, to answer your question, use the geo: properties for geo coordinates. Use 
the dbpprop properties if a resource doesn't have geo properties, this means 
that the mappings haven't been made for that infobox yet. In this case you 
"could" also create the corresponding mappings.

Hope this helps.

Cheers,
Alexandru

On Tue, Apr 28, 2015 at 2:55 PM, Fabian Cretton <fabian.cret...@hevs.ch> wrote:


Hi,
It seems different properties are used for geo data, as already pointed out in 
2009 [1]
dbpprop:latDeg, latMin, latSec etc. 
geo:lat, geo:long 
dbpprop:latLong 
Is there any documentation about those properties, and when to expect which one 
?
When SPARQLing about a resource to find out if that resource does have a 
geolocation or not, should all properties be queried (OPTIONAL), and if one of 
them is found we can assume it is the one to use - no need to check about the 
other ones ?
Thank you for any information
Fabian
[1] http://comments.gmane.org/gmane.comp.web.semantic.dbpedia.general/931

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Dbpedia-discussion mailing list
Dbpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion



------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Dbpedia-discussion mailing list
Dbpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to