Brian Prangle <[email protected]> schrieb: > 6. Towards is not in the NapTAN data and is a local OSMer decision > ( Andy always tags these, I'm a bit hit-and-miss --%<-- > 3. Ref numbers NaPTAN vs local. Lots of discussion and examples > around this one and I'm still confused. But I think it will resolve > itself if we import AtcoCode, NaptanCode,and PlateCode(even though > this one breaks my rule of being an optional field). Then any > OSMer-generated data using ref or local_ref (i.e what's seen on the > ground) can be kept and OSMers can keep collecting such local data.
Perhaps it helps to compile a list of tags that mappers in the West Midlands used for bus stops and try to match these with the Naptan fields? > 4. Thomas - do you agree that Christophe's time would be better spent > on a Dracos-style data analysis tool? > http://www.dracos.co.uk/play/locating-postboxes/ I'll have a go on this one. I already explained Thomas how I imagine such a tool at the moment: "I'm thinking of a tool that displays all bus stops from Naptan and the ones currently in the OSM database on top of a map. A click on a bus stop shows all its tags and a list of bus stops with similar attributes (e.g. same reference code, same name, closeby location) from the other data set. Clicking on a "Combine" link links the two bus stops together and a combined tag set can be created by selecting tags from one of the two original bus stops. Once this is done the data can be merged into the OSM database." Christoph _______________________________________________ Talk-transit mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-transit
