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
