[Osmf-talk] Question to board members
osm at tobias-knerr.de
Fri Aug 24 14:44:11 UTC 2012
On 24.08.2012 00:30, Jaakko Helleranta.com wrote:
> There will be less and less people who are interested to continue to
> contribute to something that they (as "Sunday mappers") won't see. ..
> But it _does_
> matter if shop=mattress doesn't show up (an example pulled out of my
> hat). It would matter to the random mapper that didn't get the reward,
> it would matter to the shopowner/manager that see it in/on OSM but has
> seen in in Google Maps for years, it matters to OSM as a project because
> people are not getting server. It wouldn't matter to Garmin navigator
> only -users or other "taylored-systems" users that would see it -- but
> that's a minority.
You have mentioned it in passing, but I think it deserves emphasis that
"It's not on osm.org" doesn't mean "a Sunday mapper won't see it". A
mapper might well start to contribute to OSM in the first place because
they use OSM-based routing apps on their smartphone, because their
favourite website includes a specialist OSM rendering, or because their
flight sim uses OSM-based scenery. So there are other places to see the
fruits of their labour besides osm.org.
I'm not saying that it wouldn't be useful to show more stuff on OSM.org
- in fact I would very much support a z19 or even z20 if we can afford
it, as well as showing every shop=* on these zoom levels with some
default icon, and implementing that Top Ten Task #6, "Clickable POIs on
However, with all that talk about improvements to osm.org, we should not
forget that the ability to creatively use OSM data elsewhere is a major
feature of OSM and one of the main differences compared with proprietary
crowdsourcing efforts. Thus, our strategy should include supporting the
creation of OSM-based applications and specialist styles, as well as
making users of these products aware of the possibility to contribute to
OSM and encouraging them to do so.
Imo, if a majority of the people who encounter an OSM product only ever
do so on osm.org, we have done something wrong.
More information about the osmf-talk