[Talk-transit] Naptan import
roger at slevin.plus.com
Wed Jul 29 23:12:57 BST 2009
The polygon should be closed by linking the final entry back to the first
entry in the file for each PlusBus Zone
From: talk-transit-bounces at openstreetmap.org
[mailto:talk-transit-bounces at openstreetmap.org] On Behalf Of Thomas Wood
Sent: 29 July 2009 22:58
To: Public transport/transit/shared taxi related topics
Subject: Re: [Talk-transit] Naptan import
2009/7/29 Christoph Böhme <christoph at b3e.net>:
> Christoph Böhme <christoph at b3e.net> schrieb:
>> Thomas Wood <grand.edgemaster at gmail.com> schrieb:
>> > 2009/7/29 Christoph Böhme <christoph at b3e.net>:
>> > > Talking of the NaPTAN import: The NPTG data also contains polygons
>> > > for the Plusbus Zones. This data is self-contained and can easily
>> > > be imported. They could be either imported as ways tagged with
>> > > their zone code and their name or we could create an additional
>> > > relation that holds all the bus stops which are part of the zone
>> > > as well. The latter would, of course, only be necessary if there
>> > > are bus stops within the polygon which are not part of the zone
>> > > or vice versa.
>> > I tried to create a relation for plusbus zone stops from the NaPTAN
>> > data but there were simply too many - we quickly hit the OSM
>> > relation member maximum.
>> Okay, that answers the question. I simple create a polygon then. I
>> suggest the following tagging scheme for the ways:
>> ref=Plusbus zone ref
>> name=Plusbus zone name
>> Is pay scale area the correct general name for things like the plusbus
> I transformed the Plusbus Zones into a josm-file (XSLT is cool :-).
> Thomas can you import it using the naptan-user if no one objects to the
> tagging scheme?
> Talk-transit mailing list
> Talk-transit at openstreetmap.org
That looks fine, the only issue is that none of the polygons are closed!
Talk-transit mailing list
Talk-transit at openstreetmap.org
More information about the Talk-transit