Skip to content

Layer redesign: mix-and-match map style #970

@hiddewie

Description

@hiddewie

Consider this issue an overview issue. This is a broad idea.

Child issues/discussions:

There are multiple discussions and issues about showing different kind of data on the map, in one of the layers.

Currently these choices and configurations are bound to a layer. If we add the rendering of the owner of a railway line to the operator layer, the same is not visible/usable in the infrastructure layer.

For example the operator layer currently shows show signal boxes, yet the speed layer does not. If the user wants to view signal boxes in the speed layer this is not possible.

Instead, we could discard the idea of the current layers (map styles), and combine them all into a single map style. This style would become much more configurable, and the map style would be less repetitive. The map elements would become configurable, for example railway lines, signal boxes, stations, signals, etcetera. For each of those elements, we could configure the map to show some relevant property of the element. For example railway lines can show their infrastructure type (main, branch, industrial, etcetera), their speed, their train protection. Signals can render main signals, distant signals, combined signals, or any of the other available 40 signal categories. Platforms can render their height, a plain color, or nothing. Switches can be rendered or not.

All of these elements should be configurable, such that the user can mix and match the map to view to their use case and liking.

To keep the current easy functionality of clicking a single button to choose the map view, without complex configuration, we could have "presets" that configure the map using the current layers/styles like infrastructure, speed, train protection, track, operator and routes showing similar things to what is shown today on the map.

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