Draw distant H/V signals with lower priority than main signals

[besentv]

Right now distant H/V signals take higher priority over their main counterparts, causing main signals with a distant signal attached to be drawn as distant signal, which is wrong, as the main signal is more important.

Example now https://openrailwaymap.fly.dev/#view=16.48/49.470724/10.991369&style=signals

With this fix all signals with a main signal ref, e.g. (N|P|S|R)[1-9]+ are drawn correctly. This matches the old ORM style:

[hiddewie]

Thanks!

[hiddewie]

This got me thing a bit more.

It is possible to have a single node tagged with multiple types of signals, like this example a main and distant signal. This is correct tagging and according to the widely used tagging scheme from https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging.

So it would be better if the database could store a feature per type of signal. Currently this is done only to split "speed" signals, "electrification" signals and "the rest" because these features are shown on different layers. However we should also be able to split every type of feature, e.g. combined, main, distant and all other kinds of signals.

Once we have that, we could render all available features (with some offset) for a single node. It would look somewhat like the physical way signals are put on the metal pole: first main signals, then distant signals, then speed markers, then other additions (like which track the signal belongs to, or many others).

Rendering could work with offsets, rendering the second icon of a node a bit lower than the first icon, such that there is no overlap of the icons belonging to the same node.

--> #187

[besentv]

This got me thing a bit more.

It is possible to have a single node tagged with multiple types of signals, like this example a main and distant signal. This is correct tagging and according to the widely used tagging scheme from https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging.

So it would be better if the database could store a feature per type of signal. Currently this is done only to split "speed" signals, "electrification" signals and "the rest" because these features are shown on different layers. However we should also be able to split every type of feature, e.g. combined, main, distant and all other kinds of signals.

Once we have that, we could render all available features (with some offset) for a single node. It would look somewhat like the physical way signals are put on the metal pole: first main signals, then distant signals, then speed markers, then other additions (like which track the signal belongs to, or many others).

Rendering could work with offsets, rendering the second icon of a node a bit lower than the first icon, such that there is no overlap of the icons belonging to the same node.

--> #187

Looking great. Sorry that I'm not much of a help here. 😅