[Monitor] "Ignore" method for reported differences

[pelderson]

Many (but not all) small differences and some bigger differences are to be ignored, or ignored until further notice. I think a mechanism to indicate that a difference is to be ignored, would be required for active maintenance/follow-up. Because many differences will never be solved (the operator's GIS just handles things differently) and some differences require time to explore and/or to correct things in the real world. Some take minutes, some take months, some are never solved and we have to live with it.
The "Ignore this difference" setting should hold until the reference is changed. I think it should be valid for all monitor users for the route.

I know it's a challenge - because the actual OSM route can change any time. Maybe the mechanism could be available only in combination with a Freeze mode, i.e. the OSM-route does not refresh unless the user hits the Reload OSM button (or changes the reference).

[hgcvm]

I think you talk about two types of issues that can be ignored?

1. Ignored because they are minor differences and will / can never be solved (for example bad GPS reception by person walking route and creating GPX)
2. Ignored for now because it will take time to solve.

For nr.1, I have a dirty hack. I solve all issues possible untill I think OSM and the GPX are 100% in sync, except for those small and insignificant differences. Then I download the OSM GPX through waymarked trails and upload that as a reference GPX (or you can actually set an osm relation from specific date as reference).

For nr.2, I leave those open. Even if it takes time to survey in the real world, I don't think they should be ignored.