Who is the "we" & "our" you speak of?
There is an expression in OSM: "Don't tag incorrectly to suit the
renderer/router/etc"
You can't create fantasy tags, such as gtfs:stop_id:GB-Aubin, purely to
sort out the faults in your private software project.
You've still left numerous, erroneous naptan:AtcoCode tags on railway
platforms.
DaveF
On 15/01/2026 22:41, Michael Tsang wrote:
On Tuesday, 13 January 2026 22:28:19 Greenwich Mean Time Dave F via Talk-GB
wrote:
Which NapTan database contains codes such as 9100VICTRIC16?
DaveF.
Sorry I made a cock-up in the tagging for these rail station codes. The NaPTAN
schema guide (https://naptan.dft.gov.uk/naptan/schema/2.5/doc/
NaPTANSchemaGuide-2.5-v0.67.pdf ) has given an example that the platforms of
the rail stations are labelled in the form of 9100FARNHAM1 where FARNHAM is
the TIPLOC code and the 1 is the platform number, and the timetable data from
TfL also appear to support this as well, so I started tagging some rail
stations in this way to force my journey planner to associate it to the
correct platform rather than the bridge above / tunnel below.
However, in reality, it seems that the NaPTAN database has problems in these
platform numbering including missing platforms, and TfL has started to "make
up" codes to use in their timetable data (ref:https://techforum.tfl.gov.uk/t/
resolving-platform-names/3873/9 see reply #9 and #20 ). Therefore I am tagging
the metro stations ids from TfL timetable data into the "naptan:AtcoCode" tag.
Unfortunately it seems that TfL does not always make up codes using the exact
platform number in the same way as the NaPTAN guide and my application - they
do make up codes for rail stations such as Stratford or Tottenham Court Road
but they make up codes using other suffixes instead of the platform code (like 0
and 1 instead of A and B).
They also do not normally publish the TransXChange data used in their journey
planner for rail services, as it is derived from the National Rail timetable,
not their primary data (they did release it in the past by accident and
retracted it later) so I am unable to verify the actual codes used in the TfL
journey planner against the made-up codes by appending the platform number
after the TIPLOC code.
We are trying to resolve these problems with the NaPTAN dataset.
To prevent further problems (especially when combining our data with TfL Go
results), I have retagged these made-up rail platform codes with another key
and reconfigured our journey planner. If there is a way to find out the code TfL
actually makes up, please let me know so we can rewrite our application to use
the same code TfL makes up.
Sorry for the confusion. The points made in the opening message are still
valid - for non-National Rail platforms, we are sourcing the codes directly
from official sources (like BODS, Traveline, TfL), but the official sources do
not
contain a platform number so we are manually investigating the timetable data
to assign the code to the correct physical platform, such that a platform
number can be shown in the journey planner.
Michael
On 12/01/2026 23:48, Michael Tsang wrote:
On Sunday, 11 January 2026 14:56:52 Greenwich Mean Time Michael Tsang
wrote:
Hi all,
I am the lead developer of Aubin which is a public transport journey
planner using OpenTripPlanner as its backend. We have now released an
update which shows the position of the station entrances where you need
to use during your journey on the map.
This feature has helped me a lot in finding errors in underground station
mappings, because if I expect to use an entrance to go underground but a
symbol doesn't appear, it strongly suggests that there is some mess up in
the map which makes me teleport between levels, or alternatively the
platforms aren't mapped properly with the right naptan:AtcoCode
populated,
or the entrance themselves not being mapped, or the platforms aren't
correctly connected to the street network. I have already found and fixed
some errors in the map like Oxford Circus.
I am not trying to promote the features of Aubin not directly related to
OpenStreetMap but you should try to use it because it uses OpenStreetMap
data to guide you directly to the best entrance to the correct platform,
giving a realistic time to access / change trains, as long as the map
data
is of high quality.
Also, I live in London, if you find some dodgy journey planner results
planning a trip in London but can't fix it yourself, please let me know
where the problem is and I may be able to have a site visit (I did some
in
South East London yesterday).
Thanks,
Michael
Further to the above, please also check that the app can correctly show
the
platform numbers for metro journeys. They can be shown in the app when all
the following are present:
- a `ref` on the platform
- a `naptan:AtcoCode` on the platform
- the platform is a member of the stop area
If multiple platforms function as a group (for example, terminus
platforms), tag them with the same `naptan:AtcoCode`, in such case we can
show in the app in the format such as "Platform 3-6".
Please help to complete these information in the map.
Thanks,
Michael
_______________________________________________
Talk-GB mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-gb
_______________________________________________
Talk-GB mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-gb
_______________________________________________
Talk-GB mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-gb
