Comments (8)
Thanks for the explanation and the useful documentation @wetneb. Did not know we can set the columns for matching with P625@lat, P625@lng
Currently a score of 0 is reached when the points are 1km away from each other
As a first step it would be great if this could be tuned by the user since it would vary on the type of dataset. For example, for matching city locations, the centroid could vary from Wikidata by over 5 kms and it still should be ok. For a mountain range this could be 100kms etc.
from openrefine-wikibase.
from openrefine-wikibase.
@planemad ideally i'd prefer not to hard-code this in the reconciliation interface. AFAICT the ideal situation would be that people use the dedicated "precision" field in Wikibase in a meaningful way with regard to the object they are representing. But unfortunately this precision field is not really used yet (it is poorly exposed in the UI and in the SPARQL query service).
from openrefine-wikibase.
Hi @planemad, thanks!
This is already possible to some extent: https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation#comparing-values
The issue is that we are limited by the reconciliation API: it does not let the server return the matching scores for individual properties, only one global matching score per query. However, once the matching is done, it is straightforward to retrieve the coordinates of the matched items (especially with the data extension dialog), and compute the distance in OpenRefine.
I agree the user story you have would be ideal, but it requires some changes on OpenRefine's side (which we should totally consider! it will just take more time to agree on an improved protocol, and so on).
from openrefine-wikibase.
@planemad yes I agree this should be user-defined… but how?
Essentially, the problem we have here is that all the matching heuristics are server-side, while we would need to have some finer control on them client-side, and the reconciliation API does not give any control over that…
from openrefine-wikibase.
@wetneb do you know where the code is that scores matches only upto 1km?
from openrefine-wikibase.
The only idea I can think of is to store a mapping of common instance types and acceptable distance threshold for a match. eg:
- building: 50m
- road: 100m
- airport: 5km
- city: 20km
- river:100km
- country: 200km
- landform: 500km
Tbh, for most general cases 1km would work fine. This is an issue only for features that are bigger than 1km and maybe the use case is too limited.
from openrefine-wikibase.
Closing this, the orignal issue of matching using coordinates is already documented.
Agree that either 'precision' or some other property on Wikidata should indicate to external services how to set a suitable proximity threshold. This is out of scope for this API.
from openrefine-wikibase.
Related Issues (20)
- Document deployment with gunicorn HOT 1
- app uses debug mode in production HOT 3
- Allow exclusion of classes/types from the reconciliation process HOT 1
- Exception caught: java.lang.NullPointerException HOT 10
- Add custom wikibase from WBstack HOT 1
- Some items are not found by reconciliation ... maybe due to a large number of similar items? HOT 2
- Reconcilation fails when specifying type work (Q386724) - sometimes giving 502 response HOT 10
- Differences in results returned with suggest.py and wbsearchentities HOT 2
- "Only the best rank" in "Add columns from reconciled columns" should not output deprecated values
- failed-save error when creating new items on Wikidata HOT 1
- Data extension: sitelinks (Wikidata) are sometimes not shown/extracted, while they do exist
- Occasional error messages in hover popup for Wikidata reconciliation suggestions HOT 1
- Latest Jinja causing Docker build to fail. HOT 2
- Custom manifest and IRI url HOT 1
- Problem setting up service with docker compose HOT 7
- Wikidata reconciliation query/scores when multiple variable on same property and date precision HOT 19
- Should empty properties scores to 0? HOT 4
- Curious response to property proposal request
- Property values being cached for longer than they should HOT 2
- This repository has migrated!
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openrefine-wikibase.