<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>Hi Matthijs,</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Wherever possible the names in NaPTAN should match what is on the flag or shelter. There are however some instances where this is not possible or desirable. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">For instance, the stop might carry a historic name such as for a long closed pub which has been updated in data but not on the ground. Or perhaps the name is a compound name (often of the "Main Street / Side Road" variety) where
this is better held as two separate fields in NaPTAN. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">But in general any discrepancies should be queried with the data owner who is normally the County or Unitary council. In West Midlands it is the old Centro / new TfWM. I have contacts there, as obviously does Brian, but I ought
to check that they are happy for me to post their email address on the list for all to use.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Regards</div>
<div id="AppleMailSignature">Stuart</div>
<div id="AppleMailSignature"><br>
</div>
<div><br>
On 5 Feb 2017, at 19:35, Matthijs Melissen <<a href="mailto:info@matthijsmelissen.nl">info@matthijsmelissen.nl</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 3 February 2017 at 19:29, Stuart Reynolds <span dir="ltr">
<<a href="mailto:stuart@travelinesoutheast.org.uk" target="_blank">stuart@travelinesoutheast.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>Also, there is often some confusion about what name goes into which fields - people will insist on compounding names, for example, because that’s what their consuming system wants, rather than getting the consumer to read the data properly. But that’s
too much to go into here, and if reviewing the names is in scope then I would be happy to offer to help. One of my other “hats" is as the Public Transport Data Standards Advisor / Expert for DfT, which includes advising on NAPTAN.</div>
<div><br>
</div>
</div>
</blockquote>
<div>Hi Stuart,</div>
<div><br>
</div>
<div>Great to have your support. I noticed that there are a few stops in the West Midlands where the name in Naptan doesn't match the name on the flag (unfortunately I don't remember by heart which ones). This means the visual announcement in the announcement
in the bus (and the information in online timetables) is different from the name on the flag, so from a usability perspective it would make sense to fix this. Is there any process of reporting situations like that?</div>
<div><br>
</div>
<div>-- Matthijs</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Talk-GB mailing list</span><br>
<span><a href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</a></span><br>
<span><a href="https://lists.openstreetmap.org/listinfo/talk-gb">https://lists.openstreetmap.org/listinfo/talk-gb</a></span><br>
</div>
</blockquote>
</body>
</html>