Proposal:Platform exits

From OpenStreetMap Wiki
(Redirected from Key:exit:carriages:backward)
Jump to navigation Jump to search
Platform exits
Proposal status: Draft (under way)
Proposed by: Kylenz
Tagging: exit:carriages=*
destination:carriages=*
destination:carriages:*=*
destination:*:carriages:*=*
Applies to: node
Definition: Indicates which carriage of a subway/train is closest to the platform exit
Statistics:

Draft started: 2024-02-13
RFC start: 2024-02-13

Rationale

Some train platforms only have an exit on one end of the platform, which means people might need to walk a long distance down the platform if they arrive in the wrong carriage.

exit:carriages=* indicates which carriage of a train is the closest to the exit when arriving at the station, to avoid a long walk down the platform to the exit or elevator.

The type of exit (stairs, escalator, or lift) can also be specified, so that routing software can suggest a different carriage for users who need a wheelchair-accessibile route.

Proposal

The tag works similarly to *:lanes=*. Instead of lanes, each carraiage is separated by a | character, starting from the first carriage that passengers can use at front of the train[1]. Note that this tagging style only works if all trains that use this stop have the same number of carriages.

How to map

The tag(s) should be used on public_transport=stop_position nodes, which should also have a ref=* tag so that data consumers can match the OSM data to an external dataset such as GTFS.

This simplest option is to use yes/no. yes means that an exit is located next to that carriage.

For example, exit:carriages=no|no|yes|yes defines the arangement for a 4-car train. Here, it would be smarter to travel in the last 2 carriages if you want to avoid walking down the platform.

To provide more useful information, you can specify the type of exit instead of using yes. Other values include stairs, escalator, or lift.

For example: exit:carriages=lift;stairs|no|no|no|no|stairs. In this case, it would be smartest to travel in the 1st carriage if you need the lift. If you can use the stairs, then the 1st or 6th carriage would be best to minimise walking time.

no, none, and (blank) can be used interchangably, but no is preferred.

Bidirectional platforms

If a platform supports bidirectional operation, you can use exit:carriages:forward=*, where *:forward=* refers to the direction of the way. If someone reverses the way, editors like iD will automatically flip the *:forward=* or *:backward=* tags so they remain correct.

Examples

Limitations

This tagging system will be too limited for many scenarios. The defintion was written based on how the tag is used in one city.

Destinations

At some (modern) train stations, all exits from a platform lead to the same concourse area, so it doesn't matter what exit you take. In these cases, you don't need this tag.

At other stations, you need to walk to a specific point along the platform to find the right exit. destination:carriages=* can be used to define which exit is closest to each carriage of the train.

Destination tags follow the same system as destination:*:lanes:*=*, except that lanes is replaced with carriages.

Example with destinations


See Also

  • access:carriages=* - if you're forced to use a certain carriage because of the train is too long to fit on the platform.
  • carriage=* - an unrelated mode of transport with a confusingly similar name

Use cases

Usage

Rendering

No

Features/Pages affected

External discussions

Comments

Please comment on the discussion page.

Footnotes

  1. This definition is compatible with the GTFS standard's definition
  2. a blank value is equivilant to no or none