Invalid stop name for Jubilee station North Greenwich

Hi,

we are using the timetables for TfL Tube within the ZIP archive in https://tfl.gov.uk/tfl/businessandpartners/syndication/feed.aspx?feedId=15 (with our username in the query parameter),

and have found that at least one stop name appears to be corrupt, starting around May 15th or around that date;

inside the archive there are two files:

  • tfl_1-JUB-_-y05-1745502.xml
  • tfl_1-JUB-_-y05-2155202.xml

Both files contain the following entries for the North Greenwich station:

	<StopPoint CreationDateTime="2020-05-11T00:00:00">
		<AtcoCode>9400ZZLUNGW2</AtcoCode>
		<Descriptor>
			<CommonName>2+3 | Westbound</CommonName>
		</Descriptor>
		<Place>
			<NptgLocalityRef>N0077702</NptgLocalityRef>
			<Location Precision="1m">
				<Easting>539269</Easting>
				<Northing>179880</Northing>
			</Location>
		</Place>
		<StopClassification>
			<StopType>RPL</StopType>
			<OffStreet>
				<Rail>
					<Platform />
				</Rail>
			</OffStreet>
		</StopClassification>
		<AdministrativeAreaRef>000</AdministrativeAreaRef>
		<Notes>2+3 | Westbound</Notes>
	</StopPoint>

	<StopPoint CreationDateTime="2020-05-11T00:00:00">
		<AtcoCode>9400ZZLUNGW1</AtcoCode>
		<Descriptor>
			<CommonName>1 | Eastbound</CommonName>
		</Descriptor>
		<Place>
			<NptgLocalityRef>N0077702</NptgLocalityRef>
			<Location Precision="1m">
				<Easting>539233</Easting>
				<Northing>179895</Northing>
			</Location>
		</Place>
		<StopClassification>
			<StopType>RPL</StopType>
			<OffStreet>
				<Rail>
					<Platform />
				</Rail>
			</OffStreet>
		</StopClassification>
		<AdministrativeAreaRef>000</AdministrativeAreaRef>
		<Notes>1 | Eastbound</Notes>
	</StopPoint>

Clearly the names “1 | Eastbound” and “2+3 | Westbound” are not the correct stop names for the North Greenwich platforms. I’m hoping this can be fixed soon.

It seems that the only stops with a “CreationDateTime” year 2020 are the above two stops; stop names with a “CreationDateTime” year 2019 seem fine.

Thanks!

2 Likes

@Shortcut

I’m confused… what is wrong with the descriptors? North Greenwich station has three sections, the upper concourse, the platform 1/2 island for services into Central London and the bay area aside platform 3 to Stratford.

image

Platform 1 is for though trains (from West Ham to West Hampstead)
Platform 2 is for train terminating (from Canary Wharf)
Platform 3 is for though trains (from West Hampstead to West Ham)

Is the problem that it says 1 and 2/3 rather than 1/2 and 3?

1 Like

oic. Let’s ping @jamesevans

The issue is that the name of the station is “1 | Eastbound” or “2 + 3 | Westbound” where I would expect the name to be “North Greenwich”.

It’s fine if this internal code was in some special internal code field, but it’s in the field which is presumably where the stop name should be and where every other stop has its actual name specified.

Even simply “North Greenwich 1” (or similar) would be better than “1 | Eastbound”.

Also, every other Jubilee XML file has the correct name, e.g. tfl_1-JUB-_-y05-426211.xml

	<StopPoint CreationDateTime="2018-03-19T00:00:00">
		<AtcoCode>9400ZZLUNGW1</AtcoCode>
		<Descriptor>
			<CommonName>North Greenwich</CommonName>
		</Descriptor>
        ...
	</StopPoint>

	<StopPoint CreationDateTime="2018-03-14T00:00:00">
		<AtcoCode>9400ZZLUNGW2</AtcoCode>
		<Descriptor>
			<CommonName>North Greenwich</CommonName>
		</Descriptor>
		<Place>
        ...
	</StopPoint>

Example of a station without the issue (note the CommonName field):

	<StopPoint CreationDateTime="2018-03-19T00:00:00">
		<AtcoCode>9400ZZLUCWR2</AtcoCode>
		<Descriptor>
			<CommonName>Canada Water Station</CommonName>
		</Descriptor>
		<Place>
			<NptgLocalityRef>N0077637</NptgLocalityRef>
			<Location Precision="1m">
				<Easting>535490</Easting>
				<Northing>179478</Northing>
			</Location>
		</Place>
		<StopClassification>
			<StopType>RPL</StopType>
			<OffStreet>
				<Rail>
					<Platform />
				</Rail>
			</OffStreet>
		</StopClassification>
		<AdministrativeAreaRef>000</AdministrativeAreaRef>
		<Notes>Canada Water Station</Notes>
	</StopPoint>

@Shortcut

I can’t think of anything useful to add to point. I suspect it’s incorrect as you say.

1 Like

I’ve newly stumbled on to this issue, which looks like it’s not fixed yet. I’m wondered if there’s an update? For now, I’ve done a bodge.

Rob

It’s always sensible to have a way of fixing things you get from an API if you can!

Apologies for the delay @Shortcut

I have asked the Journey Planner team to take a look into this.

Thanks,
James

1 Like