This bus stop ("South terrace Surbiton Library Stop SM”) has been moved for quite some time. But is still shown in its old position. The new position is 115 yards south from the old position.
The bus stop is now directly in front of Surbiton Library. The photo shows Surbiton Library plus a bus stop in front with “South terrace Surbiton Library Stop SM” on the bus stop sign.
Google Maps has the new location correctly. But TFL still has the old position.
Please can this be fixed?
Here’s a diagram showing the old location on the TFL map with the new location marked by me. It’s directly in front of “Surbiton Library”
Its NaPTAN entry needs fixing as well as the TfL map.
Interestingly both Google Maps and Open Street Map plot SM in the correct location (by the library) but if you look into their stop data they still associate it with the old location (by the Telephone Exchange).
hi @alexd - welcome to the forum.
@MScanlon in our Journey Planner team has updated the coordinates.
This will now be updated in NaPTAN in the next few days and should be in our API next week. I’ll let you know when that goes live.
Many thanks,
James
Hi @jamesevans @MScanlon There is also the same issue with the below stop on route 240 which moved location about a year ago - Medawar Drive - Transport for London
Also, a question about bus stop names and the ‘towards’ information; when this info is changed on the physical bus stops, how much time before they feed through to the website? I have seen a number of discrepancies between what stops are named on the physical stop flag versus what is shown on website/apps and announced/displayed onboard buses and was wondering whether I should list them all out for correcting or if it just takes time a long while for them to update! Thanks
I think the ‘towards’ information tends to indicate the general direction of buses from the stop rather than destinations of the individual routes although the two sometimes coincide.
Hi @FraserAB (welcome to the forum!) and @misar,
I’ll let my colleagues comment on the Medawar Drive issue, but regarding bus stop location names and towards information…
The location name and towards information we display on our website (and in our unified API) come from the bus stop asset management system, which in the vast majority of cases reflects the physical bus stop flag:
When the physical signage changes, it should be reflected in the asset management system and eventually make its way to the website. This process can take a couple of weeks, but I reckon that if a change isn’t reflected on the website within four weeks, there’s likely some kind of issue.
The location name should be the same:
The towards information should be the same:
The towards information is not used on board the bus.
As @misar mentions, the towards information is not to be confused with a destination name or the name of the final bus stop on a route.
Anyway, issues with information in our unified API can be reported on this forum. Issues with information at bus stops and on board can be reported via our contact form. Discrepancies that are only in unofficial apps should be reported to the publishers of those apps.
