Helium314

I just experienced a similar issue, apparently json files got corrupted. This was probably after a system crash that happend just before this issue, there is one empty log file...

Thanks for creating this issue. To make clear why I asked in https://github.com/Helium314/StreetComplete/issues/384: I implemented an Osmose quest in my fork of StreetComplete, which essentially just shows available issues and...

In most cases I found, `surface` was tagged before someone added `surface:lanes[:*]`. But there are some cases where StreetComplete users only tagged one of the surfaces, changed `paved` to one...

Asking for `sidewalk:surface` _is_ already asking smoothness for all sidewalks, be it on a road or on a cycleway. ~Though this case is unclear to me, is it really a...

> Dutch OSM community decided to tag such a path as a cycleway with sidewalk **instead** of a segregated way for cycles and pedestrians So the tagging of the way...

If such duplicate surface tagging is seen as correct, SC smoothness quests for both `sidewalk:surface` and `footway:surface` will certainly be a waste of user's time.

You linked to a way that has `sidewalk:surface` __AND__ `footway:surface` and confirmed that tagging is correct and not duplicate, and then claim it's __EITHER__ `sidewalk:surface` __OR__ `footway:surface`. I really don't...

> Maybe that should be the approach when mapping in foreign countries? The main issue with this approach is that several quests depend on the shop / restaurant /... having...

> (I should make a list of issues solved with this migration for the changelog, it should be quite impressive) Also closed (previously unfixable) issues like #4449 to make the...

> Because I fail to see the functional difference between them As far as I understand `1022-10` allows use with bicycle, while `DE:240` makes use obligatory. But tagging `bicycle=use_sidepath` on...