StreetComplete’s maintainers have done a good job of reminding us to adhere to the Unix philosophy (every key does one job well). Everyone wants a StreetComplete quest for their pet tagging scheme, so there’s a good incentive to follow that principle these days. This benefits other preset-centric editors too.

The problems you’re noticing are probably concentrated in older tagging schemes that first arose when most mappers were managing raw tags manually, so brevity was more important than modularity. The community is slowly evolving those tagging schemes as the need arises. The most prominent example of that is probably crossing=*.

The surveillance tagging scheme is pretty old too, but I’m surprised to see it come up as an example of monolithic tagging. For the longest time, we’ve just mapped man_made=surveillance and a few other keys for those who bother. Simple tagging is still possible if you’re using a mainstream editor. If you’re using something like DeFlock, then by all means they can get down in the weeds, just like the specialized editors for street parking, bus routes, and trees. That’s kind of the point of keeping those editors separate.

Love what you’ve done with the fairgrounds! By the way, the thing that spells out “Little Brown Jug” is a classic case for a multilinestring. Now that you know, you’ll see these things everywhere and won’t be able to resist the urge to map them.

I’m not sure that there’s an existing unifying tag for all these concepts. I’ll pile on one more: historic=manor could cover a still-standing plantation house, whether or not it still functions as an estate. (One that I’ve mapped is these days considered just another home; another has a local historical museum inside.)

Hi, you might be interested in this proposed rewrite of a very frequently used template. Among other things, it replaces a gendered icon and prominent gendered parameters with a gender-neutral icon that better fits the wiki’s skin anyways.

Great, that’ll be very useful!