Opened 16 years ago
Closed 16 years ago
#2172 closed defect (fixed)
[PATCH] ReverseWayTagCorrector's role correction is broken
Reported by: | anonymous | Owned by: | framm |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
Route members with role of forward/backward are sensitive to the direction of a way. So it would be nice to show a warning if the user wants to reverse such a way. This way it should be harder to mess up a route accidentally.
Attachments (1)
Change History (4)
comment:1 by , 16 years ago
by , 16 years ago
Attachment: | reversemember.patch added |
---|
comment:2 by , 16 years ago
Component: | unspecified → Core |
---|---|
Summary: | warn on reversing ways which is a direction sensitive member → [PATCH] ReverseWayTagCorrector's role correction is broken |
Type: | enhancement → defect |
Version: | → latest |
This is actually a bug, the ReverseWayTagCorrector gives the new version of the way to be checked with realEqual, which always fails because the reversed way's node list is in reverse order.
This patch adds the old way as a parameter for TagCorrector, and also changes the PrefixSuffixSwitcher to accept only the supplied prefix as-is (as route relations have only forward or backward as a role).
Ticket #2629 has been marked as a duplicate of this ticket.