Hi All I've added to Thomas's initial work and completed what I think we should import and what the tagging scheme should look like in http://wiki.openstreetmap.org/wiki/NaPTAN/Tag_mappings. Please take a look and shoot down in flames/agree/amend: particularly inclusion/exclusion proposals
Generally if the text of the proposed tag following the naptan: preamble is in the format "word1_word2" it is our substitute for an ambiguous or verbose NaPTAN field name, otherwise it's a copy (complete with CapitiLisation) of the NaPTAN field name Three questions: Hail and ride section of route, with a linear footprint. Flexible zone, with an area footprint. 1.Presumably these are represented for HAR with 2 nodes (start and end) and for FLX with multiple nodes (min 3) for which we would have to draw a way between them and add a tag to the way. (naptan:HAR=yes and naptan:FLX=yes) 2.Thomas- how easy is this to add the way and tag it within the import process or should drawing the way and tagging it be left to manual intervention? Roger – how many of these are there? 3. If we can agree the entire tagging and import scheme would we get any extra benefit from offering it for discussion on talkgb or should we just get on with it? An observation: With about 30 fields to be imported are editor screens going to look too cluttered for the average OSMer? TIGER data takes up a lot of screen real estate and there's a lot less fields. Should we (can we) cull the fields to be imported?
_______________________________________________ Talk-transit mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-transit
