Skip to content

OpenRailwayMap-vector integration#132

Open
hiddewie wants to merge 740 commits into
OpenRailwayMap:masterfrom
hiddewie:master
Open

OpenRailwayMap-vector integration#132
hiddewie wants to merge 740 commits into
OpenRailwayMap:masterfrom
hiddewie:master

Conversation

@hiddewie
Copy link
Copy Markdown
Contributor

@hiddewie hiddewie commented Jun 7, 2025

Hi!

Over the past years I have been working on a fork of the OpenRailwayMap.

The announcement can be found on the OpenRailwayMap mailing list and on the OpenStreetMap community forum.

The fork has several features, and is actively being developed by me and several more contributors:

  • Vector-based data: the map is interactive with e.g. hover and popup showing data details.
  • Map style improvements: station size, state of lines and statons, signal support for many new countries.
  • Visual UI improvements like: configurable background map, map settings and dark mode.
  • Additional layers: loading gauge and track class.
  • Daily data updates for the entire planet.
  • OpenHistoricalMap integration for historical railway infrastructure.

At the moment the fork is hosted on https://openrailwaymap.app using Fly.io. This is purely practical, it could be hosted anywhere else.

This pull request is a starter to discuss:

  • Can we integrate the fork into the Github OpenRailwayMap organization
  • Can we publish the fork on the domain openrailwaymap.org?

These are open questions, any response is appreciated!

hiddewie and others added 29 commits October 4, 2025 15:11
Fixes #554

Documentation in
https://wiki.openstreetmap.org/wiki/Relation:public_transport#public_transport.3Dstop_area_group.

