<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>It's was not just location that was flawed, the direction, road
names, NaPTAN ref number and other details were often wrong. There
was a scheme set up to verify and correct the imported data.
Hopefully things are better today, but don't forget all that
'official' data was created by someone who might have been having
on off day or just made a mistake, so don't be afraid to correct
it in OSM with what is actually on the ground. Imports are rarely
perfect.</p>
<p>Chris Hill (chillly)<br>
</p>
<div class="moz-cite-prefix">On 15/12/2021 13:22, SK53 wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAELijW8jQe-p5Dmp+Frmb2ZMJtxL6xNjJZ8sQjkQFCACyiDxQg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Further to what Chris says:</div>
<div><br>
</div>
<div>I believe that the locational accuracy of Naptan data is
way better than what it was, but care still needs to be
exercised.</div>
<div><br>
</div>
<div>There is currently a stop described as Cosmeston Country
Park located in the sea W of the Isles of Scilly, and 364
located at OSGB Null Island (-7.55 W, 49.76 N).</div>
<div><br>
</div>
<div>Jerry<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 15 Dec 2021 at 13:06,
Chris Hill <<a href="mailto:osm@raggedred.net"
moz-do-not-send="true" class="moz-txt-link-freetext">osm@raggedred.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
did a lot of work with NaPTAN data in Hull and the East Riding
or <br>
Yorkshire. My experience would lead me to say that a ground
survey <br>
always overrules any such import. Do not be afraid to update
the map <br>
data with what you actually find on the ground. There is no <br>
NaPTAN-sourced data structure that can be broken, it was
imported and <br>
has been widely altered, added to and adjusted since. If a
further <br>
NaPTAN import is made in an area it will have to be done in a
way that <br>
respects surveyed data, which was much less of a problem in
2008.<br>
<br>
Chris Hill (chillly)<br>
<br>
On 15/12/2021 12:43, Chris Hodges wrote:<br>
> Bristol Parkway Station (located in South Glos) now has 4
bus stops <br>
> A-D. OSM Shows the old B (where the new C is) and C
(where there's no <br>
> longer a stop). I had some time to kill there yesterday
and did a <br>
> quick survey so have enough information to update the
map.<br>
><br>
> But:<br>
><br>
> If I go in and start editing, I'm likely to break the
existing <br>
> NaPTAN-sourced data, and I don't see an easy route to
query NaPTAN in <br>
> a human-readable way to compare it or add the new stops.
For someone <br>
> who's not going to get into mass edits or data imports,
what's the <br>
> best way to proceed? Should this be re-imported, or is
there a <br>
> datasource I'm missing?<br>
><br>
><br>
<br>
_______________________________________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>
</blockquote>
</div>
</blockquote>
</body>
</html>