That’s still equating tagging for the renderer and mistagging for the renderer, which is confusing, because it makes it sound like all tagging for the renderer is mistagging for the renderer.

Here is my attempt to explain the situation a bit better:

“Tagging for the renderer” is a phrase commonly used in the OpenStreetMap community to mean specifically the bad practice of using incorrect tags (or otherwise skewing the data) for the map features, so that they show up in the mapper’s renderer of choice. Such tagging goes against the basic good practice principles.

Of course, adding correct data to the map is perfectly fine, even when it is motivated by a desire to make the map look better (e.g. more accurate) in one particular renderer. The phrase has therefore been criticised for being confusing, and it has been suggested that it would be more accurate to speak of “mistagging for the renderer” and “lying to the renderer”. However, “tagging for the renderer” is the most widely used variant.

About the suggestion to rename page: the phrase that people use, for better or worse, is “tagging for the renderer”, even though they mean “lying to the renderer”. The point of the page is to explain what they actually mean.

Precisely. It’s a confusing Wiki page trying to explain a confusing phrase.

There’s nothing wrong with wanting to make pretty maps, or with being motivated by this. But it’s common in some OSM circles, like the community forum, to accuse people of “tagging for the renderer”. When the Wiki page equates “tagging for the renderer” with “lying to the renderer”, then what the page is trying to explain is that when people use that phrase, they’re accusing someone else of knowingly entering bad data.

Auf openstreetmap.org rechts auf Ebenen klicken, dann ganz unten “Hinweise/Fehlermeldungen” aktivieren :-)

Übrigens würde ich solche Fragen in Zukunft besser im Community-Forum stellen: https://community.openstreetmap.org/c/communities/de/56 Da lesen mehr Leute mit! Ich habe deine Frage hier nur zufällig gesehen.

When I make category 2 notes, I put #surveyme in the note text. This allows people only interested category 1 to easily filter them out.

Deduplicating and removing inconsistencies in the information on those pages sounds like a good idea to me, but I would suggest creating a thread in the community forum. You will probably get more comments there than here or on the Wiki discussion page.

@dieterdreist: many peaks have a wikidata tag, the wikidata items for mountains often in turn link to the items for the mountain ranges they are in, and these are organised in a hierarchy :-) so someone who is looking for this data should be able to find it there!

The natural=massif Wiki page is a byproduct of this community forum discussion in German about the topic.

Really interesting analysis, thanks!

That took about 3 days 😅

This sort of thing can be done with Geodesk in a few minutes, though it requires first downloading a planet file or extract and then preprocessing it once (this step takes about half an hour on an SSD for the full planet).

Thanks for the write-up.

I’ve noticed that there are about 800 place=island or place=islet nodes with a GNIS tag, many apparently from the old import, where the same island is also mapped as an area. An example is here: osm.org/node/357581849

I’ve made a MapRoulette challenge, set to non-discoverable for now. I would welcome feedback if any more experienced mappers / MapRouletters have any thoughts on this. https://maproulette.org/challenge/42539/

Great post! I’ve added the tag to Jersey’s Martello towers. Now we just need a tag for the earlier round towers in Jersey that are commonly called Martello towers but precede the “true” ones by two decades… https://www.theislandwiki.org/index.php/Coastal_towers

Re questions 1 and 2: I think it would be great if we had an app to systematically add smoothness data to OSM, if it can be confirmed that the accelerometer measurements correlate well with OSM’s definition of the smoothness tag. This data is missing from many ways and adding it could benefit a lot of users: I know GraphHopper and OSRM already take this tag into account, as do CycleStreets and some Brouter profiles.

StreetComplete has a quest for adding it, but in my experience it’s hard to make the correct decision when walking, because the tag is about movement on wheels. When cycling or driving, you eventually develop an intuitive understanding of how the different values feel. A well working app could average observations (while still making sure that every change is reviewed and attributed to one user), improve objectivity, and help beginners make the decision between similar values.