<html><head></head><body>Yeah this is probably not the best route forward, given that wikidata is so big and contains a lot of osm unrelated data.<br><br><div class="gmail_quote">James <james2432@gmail.com> skrev: (9 augusti 2020 14:31:57 CEST)<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="auto">and if the solution is to download the data then download wikidata, it's even more clunky than the name tag itself</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun., Aug. 9, 2020, 8:29 a.m. Jeremy Harris, <<a href="mailto:jgh@wizmail.org">jgh@wizmail.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 09/08/2020 09:25, pangoSE wrote:<br>
> I suggest we create a roadmap for deprecating of storing and updating names in OSM for objects with a Wikidata tag.<br>
<br>
> Substantial changes will have to be made:<br>
> * nominatim will need to support fetching names from wikidata somehow. It could probably be done on the fly.<br>
> * <a href="http://openstreetmap.org" rel="noreferrer noreferrer" target="_blank">openstreetmap.org</a> will need to fetch from wikidata when displaying any object. <br>
> * rendering the standard map will have to support fetching from wikidata.<br>
<br>
How would that work for an offline renderer?<br>
Not everyone has, or wants to have, their phone connected 24/7.<br>
-- <br>
Cheers,<br>
Jeremy<br>
<br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank" rel="noreferrer">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br>
</blockquote></div>
</blockquote></div></body></html>