Bus stops in NaPTAN with indicator "Stop"

Open Data
1

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.

2

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
3

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

4

Hi Leon, just a heads up, the issue still remains. Stops at Victoria bus Station are still showing the indicator as just ‘stop’. Dorchester Hotel on Park Lane, various stops around Tower Bridge/Tower Gateway and London Bridge Bus Station are other examples. Plenty of places though where it’s just one or two random stops missing their indicator. I’d be here all week finding all of the ones still missing stop letters.

5

Hi, could you please confirm whether you’re looking at the data in NaPTAN or the Unified API (or elsewhere)?

I just downloaded the latest Greater London (490) dataset from the NaPTAN website, and the stop indicators are in there correctly:

<StopPoint CreationDateTime="1970-01-01T00:00:00" ModificationDateTime="2017-05-16T09:15:01" Modification="new" RevisionNumber="12" Status="active">
	<AtcoCode>490006111S1</AtcoCode>
	<NaptanCode>77410</NaptanCode>
	<Descriptor>
		<CommonName xml:lang="en">Dorchester Hotel</CommonName>
		<Street xml:lang="en">PARK LANE</Street>
		<Indicator xml:lang="en">Stop S</Indicator>
	</Descriptor>
	...
</StopPoint>

<StopPoint CreationDateTime="1970-01-01T00:00:00" ModificationDateTime="2021-06-09T13:52:23" Modification="new" RevisionNumber="27" Status="active">
	<AtcoCode>490006111N2</AtcoCode>
	<NaptanCode>54323</NaptanCode>
	<Descriptor>
		<CommonName xml:lang="en">Dorchester Hotel</CommonName>
		<Street xml:lang="en">PARK LANE</Street>
		<Indicator xml:lang="en">Stop T</Indicator>
	</Descriptor>
	...
</StopPoint>

If you’re looking at the data in the Unified API, please note that we have been unable to update it with the latest data from NaPTAN, due to the ongoing cyber security incident. We will update the Unified API as soon as we are able, which should resolve this issue.

6

Sorted. I worked it out. Thank you :slight_smile: