On Tue, Jul 2, 2019 at 10:00 AM David Woolley <[email protected]> wrote:
> In may experience, a lot of the original NaPTAN imports have decayed: > > - people have double mapped stops and the the NaPTAN one has been deleted; > > - stop have moved and got double mapped and deleted as a result; > > - stops have been temporarily out of service, e.g whilst redeveloping a > bus station, and been deleted and then lost the NaPTAN associations when > remapped. > I'm not sure why double mapping is occurring, but it seems to me that (even with these mapping mistakes) having the stops present in OSM is better than not using the data at all. If conflation can be done once, it can be repeated in future if data needs to be imported as an update. On Tue, Jul 2, 2019 at 10:00 AM David Woolley <[email protected]> wrote: > Also, all bus stops need continual maintenance because names get changed > as landmarks come and go. > > Given that few people like maintenance work, if you can't map all the > stops from first principles, it is very unlikely that imported ones will > get maintained. Retaining the NaPTAN tagging is important in allowing > any later remerge of the updated NaPTAN data. > I gather that you're suggesting future data imports will be needed to keep stop data up-to-date and so the NaPTAN tagging is needed to make that process easier? In which case I agree, although I still don't see what use the tags other than the NaPTAN ATCO code provide. It appears to be a stable identifier, which means by including it in OSM the NaPTAN data is directly associated with the tagged OSM element (reducing the need to maintain tagging in OSM). On Tue, Jul 2, 2019 at 10:00 AM David Woolley <[email protected]> wrote: > Another problem with NaPTAN stops, which applies to non-OSM users as > well is that they have virtual stops in Hail and Ride areas. Routers > seem to only like people boarding at those place, so, in my case, can > take me about 7 minutes out of my way against the direction of travel, > so tell me I have missed a bus that could be easily caught At present I don't intend to include hail and ride data in my import process. Would need to investigate further how best to handle it and I'm personally only interested in clearly marked bus stops. _______________________________________________ > 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
