The reasoning behind taking the approach I took was to make it simple of the end user. Maperitive with the new default rules displays the bus_stop name. The end users need the 4 digit number to be able to use the city's route planner but having the official name of the stop means if the bus driver announces it you know where you are or you can ask the bus driver to let you know when it comes up on his display.
Example is here. http://picasaweb.google.ca/lh/photo/qETGqJTUCEYzFln-38ugXQ?feat=directlink Yes it is possible to use the web version of the map, but it has two drawbacks, the first is render speed, it doesn't come up as fast as you might like certainly on my machine with broadband and the second is you need to teach people to use the plus sign and the data layer even then you need to locate the correct bus stop. Having worked with end users before the simpler it is the easier it is. It took the organisation I worked for three years before they were using the room booking facility of calendar. Similar process, click here, click there and select. The education level was certainly above average in that organisation, I think the minimum requirement was two years further education. To me route information changes, the bus stop id does not. GTFS has a separate file for route information which consists of a list of bus stop numbers. If you want to know how to get somewhere then you need an application to process the route and timetable information. OC has one here: http://www.octranspo.com/tps/jnot/startEN.oci I like shelter yes/no but you need to visit the location to get that information, so I think its optional. Cheerio John On 9 June 2010 20:09, Tyler Gunn <ty...@egunn.com> wrote: > > On Wed, 9 Jun 2010 18:30:21 -0400, john whelan <jwhelan0...@gmail.com> > wrote: > > I've had a discussion with the only other local mapper I'm aware of in > > Ottawa and we are proposing the following for Ottawa bus stops, which > I've > > entered in the wiki. There is a GTFS feed available for Ottawa and > > verbally > > I've been assured the data is available under an acceptable license. > > > > OC tranpo's system has a four digit number on all the stops otherwise > known > > as the GTFS stop_code which is of value since their route planner > doesn't > > always take into account footpaths. The GTFS stop_name is displayed > > internally to the driver and on a good day gets announced. > > > > So this proposal is to get agreement on how the stops should be imported > if > > need be and to give guidance to local mappers before then. > > > > Thoughts? > > > The Winnipeg WIKI page has a reasonable schema for this: > http://wiki.openstreetmap.org/wiki/Canada:Manitoba:Winnipeg > See the section on Bus Stops. > > For example: > * highway=bus_stop > * route_ref=12;65 (Include all routes that stop here, separated by > semicolon) (ie each route in winnipeg is numbered) > * name=* (The name of the bus stop, which is usually the cross street; > printed on the sign) > * asset_ref=10254 (The stop number, printed on the sign) > * shelter=yes/no (Indicate if there is as shelter at this stop) > > > Here's an example of a bus stop sign in Winnipeg from a survey I did; I > have yet to add this to OSM yet: > http://www.egunn.com/dl/bus_stop.jpg > > Ironically, here's the only example of a fully tagged bus stop in Winnipeg > that I can find (one of my first attempts at it): > http://www.openstreetmap.org/browse/node/679411842 > > Hope that helps. > Tyler >
_______________________________________________ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
