"Route relation contains a gap" validator needs to assume lack of duplicate ways
Description (last modified by )
The validator, when testing route relations, produces the validation error "route relation contains a gap" when the ways in the relations don't connect all the way in their defined order. Since JOSM has the rule of disabling adding of duplicate members to relations, some routes cannot be fixed (within JOSM). However, the validator is perfectly willing to let relations with duplicate ways pass the validation as long as the duplicate ways were already in the server data. This creates an imbalance where the error must be left alone or the user must use another editor for that task.
There are two ways I can think of to make it more fair:
1) Allow adding of duplicate members again, and/or
2) Enhance the validation check so it will forgive the lack of duplicate members in route relations.