<div dir="auto">In my view, apps like Organic Maps are one of the biggest opportunities. It should be considered to help fund efforts like this to be an end user oriented app, where the map is consumed, not just editing tools. Imagine achieving something like 5, 10, 20 million daily active users of Organic Maps. People who use the product can naturally give the feedback the builders need.<div dir="auto"><br></div><div dir="auto">Google Maps is good at this: crowdsourcing frequent validation of data because users interact with it, whether reviewing it, getting small prompts to add attributes, or having the chance to report wrong, missing, or outdated data, anonymously, for experienced mappers to fix (a note). </div><div dir="auto"><br></div><div dir="auto">Waze is also very good at this: crowdsourcing while using the data for routing, both actively (reporting dynamic things like construction) and passively (if users all keep avoiding a suggested route, maybe it changed). Waze also has a map editing tool. </div><div dir="auto"><br></div><div dir="auto">I am not sure of the impact of user reports on Mapbox and other tools, but enabling huge numbers of anonymous end users to report data or validate it's existence without anonymously making complex edits, can be a major boost.</div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 14, 2023, 05:32 Mateusz Konieczny via osmf-talk <<a href="mailto:osmf-talk@openstreetmap.org">osmf-talk@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div><br></div><div><br></div><div><br></div><div>May 13, 2023, 22:24 by <a href="mailto:osmf-talk@openstreetmap.org" target="_blank" rel="noreferrer">osmf-talk@openstreetmap.org</a>:<br></div><blockquote style="border-left:1px solid #93a3b8;padding-left:10px;margin-left:5px"><div dir="ltr"><div dir="auto"><div>Truth to be told, generic building=yes already add almost no information <br></div><div dir="auto">at all to the map relevant for data users<br></div></div></div></blockquote><div dir="auto">building=yes geometries are highly useful for orientation. And note that among OSM<br></div><div dir="auto">data consumers vast majority displays all building=* values in the same way,<br></div><div dir="auto">and on maps in general it is quite typical solution.<br></div><blockquote style="border-left:1px solid #93a3b8;padding-left:10px;margin-left:5px"><div dir="ltr"><div dir="auto"><div dir="auto">so at least render then differently (or not render at all) would disencourage <br></div><div dir="auto">low quality armchair mapping<br></div></div></div></blockquote><div dir="auto">mapping accurate building=yes is highly helpful (low quality armchair mapping has<br></div><div dir="auto">dubious or negative utility, but mapping building=yes is not indicator of this - rather<br></div><div dir="auto">inaccurate guessing of building=* value is a bigger problem)<br></div><blockquote style="border-left:1px solid #93a3b8;padding-left:10px;margin-left:5px"><div dir="ltr"><div dir="auto"><div dir="auto"> <br></div></div></div></blockquote><div dir="auto"><br></div> </div>
_______________________________________________<br>
osmf-talk mailing list<br>
<a href="mailto:osmf-talk@openstreetmap.org" target="_blank" rel="noreferrer">osmf-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/osmf-talk" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/osmf-talk</a><br>
</blockquote></div>