|
How should I map a bus stop where the stop sign and the shelter are separate? See here. I've tagged the shelter as a shelter, and the bus stop as a bus stop, but as they're only metres from each other the result on OSM Carto is unsatisfactory: the shelter appears in the middle of the road and the bus-stop (normally blue) disappears. I know we don't tag for the renderer, but assuming the renderer makes good sense of good tagging, should I instead tag amenity=shelter on the bus stop node itself, and not on the physical shelter nearby? Related, presumably the name of the bus stop is all the white text on navy blue here, even though it's quite long? And (UK people especially) the txt-info code, now obsolete, is presumably no use for anything at all, even identifying the stop? |
|
Looks fine to me at z19 so I wouldn't worry about your mapping. (Aside: Eleb3 is the txt-info code obsolete? I've just checked a current timetable and the last page lists all the text codes and stop names relevant for the route underneath this text:
Having said that, searching the naptan data as it was in January shows the name of this stop (as used in timetables) as Splash Lane and the NaptanCode as PETGTPM rather than PEDGTPM for stop with AtcoCode 0590PGC726) Ah, I didn't realise that was a Naptan code. Maybe it's just my mobile/provider, but having tried in several districts to get info by text, my handset always tells me the text couldn't be sent. I've always presumed that's because the shortcode 84268 is no longer in service - and that in these days of smartphones the service is completely disbanded.
(05 Nov '19, 13:37)
eteb3
|
