Hi Matthijs I echo Stuart - it's best to deal with these with the local NaPTAN maintainer, who works in TfWM
Regards Stuart On 5 February 2017 at 21:22, Stuart Reynolds < [email protected]> wrote: > Hi Matthijs, > > 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. > > 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. > > 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. > > Regards > Stuart > > > On 5 Feb 2017, at 19:35, Matthijs Melissen <[email protected]> > wrote: > > On 3 February 2017 at 19:29, Stuart Reynolds <stuart@travelinesoutheast. > org.uk> wrote: > >> 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. >> >> Hi Stuart, > > 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? > > -- Matthijs > > _______________________________________________ > Talk-GB mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-gb > > > _______________________________________________ > Talk-GB mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-gb > >
_______________________________________________ Talk-GB mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-gb
