Re: [Tagging] traffic_signals:lanes? (specific signal types for certain lanes)

2017-12-26 Thread Albert Pundt
The situation might not be common, but applying the :lanes methodology to
the key traffic_signals is just a logical extension of existing conventions.

I wasn't aware traffic_signals:continuous_green was so uncommon; I just
noticed it documented on the wiki and figured it must be at least somewhat
recognized, though I'm sure there's occasionally dubious tagging methods
that sometimes get added.

On Tue, Dec 26, 2017 at 11:23 PM, Paul Johnson  wrote:

>
>
> On Tue, Dec 26, 2017 at 5:04 PM, yo paseopor  wrote:
>
>> I will not discuss here if continuous_green would be a realistic value
>> with full possibilities in a future. But according to taginfo [1] there are
>> only 6 nodes around the world.
>> Also I am asking myself: if continuous_green is continuous green
>> really...is it usefull for the map? (because there is no action here, it
>> would be a traffic light, a painting, or some big commercial ad pannel in
>> the middle of the highway).
>>
>> In this case I think it would be more useful and accurate to separate the
>> left lane a couple of meters before it really does and put a traffic signal
>> for this new way with one lane that turns left. I think it would be
>> unusefull to put a traffic signal on the other way with continuous green.
>>
>
> Only similar situation I can think of was where the west end of US 30
> BYPASS met US 30 at the northwest ramp of the St. John Bridge in Portland
> until sometime around 2005.  The arrangement was such that all three
> eastbound lanes of US 30 had a traffic light (two general access lanes and
> a bicycle lane.  Westbound, the two left lanes had a full signal (a general
> access left turn lane and a general access through lane), then there was a
> set of no-lane-change stripes to the right of that, then a general access
> through lane with a permanent green through arrow, and a bicycle lane with
> a permanent green through arrow.
>
> US 30 was then (and still is now) a single carriageway with no separation
> at that location; wouldn't be accurate to add a median where there isn't one
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
>


-- 
—Albert
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] traffic_signals:lanes? (specific signal types for certain lanes)

2017-12-26 Thread Paul Johnson
On Tue, Dec 26, 2017 at 5:04 PM, yo paseopor  wrote:

> I will not discuss here if continuous_green would be a realistic value
> with full possibilities in a future. But according to taginfo [1] there are
> only 6 nodes around the world.
> Also I am asking myself: if continuous_green is continuous green
> really...is it usefull for the map? (because there is no action here, it
> would be a traffic light, a painting, or some big commercial ad pannel in
> the middle of the highway).
>
> In this case I think it would be more useful and accurate to separate the
> left lane a couple of meters before it really does and put a traffic signal
> for this new way with one lane that turns left. I think it would be
> unusefull to put a traffic signal on the other way with continuous green.
>

Only similar situation I can think of was where the west end of US 30
BYPASS met US 30 at the northwest ramp of the St. John Bridge in Portland
until sometime around 2005.  The arrangement was such that all three
eastbound lanes of US 30 had a traffic light (two general access lanes and
a bicycle lane.  Westbound, the two left lanes had a full signal (a general
access left turn lane and a general access through lane), then there was a
set of no-lane-change stripes to the right of that, then a general access
through lane with a permanent green through arrow, and a bicycle lane with
a permanent green through arrow.

US 30 was then (and still is now) a single carriageway with no separation
at that location; wouldn't be accurate to add a median where there isn't one
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] traffic_signals:lanes? (specific signal types for certain lanes)

2017-12-26 Thread yo paseopor
I will not discuss here if continuous_green would be a realistic value with
full possibilities in a future. But according to taginfo [1] there are only
6 nodes around the world.
Also I am asking myself: if continuous_green is continuous green
really...is it usefull for the map? (because there is no action here, it
would be a traffic light, a painting, or some big commercial ad pannel in
the middle of the highway).

In this case I think it would be more useful and accurate to separate the
left lane a couple of meters before it really does and put a traffic signal
for this new way with one lane that turns left. I think it would be
unusefull to put a traffic signal on the other way with continuous green.

That's my opinion. What do you think?

Salut i semàfors (Health and traffic signals)
yopaseopor

[1] https://taginfo.openstreetmap.org/search?q=continuous-green#values
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] cycleway:both=no in StreetComplete

2017-12-26 Thread Volker Schmidt
Wish for the New Year: a world where all streets have cycleways and hence
cycleway=no is a useful tag to indicate the few exceptions.

More realistically, cycleway=no is useful to indicate that someone has
verified there is no cycleway.
For example to indicate that the large sidewalk that is clearly visible on
the satellite pictures is not a cycleway despite the fact that it clearly
looks so and armchair mappers (like me) are tempted to put it on the map.

A similar argument is valid for oneway=no. There are cities where oneway=no
is the exception (one that I remember vividly is Salta in Argentina).
It is also useful in cities (like mine) where the administration is very
active in changing the oneway directions every few months,

If someone maps *=no don't remove it unless it is wrong.





>

Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging