-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add links to locations in wikidata using dct:spatial #42
Comments
We should also do this for values in field 700n=96|97, see #53. As we encounter some problems with looking up Nominatim API and linking to LinkedGeoData, we might rather use Wikidata as default. |
Here is an example search for "Köln" in the wikidata API: Result:
|
I've played around a bit with Wikidata Query. One can quite easily extract the Wikidata subset of all settlements in Northrhine-Westphalia. Here are the classes and properties needed for this:
Queries:
As far as I can see, one can not query this API for labels, thus, to map NWBib spatial albels to Wikidata one has to combine this with other techniques. Proposal: a) Get data for the 6756 wikidata items of query: OR b) Query the "official" Wikidqata API à la |
This is how to get the JSOn data for the wikidata item with ID For example "Cologne": https://www.wikidata.org/wiki/Special:EntityData/Q365.json |
Edge cases and tests (to be amended):
|
Hm. Possible solution could be to store all the wikidata items and query against that data locally to build a concordance list. |
See hbz/nwbib#42. * update test * update flux' (i.e. remove dynamical lookup of OSM)
See hbz/nwbib#42. * update test * update flux' (i.e. remove dynamical lookup of OSM)
See hbz/nwbib#42. * update test * update flux' (i.e. remove dynamical lookup of OSM)
See hbz/nwbib#42. * update test * update flux' (i.e. remove dynamical lookup of OSM)
See hbz/nwbib#42. * update test * update flux' (i.e. remove dynamical lookup of OSM)
See hbz/nwbib#42. * update test * update flux' (i.e. remove dynamical lookup of OSM)
Uses wikidata to link wikidata entities with geo coordinates. Stores the data directly on the resource with property (query "how much resources exist having a field
|
Deployed to staging. |
We should use the "concept URI" for the RDF, e.g. http://www.wikidata.org/entity/Q4094. |
See hbz/nwbib#42#issuecomment-63292242
@acka47 Have a look at the test ntriples at the above commit. Merge it if you're positive with it. |
I leave this issue open for now as we peobably will have to improve the mapping to wikidata. |
Correcting #42 (comment): According to hbz/lobid#91 (comment) the optimum is 250,583. That means that 250,583 - 203,226 = 47,357. |
Now I would like to know how many of the linked Wikidata resources actually have geo coordinates. So, what does the query look like for all resources that have a |
=>135 |
I found an error : All the titles under http://lobid.org/resource?q=Q2176071 should link to http://www.wikidata.org/entity/Q1736878 instead of http://www.wikidata.org/entity/Q2176071 This will probably be correct as soon as we adjust the mapping to wikidata. |
Closing this issue as we already added wikidata data. As already noted, the mapping has to be improved, though. Thus, I created #83 for this. |
As addition to OSM and GeoNames links (see #17), we should also add links to the corresponding wikidata resource to NWBib resources.
The text was updated successfully, but these errors were encountered: