On 01/08/14 01:36, Will Phillips wrote: > I do not believe the stop areas should have been imported at all because > they are not verifiable on the ground. Also, I am often unable to find > much logic in the groupings other than the stops are relatively close > together, so I don't think they are really useful.
This is where having a unique ID for ab object comes into it's own. That is if the data source allows you to access that data using it. All that needs to be in the OSM data is 'bus stop' and it's NaPTAN reference, and anything else comes from a secondary read. Although names and the like may be worth duplicating. Where a source of a data import is readily accessible, then we don't need to duplicate the 'non-mapping' data. It may be for some imports we need a private copy of the data to make this work nicely, but that should be a natural part of the import process anyway. A clean copy of what was imported. What is available and easily accessible is growing daily ... but it does not need to be all imported into one database :) -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk _______________________________________________ Talk-GB mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-gb
