Matija Nalis

I agree with @rhhsm about not coloring in `red` such already detail-mapped cases; as it basically _invites users to **lower the OSM data quality**_ (and also _needlessly wastes mapper time_,...

> Just because it is supported by app it does not mean that using this tagging scheme is incorrect. I agree; in hindsight it was bad idea to name this...

I'm not sure if we're talking about same thing, I was thinking more about just **not coloring in _red_ such already-complexly-mapped surfaces in Surface overlay**; not about fixing strange values...

> I am not proposing to do it instead of perfectly valid `surface:lanes` but in addition to it So (if I'm understanding it correctly), e.g. taking the example from the...

OK, I'll give it a go

> It may be worth locking by region but if you're paying for parking in America there's usually some indication of who you're paying So, _"🐿️ **Easily** answerable by **any...

> So, I guess it could be enabled at least in the US for Or perhaps allowed everywhere (but maybe disabled by default)? So users could choose what they prefer,...

> I think simply offering the third option of "multiple/idk" would help highlight lots that need more attention @zyphlar As for that [IDK](https://en.wiktionary.org/wiki/IDK) , every quest in StreetComplete has `Other...

> Surely it couldn't be nearly as spammy as asking for the surface of each road, Yes, it can be much more spammy. I've given example of Zagreb, where over...

> That makes sense, actually, the quest should be _replaced_ by an overlay. While I'd like to have smoothness overlay and would use it sometimes, I must note that I...