<html><head></head><body>Reading the discussion, I can't help but feel greatful for Edward's effort to ensure good quality. Have a read again on his first post: a lot have already been thought already. Don't give the impression you blame the tool! <br>
Just a feeling, I'm not fond of external IDs in OSM myself. <br>
Yves <br>
<br><br><div class="gmail_quote">Le 7 juin 2017 23:08:28 GMT+02:00, Edward Betts <edward@4angle.com> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I've built a tool for mappers to match things in OSM with Wikidata and add the<br />appropriate wikidata tag to OSM.<br /><br /><a href="https://osm.wikidata.link">https://osm.wikidata.link</a>/<br /><br />Users can search for a administrative area or city, then pick an area to<br />analyse. It works best if mappers pick areas they're familiar with.<br /><br />The matcher can take a few minutes to run. It grabs items from Wikidata and<br />figures out a target set of tags and keys to search for. Then it downloads OSM<br />data and looks for matches. The matching is based on tags and names, currently<br />the wikipedia tags aren't considered.<br /><br />The OSM data is retrieved from the Overpass API, large (more than 1,000 sq km)<br />or dense areas might fail with a timeout error.<br /><br />The results are cached in the system and are available here:<br /><br /><a href="https://osm.wikidata.link/places">https://osm.wikidata.link/places</a><br /><br />Once the matching process is complete the mapper is given a tabbed page with<br />the results. The five tabs are:<br /><br /> Match candidates - things on OSM that might be considered for tagging<br /> Already tagged - matches that are already tagged in OSM<br /> No match - items from Wikidata with no match found in OSM <br /> Wikidata query - the query used to find Wikidata items<br /> Overpass query - the Overpass query to find OSM objects in this area<br /><br />To start tagging the mapper is able to login to OSM via OAuth. Tick boxes will<br />appear next to the likely matches, the mapper can tick the box next to the<br />matches they want to upload, then add a change comment and upload them using<br />their own OSM account. Uploads within an area are combined into a single<br />changeset.<br /><br />If the mapper sees an obviously incorrect match they can use the 'report bad<br />match' option to warn other mappers and provide feedback that I can use to<br />improve the algorithm.<br /><br />This tools doesn't add any new objects to OSM. The only change it makes is<br />adding a wikidata tag to existing things.<br /><br />My approach is to aim for a one-to-one mapping between Wikidata and OSM. If<br />there are two or more things in OSM that look like a Wikidata item then it<br />isn't a good match. This means for example that most road and rail bridges<br />won't be tagged because they are represented as two OSM ways. I might change<br />this at some point.<br /><br />There are occasional duplicates in Wikidata, this tool should spot them and<br />refuse to add wikidata tags until the Wikidata duplicate is resolved.<br /><br />The bug/todo list is here: <a href="https://github.com/EdwardBetts/osm-wikidata/issues">https://github.com/EdwardBetts/osm-wikidata/issues</a><br /><br />Any ideas or suggestions are welcome.</pre></blockquote></div></body></html>