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

On Fri, Jul 5, 2019 at 8:04 AM Silent Spike wrote: > Using the following established tags: > After all discussion so far I would update the list of tags to import as follows: - `highway=bus_stop` - `public_transport=platform` - `bus=yes` - `name` [Imported - defer to existing

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

On Fri, Jul 5, 2019 at 1:41 PM Andy Townsend wrote: > The most interesting bit would be the "Manually conflate and review the > data before upload using JOSM" - any JOSM CSS style that you end up using > to highlight duplicates would be really useful, as would a basic OSM diary > entry

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

If you wanted to conflate indicator and common name into the OSM “name” field, then I can provide a list of what we call “prefix indicators” as opposed to “suffix indicators”. It’s fairly self-explanatory, as prefix indicators are generally those that are positional e.g. o/s, opp, adj, nr etc.

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

On Fri, Jul 5, 2019 at 1:33 PM Stuart Reynolds < stu...@travelinesoutheast.org.uk> wrote: > what did you have in mind? To the end-user of the data (i.e. someone > wanting to know about where to catch the bus) this is absolutely critical. > > For example, in my previous post I face a suggestion of

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

Stuart wrote: > Even more so in bus stations. The name Derby Bus Station (actually > just "Bus Station” in the locality of Derby) applies equally to all 29 > bays in the bus station. “Bay 1” through “Bay 29” are the indicators. Agreed this is useful when adding the stops for the mapper, but

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

On 05/07/2019 13:19, Silent Spike wrote: On Fri, Jul 5, 2019 at 1:02 PM Gareth L > wrote: Forgive me if this is silly question/statement, but the adj/alt names etc are in the naptan dataset. Wouldn’t it be better to have the link made between the stop in OSM

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

When you say that the indicator field is somewhat meaningless to a data consumer what did you have in mind? To the end-user of the data (i.e. someone wanting to know about where to catch the bus) this is absolutely critical. For example, in my previous post I face a suggestion of “Stuart

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

On Fri, Jul 5, 2019 at 1:02 PM Gareth L wrote: > Forgive me if this is silly question/statement, but the adj/alt names etc > are in the naptan dataset. Wouldn’t it be better to have the link made > between the stop in OSM and the record in naptan (using the codes prior > mentioned). > My

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

Forgive me if this is silly question/statement, but the adj/alt names etc are in the naptan dataset. Wouldn’t it be better to have the link made between the stop in OSM and the record in naptan (using the codes prior mentioned). My thinking is data consumers could link and retrieve values using

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

On Fri, Jul 5, 2019 at 11:35 AM Stuart Reynolds < stu...@travelinesoutheast.org.uk> wrote: > -snip- > > Hope that helps. > Pretty much the perfect response, thank you! Good point about alternate names, will add support for those to my script now (maybe unnecessary for my area, but I'd like to

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

From your original post, I didn’t think so, especially. However, the fields in NaPTAN are designed to be granular, and while many may seem to be irrelevant to OSM (e.g. why have a street name when the street is named on the map) different local authorities will have different approaches to

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

On Fri, Jul 5, 2019 at 10:52 AM Stuart Reynolds < stu...@travelinesoutheast.org.uk> wrote: > Yes, both are still in use > > -snip- > > Regards, > Stuart Reynolds > for traveline south east and anglia > As someone more in the know, are there any fields of the NaPTAN data which you think should be

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

On Fri, Jul 5, 2019 at 10:17 AM Mateusz Konieczny wrote: > 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) >

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

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

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

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 mailto:matkoni...@tutanota.com>> wrote: 5 Jul 2019, 09:04 by

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

Since the other thread has become a tagging discussion on the pros and cons of PTv2, let's try this again. Would there be any objections to an import of the following scope: 1. Import data specifically for the Aberdeen admin area (ATCO code 639) 2. Import stops of type BCT ("On-street Bus