id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22546	[patch] Warn about floating railway switches and crossings	Famlam	team	"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`"	enhancement	closed	normal	23.12	Core validator		fixed	railway switch railway_crossing	gaben