Hannover Hauptbahnhof
(http://localhost:8000/#view=16.12/52.377561/9.743367):
<img width="1155" height="727" alt="image"
src="https://github.com/user-attachments/assets/be8949fa-57f5-474c-b467-6dff9945ad37"
/>

Hamburg (http://localhost:8000/#view=15.2/53.552922/10.008825):
<img width="1155" height="727" alt="image"
src="https://github.com/user-attachments/assets/be7405ba-8cdd-442c-926e-286c54e1642b"
/>

Leipzig (http://localhost:8000/#view=15.71/51.345353/12.382657):
<img width="1155" height="727" alt="image"
src="https://github.com/user-attachments/assets/498cbaa9-4356-46b5-8142-873c8da62eb3"
/>

Magdeburg (http://localhost:8000/#view=17.11/52.13075/11.627597):
<img width="1188" height="879" alt="image"
src="https://github.com/user-attachments/assets/d1762be1-3461-4535-8a21-2fc3a81de3b9"
/>
Fixes #310

The derailer and buffer stop receive a slightly dark red color.

Derailer and buffer stop and their signals will only be visible from
zoom 16.

Tested in
http://localhost:8000/#view=17.39/51.350645/12.394897&style=signals:
<img width="1010" height="700" alt="image"
src="https://github.com/user-attachments/assets/9b8c1b63-00a3-4a7d-9963-1192e47b12dc"
/>
<img width="1010" height="700" alt="image"
src="https://github.com/user-attachments/assets/2a294fc0-81af-4bea-a6a5-d9565ad44a64"
/>
For some reason the halo and hover of the signals became almost black.
For the railway lines and text labels this is fine, but for the signals
a more clear halo is nicer.


(http://localhost:8000/#view=17.22/48.629921/9.343935/-76.9&style=signals):

Before:
<img width="1586" height="381" alt="image"
src="https://github.com/user-attachments/assets/5f68fe35-42d6-4f52-92e3-1c453d3afaf1"
/>


After:
<img width="1586" height="381" alt="image"
src="https://github.com/user-attachments/assets/0f866d28-391c-42a0-b4f9-eff723be59c7"
/>
the Australian community is slowly developping a tagging scheme for
signals, this PR adds [NSW - Sydney
Metro](https://osm.wiki/Australian_Tagging_Guidelines/Railways#NSW_-_Sydney_Metro),
which is the first system with a proper tagging schema.

<img width="300" alt="image"
src="https://github.com/user-attachments/assets/04d9a46e-b267-4af4-b81d-3b3064c4b987"
/>


<img width="400" alt="image"
src="https://github.com/user-attachments/assets/4d34ce8f-ebfc-456a-940e-06cd5d57c82b"
/>

Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Hi, I've (finally) created graphics for tram signs in Poland - some of
them should appear in a short time in OSM database. (AT-3 and AT-4 signs
aren't yet rendered since we still have discussion for slope/incline
signs tagging). The city's default switch signs have no standarisation
in PL legislation thus I've used the `PL-tram:switch_<city>` template.

Wiki:
https://wiki.openstreetmap.org/wiki/Pl:OpenRailwayMap/Tagging_in_Poland/Other_lines#Tramwaje

---------

Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Fixes #594 

This requires the station to have a correctly tagged `stop_area`
relation including both the station and the platforms.

Some stations become rather long, but this should not really be a
problem I think.

(http://localhost:8000/#view=17.8/54.51612/13.638059):
<img width="1130" height="746" alt="image"
src="https://github.com/user-attachments/assets/c5f8a403-00c6-4d51-8929-b0776e22fb7a"
/>

(http://localhost:8000/#view=16.26/53.016288/13.995449):
<img width="1012" height="928" alt="image"
src="https://github.com/user-attachments/assets/0bdb21b7-59cc-4c20-a0be-8592c9faed53"
/>

(http://localhost:8000/#view=16.86/52.498425/13.271625):
<img width="1365" height="709" alt="image"
src="https://github.com/user-attachments/assets/8a3c0b76-73a4-4b45-b52a-e4705f38b89e"
/>

Heidelberger Platz looks great
(http://localhost:8000/#view=16.95/52.479905/13.312576):
<img width="1177" height="1058" alt="image"
src="https://github.com/user-attachments/assets/990c2369-efa8-4d7a-af95-ee9893605c07"
/>
Adds severals well-established signals of the `railway:signal:switch`
category which has not been supported yet.

**Switch signal W 0 through W 14 (general use)**
-
[documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Weichensignale_(W))
(and [for W
0](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Allgemein))
- [440
instances](https://overpass-turbo.eu/?w=%22railway%3Asignal%3Aswitch%22%3D%22DE-BOStrab%3Aw%22+global&R)
in OSM, [example](https://www.openstreetmap.org/node/13097176655)
- Graphics are based on the `BOStrab:f` signal which similarly is
usually a "traffic light" with several signal aspects.

**Switch signal W 14 as a sign**
-
[documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Weichensignale_(W))
- [144
instances](https://overpass-turbo.eu/?w=%22railway%3Asignal%3Aswitch%3Astates%22%3D%22DE-BOStrab%3Aw14%22+global&R)
in OSM, [example](https://www.openstreetmap.org/node/13097176640)

**Switch signals W 0 through W 15 in the city of Karlsruhe**
-
[documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Weichensignale_(W)_2)
- [79
instances](https://overpass-turbo.eu/?w=%22railway%3Asignal%3Aswitch%22%3D%22DE-VBK%3Aw%22+global&R)
in OSM, [example](https://www.openstreetmap.org/node/1481190889)

**Switch distant signal Wv 0/1 in the city of Karlsruhe**
-
[documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Weichenvorr%C3%BCcksignal_(Wv))
- [35
instances](https://overpass-turbo.eu/?w=%22railway%3Asignal%3Aswitch%22%3D%22DE-VBK%3Awv%22+global&R)
in OSM, [example](https://www.openstreetmap.org/node/4121736593)

**Signal contact sign St 1**
-
[documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Signalkontakt_(St_1))
- [130
instances](https://overpass-turbo.eu/?w=%22railway%3Asignal%3Aswitch%22%3D%22DE-BOStrab%3Ast1%22+global&R)
in OSM, [example](https://www.openstreetmap.org/node/1633043598)

**Switch contact sign St 2**
-
[documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Weichenkontakt_(St_2))
- [88
instances](https://overpass-turbo.eu/?w=%22railway%3Asignal%3Aswitch%22%3D%22DE-BOStrab%3Ast2%22+global&R)
in OSM, [example](https://www.openstreetmap.org/node/13097176654)

---------

Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Fixes #599 

Current implementation uses the AWS Terrarium open data set from
https://registry.opendata.aws/terrain-tiles/.

Hillshading is used until zoom 15, after that will become a bit more
blurry.

Default disabled.

TODO:
- [x] Add layers
- [x] Tune parameters for a good look (light and shadow and highlight)
- [x] Check attribution and licencing
- [x] Test with both raster and vector tiles
- [x] Make usage of hillshading optional
- [x] Test with terrain mode (3D) -- will not be added
Corrected description and tagging of distant stop icons

---------

Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
This PR adds all light-rail signals
([osmwiki](https://osm.wiki/Australian_Tagging_Guidelines/Railway_Signals)),
except speed signs and switch signals – I'll add those in a different PR
after there's a conclusion to this thread:
#595 (comment)

<img width="84" height="97" alt="image"
src="https://github.com/user-attachments/assets/3814eddd-0142-4b80-9166-b50f595a7e82"
/>

<img width="138" height="103" alt="image"
src="https://github.com/user-attachments/assets/23b61d10-365e-48fb-9302-5610c1323f50"
/>
<img width="248" height="226" alt="image"
src="https://github.com/user-attachments/assets/55b9e9c0-8873-4b57-9ee9-9ddf30e0597d"
/>
<img width="111" height="297" alt="image"
src="https://github.com/user-attachments/assets/6a68688c-3dbd-4d2d-a31d-0a4c2c621d4b"
/>
<img width="147" height="293" alt="image"
src="https://github.com/user-attachments/assets/54abcd08-941f-4b18-bbfd-353e3cf7c571"
/>
<img width="270" height="311" alt="image"
src="https://github.com/user-attachments/assets/20161d68-4296-4d43-88e7-59daa42ab9ba"
/>
<img width="201" height="286" alt="image"
src="https://github.com/user-attachments/assets/1559ba83-92de-43a7-b168-33dcc26ca27f"
/>
<img width="218" height="330" alt="image"
src="https://github.com/user-attachments/assets/25e5b1b7-d847-4389-8acf-718a6a7159a9"
/>
<img width="1" height="1" alt="image"
src="https://github.com/user-attachments/assets/62423241-3987-4ad5-8cd7-dedef3236ced"
/>

tested
[here](http://localhost:8000/#view=14.89/-33.87949/151.20546&style=signals)
and
[here](http://localhost:8000/#view=13.94/-33.80815/150.99553&style=signals)

the signals look a bit weird, but they are actually oblong-shaped
([photo](https://github.com/user-attachments/assets/62423241-3987-4ad5-8cd7-dedef3236ced))
Fixes #611

During #580 the deactivated got lost for these zoom levels.

(http://localhost:8000/#view=14.73/49.29694/10.58621&style=signals):
<img width="731" height="425" alt="image"
src="https://github.com/user-attachments/assets/f52588c0-f1a9-43f0-b081-e5a179f9a6a5"
/>
Fixes #499

Part of #498 

Import tags of the form `railway:position:exact:LINE`, for example
`railway:position:exact:L124 = 7.721` and `railway:position:exact:L26/5
= 1.489`.

Additionally, the API can search for milestones with a position specific
to a line.

Documentation:
https://wiki.openstreetmap.org/wiki/Key:railway:position:exact

Taginfo:
https://taginfo.openstreetmap.org/search?q=railway%3Aposition%3Aexact.
This is used in China and Belgium (and possibly other countries that I
did not find).

Overpass query of nodes in Belgium using exact positions for lines:
https://overpass-turbo.eu/s/2dSo

Brussels (http://localhost:8000/#view=12.99/50.89768/4.42738):
<img width="1038" height="684" alt="image"
src="https://github.com/user-attachments/assets/20fd60c1-23aa-4a95-a1e5-56d511202ebe"
/>
Fixes #466

Currently only the infrastructure and electrification layers show
disused railway lines.

The other styles do not show them at all.

### Testing

Bielefeld (http://localhost:8000/#view=12.53/52.02747/8.56201)

Infrastructure
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/3f9f3f9c-cfa8-4c3e-b857-cda559b98fbb"
/>

Speed
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/ce156431-30fe-4d99-9674-4255fa3f7af3"
/>

Train protection
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/fd3541ae-69eb-4279-9709-b0c3c3de8278"
/>

Electrification
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/0ea9bb2a-3465-45cd-a467-0b71b7fe169e"
/>

Gauge
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/6bed66a7-a146-4658-8d18-7b64528e01e2"
/>

Loading gauge
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/9eb28c82-a890-4191-996e-a0653b38c2ec"
/>

Track class
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/a199d867-0547-463f-a684-3ebf80e6e7ba"
/>

Operator
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/856e716a-e55b-4484-92f1-6a731b74da75"
/>
Fixes #615

(http://localhost:8000/#view=18.11/50.893004/4.314001):

Before:
<img width="1433" height="852" alt="Image"
src="https://github.com/user-attachments/assets/bbc1dc07-8e57-4a72-a9df-1956f6e5f353"
/>

After:
<img width="1433" height="852" alt="image"
src="https://github.com/user-attachments/assets/aa6148e2-d074-4bad-a410-9386fe1a7407"
/>
Allow configuring whether station references or names should be shown on
zoom levels 5 to 10. For the infrastructure and operator layers.

The default will remain unchanged, showing references which shows many
more labels on the map because the references are only a few characters.

Names will show for the large stations first, then for the smaller
stations. So on low zooms only a few station names of the largest
stations of a country will show.

The station circles will always show (and overlap), and remain
clickable.

Fixes #598 

(http://localhost:8000/#view=5.81/50.671/6.58):
<img width="573" height="490" alt="image"
src="https://github.com/user-attachments/assets/d7eca4b8-c7fd-4f2e-bbe9-e6d4591d2524"
/>

(http://localhost:8000/#view=7.54/50.833/4.928):
<img width="1195" height="880" alt="image"
src="https://github.com/user-attachments/assets/b80e58c4-abbb-44f2-9ba2-1ae36b299a64"
/>

Configuration:
<img width="990" height="397" alt="image"
src="https://github.com/user-attachments/assets/3200fe95-98ad-4b67-8ca4-60f2ddc72147"
/>
Fixes the dwarf version not showing up

<img width="1678" height="673" alt="image"
src="https://github.com/user-attachments/assets/43977e49-3887-4ca0-a7c6-67632a07f877"
/>
<img width="339" height="868" alt="image"
src="https://github.com/user-attachments/assets/6d2f8489-66f8-4b08-a047-3773ee1ebd82"
/>
<img width="339" height="868" alt="image"
src="https://github.com/user-attachments/assets/876a98b1-6d84-4518-ab22-0f7ade2e3248"
/>

Only very few of these still exist on the line between Augsburg and
Donauwörth, so I didn't give them much effort. They are in some sense
very similar to the Ks system, so I used the same logic here.
Fixes #484

Postgres 18 is released:
https://www.postgresql.org/about/news/postgresql-18-released-3142/

PostGIS 3.6 is released:
https://gitea.osgeo.org/postgis/postgis/raw/tag/3.6.0/NEWS

https://hub.docker.com/r/imresamu/postgis/tags

Using the base image `imresamu/postgis:18beta1-3.6.0alpha1-alpine`, the
signal feature generation time goes from >2 minutes to 17 seconds 🎉

~The current tag is a beta (Postgres) + alpha (PostGIS) release, but so
far it looks good.~
see the
[osmwiki](https://osm.wiki/Australian_Tagging_Guidelines/Railway_Signals#NSW_Other_Signs)
page.

Unfortunately many signs have tiny text (the New South Wales system is
dumb...). Because of this, I've used a simplified icon with less text in
a few cases (for example:
[original](https://osm.wiki/File:NSW_Railway_Sign_End_Signalled_Authority.svg)
vs
[icon](https://github.com/k-yle/OpenRailwayMap-vector/blob/922505/symbols/au/nsw/signs/end_signalled_authority.svg))

<img width="136" height="113" alt="Image"
src="https://github.com/user-attachments/assets/d8458273-0c25-4c45-afab-7d7362b71e91"
/>
<img width="96" height="115" alt="Image"
src="https://github.com/user-attachments/assets/a819f1da-da3a-4853-b06b-1d06605031e1"
/>
<img width="141" height="142" alt="Image"
src="https://github.com/user-attachments/assets/2d318b05-ebea-4651-92eb-31fd7e178817"
/>
<img width="117" height="135" alt="Image"
src="https://github.com/user-attachments/assets/a5b83ee5-da82-4b73-940e-476b4bc59ad1"
/>
<br />

<img width="67" height="68" alt="Image"
src="https://github.com/user-attachments/assets/627cd7d8-9c1e-47de-a3e4-dc33edd992c7"
/>

<img width="52" height="64" alt="Image"
src="https://github.com/user-attachments/assets/0214beca-45df-434e-9dc6-49faa38c3316"
/>

<img width="71" height="71" alt="Image"
src="https://github.com/user-attachments/assets/b32cf353-8d27-4726-b6e7-326d2825a070"
/>

<img width="56" height="55" alt="Image"
src="https://github.com/user-attachments/assets/5ac1cd8f-931d-4f42-9af0-350e17733f34"
/>

<img width="53" height="45" alt="Image"
src="https://github.com/user-attachments/assets/76dd72b9-6f84-4cf7-9cd5-1f44c199f2fd"
/>

<img width="75" height="70" alt="Image"
src="https://github.com/user-attachments/assets/2b38b989-7c5c-4ad7-b9c5-5dc6e699e475"
/>

<img width="40" height="26" alt="Image"
src="https://github.com/user-attachments/assets/ac057f44-3e11-410d-86e7-f9ec2ae8969f"
/>

<img width="57" height="49" alt="Image"
src="https://github.com/user-attachments/assets/0f16bbd8-b224-4f1c-9999-6f9ca6418c5f"
/>

<img width="49" height="49" alt="Image"
src="https://github.com/user-attachments/assets/54d56d9c-950c-4c16-9448-c3c9e4d6243f"
/>

<img width="44" height="40" alt="Image"
src="https://github.com/user-attachments/assets/5590c552-eb63-4ca2-bf00-287be7da3420"
/>

<img width="93" height="77" alt="Image"
src="https://github.com/user-attachments/assets/116fcdd0-c05b-4ddf-bfdb-06ec514afec7"
/>

<img width="51" height="53" alt="Image"
src="https://github.com/user-attachments/assets/003af980-837f-4ad2-a515-8a6c02e89a82"
/>

<img width="57" height="62" alt="Image"
src="https://github.com/user-attachments/assets/ea96ee0f-03bb-4694-ad68-66d5bbdefe4e"
/>

Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Closes #498

Add tests for the OpenRailwayMap Lua Osm2psql import script.

Some tests verify the importing logic, giving meaning to OpenStreetMap
tags.

Some tests verify the importing logic, providing a node/way/relation
with certain tags, and verifying the expected rows with values in the
Postgres tables.
This reduces the context which needs to be sent to the Docker daemon for
individual image builds, which speeds up the builds.
Part of #555 

## Approach

Consider the zoom levels 0 up to and including 6.

These zoom levels only show the main and present lines, no historical or
future, nor branch/service lines.

For every layer, the railway lines are grouped in their geometries,
making a single line with the same properties for that layer.

For example, in the infrastructure layer, the lines with the same
reference and high-speed indication are grouped together to form a
single line. That geometry is easier to simplify (remove points close
together).

Layers:
- infrastructure: group by reference, name, highspeed
- speed: group by reference, name, highspeed, speed
- electrification: group by reference, name, electrification state,
voltage, frequency
- gauge: group by reference, name, gauge (only the first if the line has
multiple)
- loading gauge: group by reference, name, loading gauge
- track class: group by reference, name, track class
- operator, group by reference, name, owner, operator

In particular this means that every layer can have slightly different
geometries, and will have different properties. In particular, railway
lines grouped by e.g. speed cannot have a property with e.g. gauge,
because that property is not grouped on. The popup will not show the
properties of the other layers for the low zooms. Also the aggregated
railway lines will not show the OSM links to view/edit a railway line,
because the line can consist of **many** OSM lines. Every layer will
have its own source for the low zoom railway line data because of this.

Technical note: ouputting repeated properties, such as `state:
'present'` and `usage: 'main'` which every low zoom tile has, is no
problem. The tiles are compressed, so repeated values of the same
property consume almost no space.


## Testing

The map view has some small differences because of the grouping of the
railway lines. The lines are smoother and less "thick" where many small
line segments are in OSM data. This improves the map clarity.

In screenshots below: ignore transfered data, only look at loaded data.
On localhost, caching is not enabled.

### Zoom 5

Before (https://openrailwaymap.app/#view=5.9/50.984/6.043):
<img width="1433" height="139" alt="image"
src="https://github.com/user-attachments/assets/ea8a940d-59bd-4f48-a313-772566a1d9a4"
/>
<img width="882" height="491" alt="image"
src="https://github.com/user-attachments/assets/b012bd8d-36e5-4e89-91ef-0b5df1554fb4"
/>
<img width="1433" height="755" alt="image"
src="https://github.com/user-attachments/assets/65dd6ab9-163d-4b54-8e22-c21b4d5eac09"
/>
<img width="1433" height="357" alt="image"
src="https://github.com/user-attachments/assets/0da62783-22ee-4083-8088-0bad4499dcfb"
/>

28 MB of data loaded





After (http://localhost:8000/#view=5.9/50.984/6.043):

<img width="1430" height="122" alt="image"
src="https://github.com/user-attachments/assets/7b86ec54-41f7-40d0-849a-e4afc016dfe2"
/>
<img width="784" height="400" alt="image"
src="https://github.com/user-attachments/assets/7a1f3f36-f0bc-4bed-9024-3a192af2cfe3"
/>
<img width="1433" height="755" alt="image"
src="https://github.com/user-attachments/assets/2c958e64-1df1-4138-8bb4-91a077a69ba2"
/>
<img width="1433" height="357" alt="image"
src="https://github.com/user-attachments/assets/0349be3c-4c9f-4420-92de-7166fb475c4d"
/>


9 MB of data loaded

## Zoom 2

Before (https://openrailwaymap.app/#view=2/54.55/42.19):
<img width="1433" height="753" alt="image"
src="https://github.com/user-attachments/assets/515432cb-0cbb-4637-a9a4-4e7845c6a701"
/>
<img width="1432" height="359" alt="image"
src="https://github.com/user-attachments/assets/a54385d9-a1cb-48ef-b40a-5029c7d53b34"
/>

30 MB of data loaded

After (http://localhost:8000/#view=2/54.55/42.19):
<img width="1433" height="753" alt="image"
src="https://github.com/user-attachments/assets/09cf29b2-b48f-4142-8d17-a18cc3915f65"
/>
<img width="1432" height="359" alt="image"
src="https://github.com/user-attachments/assets/335c363e-ea80-4fed-9022-2cbc2513d7f4"
/>

10.5 MB of data loaded

### Funny detail

Many lines in Russia, middle east, and Asia do not have a reference nor
name. They will all be grouped together and highlighted as a single
(huge) line.
<img width="790" height="619" alt="image"
src="https://github.com/user-attachments/assets/74568672-0ef5-4e70-9b6d-b92940477f77"
/>


## Followups

- Booleans, do not send `false` but only `null` or `true`
hiddewie and others added 30 commits May 3, 2026 16:04
Followup on #908.
Related to #888.

The materialized view openrailwaymap_facilities_for_ref_search already
contains the merged index for reference searching.
<img width="663" height="469" alt="image"
src="https://github.com/user-attachments/assets/ab2d0721-037e-45d5-b547-ca35fc8bbad0"
/>
For #796

Ensure every table has a primary key defined that is natural, based on
OSM type, OSM ID and feature properties.

When this primary key will be used for lookup of features using the API,
the same OSM feature will always keep the same primary key for lookup,
allowing caching the API responses even when the database is
re-imported.

Some tables import a single row per table per OSM object, and only of a
single type. In those cases the OSM id is the primary key, and the OSM
type is implicit.

Some tables import more than a single row per table per OSM object, or
of multiple OSM types. In those cases the the OSM ID and type are
imported in `osm_id` and `osm_type` columns, and the column `id` is the
primary key.

See https://osm2pgsql.org/doc/manual.html#unique-ids

For example, a grouped set of stations will have a persistent ID of
`node-29030440-light_rail-light_rail-halt`, which can then be used in
the API to query the grouped station:
<img width="1329" height="246" alt="image"
src="https://github.com/user-attachments/assets/5368caf2-9682-4a87-905e-d088b37ee911"
/>
For #796.

If the popup content is loading, and the network or API is slow, a
loading icon will be shown.

Anything from 50ms loading time is noticable.

The loading icon is embedded into the CSS, so no further image latency
will occur to show the loading icon.

With simulated network latency of 500ms:
<img width="428" height="250" alt="image"
src="https://github.com/user-attachments/assets/a1bd070f-0773-4cb9-9e34-5bbab0084ce9"
/>
Part of #796

Train protection layer:
<img width="704" height="366" alt="image"
src="https://github.com/user-attachments/assets/d3a9bf84-bad7-47f0-9a46-f7284c1381f9"
/>
<img width="704" height="366" alt="image"
src="https://github.com/user-attachments/assets/d2ddb3f2-2352-44e9-9153-0bf10f1b588e"
/>


Operator layer:
<img width="704" height="366" alt="image"
src="https://github.com/user-attachments/assets/5505f55d-50b8-40ea-85c1-47f71fc4bf5d"
/>
<img width="704" height="366" alt="image"
src="https://github.com/user-attachments/assets/d96acd25-6221-4b76-93bd-8f8fa70e97d5"
/>
For #796 

<img width="961" height="454" alt="image"
src="https://github.com/user-attachments/assets/f196e71a-3b93-417e-9538-45a669ad5149"
/>


http://localhost:8000/#view=18.55/52.615034/13.469823&style=electrification
<img width="1014" height="549" alt="image"
src="https://github.com/user-attachments/assets/f9afe402-d393-47c7-83a4-d8b4a5908358"
/>
For #796 

Clean up and add test for railway positions.
For #796

Includes localized popup content

<img width="1156" height="886" alt="image"
src="https://github.com/user-attachments/assets/c4afa063-97b0-4a01-8e43-f06da53a79c4"
/>
<img width="1495" height="761" alt="image"
src="https://github.com/user-attachments/assets/867ea75a-031d-4b4a-a182-802d7161fcaa"
/>
Closes #811.

This adds the tram signals G 3a, G 5, So 5a, So 11 and So 25 of the city
of Dresden. It further replaces the signals So 11/12 of the city of
Rostock by the more general signals St 23/24 applicable to all of East
Germany, according to a
[change](https://wiki.openstreetmap.org/wiki/DE_talk:OpenRailwayMap/Tagging_Trams_in_Germany#Vorfahrt_(gew%C3%A4hren))
of the wiki documentation.

Thanks to @jonaes for the documentation and preparation!

Signal documentation: [Dresden
signals](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Dresden),
[St
23/24](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#St_23)

There are still open questions in the issue regarding So 11 and So 25
which should be answered before merging.

### Examples
#### G 3a
[10062241384](https://www.openstreetmap.org/node/10062241384)
<img width="220" height="168" alt="Screenshot 2026-03-02 215942"
src="https://github.com/user-attachments/assets/7a43a4d9-1032-463d-b4ba-9a16379ea408"
/>

#### G 5
[13604032234](https://www.openstreetmap.org/node/13604032234)
<img width="212" height="148" alt="Screenshot 2026-03-02 220145"
src="https://github.com/user-attachments/assets/aede1c4b-169d-49f2-9e07-29cabe957295"
/>

#### So 5a
[1703088767](https://www.openstreetmap.org/node/1703088767)
<img width="200" height="175" alt="Screenshot 2026-03-02 220449"
src="https://github.com/user-attachments/assets/22ea1e40-a1f9-4df5-98a1-1a234739e457"
/>

#### So 11
[13604032252](https://www.openstreetmap.org/node/13604032252)
<img width="236" height="208" alt="Screenshot 2026-03-02 223425"
src="https://github.com/user-attachments/assets/b9d536cf-a4d2-46bd-8297-c8314e0751eb"
/>

#### So 25
[9288948889](https://www.openstreetmap.org/node/9288948889)
<img width="318" height="387" alt="Screenshot 2026-03-09 220637"
src="https://github.com/user-attachments/assets/810df7d9-ce10-4fd0-9775-e8d514e912f7"
/>

#### St 23/24
[13604032264](https://www.openstreetmap.org/node/13604032264) (St 23),
[12514198727](https://www.openstreetmap.org/node/12514198727) (St 24)
<img width="244" height="236" alt="Screenshot 2026-03-02 221819"
src="https://github.com/user-attachments/assets/3669c273-a054-4e72-a245-c7bd6bf87768"
/>

[13612313997](https://www.openstreetmap.org/node/13612313997) (St 24
with tram icon),
<img width="165" height="153" alt="Screenshot 2026-03-03 180755"
src="https://github.com/user-attachments/assets/241150a1-8377-422d-93b7-b98edfa2a2ad"
/>

---------

Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
For #796 

When #865 is implemented, the three signal layer views can be merged
into one.

Here is one incredible signal
(https://www.openstreetmap.org/node/5747403095):
<img width="1431" height="1113" alt="image"
src="https://github.com/user-attachments/assets/e82f44d0-d887-4060-8752-0d5fbd0be5e3"
/>

<img width="1033" height="481" alt="image"
src="https://github.com/user-attachments/assets/657e86bc-2b87-4f0e-a161-d99f78a843ec"
/>

<img width="1033" height="481" alt="image"
src="https://github.com/user-attachments/assets/4df91293-58ff-4c35-9687-afc121bc521a"
/>
For #796 

This is the last source to be migrated.

<img width="942" height="608" alt="image"
src="https://github.com/user-attachments/assets/439b20c7-7f3e-4e1a-811c-254e427610fd"
/>
Closes #796 

Some cleanup after all sources have been migrated from tile data to API
for full feature information.
Eisenbahnen und Verkehrsbetriebe Elbe-Weser GmbH
<img width="850" height="693" alt="image"
src="https://github.com/user-attachments/assets/ac51bc57-7c74-413e-8555-425d0cc7abe3"
/>

SWEG Schienenwege (dark blue)
<img width="1248" height="858" alt="image"
src="https://github.com/user-attachments/assets/67f3c924-e3a3-44db-9eb9-4f328f68e100"
/>

Rennsteigbahn GmbH & Co. KG (Note: some of the ways need re-tagging so
it won't immediately exactly look like that)
<img width="677" height="737" alt="image"
src="https://github.com/user-attachments/assets/e8ce4e81-dbee-4797-851f-5117280dd1f8"
/>

BayernBahn Infra
<img width="604" height="792" alt="image"
src="https://github.com/user-attachments/assets/a9d1cb08-77b5-4423-a7f3-255973171cc6"
/>
Related to #945

The OpenHistoricalMap features catalog do not have a view defined, but
should still show the popup from the available properties data.

<img width="951" height="443" alt="image"
src="https://github.com/user-attachments/assets/3d17cc7e-7853-42e7-900f-e1a74ffefab3"
/>
Extracted from work in
#674 by
@MatisseBE

When the map is pitched, 30 degrees or more, directional features such
as signals are shown only for the faced direction.

In the pitched view, signals within 75 degrees of the faced direction
are shown.

The signal direction icon will be hidden in the pitched view, as only
the facing signals are visible on the map.

First render: 
<img width="1433" height="992" alt="image"
src="https://github.com/user-attachments/assets/c6d8f424-2eaa-4b03-8f44-656765d922dd"
/>

Codewise there is quite some duplication in the style, because of the
different layers. using the same kind of data. With #865 that can be
reduced.

TODO:
- [x] signals with both directions
- [x] icons above track when in pitched mode
- [x] direction for buffer stop signals
- [x] legend
This fixes a bug in
#946 (comment)

The pitched style was always rendered not checking if the pitch is
actually > 30 degrees.



## Without pitch (`pitch <= 30`)
**This is fixed by this PR**


http://localhost:8000/#view=17.72/49.987131/14.365661/-137.6&style=signals
This PR | Previously
--- |---
<img width="338" height="855" alt="image"
src="https://github.com/user-attachments/assets/ac623a1b-2340-4001-a71f-8fd836782e6f"
/> | <img width="338" height="855" alt="image"
src="https://github.com/user-attachments/assets/d9b49e3e-9120-49f5-a755-b8d99b9ce432"
/>

Similar changes are also in the other layers with pitching implemented,
e.g. *Electricity* and *Speed*

### With pitch (`pitch > 30`)

**This is not changed by this PR**


http://localhost:8000/#view=17.72/49.987131/14.365661/-139.6/52&style=signals
This PR | Previously
--- |---
<img width="338" height="855" alt="image"
src="https://github.com/user-attachments/assets/324468d4-e093-4904-a084-b4ae05a5c517"
/> | <img width="338" height="855" alt="image"
src="https://github.com/user-attachments/assets/2408fba8-3747-49a0-bb03-4c62a683c3e2"
/>
Solves issue #956 
Fix for a bug in #939

Rendering of non-signal POIs (`power_supply` and
`isolated_track_section`) in the electrification layer was broken in
#939. This PR fixes that.

That PR was partially a preparation for #865 (Merging of signal layers).
Rendering of POIs inside signal layers might need to be reworked again
for #865.



https://localhost:8000/#view=19.19/50.0866823/19.9330909&style=electrification
| Before this fix | After this fix |
| --- | --- |
| <img width="840" height="697" alt="Image"
src="https://github.com/user-attachments/assets/79c5968c-bf6a-4305-82f9-678213085ac7"
/> | <img width="840" height="697" alt="Image"
src="https://github.com/user-attachments/assets/27d75d03-36e0-4fc5-b4af-6669b137e724"
/> |
This indicator is rare, and probably the only blue signal in Germany...
:smile: It tells the driver about the state of the technical blockage
(i.e. Indusi 2000hz magnet) to enter a line with simplified ruleset
(Zugleitbetrieb aka. ZLB). It can either be blue (blockage on) or be
flashing blue (blockage off). It does not indicate a driving permission!
The permission to enter the line is gained via radio.

It looks like this:
<img width="426" height="329" alt="image"
src="https://github.com/user-attachments/assets/9851b857-46ab-4729-9871-abf26e51e691"
/>
(cred: https://youtu.be/aEpg9_NU4Ak?t=1026)

<img width="510" height="476" alt="image"
src="https://github.com/user-attachments/assets/01c36332-daaa-4e01-b5a4-b871cfd1f106"
/>

(cred: https://youtu.be/kwirJdvKAH0?t=2852)

btw: TUZ = technically assisted ZLB
Huge list of functional changes between January and May 2026.

<img width="1430" height="1114" alt="image"
src="https://github.com/user-attachments/assets/45ff1e88-ce19-4457-a1c1-c2927ab54245"
/>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.