On 11 Jun 2010, at 01:49, john whelan wrote:
Ottawa is different. The passengers complain if the bus is one
minute early or five minutes late. Quite unlike London in the UK
where I used to live. I think it stems from the minus 30c in winter
time, with wind chill it can be even colder, t
Ottawa is different. The passengers complain if the bus is one minute early
or five minutes late. Quite unlike London in the UK where I used to live.
I think it stems from the minus 30c in winter time, with wind chill it can
be even colder, the passengers typically turn up about two minutes befor
> > You may want to follow
> > British/German standard. There is a tag that identifies stops uniquely,
> > sorry can't recall at the moment. The last time I saw it was
> > Siegburg/Bonn train station.
Do you mean the "ref" tag as on node 160621? I'd strongly advice not to follow
that way. The "re
The problem with name=stop_name is it does not identify the bus stop. In
Ottawa each stop is labeled with the stop_code and you can call a phone
number to find out the time of the next bus or use a web site to plan your
trip using that stop_code. The route planners display the stop code on the
st
IMHO merging is not necessarily the best idea. You will create yet another
standard.
I'd keep the names as name=stop_name, and add the stop_code with another
tag. Propose something that will be relevant with more North American
cities, yet that does not disturb other regions. You may want to follo
Currently bus tops mapped locally in Ottawa seem to be either untagged or
tagged in different ways. Maperitive default rules displays the icon and
the name field. The GTFS (General Transit Feed Specification was Google TFS
at one time) has three relevant tags these are stop_code, stop_name, and
s
