Modify

Opened 11 years ago

Closed 9 years ago

#8925 closed defect (wontfix)

The forward/backward role interpretation error of the relation editor about the route relation for roads

Reported by: Show-ichi Owned by: team
Priority: normal Milestone:
Component: Core Version: tested
Keywords: route relation role forward backward Cc:

Description

The document(http://wiki.openstreetmap.org/wiki/Tag:route%3Droad) is defined that ways in a dual-carriageway (one way per direction) use "forward" for one and "backward" for the other side of the road.
However, in order to display a relation editor appropriately, when direction of a way and the one-way setting direction are the same, it must set to "forward," and when reverse, you have to set to "backward."
This differs from the document clearly and needs correction.

Attachments (0)

Change History (7)

comment:1 by bastiK, 11 years ago

It follows Relations/Routes:

"If a route should only be followed in one direction for some or all of its length, the "role" can indicate this for some or all of the constituent ways. "forward" means the route follows this way only in the direction of the way and "backward" means the route runs only against the direction of the way. Rendered on the cycle map (example)."

Apparently those two wiki pages describe the same member roles, but with completely different meaning. It would be madness to use the current implementation for general route relation and switch to the semantics you suggested for route=road, only.

comment:2 by Show-ichi, 11 years ago

Of course, it is only a case of "route=road" that I propose correction. It is not necessary to change general rule implementation.

comment:3 by bastiK, 11 years ago

The wiki page on routes applies to all values of route=* including route=road. So there is clearly a contradiction to the route=road wiki page. This is not the place to resolve this issue, it should be done on the tagging mailing list, forum...

Anyway, I don't like the idea to assign a completely different meaning to the roles forward/backward depending on the value of the route=* tag. It would be better to choose different role names for different things.

comment:4 by Show-ichi, 11 years ago

If inconsistency is canceled, it will welcome with any solution. However, it is although the present implementation has not consisted with the rule of a general route concerning a dual carriageway.
When oneway directions are the same as direction of all the ways which have described the dual carriageway, one side of ways always become for reverse with direction of a route. The roll of such ways must be "backward" on a general rule.
That is, in route=road, direction of oneway and direction of a route are not necessarily made the same.

comment:5 by Don-vip, 10 years ago

Keywords: route role forward backward added
Summary: The forward/backward roll interpretation error of the relation editor about the route relation for roadsThe forward/backward role interpretation error of the relation editor about the route relation for roads

comment:6 by skyper, 10 years ago

Is this different meaning really the use-case ? In my region also route=road uses the standard meaning.

comment:7 by stoecker, 9 years ago

Resolution: wontfix
Status: newclosed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.