<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
mso-fareast-language:EN-US;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Likewise for Birmingham (and probably most of the west mids). Stop positions in NaPTAN were as much as 200m off and we still continue to reposition as an when we map out an area. This is an example of where NaPTAN is better updating its data from OSM rather than the other way around.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Cheers<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Andy<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> Chris Hill [mailto:osm@raggedred.net] <br><b>Sent:</b> 31 July 2014 15:48<br><b>To:</b> Stuart Reynolds; talk-gb@openstreetmap.org<br><b>Subject:</b> Re: [Talk-GB] NaPTAN (stop) import<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-language:EN-GB'>The NaPTAN data was imported for Hull and East Yorkshire at my request. I quickly realised that the data was of variable quality and resurveyed the ~1300 bus stops in Hull. Having corrected a large percentage of the stops, I informed the Hull council team, at their request, who then ignored me. I would not want any NaPTAN data re-imported in this area unless I was sure the quality has very substantially improved. Some working relationship with the council team who maintain the data would help too.<br><br>Cheers, Chris,<br>osm user: chillly<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-language:EN-GB'>On 31 July 2014 15:15:18 GMT+01:00, Stuart Reynolds <<a href="mailto:stuart@travelinesoutheast.org.uk">stuart@travelinesoutheast.org.uk</a>> wrote:<o:p></o:p></span></p><p class=MsoNormal>Hi,<o:p></o:p></p><p> <o:p></o:p></p><p class=MsoNormal>This is a spin off from the recent thread about imports, because I wanted to specifically talk about NaPTAN imports.<o:p></o:p></p><p> <o:p></o:p></p><p class=MsoNormal>Having briefly scanned the various wiki pages, I get the impression that the NaPTAN data was imported, once, in 2009. What I can’t see, or haven’t found, is any discussion about how & how often this data is updated. NaPTAN (and associated NPTG) is a live data set, and is changing continually as bus stops are brought into use (e.g. new developments) and taken out of service.<o:p></o:p></p><p> <o:p></o:p></p><p class=MsoNormal>As I think I have mentioned, one of the reasons that I am now on this group is because of the adoption of OSM by a number of traveline regions, whose members are the very local authorities that create and maintain the NaPTAN data (including Nottingham/Nottinghamshire, since that was mentioned in the earlier thread). We therefore have an interest in making sure that the stop data on OSM is as up to date as the mapping.<o:p></o:p></p><p> <o:p></o:p></p><p class=MsoNormal>Is there an appetite within the community to maintain and update this data? And if so, how would we go about it, and how often might it be updated? For the record, the data set is change dated, and deleted records are retained in the data for reference until (eventually) being archived (although even then the stops are still contained in a separate archive file). So I think that the process of updating can be made a) robust, and b) reversible. <o:p></o:p></p><p> <o:p></o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal>Stuart<o:p></o:p></p><p> <o:p></o:p></p><pre style='text-align:center'><hr size=2 width="100%" align=center></pre><pre><br>Talk-GB mailing list<br><a href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk-gb">https://lists.openstreetmap.org/listinfo/talk-gb</a><o:p></o:p></pre></div></div></body></html>