[patch] Warn about floating railway switches and crossings

[Famlam]

Crossings of two railways (railway=railway_crossing) and railway switches (railway=switch) by definition cannot exist as isolated nodes without any "underlying" (former) (rail)way that they're part of. Likely they're forgotten remains of now-deleted railways. Especially railway=switch seems pretty common to be remaining (already 130 in NL+BE+DE only); a 'floating' railway=railway_crossing is relatively rare (6 in NL+BE+DE)

Examples:

switch:
​https://overpass-turbo.eu/s/1ov9 (ex: ​https://www.openstreetmap.org/node/1026459392, ​https://www.openstreetmap.org/node/1051328033 (both isolated nodes next to a real switch))

railway_crossing:
​https://overpass-turbo.eu/s/1ova (ex: ​https://www.openstreetmap.org/node/4635993887 ​https://www.openstreetmap.org/node/2665878649 )

Hence I would propose to add the following to
https://josm.openstreetmap.de/browser/josm/trunk/resources/data/validator/geometry.mapcss#L277

node:unconnected:in-downloaded-area[railway=switch],
node:unconnected:in-downloaded-area[railway=railway_crossing],

as part of the existing rule isolated node which must be connected to a way

[Famlam]

Patch on Github:
​https://github.com/JOSM/josm/pull/117

[taylor.smock]

Ticket retargeted after milestone deleted

[Famlam]

Is there anything that I should still do here?

[taylor.smock]

Ticket retargeted after milestone closed

[taylor.smock]

In 18914/josm:

Fix #22546: Warn about floating railway switches and crossing (patch by Famlam)

railway=switch and railway=crossing should always be connected to a railway;
neither can exist without a railway line as they are physical features of the
railway.

[gaben]

Please consider closing the corresponding ticket on GH before it's forgotten.

[taylor.smock]

Thanks for reminding me.