An interesting thread – and one in which I agree with Tony, Mark and Peter in
saying that public transport services and timetables don’t appear to me to have
a valid place in OSM. Whilst the infrastructure on which public transport
operates and depends can and should be mapped as part of an
scheme
čet, 2. srp 2015. 16:32 Roger Slevin ro...@slevin.plus.com je napisao:
I think you are falling into the trap of trying to cover too many things in one
relationship. A stoparea to me as a public transport person is (defined
functionally) a cluster of stoppoints at which it is possible
topics
Subject: Re: [Talk-transit] different interpretations of v2 PT scheme
2015-07-02 16:31 GMT+02:00 Roger Slevin ro...@slevin.plus.com:
Eric
I think you are falling into the trap of trying to cover too many things in one
relationship.
It seems like your email client did not display
Eric
I think you are falling into the trap of trying to cover too many things in one
relationship. A stoparea to me as a public transport person is (defined
functionally) a cluster of stoppoints at which it is possible to interchange
between services – and as such it is also a collection
should
use the latest version of NaPTAN and I can supply a copy in XML or CSV format
if that would help.
Best wishes
Roger Slevin
Traveline south east anglia
From: Chris Hill [mailto:o...@raggedred.net]
Sent: 30 June 2015 10:58
To: Public transport/transit/shared taxi related topics
too.
Cheers, Chris
On 30 June 2015 11:21:39 GMT+01:00, Roger Slevin ro...@slevin.plus.com wrote:
I am surprised to hear that the current NaPTAN data (which is
continually updated) has errors in it – and I wonder therefore if the
problem may lie in the updating of NaPTAN data in OSM. The original
I have not been able to follow the large number of posts on this group in
recent weeks - but I can confirm that stopareas are an important part of
NaPTAN data in the UK, and are an important aspect of the way that stops
data are used in journey planning applications. It would be a pity if OSM
Proposal Criticism
On Mon, Jan 24, 2011 at 9:10 AM, Michał Borsuk michal.bor...@gmail.com wrote:
Am 24.01.2011 09:39, schrieb Roger Slevin:
I have not been able to follow the large number of posts on this group in
recent weeks - but I can confirm that stopareas are an important part
In NaPTAN each direction of travel must be modelled with a separate stop -
so even though you may have a sign which says stops in both directions
(but the sign is only on one side of the road) ... there are two NaPTAN
records, one showing a marked stop, and the other an unmarked one (what we
call
transport stops to pick up and set down
passengers - a reflection of the data for which can be seen on Google Maps,
for instance, in the public transport stop icons nationwide.
Roger Slevin
-Original Message-
From: talk-transit-boun...@openstreetmap.org
[mailto:talk-transit-boun
transport/transit/shared taxi related
topics
Subject: Re: [Talk-transit] Bus stops in North America from GTFS data
On Fri, Jun 11, 2010 at 11:01 AM, Roger Slevin ro...@slevin.plus.com
wrote:
And whilst Peter Stoner is correct that Oxford is unusual in having two
different next departure services
As the person who arranged the NaPTAN data supply for OSM - which Ito then
managed in a technical sense - I can confirm that it will remain possible
for OSM to take occasional downloads of data for NaPTAN. Whether you want
to do so through data.gov.uk where they appear to have taken a snapshot of
Thomas
If you want a refresh of the NaPTAN dataset, then just ask me and I
will arrange for this be made available. I appreciate that this could be a
two-edged sword it would update the data, but in the areas where work
has already been done on the data from a year ago, it may
that the use of the indicator field is still being refined
and not everything that is in the current database is good practice.
Possibly Roger (Slevin) or Peter (Stoner) will be able to give us some
more detail on this.
[1] http://www.dft.gov.uk/naptan/schema/schemas.htm#2.2
Regards,
Peter
Mann wrote:
NaPTAN has node info; I was thinking more of deriving way and relation
info.
Richard
On Wed, Sep 2, 2009 at 4:34 PM, Roger Slevin ro...@slevin.plus.com
mailto:ro...@slevin.plus.com wrote:
TfL supplies its data to NaPTAN and this is the national
official source
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
PlusBus zone boundaries are defined by the stoppoints at the edges of the
zones. It should be possible to draw straight lines between each of the
boundary points to define the polygon of the area they cover (all stops within
such a polygon are members of that PlusBus zone). The exceptional
Plusbus zones are polygons which are unrelated to the road network - so for Rye
it covers a large polygon defined by straight lines linking each pair of
adjacent nodes on the source list of defining points. The representation of
this along the roads is inappropriate - and certainly not how it
...@openstreetmap.org] On Behalf Of Christoph Böhme
Sent: 02 August 2009 11:40
To: talk-transit@openstreetmap.org
Subject: Re: [Talk-transit] Naptan import
Roger Slevin ro...@slevin.plus.com schrieb:
Plusbus zones are polygons which are unrelated to the road network -
so for Rye it covers a large polygon defined
Thomas
Thanks for this - the East Sussex one is clearly wrong (not a lot of Gaelic
spoken there) ... and is something we don't check on, and it hadn't been
spotted before. I have asked the editor to correct it (to blank or en).
I don't have that influence with Perth Kinross - though I will try.
The polygon should be closed by linking the final entry back to the first
entry in the file for each PlusBus Zone
Roger
-Original Message-
From: talk-transit-boun...@openstreetmap.org
[mailto:talk-transit-boun...@openstreetmap.org] On Behalf Of Thomas Wood
Sent: 29 July 2009 22:58
To:
[mailto:christ...@b3e.net]
Sent: 29 July 2009 18:36
To: ro...@slevin.plus.com
Cc: 'Public transport/transit/shared taxi related topics'; 'Peter Miller'
Subject: Re: [Talk-transit] Naptan import
Roger Slevin ro...@slevin.plus.com schrieb:
Christoph
Sorry - I now realise I shouldn't have referred
: Christoph Böhme [mailto:christ...@b3e.net]
Sent: 28 July 2009 22:54
To: ro...@slevin.plus.com; Public transport/transit/shared taxi related
topics
Cc: ro...@slevin.plus.com; 'Peter Miller'
Subject: Re: [Talk-transit] Naptan import
Roger,
thank you for your explanations.
Roger Slevin ro
Peter
Locality Classification was added as a possible nice to have to the
version 2 schema but it has not been populated, and no guidance has been
created to indicate how this field should be used (save for a table of
permitted values). There is no classification data in NPTG other than that
You ask about the omissions from NPTG. Perhaps it would be helpful if I
described the history of creating NPTG and what the brief has been to local
data editors in terms of what is or is not included in the database.
NPTG started life as a national statistical gazetteer based on a collation of
-Original Message-
From: Christoph Böhme [mailto:christ...@b3e.net]
Sent: 27 July 2009 22:14
To: ro...@slevin.plus.com
Cc: 'Public transport/transit/shared taxi related topics'
Subject: Re: [Talk-transit] Naptan import
Hi
Roger Slevin ro...@slevin.plus.com schrieb:
Locality
I agree with Peter's view on Custom and Practice (CUS) stops - they exist
... but they are not marked in the same way as MKD stops are marked. But
they are real as far as the user is concerned!
Roger
-Original Message-
From: talk-transit-boun...@openstreetmap.org
Brian
Good comments - and from my NaPTAN perspective I share your view that data
improvement should be a two-way thing. I am very keen to see if we can make
that work through this exercise.
I have always said that linear positioning of bus stops can be good enough
if it is +/- 10m given that a
:50
To: ro...@slevin.plus.com; 'Peter Miller'
Cc: talk-tran...@openstreetmap.org; Talk-gb-westmidlands@openstreetmap.org;
'Brian Prangle'
Subject: RE: [Talk-transit] [Talk-gb-westmidlands] Naptan alignment
Roger Slevin [mailto:ro...@slevin.plus.com] wrote:
Sent: 31 March 2009 10:16 PM
To: 'Peter
Joe
[apologies if this appears twice - last night's posting did not appear to
get through]
I think there is a misunderstanding in your question.
TransXChange is an XML schema based on Transmodel architecture and is
increasingly used within the UK to exchange route and timetable data, taking
over
Brian
Stoptype HAR has sub-records which contain two pairs of coordinates, one
representing the entry point to the linear footprint, and the other
representing the exit point. If guidance has been followed, then the linear
footprint should stay on a road link with the same name along its length
Perhaps I can authoritatively assure you that the localities data does NOT
derive from Ordnance Survey - the source was a database compiled originally
by ONS, but they were happy to allow DfT exclusive rights on the use of that
data for NPTG. So I am not aware of any reason why DfT cannot allow
32 matches
Mail list logo
