Modify

Opened 7 years ago

Last modified 3 years ago

#15530 new enhancement

Designated direction for railway tracks

Reported by: Zverikk Owned by: team
Priority: normal Milestone:
Component: Internal preset Version:
Keywords: railway direction Cc:

Description

Oneway tag is not applicable to railway=rail (and others, like railway=subway), because there are no legal obstacles to trains going either way. But usually there is a common direction of travel. Mappers use these tags to specify it:

These tags are used on 61k and 3.5k objects respectively. Could you please add both, ot at least the first one, to presets and the map style? It would help mappers not add oneway=yes on railway tracks and hint at the correct tagging.

Also it'd be great to validate railway+oneway combilation and suggest a better tagging.

Attachments (0)

Change History (10)

comment:1 by Don-vip, 7 years ago

Keywords: railway direction added

comment:2 by Klumbumbus, 7 years ago

Component: Internal mappaint styleInternal preset

comment:3 by Klumbumbus, 7 years ago

Hm, currently there are 88k ways with railway=* + oneway=*, which is more than the 61k ​railway:preferred_direction.
Is there a clear statement from the "railway fraction" of OSM about this tagging topic?

comment:4 by Zverikk, 7 years ago

Yes, oneway is not formally applicable to railways, since trains are not forbidden by law to go in opposing directions. Oneway is a kind of access: think of it as "access:backward=no". For that reason two railway communities — german and russian — invented these two tags to map designated directions of railway tracks.

comment:6 by skyper, 5 years ago

There are several solutions (some might be combined):

  • ignoring oneway for railway
  • using oneway:train=*, oneway:railway=* or similar
  • using access tags train:forward/backward or similar
  • using the proposed railway:preferred_direction=forway/backward/both and ​designated_direction=forward/backward/both

comment:7 by Zverikk, 5 years ago

Why invent new tags for what's already on the map?

in reply to:  7 comment:8 by skyper, 5 years ago

Replying to Zverikk:

Why invent new tags for what's already on the map?

  • What are railway:preferred_direction=forway/backward/both and ​designated_direction=forward/backward/both? New? Not any more I guess.
  • train:forward/backward is mentioned on the wiki page for designated_direction=forward/backward/both and not new.

Current numbers, all only ways:

  1. oneway=* together with railway=*: 98129 keys/oneway?filter=ways#combinations
  2. railway:preferred_direction=*: 77137 keys/railway:preferred_direction?filter=ways
  3. designated_direction=*: 14278 keys/designated_direction?filter=ways

comment:9 by skyper, 4 years ago

Numbers grew over the month but more or less similar for all three tags. I have to admit that I did not check how many of these numbers overlap as tag on the same object and which are combined with highway=*.

railway:preferred_direction=* is covered by the OpenRailway preset.
designated_direction=* might be useful together with conveying, but it is only used sporadically, atm.

comment:10 by skyper, 3 years ago

Just a quick update. railway:preferred_direction=* is now on top compared to oneway=* together with railway=*. designated_direction=* is crowing the least and seems to be used mostly in Eastern Europe, mainly in Russia.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to Zverikk.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


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