[Monitor] Suggestions for improving reporting and reference management

[StC-OSM]

After a few weeks of using the Monitor function on various types of routes, I have acquired the perception that there are different use cases and that the current implementation favors some over others.

Some example use cases: 1- I have an "absolute reference" gpx and I want to make sure that the OSM route never deviates from it. 2- I have a reference gpx that I use as a source and I want to monitor progress in mapping it in OSM 3- I want to review all evolutions of an OSM route and decide which are errors and which are improvements 4- I want to monitor two OSM routes that are supposed to have the same geometry

Currently I cannot mix these use cases, and use case #3 is difficult (changing reference requires cheating with dates). My suggestions would be to:

• group towards the left of the table all information that relates to the current OSM relation (ID, segments, length, etc)
• allow multiple references, either by having a variable number of columns depending on each line, or by displaying a synthetic diagnostic in the table and listing detailed results (comparison to all references) in a per-route page, e.g the map page.
• provide a way to edit references : upload a new GPX, take a new snapshot, etc.

Keep up the good work!

[vmarc]

See also: #354.