handle surface vs tracktype conflicts
ask for confirmation in case where surface mismatches tracktype resurvey in cases where either surface or tracktype is definitely wrong fixes #662 #4063
if accepted in general, I will further refactor it to avoid specifying surface/tracktype relation twice, in two separate places
see also https://josm.openstreetmap.de/ticket/22102 - especially https://josm.openstreetmap.de/ticket/22102#comment:7 that would mirror code here and may have feedback about strength of checks
@FloEdelmann I partially followed your suggestions in https://github.com/streetcomplete/StreetComplete/pull/4105/commits/5be361c8539c12564b404761b1eec67f3d95c29a
draft per
if accepted in general, I will further refactor it to avoid specifying surface/tracktype relation twice, in two separate places
I am now assuming that @westnordost is at least not disliking this idea.
Yes, idea sounds fine. It is still draft though, which is why I did not look at the code.
@matkoniecz very nice refactoring/simplification!