If we decide to import then adding the GTFS (General Transit Feed Specification) tags on additional fields such as stop_code would allow the use of Maperitive's find command to locate bus stops by stop_id even if it wasn't visible. The other two relevant tags would be stop_name which in the case of Ottawa is displayed internally on the bus and stop_id which would be significant only to an application or bot.
I'd bug Calgary nicely for a GTFS format file. GTFS started out as Google Transit Feed Specification but has since changed its name as it went through a "standards" style discussion etc. and is now used for more than just Google. Cheerio John On 9 June 2010 21:19, Tyler Gunn <ty...@egunn.com> wrote: > > On Wed, 9 Jun 2010 21:17:28 -0400, john whelan <jwhelan0...@gmail.com> > wrote: > > The problem here is you need to do the plus sign thing and look at the > data > > links. Putting the bus stop number in the name filed means that > renderers > > such as Maperitive can display it as you zoom in without needing any > > special > > training for the end user. > > > That's a very good point. > I think I'll adopt this style going forward. Adding the bus stops in > Winnipeg is on my "todo" list. I will likely contact Winnipeg Transit to > see if they have any bus stop and route data they could provide though as > I'd rather not have to go around taking pictures of every bus stop in the > city. :) > > Tyler > > -- > Tyler Gunn > ty...@egunn.com >
_______________________________________________ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
