Bus stops in NaPTAN with indicator "Stop"

A lot of StopPoints in NaPTAN – 5000+ in London by my count – have the Indicator “Stop” rather than e.g. “Stop F”. This seems to be a recent regression and they included the letters before ~27 August, even though many of the stops in question have a long-ago ModificationDateTime

E.g. Stop P:

		<StopPoint CreationDateTime="1970-01-01T00:00:00" ModificationDateTime="2016-10-06T06:35:57" Modification="new" RevisionNumber="13" Status="active">
			<AtcoCode>490007529W</AtcoCode>
			<NaptanCode>53016</NaptanCode>
			<Descriptor>
				<CommonName xml:lang="en">Winchelsea Road</CommonName>
				<Street xml:lang="en">PHILIP LANE</Street>
				<Indicator xml:lang="en">Stop</Indicator>
			</Descriptor>
[...]
			<StopAreas>
				<StopAreaRef Modification="new" Status="active" CreationDateTime="2024-08-27T09:10:04.9991629+01:00" ModificationDateTime="2024-08-27T09:10:04.9991629+01:00">490G000064</StopAreaRef>
			</StopAreas>
			<AdministrativeAreaRef>082</AdministrativeAreaRef>
		</StopPoint>

I’m aware that fortunately I can still get the platformName from the unified API, and I think the journey planner timetables TxC data includes the full indicator still. Also appreciate that this may be a low priority at the moment.

Hi there. Thanks for reporting this. We are aware of this issue and have fixed these in our internal dataset, so they should be corrected when we next upload to NaPTAN.

2 Likes

Can I ask when this may be? Is this affected by the ongoing cyber security issue?