[Talk-transit] NaPTAN data import
Hi everyone We discussed at our West Mids meeting last night the best way forward. Here is what we would like to see happen: 1. Proceeed with the import on the basis of the proposed naptan taggings. All imported data should have the naptan: prefix as we feel it is important to identify the source of the data and differentiate it from OSMer-generated data 2. If it's easy to code, generate ways between related nodes for things like plusbus zones, stopareas etc. We didn't discuss however how to tag these, so I guess just leave them untagged. If it's going to be difficult and slow down the implementation, then ignore it and just import the nodes and we'll have to generate ways manually. 3. Rather than import for the whole West Midlands, just import for Birmingham as a test area - it's easier for us to cover as there fewer bus stops in a smaller area, and it also won't piss off our neighbours in Coventry - most of us are based in Birmingham. 4. The import should not tag the data with highway=bus_stop. We'd rather have un-rendered nodes that we can see in the editors and then either merge with existing data or switch on by tagging where we haven't yet surveyed. It is OK however to tag taxiranks with amenity=taxi (very few people have been surveying and tagging these) 5. Can we have a csv file of the data so we can keep track of our verification and record variations, problems on the ground etc. and co-ordinate activities so we don't go off duplicating effort? In the future other OSMers will have the benefit of Christophe's visual tool to do this. We'll give regular updates here on how we're faring and produce a short report summarising our experience for future imports. 6. As a local initiative we are proposing to cease using (and convert existing data) the ref=xx tag for identification plates we find on the ground as it doesn't currently match any naptan data (and so can't be regarded as a global standard reference) and we will use instead asset_ref=xxx. This is Andy's suggestion and as he's the one who's entered most of this data and he'll have to do most of the work - we all agreed readily! Let us know if there are any problems with this Regards Brian ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
Re: [Talk-transit] [Talk-gb-westmidlands] NaPTAN data import
On 6 Mar 2009, at 13:17, Peter J Stoner wrote: There is a file StopPlubusZones.csv in the West Midlands NaPTAN which contains a list of 12107 bus stops. I have taken these to be all the stops within the West Midlands PlusBus zone. http://www.plusbus.info/stations/station.php?item=1811back= Ok, so if a plusbus zone it is a list of bus stops then it is probably a relation not a polygon. To be clear I don't think anyone is suggesting we should never import Plusbus zones, it is just a matter of if it is in the first pass and at the end of the day that is going to be up to the person writing the code! Great stuff, Peter -- Peter J Stoner UK Regional Coordinator Traveline www.travelinedata.org.uk a trading name of Intelligent Travel Solutions Ltd company number 3826797 Drury House, 34-43 Russell Street, LONDON WC2B 5HA ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
Re: [Talk-transit] [Talk-gb-westmidlands] NaPTAN data import
On 6 Mar 2009, at 18:28, Andy Robinson (blackadder-lists) wrote: Gerrit - NaPTAN references nodes as being part of a StopArea, somewhat like our relation structure. The converter is already pulling them in according to the unified stop area spec. (Except for not having the stop-points on the road way, just beside, but thats just a moot point) In the EU a Stop Point is the place that the person waits for the vehicle, which is beside the road/track and the place where the vehicle stops in called a Stopping Point is on the road/track. Can we agree that a Stop in OSM is the same as a Stop Point and is therefore correctly positioned beside the track. What OSM is proposing to call a Halt is on the track and is the same as a Stopping Point. The unified Stop Area proposal is a great one to settle this one for good for all public transport modes. I do hope we can drop that as a 'moot point' soon! http://wiki.openstreetmap.org/wiki/Proposed_features/unified_stoparea Regards, Peter -- Regards, Thomas Wood (Edgemaster) Cheers Andy ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit ___ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
