Re: [Talk-transit] NaPTAN Merging Guidelines

2009-08-18 Thread Roger Slevin 
Bryce

NaPTAN does not allow the character / to be part of a commonname as NaPTAN
rules (not fully adhered to by TfL or LBSL) do not allow composite
commonnames.

Underground station entrances are included in NaPTAN data ... they are part
of the 490 area data (whereas the stations themselves are in a national
dataset prefixed 940)

Roger

-Original Message-
From: talk-transit-boun...@openstreetmap.org
[mailto:talk-transit-boun...@openstreetmap.org] On Behalf Of Bryce McKinlay
Sent: 18 August 2009 01:08
To: Public transport/transit/shared taxi related topics
Subject: Re: [Talk-transit] NaPTAN Merging Guidelines

Thank you very much for your efforts on this, Thomas, and everyone
else involved - I've been waiting for the London import for a while,
and it's fantastic to see this data in OSM!

I have one bug to report: Is it possible that special characters are
being dropped from the stop names during the import? For example:

 node id=469789137 lat=51.5122005 lon=-0.1420652 version=1
changeset=2177128 user=NaPTAN uid=104459 visible=true
timestamp=2009-08-17T13:40:06Z
tag k=name v=Conduit Street  Saville Row/
tag k=naptan:CommonName v=Conduit Street  Saville Row/
...

TfL refers to this as Conduit Street / Saville Row, so it seems the
/ characters are going missing somewhere?

Also, I'm curious whether, in addition to the bus stop data, NaPTAN
contains precise locations for Underground station exits, and if so,
whether there is any plan to import these? OSM often contains only one
node for stations that have multiple exits, and in some cases the node
is ambiguously placed such that it isn't clear which street (or which
side of the street) an exit is on. This level of precision does become
significant when producing walking maps/directions...

Bryce



On Mon, Aug 17, 2009 at 3:50 PM, Thomas Woodgrand.edgemas...@gmail.com
wrote:
 I've only just realised that my previous message regarding the imports
 beginning only went to talk-gb and talk-gb-london.

 Greater London is now imported as changeset 2177128.
 I was planning to import Hull and Suffolk also this week.

 Now that we're importing the data, we really need to get our
 guidelines on how to merge and tidy the data sorted. I've pulled out
 the relevant pieces from the Birmingham wikipage out to

http://wiki.openstreetmap.org/wiki/NaPTAN/Surveying_and_Merging_NaPTAN_and_O
SM_data
 It really needs to be tidied and beaten into a useful document before
 we let more people loose with the data.

 --
 Regards,
 Thomas Wood
 (Edgemaster)

 ___
 Talk-transit mailing list
 Talk-transit@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-transit


___
Talk-transit mailing list
Talk-transit@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-transit


___
Talk-transit mailing list
Talk-transit@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-transit

Re: [Talk-transit] pay_scale_area

2009-08-18 Thread Chris Morley 
Christoph Böhme wrote:
 In my opinion the name tag is used as a general purpose tag in OSM for
 names of all sorts of things. So, it appeared quite natural to use it
 for recording the names of the plus bus zones as well. From the other
 tags renderers can easily guess what type of object the name belongs to
 and the decide if it should be displayed. So there is no need to use
 namespaced versions of the name tag just to prevent the renderer from
 displaying it.

It is rather useful that Mapnik will display a name of a feature which 
is of general interest but may have unknown tagging. For a new feature 
like PlusBus zones that are not intended for display on a general 
purpose map, it make more sense for them not to have a name or ref tag 
than to enter each one of them for non-display in the general Mapnik 
stylesheet. As a general rule, a new feature should not break existing 
code if possible. It is easily possible in this case by adding a 
prefix, with very little downside.

Chris

___
Talk-transit mailing list
Talk-transit@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-transit

Re: [Talk-transit] NPTG locality viewer

2009-08-18 Thread Christoph Böhme 
Christoph Böhme christ...@b3e.net schrieb:

 The NPTG viewer and the Novam tools are not working at the moment
 because a server update went wrong. So, don't be surprised when you
 see a 500 - Internal Server Error. I'll try to sort it out tonight.

The NPTG viewer and the Novam tools are working again.

Christoph

___
Talk-transit mailing list
Talk-transit@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-transit