OpenRailwayMap-vector integration#132
Open
hiddewie wants to merge 681 commits intoOpenRailwayMap:masterfrom
Open
OpenRailwayMap-vector integration#132hiddewie wants to merge 681 commits intoOpenRailwayMap:masterfrom
hiddewie wants to merge 681 commits intoOpenRailwayMap:masterfrom
Conversation
Following performance scanning from https://gtmetrix.com/reports/openrailwaymap.app/IynOcHM9/ and Google Lighthouse. Changes: - Put the `<script>` includes in the page head, with `defer`. Execution order is important - Lazy load the banner image - Enable gzip compression on more content types (taken from https://www.digitalocean.com/community/tutorials/how-to-improve-website-performance-using-gzip-and-nginx-on-ubuntu-20-04)
Fixes #476 (http://localhost:8000/#view=19/52.5065983/13.4797794) <img width="1226" height="886" alt="image" src="https://github.com/user-attachments/assets/1c7fe13e-db76-4cac-9745-90e5c185aecf" />
Part of #35 See https://www.bane.dk/Jernbanevirksomhed/Sikkerhed/Trafikale-regler/SR/SR, https://www.bane.dk/da/Jernbanevirksomhed/Sikkerhed/Trafikale-regler/SR/SR/-/media/FF191FAA53244E349DC70B4FABBB9C97.ashx See https://www.lundsten.dk/dk_signaling/dksignal.html See https://qelectronics.de/downloads/signalbuch/signale.denmark.pdf See https://www.bane.dk/Jernbanevirksomhed/Sikkerhed/Trafikale-regler/SR/SR See https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging_in_Denmark
Fixes #494 Followup of #481 Part of #392 Changes: - Match exact positions against non-exact positions. If exact positions do not have a corresponding non-exact position, they are used as is. - Use textual position (not exact position) for determining if a milestone is a zero. (https://openrailwaymap.app/#view=10.39/49.5818/11.4117&style=signals) Before: <img width="1418" height="1110" alt="image" src="https://github.com/user-attachments/assets/2f26bb69-58b7-4545-988c-8c4c82ac613b" /> After: <img width="1417" height="1113" alt="image" src="https://github.com/user-attachments/assets/23e64517-4986-406a-8bf9-db51c51a3b02" />
Part of discussion in #496 (Paris: https://openrailwaymap.app/#view=12.27/48.86185/2.33082&style=signals) Before: <img width="1433" height="1115" alt="image" src="https://github.com/user-attachments/assets/1a2c66b0-76b1-4f1c-9f8a-59c79d7a7e44" /> After: <img width="1433" height="1115" alt="image" src="https://github.com/user-attachments/assets/322bb8a6-aa50-4861-b903-170ebcd4d9ff" />
Part of #35 See https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Signals_in_Italy and discussion on https://wiki.openstreetmap.org/wiki/Talk:OpenRailwayMap/Signals_in_Italy. These signals are also getting tagged in OSM: https://overpass-turbo.eu/s/28Gn. Sources: - https://www.segnalifs.it/sfi/it/sa/2016_segnali.htm - https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Signals_in_Italy - https://web.archive.org/web/20180722011447/http://site.rfi.it/quadroriferimento/files/RS%202018-01-30.pdf
Hi there, I've created and added rendering for PL 6-cell semaphores -> those are tagged similarly to 4- and 5-cell combined signals, but they additionally include `railway:signal:combined:shape=two_column` tag. I've recently updated OSM wiki and semaphores on map (in Radom Wschodni, Gdańsk Główny and Ełk stations) Examples of IRL 6-cell semaphores: http://lighting-gallery.pl/viewtopic.php?f=55&t=1125&start=170#p274717 <img width="1024" height="576" alt="image" src="https://github.com/user-attachments/assets/152420ce-68a9-4773-9cf4-1020ec280689" /> http://lighting-gallery.pl/viewtopic.php?f=55&t=1125&start=170#p275045 <img width="1024" height="575" alt="image" src="https://github.com/user-attachments/assets/0428848d-d42f-453e-8520-9b6ea572789a" /> --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Fixes #503 Import all switches, including those without a `ref`. http://localhost:8000/#view=17.71/50.956407/7.012742 Before: <img width="1434" height="1114" alt="image" src="https://github.com/user-attachments/assets/ef650870-d709-408d-a552-08ce602ff7cb" /> After: <img width="1434" height="1114" alt="image" src="https://github.com/user-attachments/assets/ba5b471a-4f84-4896-9c0b-1ef937332d14" />
Fix the order of the integration test results, which depends on the Berlin OSM data.
There's no "CM" track class and I changed the only occurrence yesterday to the correct one (Value of "CM4" taken from trassenfinder.de). There are also a few other lines in the former GDR that have "CM4" set.
Part of #270 Solution strategy: make the cone larger for high (16+) zooms when the references are visible, such that the reference cannot fully cover the signal cone. Changes: - Large signal cone from zoom 16+ - Lower opacity a bit for signal cone between zooms 13 and 16. Zoom 13-16: signals with small cones and references/captions <img width="872" height="963" alt="Image" src="https://github.com/user-attachments/assets/ff3adb6e-2e41-4186-98f6-e3747cf116a7" /> Zooms 16+: signals with big cones, partially transparent, and references/captions <img width="872" height="963" alt="Image" src="https://github.com/user-attachments/assets/a507698f-c794-4c55-95b0-ebc0a1c9d0c5" />
Fixes #500 This pull request moves the symbols for borders and owner change to the operator layer. In the future, if we like, we could also display a symbol (POI) on multiple layers (e.g. _infrastructure_ and _operator_). For e.g. borders this could be sensible. (http://localhost:8000/#view=16/52.48671/13.373722&style=operator) <img width="909" height="575" alt="image" src="https://github.com/user-attachments/assets/77b382af-70ce-4abd-a6bb-bc351dadd6d3" />
This code/filtering in the style is no longer needed because tiles are available for every zoom level.
Path rewriting for source URLs is no longer needed because everything runs in Docker with the same proxying rules. No tiles with different URLs.
Part of #513 Document and automate the downloading and publishing of filtered OSM planet data.
Part of #35 Followup on #502 Changes: - Combined signals (Segnale accoppiato) - Distant signals with striped pole - A few route signals (numbers 1 to 4), and put them below main/combined signals - Avvio and avanzamento on main and departure signals - State handling for main, distant and combined signals. Main problem is now the number of combinations of tags on the main signals. Shape and arrow cannot be taken into account yet, and there are already 12 combinations of main signal icons. Maybe we need to make some way so compose SVG icons from components based on tags. See https://en.wikipedia.org/wiki/Italian_railway_signalling and https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Signals_in_Italy
Renders [`railway=hirail_access`](https://osm.wiki/Tag:railway=hirail_access) using the same icon as [`railway=rolling_highway`](https://osm.wiki/Tag:railway=rolling_highway)
Finland has a classification system that differs from the EN 15528. I've added the missing classes for rendering. This is not an ideal solution because there is overlap with existing class codes and their colours might not be very distinctive, but maybe this will be just fine. Documented here: https://wiki.openstreetmap.org/wiki/Key:railway:track_class
This adds Junakulunvalvonta (JKV) train protection system used in Finland. It is currently mapped as **railway:jkv=yes** on lines equipped with JKV and **railway:jkv=no** for unprotected lines respectively. Note that the system itself is technically EBICAB 900 but only few lines have been retagged to railway:ebicab=900, so I've reused the pink colour to facilitate possible retagging. Documented here: https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging#Train_protection_systems --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
See https://github.com/maplibre/maplibre-gl-js/releases/tag/v5.7.0 and https://github.com/maplibre/maplibre-gl-js/releases/tag/v5.7.1 Two issues related to `global-state` are solved (maplibre/maplibre-gl-js#6209, maplibre/maplibre-gl-js#6301), which unblocks using global-state for theme coloring and more dynamic styles while reducing duplication.
Add a fallback for signals boxes that have no name to show the reference instead. (http://localhost:8000/#view=17.38/61.509956/23.681484&style=signals) <img width="1296" height="820" alt="image" src="https://github.com/user-attachments/assets/fe0380f5-96b6-4ec0-af55-1ec749bbd865" />
svg icon file refers to italian christmas tree crossing signal. The tag should be set accondigly. Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
<img width="1072" height="229" alt="image" src="https://github.com/user-attachments/assets/dede7aa1-a97b-4514-b800-b123d6ff6867" /> <img width="1287" height="701" alt="image" src="https://github.com/user-attachments/assets/522cd2ae-5358-4796-91bb-6249c40ca399" /> <img width="660" height="675" alt="image" src="https://github.com/user-attachments/assets/30947b58-e425-48de-be36-1ab1f33c4dc4" /> <img width="660" height="675" alt="image" src="https://github.com/user-attachments/assets/33e9d5c9-687a-4056-aede-0077dd9b6803" /> --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Adds [whistle boards](https://www.railsigns.uk/sect15page1.html) to signals for GB. `whistle-board.svg` and `whistle-stencil.svg` are compliant to the standard save as to typeface (very close approximation). `whistle-continuous.svg` is not drawn from a standard. Photos of board and continuous can be found [here](https://www.railsigns.uk/photos/p_whistle1.html#pic_wboard). Note: I think that no `tags:` section is needed because otherwise it'd just be duplicating tags unnecessarily in the data. If this is technologically impossible please inform me and I will change as needed to implement this. --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
…ist (#535) many light rail/tram networks are mapped with `oneway=*` instead of `railway:preferred_direction=*`. It's trivial to support both tags Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Fixes #519 Implement the Italian PL sign instead of the almost unused ungarded crossing sign. There are currently no signals tagged with `railway:signal:crossing = IT:PL` yet.
Fixes #514 This pull request removes the importing of multi-line signal references, and all extra logic in the map style to render Blockkennzeichen with text on icons. The different-sized icons are also removed.
Fixes #520 See wiki about regime tagging on https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging_in_Belgium#Regime Tested in Brussel (http://localhost:8000/#view=18.43/50.8245989/4.3233201&style=signals): icon is now inverted in opposite regime: <img width="1015" height="824" alt="image" src="https://github.com/user-attachments/assets/7e3bf5d6-5759-4585-9e46-c97679ec2189" />
added ~~`ctc` ([enwiki](https://en.wikipedia.org/wiki/Centralized_traffic_control), [osmwiki](https://osm.wiki/Key:railway:ctc))~~ and `twc` ([enwiki](https://en.wikipedia.org/wiki/Track_Warrant_Control), [osmwiki](https://osm.wiki/Key:railway:twc)) p.s. would you accept a PR to autogenerate `taginfo.json` based on the values in the yaml files? Currently nothing in `train_protection.yaml` is documented in `taginfo.json` Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
Part of #441 Fixes #819 Import of references. They are the references with 200 or more usages worldwide from the list in #441 (comment). Implementation: store all references in a hash in the stations table, to ensure they can be searched generally. The station popup shows all station references, sorted by importance (order in the definition list). Search searches all known references, and the search results show the references next to the station names. The search option for UIC reference has been removed because it is automatically included in the reference search. The references are exported in the Taginfo output as well.
Part of #441. Import station references for stop areas, and render them in the popup for grouped stations. For example Malmö C, https://www.openstreetmap.org/node/25589138. with stop area https://www.openstreetmap.org/relation/2556732, where the Swedish community tag the Rikshållplats. <img width="704" height="741" alt="image" src="https://github.com/user-attachments/assets/58ff5220-04b1-4140-b1f0-6e687175f619" /> Search includes stop areas: <img width="898" height="450" alt="image" src="https://github.com/user-attachments/assets/25366026-9ba1-4e77-bf92-a0db04321442" />
This improves two German tram signals as part of #811. ### Departure signals A 1 / A 2 Currently, at departure signals ([documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Abfertigungssignale_(A))) which can show both the A 1 and A 2 aspect, only the A 2 one is rendered. This PR fixes that. #### Example ([12377252458](https://www.openstreetmap.org/node/12377252458)) <img width="442" height="472" alt="Screenshot 2026-03-01 162702" src="https://github.com/user-attachments/assets/d1f01920-6eab-4e53-a862-839f52f97d09" /> ### Fahrsignal The Fahrsignal `DE-BOStrab:f` ([documentation](https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging_Trams_in_Germany#Fahrsignale_(F))) has two problems at the moment: * The F 0 aspect is not rendered. Instead, every Fahrsignal has an additional "empty" signal light. I don't know whether this was an intentional choice, but (as noted in #811) this makes it impossible to distinguish (rare) signals without an F 0 aspect. * Signals where the states are not explicitly tagged are not rendered at all. There is a `tram Fahrsignal (unknown)` in the signal specification, but this is never reached as these signals also match the section above. This PR makes the following changes: * The F 0 aspect is rendered when tagged. * The rendering of the additional "empty" signal light is removed. * Instead, an additional empty light is rendered if there are further, untagged aspects (indicated by a `?` in `railway:signal:main:states`). This allows to visually distinguish signals which are tagged completely from those which are not. It also ensures that (as before) no signals are rendered with only one light, as this looks not nice – except for the case where there really is only one light on the ground (see example). * Signals without any tagged states are now rendered, as the "normal" Fahrsignal now matches only to those signals where at least one state has been tagged. * For this case, I replaced the previous symbol `de/bostrab/f-unknown` (traffic light showing a question mark) by `de/bostrab/f0-old` (traffic light showing F 0). I think this is better since it allows to visually recognize the signal as a Fahrsignal (as opposed to e.g. a switch signal which also "looks like a traffic light"). There are several hundred Fahrsignale without tagged states. Almost every Fahrsignal has an F 0 aspect, which is also why F 0 was the default icon for the Fahrsignal before the more detailed rendering was introduced. #### Examples (before/after) typical case ([13015719193](https://www.openstreetmap.org/node/13015719193)) <img width="210" height="198" alt="Screenshot 2026-03-01 165253" src="https://github.com/user-attachments/assets/564be6bd-204f-4010-81b5-305ae7255d83" /><img width="205" height="197" alt="Screenshot 2026-03-01 165304" src="https://github.com/user-attachments/assets/11d16675-38a6-45c2-aec5-c932ec61a092" /> without specified states ([10963864069](https://www.openstreetmap.org/node/10963864069)) <img width="313" height="284" alt="Screenshot 2026-03-01 162616" src="https://github.com/user-attachments/assets/0b48a8b2-c24e-43ca-8352-39d7c9e08bc3" /><img width="299" height="268" alt="Screenshot 2026-03-01 162627" src="https://github.com/user-attachments/assets/7187b65f-797c-4358-b127-946075e96858" /> without F 0 state ([13015719198](https://www.openstreetmap.org/node/13015719198)) <img width="226" height="194" alt="Screenshot 2026-03-01 165147" src="https://github.com/user-attachments/assets/d2d9af1f-4715-4e5c-b2d2-8dfff03c74ce" /><img width="201" height="174" alt="Screenshot 2026-03-01 165153" src="https://github.com/user-attachments/assets/5e8f25a9-03ad-421a-ba46-1e9dd8a0c82f" /> with additional `?` states (on the left, [13449257639](https://www.openstreetmap.org/node/13449257639)) <img width="205" height="174" alt="Screenshot 2026-03-01 165945" src="https://github.com/user-attachments/assets/d33f4c5f-7738-4a96-b08f-908e6fd70234" /><img width="202" height="176" alt="Screenshot 2026-03-01 165959" src="https://github.com/user-attachments/assets/33eff484-1b38-423b-910d-e245abe75388" />
This is a regression from #832, noticed in #832 (comment). The variable `value` was overwritten by the formatted key/value pairs in the body of the popup items. After this pull request <img width="642" height="382" alt="image" src="https://github.com/user-attachments/assets/7446e820-2aef-42af-85b3-8e9b0b02a34a" />
This adds a symbol for unknown slope signals (in grey like other low priority signals). Before/after ([1504400550](https://www.openstreetmap.org/node/1504400550)): <img width="186" height="147" alt="Screenshot 2026-03-10 125728" src="https://github.com/user-attachments/assets/bc4c3000-99f7-4673-aa0e-e68710ab9f90" /> <img width="151" height="127" alt="Screenshot 2026-03-10 130309" src="https://github.com/user-attachments/assets/26e674d7-04ed-4f4d-b347-22f0da6cc418" />
Merge classes "tarcze zaporowe" into one (differentiate by form) - before that, somehow, semaphore minor Tz signals weren't displayed at all (eg. https://openrailwaymap.app/#view=18.73/52.5293808/17.6071616&style=signals) --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
This adds the slope signal for the UK. Documentation: https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging_in_the_United_Kingdom#Gradient_post ### Examples Board shape: [13565427184](https://www.openstreetmap.org/node/13565427184) <img width="237" height="201" alt="Screenshot 2026-03-10 032425" src="https://github.com/user-attachments/assets/6da79927-b000-4c9e-99a0-82c0be31f41b" /> Arms shape: (test only, not yet used in OSM) <img width="219" height="200" alt="Screenshot 2026-03-10 034142" src="https://github.com/user-attachments/assets/c1ef1e2b-ef5d-4ce5-a4b9-5c213ef3c7ea" /> --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
This selects the best image according to [Wikidata rank](https://www.wikidata.org/wiki/Help:Ranking), which is not necessarily the earliest image in the API response. Fixes #849. Also migrates to the REST API endpoint for the flatter, cleaner response structure. --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
See changes on wiki in https://wiki.openstreetmap.org/w/index.php?title=OpenRailwayMap/Tagging_in_Belgium&diff=0&oldid=2948607 Part of #763 Followup on #821 On http://localhost:8000/#view=18.47/50.8828234/4.3905015&style=signals: <img width="1019" height="706" alt="image" src="https://github.com/user-attachments/assets/777a02a0-5af2-4b2f-8f74-ace13bb58963" />
Adds rear clear marker/indicator. Adds engineering stop board (these are used permanently/semi-permanently). Tagging ~~will be~~ added ~~shortly~~ to the wiki. Examples can be found at Reading (rear clear), and Ashford Depot (engineering stop board).
Part of #848 In addition to querying the images from WikiData, we also need to query the WikiMedia Commons API to determine the image file metadata. Example query from WikiMedia Commons: https://www.wikidata.org/w/api.php?action=query&prop=imageinfo&iiprop=extmetadata&titles=File%3aReading_Station_drone_view.jpg&format=json
From discussion in #371 Fixes #858 The proposal in https://wiki.openstreetmap.org/wiki/Proposal:Unified_ETCS_Signals_(railway) has been approved. The result is being documented on https://wiki.openstreetmap.org/wiki/OpenRailwayMap/ETCS_Markers. Now we can implement the proposal 🎉 Tested on the first tagged signals with the new tagging (https://overpass-turbo.eu/s/2mes), for example https://www.openstreetmap.org/node/13649914353: (http://localhost:8000/#view=14.02/50.27029/11.01936&style=signals): <img width="1344" height="649" alt="image" src="https://github.com/user-attachments/assets/462c8a5f-a0c6-47c7-b525-a3c043a0a48a" /> <img width="690" height="1250" alt="image" src="https://github.com/user-attachments/assets/d6479ed3-d3e6-49b9-a2c7-328e264c5da0" />
Fixes #846 This pull request adds the import and rendering of the owner for stations and other facilities. Tested on http://localhost:8000/#view=15/41.66054/-0.90693: <img width="904" height="804" alt="image" src="https://github.com/user-attachments/assets/eb0fcc4e-9c57-40da-8048-1943192503db" />
Fixes #862. The Italian Rappel signals were too squared and the lights were also not rounded off compared to the official specifications. Tested near Padua (http://localhost:8000/#view=17.58/45.41862/11.892345&style=speed). Before: <img width="1427" height="903" alt="image" src="https://github.com/user-attachments/assets/64f51f6a-463a-47a7-b860-05dcac5704cf" /> After: <img width="1427" height="903" alt="image" src="https://github.com/user-attachments/assets/c70b388d-24aa-4508-959e-d95512a7977c" />
From #762 (comment) See https://taginfo.openstreetmap.org/tags/railway%3Actcs=3 and https://taginfo.openstreetmap.org/tags/railway%3Actcs=3D The `3D` tagging is not used anywhere. See https://wiki.openstreetmap.org/wiki/Key%3Arailway%3Actcs for the supported values. The original error was on the wiki https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging#Train_protection_systems: <img width="1339" height="334" alt="image" src="https://github.com/user-attachments/assets/6da0c9a0-2e38-4392-b3ef-41b6b7f076e9" /> Tested on http://localhost:8000/#view=4.08/36.11/110.79&style=signals. Before: <img width="1432" height="992" alt="image" src="https://github.com/user-attachments/assets/19fa9d40-f934-499d-9d2c-0ec0356ae6eb" /> After: <img width="1432" height="992" alt="image" src="https://github.com/user-attachments/assets/8f5b5ecc-3937-4086-a88e-92bab9487d58" /> In the future we could show the different levels of CTCS with different colors, just like ETCS.
The type of rail was taken into account for filtering the legend. The legend only contains `railway = rail` features, so all of the subway and light rail rail features on the map were not shown in the legend because their keys did not match. Tested in http://localhost:8000/#view=15.58/40.736959/-74.164143&style=signals: <img width="1427" height="1110" alt="image" src="https://github.com/user-attachments/assets/e66a9ff2-8a09-46ba-afac-793d59fd7452" />
Hey there, recently I've been adding signals to freight stations (Hrubieszów to be exact) - there a certain subtype of PL W21 (speed limit) signal is present eg. https://www.bazakolejowa.pl/index.php?dzial=stacje&id=10832&ed=0&okno=galeria&photoid=219384 (Hrubieszów LHS). Another station that has them is Dorohusk (not yet edited* - edited recently xd). --------- Co-authored-by: Hidde Wieringa <hidde@hiddewieringa.nl>
* Rename CTCS-0/1 (conventional signaling) per [wiki](https://wiki.openstreetmap.org/wiki/Key:railway:ctcs). ([naming ref](https://www.nra.gov.cn/jglz/sbjg/jgsb/202104/t20210428_199140.shtml)) * Split CTCS-2 and Split-3 with regarding to ETCS compatibility. Relates to #866. Color selection to be refined.
Part of #765 The dark mode currently contains dark colors which have too low contrast. ## Speed layer with high speeds (http://localhost:8000/#view=5.02/34.7/117.1&style=speed) Before: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/9e055d67-c092-485c-9c9a-080c046efc42" /> After: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/f8be404f-ea6e-47bc-879b-f56de75c52b9" /> (http://localhost:8000/#view=9.12/39.9593/116.3937&style=speed) Before: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/a2d88d21-3e1a-4cac-9151-a035103f9bd0" /> After: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/413e5200-3114-4874-841e-1f296216804b" /> ## Catenary portals (http://localhost:8000/#view=16/52.377028/4.909388&style=electrification) <img width="1429" height="636" alt="image" src="https://github.com/user-attachments/assets/6afa4442-e6e0-4dfb-b560-d8ca8ada826e" /> ## Catenary masts (http://localhost:8000/#view=17.17/52.284761/4.683437&style=electrification) <img width="1429" height="781" alt="image" src="https://github.com/user-attachments/assets/79c046fc-9bf3-4126-bc56-afa76e678ac2" /> ## Operators (http://localhost:8000/#view=11.08/51.5113/-0.1356&style=operator) Before: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/8e5bea62-d87c-4bcc-9230-dde59223be69" /> After: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/5143f6e3-efbb-4c03-8eb8-ee450f63e0cb" /> (http://localhost:8000/#view=9.41/51.6605/-0.0527&style=operator) Before: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/2c3dace9-f3a0-4c56-b869-0dd5ac4871e0" /> After: <img width="1429" height="1113" alt="image" src="https://github.com/user-attachments/assets/42ee6b69-4cdd-4fc3-9c9a-7bbf440b8695" />
hi again! there are a few miscellaneous signals for Australia and New Zealand that were forgotten in the Pull Requests last year. This PR adds the missing ones. documentation [here (for AU)](https://osm.wiki/Australian_Tagging_Guidelines/Railway_Signals) and [here (for NZ)](https://osm.wiki/New_Zealand/Railways). i saw someone leaving rude comments about czech signals 😭 but the ones in this PR are uncontroversial, they were discussed on discord and everyone is using them now <img width="127" height="142" alt="image" src="https://github.com/user-attachments/assets/437a011f-2933-4650-9232-7b9bf628c8a3" /> <img width="110" height="86" alt="image" src="https://github.com/user-attachments/assets/318ed96f-845c-4d6e-bd6b-cfb75b90f16c" /> <img width="84" height="106" alt="image" src="https://github.com/user-attachments/assets/5c9d628d-6724-400e-a567-c510eb32dd5f" /> <img width="130" height="151" alt="image" src="https://github.com/user-attachments/assets/aa56f525-5d11-4ea5-82a6-eee61d5552c0" /> <img width="219" height="151" alt="image" src="https://github.com/user-attachments/assets/4b5bd9b0-4179-4e65-b85f-73debb840ff7" /> <img width="143" height="158" alt="image" src="https://github.com/user-attachments/assets/aebab33b-6b01-4693-a8e5-05ddfcf4f372" />
Basic implementation of https://wiki.openstreetmap.org/wiki/JA:OpenRailwayMap/Tagging_in_Japan and https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging_in_Japan#Signals_and_signs. (http://localhost:8000/#view=17.85/36.059343/139.260004&style=signals): <img width="797" height="560" alt="image" src="https://github.com/user-attachments/assets/eee75cff-100b-4e77-be66-9c666d866500" /> (http://localhost:8000/#view=17.84/34.664862/135.550818&style=signals): <img width="797" height="560" alt="image" src="https://github.com/user-attachments/assets/619386c0-7a34-4a55-a7bd-7eb0897841d0" /> (http://localhost:8000/#view=15.95/35.91134/139.480024&style=signals): <img width="797" height="560" alt="image" src="https://github.com/user-attachments/assets/bdd6ff92-37b4-4ef4-b60b-4441e0943dde" /> (http://localhost:8000/#view=18.82/35.9160436/139.4755006&style=signals): <img width="741" height="548" alt="image" src="https://github.com/user-attachments/assets/848cd64b-3099-4c2b-a841-df6263b6e605" /> Distant and main repeated signals are not tagged yet.
Closes #750 Adds support for formatted names of common radio systems. LTE-R (http://localhost:8000/#view=9.38/35.8942/128.7936): <img width="944" height="611" alt="image" src="https://github.com/user-attachments/assets/117c19fa-0152-4487-b2c6-58ad32f45621" /> VIRVE (http://localhost:8000/#view=7.12/65.303/25.735): <img width="944" height="611" alt="image" src="https://github.com/user-attachments/assets/4041b1f3-2bae-4c8d-ad3c-3c9cc8e946de" /> Radio mast with GSM-R (http://localhost:8000/#view=15.57/50.098341/8.757683): <img width="995" height="492" alt="image" src="https://github.com/user-attachments/assets/5a69df6a-8aa6-4808-9cea-b38f8ca9cedb" />
Fixes #863 This pull request adds the emergency phone number to places of interest, like level crossings. The number will become a link in the popup, allowing clicking to dial the number. Example in Italy (http://localhost:8000/#view=16.28/45.74482/11.775616): <img width="670" height="425" alt="image" src="https://github.com/user-attachments/assets/bf0cbff2-c378-485d-bb23-dda6ac09a03f" />
Part of #872 This pull request adds support for considering station names with tags `construction:name`, `proposed:name`, `disused:name`, `preserved:name`, `razed:name` and `abandoned:name` for stations with this state. If such a tag is not present, the `name` tag is still considered, followed by the fallback on the `short_name` tag. Search will also consider these tags. This change does not influence when stations are actually shown on the map. That is still controlled by the user preferences.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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:
openrailwaymap.org?These are open questions, any response is appreciated!