I’m developing a web app and want to show the nearest bus stop(s) to the user.
Unfortunately, the /StopPoint search within a radius of a given lat/lon pair seems to be almost useless as it is truncating the given lat= and lon= to only three places of decimals. Sometimes, when standing at a bus stop, the inaccuracy is so great that the stop you’re standing at is outside the 200m radius search!
As an example, the following query:
Returns as part of the JSON:
"$type": "Tfl.Api.Presentation.Entities.StopPointsResponse, Tfl.Api.Presentation.Entities", "centrePoint": [ 51.526, -0.107 ],
which rather proves the point. Could this be fixed please, or do I need to source my own database of accurate stop locations?
I know that when returning a bus stop’s StopPoint, the lat and lon are returned to 6 decimal places. Not quite GPS accuracy, but certainly close enough to be useful; this makes it doubly odd that the search is limited to only 3 decimal places!
Thanks in advance,