[Talk-GB] Importing NaPTAN Data [Thread 2]

[Stuart Reynolds]

Yes, both are still in use

AtcoCode is the unique “ID” of the bus stop and is the key that is used in databases to identify the stop. It is therefore also the key that gets used in an AnnotatedStopRef within the TransXChange (timetable) data.

NaptanCode is, in my view, unhelpfully named because in a NaPTAN database you would tend to think of it as the key. But it isn’t. It is certainly unique, but it has some constraints around which characters can follow other characters so that on (very old style, now) phones you didn’t have to push the same button twice in succession (and actually using a combination of letters that use the same key sequence also works). By and large it is text (except in Scotland, if I recall, where it is numeric) and is the code that you would send to the (charged for) 84628 “next departures” SMS service (Nextbuses). You can also use it online at nextbuses.mobi for free, although there you can also use the AtcoCode, confusingly.

For example, Southend Travel Centre stop A has the AtcoCode 15800720 (158 is the Southend prefix) and the NaptanCode soadjdaw (where soa is the Southend prefix). The next departures can be seen using  http://nextbuses.mobi/WebView/BusStopSearch/BusStopSearchResults/soadjdaw

Both the SMS and Nexbuses services are still active, and not planned to be turned off any time soon.

Regards,
Stuart Reynolds
for traveline south east and anglia

On 5 Jul 2019, at 10:27, Gareth L <o.i at live.co.uk<mailto:o.i at live.co.uk>> wrote:

I’m certain I’ve seen “text this bus stop code to see next departures” use the naptan code. Whether or not that service is still live, I dunno.

On 5 Jul 2019, at 10:17, Mateusz Konieczny <matkoniecz at tutanota.com<mailto:matkoniecz at tutanota.com>> wrote:


5 Jul 2019, 09:04 by silentspike100 at gmail.com<mailto:silentspike100 at gmail.com>:

     *   `naptan:AtcoCode=*` [Imported]
     *   `naptan:NaptanCode=*` [Imported]

I reformatted
https://wiki.openstreetmap.org/wiki/Key:naptan:AtcoCode
https://wiki.openstreetmap.org/wiki/Key:naptan:NaptanCode
(added templates making them machine readable, descriptions will appear
for example at Taginfo)

Is it useful to use both? What is the difference between them?
Is NaptanCode actually used as planned ("referring to the stop in public facing systems")?

Alternatively, if you support the proposal then it's also useful to know 😊

It may help to include example (of full) .osm data file to make easy for mappers
to judge data quality in their area.
_______________________________________________
Talk-GB mailing list
Talk-GB at openstreetmap.org<mailto:Talk-GB at openstreetmap.org>
https://lists.openstreetmap.org/listinfo/talk-gb
_______________________________________________
Talk-GB mailing list
Talk-GB at openstreetmap.org<mailto:Talk-GB at openstreetmap.org>
https://lists.openstreetmap.org/listinfo/talk-gb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-gb/attachments/20190705/0d08b262/attachment.html>