Openrailwaymap

openrailwaymap@openrailwaymap.org

306 discussions

Re: Elektrische Streckentrennung
by Björn Mahrt 19 Jun '22

19 Jun '22

Moin, in dem Fall geht es um das Orientierungszeichen "elektrische Streckentrennung" (s. z.B. hier zu sehen http://www.tf-ausbildung.de/SignalbuchOnline/streckentrennungsschild.htm). Es steht als oschon im Signalbuch, ist aber kein Signal; und im Gegensatz zu den El-Signalen, die weit vebreitet gemappt sind, gibt es da noch kein Tagging für. Beste Grüße Björn Am 19.06.22 um 19:13 schrieb Michael Kellerhoff: > Moin Björn, > moin Michael, > > ich nehme an, es geht um die Signale, die unter folgenden Link > beschreiben sind: > http://www.tf-ausbildung.de/SignalbuchOnline/elsignale.htm > > Diese Signale geben dem das Triebfahrzeug führenden Menschen (kurz: TF) > Anweisungen, wie er sich zu verhalten hat: > > Signale: > El 1v: Signal El 1 erwarten. > El 1: Ausschaltsignal > El 2: Einschaltsignal > El 3: "Bügel ab"-Ankündesignal > El 4: "Bügel ab"-Signal > El 5: "Bügel an"-Signal > El 6: Halt für Fahrzeuge mit gehobenen Stromabnehmer > > Der technische Grund sei dabei für den TF egal. > > > In JOSM gibt es eine entsprechende Vorlage: > > > die wie folgt erreichbar ist: > > > Ich hoffe es hilft. > > Viele Grüße > Michael (mikeho) > > > Am 19.06.2022 um 03:15 schrieb Michael Kümmling: >> Hallo Björn, >> >> Am 18.06.22 um 20:23 schrieb Björn Mahrt: >>> Moin, >>> >>> mittlerweile tauchen immer mehr Signale für Beginn/Ende der elektrischen >>> Streckentrennung auf. Bisher konnte ich da noch kein Tagging für finden. >>> >>> Wie ließe sich das sinnvoll umsetzen? >>> >>> railway=signal >>> railway:signal:electricity=DE-ESO:streckentrennung (?) >>> railway:signal:electricity:form=sign >>> railway:signal:electricity:type=begin/end_of_separation (??) Ist das >>> sinnvolles Englisch / trifft das die Bedeutung? >> die englische Übersetzung für Streckentrennung ist insulated overlap. >> >> Viele Grüße >> Micha >> Openrailwaymap mailing list -- openrailwaymap(a)openrailwaymap.org >> To unsubscribe send an email to openrailwaymap-leave(a)openrailwaymap.org >> Archived version of this message: >> https://lists.openrailwaymap.org/mailman3/hyperkitty/list/openrailwaymap@op… >> Archive of this list: >> https://lists.openrailwaymap.org/mailman3/hyperkitty/list/openrailwaymap@op…

4 4

Re: Elektrische Streckentrennung
by Michael Kümmling 19 Jun '22

19 Jun '22

Hallo Michael, Am 19.06.22 um 19:13 schrieb Michael Kellerhoff: > ich nehme an, es geht um die Signale, die unter folgenden Link > beschreiben sind: > http://www.tf-ausbildung.de/SignalbuchOnline/elsignale.htm Nein, es geht um das Orientierungszeichen Elektrische Streckentrennung: https://www.tf-ausbildung.de/SignalbuchOnline/streckentrennungsschild.htm Dafür existiert bisher m.E. kein Tagging. Viele Grüße Micha > > Am 19.06.2022 um 03:15 schrieb Michael Kümmling: >> Hallo Björn, >> >> Am 18.06.22 um 20:23 schrieb Björn Mahrt: >>> Moin, >>> >>> mittlerweile tauchen immer mehr Signale für Beginn/Ende der elektrischen >>> Streckentrennung auf. Bisher konnte ich da noch kein Tagging für finden. >>> >>> Wie ließe sich das sinnvoll umsetzen? >>> >>> railway=signal >>> railway:signal:electricity=DE-ESO:streckentrennung (?) >>> railway:signal:electricity:form=sign >>> railway:signal:electricity:type=begin/end_of_separation (??) Ist das >>> sinnvolles Englisch / trifft das die Bedeutung? >> die englische Übersetzung für Streckentrennung ist insulated overlap. >> >> Viele Grüße >> Micha >> Openrailwaymap mailing list -- openrailwaymap(a)openrailwaymap.org >> To unsubscribe send an email to openrailwaymap-leave(a)openrailwaymap.org >> Archived version of this message: >> https://lists.openrailwaymap.org/mailman3/hyperkitty/list/openrailwaymap@op… >> Archive of this list: >> https://lists.openrailwaymap.org/mailman3/hyperkitty/list/openrailwaymap@op…

1 0

Elektrische Streckentrennung
by Björn Mahrt 19 Jun '22

19 Jun '22

Moin, mittlerweile tauchen immer mehr Signale für Beginn/Ende der elektrischen Streckentrennung auf. Bisher konnte ich da noch kein Tagging für finden. Wie ließe sich das sinnvoll umsetzen? railway=signal railway:signal:electricity=DE-ESO:streckentrennung (?) railway:signal:electricity:form=sign railway:signal:electricity:type=begin/end_of_separation (??) Ist das sinnvolles Englisch / trifft das die Bedeutung? [..] height/position/direction nach Bedarf Gibt es Gegenvorschläge? Viele Grüße Björn

2 1

Spotting
by Natfoot 22 May '22

22 May '22

Hello to the list serve, Do we have a tag for spotting train cars? We have industries in North America that have spotting markers for cars. Thanks Nat P email: natfoot(a)gmail.com

1 0

Experience upgrading from Ubuntu 20.04 LTS to 22.04 LTS
by Jonathan J. Bittner 11 May '22

11 May '22

Recently I upgraded my ORM development VM to Ubuntu 22.04 LTS (Jammy Jellyfish) and thought I'd share some experiences. I'm mostly going from memory here. The supplied version of osm2pgsql is updated and can work with multiple files, e.g. it can import a filtered North America file and filtered Europe file without having to combine the two via osmium. This is a plus Apache/PHP: right off the bat I had an issue with Apache not starting. Apparently the PHP version had updated and I needed to use a2enmod/a2dismod to get the right PHP module enabled which allowed the server to run. Postgres: new version (14) required migration to new database format and then deletion of old database. I think It was pretty seamless as there were commands to handle this, even configuration/tuning parameters were migrated. I might have had to readd user permissions manually. Tirex: version 0.7 is shipped with Jammy. Previously I had downloaded 0.6.3 via github and compiled and built deb packages. This introduced quite a few changes: -the default user is _tirex instead of tirex. I had to chown my tiles directories, grant database permissions, etc. I believe _tirex is created without a home directory so the .pgpass file (if one was needed) cannot be reused -tirex installs as one package, where in the past it had been split between multiple packages. tirex-core, tirex-backend-mapnik, etc. needs to be removed manually. -some of the plugin folders had changed. The new config files are supplied with the .dpkg-dist extension. Compare the files and update accordingly. -the socket file has moved from /var/lib/tirex/ to /run/tirex and the apache tileserver config needs to be updated accordingly -the systemd scripts in /etc were not updated. They needed to be "imported" from /usr/lib via a systemctl enable API/Node.js: Now I've never used the API, not even for search since I didn't have the right indexes in my DB (Thanks Rolf, PR 779) but there were two issues I encountered -there were errors from using an older version of graceful-fs that caused it to error out, something about "primoridials." Update graceful-fs and rebuild -this one I haven' figured out. I'm not a node expert and despise JS. Apparently there have been changes in log4js with setting up the configuration with regard to "appenders." Either we'd need a code change (would that break folks who haven't updated/upgraded) or maybe there's a way to play with package.json to force an older version or something. I have no idea if older versions of the package even work with newer versions of node. If you have an idea, let me know. Otherwise, I haven't noticed any issues with carto or kosmtik. I hope this helps someone else. My best, Jon

