Brian Stoptype HAR has sub-records which contain two pairs of coordinates, one representing the entry point to the linear footprint, and the other representing the exit point. If guidance has been followed, then the linear footprint should stay on a road link with the same name along its length (but evidence indicates that the rules are not always followed strictly, either because they have been overlooked, or because the creator of the data hasn't appreciated where a road name changes takes effect). An HAR stop is a three point linear feature, anchored on the "central" point of the three.
Stoptype FLX has sub-records which contain three or more pairs of coordinates which represent the boundary of the zone which is being described. The guidance indicates that the polygon formed by linking the points with straight lines should cover the relevant area - but of course it does not have to be precise, The points should be in sequence within the sub-records - and generally will be points where the boundary intersects roads entering/leaving the zone, plus additional points that pull the boundary so that it completely bounds the zone. In this process the inclusion of non-significant territory is normally ignored - the test is "does the zone cover all the roads that could be used by the Demand Responsive Transport service, and does it not cover any sections of road that are not to be used by the DRT service?" I don't have an easy way to check on the number of HAR and FLX stops there are across the country. HAR is quite common across the whole country. FLX exist in relatively few very rural areas - with Lincolnshire being one county which has a lot of them. There are few if any, however, in the whole of the South East region at present. Peter from Ito may be able to check more easily on the totals than I can. Roger _____ From: talk-transit-boun...@openstreetmap.org [mailto:talk-transit-boun...@openstreetmap.org] On Behalf Of Brian Prangle Sent: 28 February 2009 10:11 To: talk-transit@openstreetmap.org Subject: [Talk-transit] NaPTAN bus stop database import 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 Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
