On Wed, Mar 6, 2013 at 4:37 PM, Ronnie Soak
wrote:
>> Fortunately there is no such thing as regional trams :)
>>
>
> I learned very early on that there is no such thing as 'no such thing' in
> OSM.
>
> There are quite a few regional trams here in Germany alone:
... in Victoria.
Steve
__
Am 06.03.2013 03:56 schrieb "Steve Bennett" :
>
>
>
> Fortunately there is no such thing as regional trams :)
>
I learned very early on that there is no such thing as 'no such thing' in
OSM.
There are quite a few regional trams here in Germany alone:
http://de.wikipedia.org/wiki/%C3%9Cberlandstr
On Tue, Mar 5, 2013 at 11:13 PM, Marc Gemis wrote:
> Let me try to clarify this.
> In case there are 2 companies stopping at a particular station, they both
> might have different properties for that stop: e.g. the names, reference
> numbers and zones.
>
> So the zone might depend on the company (
Am 05/mar/2013 um 13:13 schrieb Marc Gemis :
> So the zone might depend on the company (both bus transportation), not on the
> form of transportation (bus vs. metro). This means that you need to group
> those attribute name, route_refs, refs, zones, etc.) per company.
>
> You could either a
Let me try to clarify this.
In case there are 2 companies stopping at a particular station, they both
might have different properties for that stop: e.g. the names, reference
numbers and zones.
So the zone might depend on the company (both bus transportation), not on
the form of transportation (bu
On Tue, Mar 5, 2013 at 3:27 AM, Marc Gemis wrote:
> Why is zone ambiguous on a bus_stop ? Or any more ambiguous than "name" ?
> The latter is also used for so many different things.
These are deep semantic philosophy questions :) I'd point out that
renderers can naively render "name" tags and pro
Why is zone ambiguous on a bus_stop ? Or any more ambiguous than "name" ?
The latter is also used for so many different things.
I see no need to make new tags for each new "zone" concept. This is only
needed when 1 item can belong to different types of zones.
When you need 2 different zones for m
On Sun, Mar 3, 2013 at 8:21 PM, Martin Koppenhoefer
wrote:
> If you would prefer to use something generic referring to public
> transport it would be better to use something like
> public_transport_zone=* instead of just "zone" (but I'd prefer the
> approach proposed by Steve and the most used acc
Le 03/03/2013 10:21, Martin Koppenhoefer a écrit :
2013/3/3 Jo :
I would simply use zone=1, zone=2 or zone=1;2 on them. That's how it's done
in Belgium and The Netherlands. Although we don't have overlapping zones.
I would use something more specific, "zone" is way too generic and can
mean eve
2013/3/3 Jo :
> I would simply use zone=1, zone=2 or zone=1;2 on them. That's how it's done
> in Belgium and The Netherlands. Although we don't have overlapping zones.
I would use something more specific, "zone" is way too generic and can
mean everything or nothing (e.g. maxspeed zones, low emiss
I would simply use zone=1, zone=2 or zone=1;2 on them. That's how it's done
in Belgium and The Netherlands. Although we don't have overlapping zones.
The rules (which change every so many years) in Flanders, the northern part
of Belgium, are: travelling through 1 or 2 zones has one tariff, and
trav
Hi all,
I don't see any wiki documentation on public transport zones: that
is, how to tag that station X is in zone 3, station Y is in zone 2,
for systems where the price of a ticket depends on the zones
travelled.
For example, in Melbourne, there are two zones. Some train stations
are in zone 1
12 matches
Mail list logo