1 0

e-layer higher zoom levels not updated for month
by Axel Zöllich 02 Apr '22

02 Apr '22

The higher zoom levels of the electrification layer on openrailwaymap don't get updated since lets say some months. for example: Wesel-Bocholt remains unaltered "under construction" Herzogenrath changes aren't rendered As I don't know how to get the actual zoom level I cannot cite his number.

2 3

Way vs relation rendering conflict AND turntable rendering
by Jonathan J. Bittner 16 Mar '22

16 Mar '22

Topic 1: I had seen some interesting behavior where the name of an abandoned line was rendered even though it was not tagged in the way but was tagged in a relation. I also saw cases where a street was rendered with an abandoned line even though it wasn't tagged on the way but was included in the relation. I've also seen instances in the electrification layer where there's a double render: both the electrification color and a gray line appeared in the same location conflicting. Thirdly I've seen instances where the way and the relation were tagged 'abandoned' and the line showed up as solid rather than dashed. It took me a while to figure out what was going on since I had seen ORM documentation that says we do not render relations. It turns out that the OSM backend turns relations into ways, assigning them a negative osm_id. ORM then renders these ways. Basically, if a relation is tagged railway=construction/abandoned/razed/disused/rail/light_rail/tram/subway, it will render in ORM. There are guidelines that say don't use railway=rail on a relation (https://wiki.openstreetmap.org/wiki/Tag:route%3Drailway). Perhaps they should be expanded. Maybe even a validation rule should be added to the editors. So the question I have is what's the best way to deal with these relations? For some the easiest thing to do is remove the railway tag from the relation. For others, the relation is so large (I saw one last night that was 500+ ways), and not every way is individually tagged that map accuracy would be decreased if the railway tag was removed from the relation. For those cases, it seems easier to de-tag a few ways and let the relation take over. But then if the way ends up being blank, I feel guilty and I then rely on others to not delete it and realize it's part of a relation. I also feel like I'm violating the rule of not tagging just for the sake of the renderer. Thoughts? Are there any guidelines? Topic 2: The ORM renderer will shade in turntables and traversers if and only if they are polygons. Took me a while to figure out why some were rendering (like https://openrailwaymap.org/?style=standard&lat=40.87473288924837&lon=-73.52…) and others weren't. It seems that a "closed way" (group of nodes joined by a line where the starting node is the ending node) isn't automatically a polygon unless certain tags are present. I'm thinking in the above case the tourism=attraction tag may have tripped the above case into a polygon. An area=yes tag will always force the database to create a polygon. So the question is what do we do with all these turntables and traversers that are closed ways and not polygons? -retag with area=yes to force the renderer? I've done this for several but I'm not sure it's the right thing to do -request the OSM Project make a change so that a closed way tagged 'railway'='turntable' is treated as an area when uploaded. Not sure if this is a backend or editor issue. Is this even a backend thing or is it a local database thing? -have ORM render closed ways and areas/polygons. Not sure that's even possible with the rendered. Thanks for reading, Jonathan

1 0

kosmtik users: reference background??
by Jonathan J. Bittner 16 Mar '22

16 Mar '22

I just started doing some ORM development and I'm using kosmtik. While I like it, it's sometimes hard to figure out where you are or more appropriately, where you are trying to go. Some areas I can recognize by geography: single lines on peninsulas, major rail hubs like Chicago or Kansas City, by shape/lines once you know the area, etc. I can also get a permalink from ORM and put the coordinates into the url for kosmtik. However, I was wondering if there was a way to get the ORM background (Mapnik Grayscale) or similar to display behind the renderings from the MML file. There seems to be quite a few additional plugins for kosmtik but it's a bit confusing as to what they do or how they work. I've seen ones that will render side by side or over but not under. Not sure if I'd fully need to render the "world" or if the grayscale tiles could be pulled in from an existing tileserver. Also, did anyone have any luck working with two sessions of kosmtik? I can run a second .mml and specify a different port number, but sometimes, the browser, seeing the same url (despite differing port numbers), caches the tiles and requires a hard refresh to get the correct view. I could probably play around with running the mml files out of a different folder or symlinking them. Thanks, Jonathan

2 4

[Tagging] Feature Proposal - RfC - railway:signal:height
by Rolf Eike Beer 04 Mar '22

04 Mar '22

https://wiki.openstreetmap.org/wiki/Proposed_features/railway:signal:height Simplification for tagging multiple signals at the same pole (i.e. using the same node). Currently the height of every sub-aspect has to be given explicitely, while they are often all the same.

1 0

search doesn't work
by Axel Zöllich 03 Mar '22

03 Mar '22

Searching doesn't find anything at the moment. There is always "Nothing found."

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Openrailwaymap