Skip to content

TrailView parts P9: level crossing equipment #3686

Open

Description

@timohueser

Status: explored

Part of #3651.

Size: M (the feature bake, a contract change, the viewer's kinds)

Problem

Test box B has 232 level crossings of a railway with a road, a service way, a track or a path. The tiles hold them as the kind level-crossing with their barrier, light and saltire tags, but nothing draws them: a rider sees no barrier, no light and no cross at any crossing.

Scope

  • The bake places the equipment at each place where a road, a service way or a track crosses a railway at grade, as point features with a heading; a crossing of a path alone gets none.
  • One set at each approach of the way, on the right of the direction of travel, off the carriageway, before the first rail by a distance from parts.json.
  • The set from the tags of the level-crossing point (the owner's rule of 2026-11-03 for a crossing with no tags): crossing:barrier full, half or double_half: a barrier with a raised arm and a light with a cross; no barrier tag or no, on a road: a light with a cross; on a service way or a track: a cross; crossing:light=yes adds the light.
  • The viewer draws the sets as instances of kinds (builder/web/src/lib/trailview/kinds/, models/).
  • The rails through the road are not in this item (TrailView ground plan GP13: railways and steps: rails, sleepers, rack and cable, platforms, level crossings with gates and lights, step treads #3106).

Depends on

#3678 (the module parts only).

Open questions for the design

  • The kind names and tags of the point features, and the place of their section in specs/trailview-features.md.
  • How the bake finds the approach sides where the OSM point lies off the way or between two tracks.
  • The models: sizes, colours and the detail at distance.

Requirements: none


Generated by Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions