Proposal:Between and beside rails
| between and beside rails | |
|---|---|
| Proposal status: | Draft (under way) |
| Proposed by: | TrainTraveller |
| Tagging: | between_rails:surface=*, beside_rails:surface=*, between_rails:embedded=*, beside_rails:embedded=* |
| Applies to: | way 
|
| Definition: | Proposal to describe different areas of a railway track |
| Rendered as: | * |
| Draft started: | 2025-02-28 |
| RFC start: | * |
| Vote end: | * |
Proposal
This proposal introduces a tagging system to specify the surface material between and beside the rails of embedded railway tracks, as well as cases where only certain areas of the track are embedded, in OpenStreetMap. While the existing surface=* and embedded=* tags can describe the overall surface of roads or embedded railway tracks, they do not provide enough granularity to differentiate between areas between the rails and beside the rails. This distinction is crucial for mapping pedestrian accessibility, maintenance, and urban planning.
Currently, there is no standardized way to describe these variations. Some mappers might use a multi-value attribute, such as surface=paving_stones;asphalt, in combination with railway=*, but this does not accurately distinguish between different areas. This proposal presents a structured tagging system that introduces a more refined approach, using specific tags to differentiate between distinct areas of the railway track: between_rails:surface=*, beside_rails:surface=*, between_rails:embedded=*, and beside_rails:embedded=*. These tags enable precise mapping of both the material and embedded status of areas between and beside the rails.
More granular tags for left and right areas: between_rails:left:surface=*, between_rails:right:surface=*, beside_rails:left:surface=*, beside_rails:right:surface=*, between_rails:left:embedded=*, between_rails:right:embedded=*, beside_rails:left:embedded=*, beside_rails:right:embedded=*.
Additionally, this proposal introduces the concept of using the prefixes between_rails:* and beside_rails:* for further railway tagging extensions. These prefixes provide a structured way to apply other attributes relevant to specific areas of railway tracks in the future.
This proposal ensures consistent, clear, and non-redundant tagging while maintaining compatibility with existing mapping practices.
Rationale
1. More Detailed Surface Descriptions:
The surface=* tag alone does not distinguish between different surface materials in railway tracks, particularly when different materials exist between and beside the rails.
2. Improved Mapping Precision:
The new attributes allow mappers to specify details relevant for accessibility, maintenance, and urban design, especially in pedestrian or mixed-traffic zones.
3. Flexibility for Various Rail Types:
Whether for tramways in streets, industrial railways, or rail corridors with mixed materials, the new tagging scheme covers diverse cases.
4. Expandability for Future Tagging Needs:
By defining the prefixes between_rails:* and beside_rails:*, this proposal establishes a framework for future enhancements where specific properties of railway tracks need to be mapped at a more detailed level.
Tagging
The prefix between_rails:* refers to the area enclosed by the rails, while the prefix beside_rails:* covers the area immediately outside of the rails. In this context, between_rails refers only to the two outermost running rails on which train wheels travel and does not include additional rails such as power rails or guiding rails. The areas between_rails and beside_rails are, by definition, separated by the rails in a standard two-rail system.
The boundary of between_rails:left and between_rails:right is not strictly defined. In standard two-rail tracks, it is approximately the middle between the two rails. However, in multi-rail tracks, the boundary may also be defined by the middle rail if it is not positioned exactly in the center.
between_rails:surface=* – Specifies the surface material between the rails of an embedded railway track.
beside_rails:surface=* – Specifies the surface material beside the railway tracks.
between_rails:left:surface=* / between_rails:right:surface=* – Allows tagging different materials on each side of the track center.
beside_rails:left:surface=* / beside_rails:right:surface=* – Allows tagging different materials on each side of the track outside.
If a railway track is embedded in a single material, surface=* alone remains sufficient. These new attributes are necessary only when differentiation is needed.
between_rails:embedded=yes – Specifies that the area between the rails of a railway track is embedded. This tag can be used instead of surface=* when the material itself is not relevant, and only the embedded nature of the rails needs to be recorded.
beside_rails:embedded=yes – Specifies that the area beside the rails of a railway track is embedded, without giving information about the material itself.
Examples
| OSM-tags | Description | Picture |
|---|---|---|
| railway=tram between_rails:surface=paving_stones beside_rails:surface=concrete:plates |
a tram track embedded with paving stones between the rails and concrete plates beside the rails | |
| railway=tram surface=concrete:plates beside_rails:right:surface=asphalt |
a tram track embedded with concrete plates but with asphalt in only one side of the rails | |
| railway=tram between_rails:embedded=no beside_rails:surface=concrete |
a tram track not embedded between the rails but embedded with concrete beside the rails | |
| railway=rail beside_rails:embedded=yes |
an industrial railway track not embedded between the rails but embedded directly beside both rails |
Compatibility with Existing Data
This proposal does not alter the usage or values of surface=* or embedded=* where a uniform surface applies.
Mappers can continue using surface=* or embedded=* for general cases, while the new tags provide additional specificity when needed.
See Also
Discussion
Please share your feedback or comments on this proposal in the discussion page.
Voting
Voting will start in April 2025 at the earliest. Supporters are invited until then to contribute examples or photos, if they want.