Re: [Tagging] How to tag traffic islands ?

> On Nov 1, 2015, at 3:02 PM, Paul Johnson wrote: > > > I commonly tag the center-lane variety as lanes:both_ways=1, > access:lanes:both_ways=no I completely forgot about the center common bi-directional turn lane. Tons of them in the US, never seen one in Japan yet. Javbw. _

Re: [Tagging] How to tag traffic islands ?

I tag only those traffic islands that have a curb around them to prevent vehicle access. I tag the enclosed area with highway=pedestrian, area=yes, and the way surrounding it with barrier=kerb (although I prefer "curb"). I ignore painted, cross hatched or striped, areas. Cheers, Dave On Sun, Nov

Re: [Tagging] How to tag traffic islands ?

I fear I've mixed two very different probems, so I'll open another thread for my problems with the tagging of junctions/crossings. Gerd Von: Volker Schmidt Gesendet: Samstag, 31. Oktober 2015 19:36 An: Tag discussion, strategy and related tools Betreff: Re: [T

[Tagging] Often seen tagging problems regarding junctions

Hi all, while trying to clean up wrong highway=* tags in the OSM database I noticed a few error patterns. Not sure if I can call it an error when other people are using tags in a completely different way, but I think I should report them: 1) the tag highway=crossing is/was used for ways, oft

Re: [Tagging] Often seen tagging problems regarding junctions

I use highway=footway+crossing=X+crossing_ref=Y on *ways* (as well as placing a wiki-compliant node at the intersection of the crossing way and the road way). This makes it (relatively) easy to draw a Zebra crossing, correctly orientated along the way. Richard On Sun, Nov 1, 2015 at 10:05 AM, Ge

Re: [Tagging] tunnel=culvert

On Fri, Oct 30, 2015 at 07:36:45PM +0100, Martin Koppenhoefer wrote: > 2015-10-30 19:02 GMT+01:00 Richard : > > > > What is the advantage of a node, one click less? > > > > did you count the clicks? > > node: "n"+ 1 click + 1 tag/value > > way: "n"+2x(click+"p") + "s"+ click + 2 tag/values > > >

Re: [Tagging] How to tag a "overhead electronic display" ?

johnw wrote: >> traffic_sign=changing >> or > >traffic_sign=variable > The matrix displays and variable signs are very different. > a matrix sign can become entirely different signs. They are also a source > for alerts and current info no matter the topic - whereas a variable sign > for the speed

Re: [Tagging] tunnel=culvert

> On Nov 1, 2015, at 8:56 PM, Richard wrote: > > a way > which is shared by a waterway, a mulptipolygon forrest and an > administrative boundary. Clean up the inaccurate mapping and then do it the right way. I'm sure you can find an airport boundary, a fence, and a power line sharing a node t

Re: [Tagging] Feature Proposal - Voting - aeroway=heliport

Apologies, I'm late to this discussion. On 20/10/2015 18:23, Daniel Koć wrote: ...and we should start changing these aeroway=* values, but I'm not sure what is the best way to do this effectively. Maybe mass edition would make sense? As you suggest a mass edit you appear to be implying there

Re: [Tagging] Feature Proposal - Voting - aeroway=heliport

W dniu 01.11.2015 14:39, Dave F. napisał(a): Apologies, I'm late to this discussion. On 20/10/2015 18:23, Daniel Koć wrote: ...and we should start changing these aeroway=* values, but I'm not sure what is the best way to do this effectively. Maybe mass edition would make sense? As you sugge

Re: [Tagging] How to tag a "overhead electronic display" ?

On Sun, Nov 1, 2015 at 7:07 AM, Lauri Kytömaa wrote: > johnw wrote: >>> traffic_sign=changing >>> or >> >traffic_sign=variable >> The matrix displays and variable signs are very different. I have being using guidepost=vms (for variable message sign) for these. Electronic signs which tell you how

Re: [Tagging] How to tag traffic islands ?

> On Nov 1, 2015, at 5:10 PM, Dave Swarthout wrote: > > access. I tag the enclosed area with highway=pedestrian, area=yes, and the > way surrounding it Your road islands have people on them? They have big signs here saying "no crossing - cross at the light" with a fence or hedge down the ce

Re: [Tagging] "What can I ask ..." list for browsing people

You click on "Help" then on "Beginners Guide" Am 01.11.2015 um 19:10 schrieb André Pirard: > ... > > What can I show to Mr X? > This is extremely off topic btw. signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@open

Re: [Tagging] How to tag a "overhead electronic display" ?

Andrew MacKinnon wrote on 2015-11-01 23:00: I have being using guidepost=vms (for variable message sign) As said here before, acronyms are bad. They can mean too many things: https://en.wikipedia.org/wiki/VMS ___ Tagging mailing list Tagging@openstr

Re: [Tagging] How to tag traffic islands ?

Pedestrians are seldom actually present but because of the curb they are safe zones for crossing and off limits for vehicles. Pedestrians are pretty much on their own here in Thailand. Even where there are zebra crossings motorists don't stop or even slow down. Although there are many cycle lanes h

Re: [Tagging] How to tag a "overhead electronic display" ?

That sounds reasonable. -- John F. Eldredge -- j...@jfeldredge.com "Darkness cannot drive out darkness; only light can do that. Hate cannot drive out hate; only love can do that." -- Martin Luther King, Jr. On October 29, 2015 4:03:49 AM Paul Johnson wrote: On Thu, Oct 29, 2015 at 3:57 AM

Re: [Tagging] Feature Proposal - Voting - aeroway=heliport

sent from a phone > Am 01.11.2015 um 14:39 schrieb Dave F. : > > In my city there's a corner of a recreation ground that used to land > emergency helicopters for the adjacent hospital. No other facilities, not > even a 'H' painted on the ground. Helipad is the perfect tag & is rendered in >

Re: [Tagging] Feature Proposal - Voting - aeroway=heliport

sent from a phone > Am 01.11.2015 um 21:50 schrieb Daniel Koć : > > I was just wonder if we could turn the aeroway=helipad wih "heliport" in name > into aeroway=heliport (not all of them, because helipad is different beast, > as you just wrote), but after more research I am now more cautious:

Re: [Tagging] Often seen tagging problems regarding junctions

sent from a phone > Am 01.11.2015 um 12:30 schrieb Richard Mann > : > > I use highway=footway+crossing=X+crossing_ref=Y on *ways* (as well as placing > a wiki-compliant node at the intersection of the crossing way and the road > way). > > This makes it (relatively) easy to draw a Zebra cro

Re: [Tagging] How to tag a "overhead electronic display" ?

I also liked the traffic_sign=variable, but now I think we have to separate those traffic_signs from pure informational displays showing e.g. temperature, wind, or other weather conditions, as well as traffic status (traffic jam, tunnel closed,free parking places and so on) from those which wil

Re: [Tagging] How to tag traffic islands ?

sent from a phone > Am 01.11.2015 um 23:02 schrieb John Willis : > > Or were you referring to the little piece of the crosswalk that in on/in the > island there are these traffic planning/managing fails, where pedestrians get a green light to cross just halfways, leaving them on the traffic

Re: [Tagging] How to tag traffic islands ?

sent from a phone > Am 02.11.2015 um 00:36 schrieb Dave Swarthout : > > Pedestrians are pretty much on their own here in Thailand. Even where there > are zebra crossings motorists don't stop or even slow down. it's the same in Italy, at least in the central and southern parts. You better wa

Re: [Tagging] Often seen tagging problems regarding junctions

okay, what do you use when there are traffic lights at a zebra crossing? Or let's say what would you recommend? My (current) understanding is that the zebra crossing is a "fall back" in case that the traffic lights are not working, so I'd say they are not important. The problem: Aerial images s

Re: [Tagging] How to tag traffic islands ?

okay, thanks for all the input. I think nobody said that we should use the word island or traffic island for an area that is just marked with paint. Now what do we call this area? I think it is not a highway=* or a surface=* or a landuse=* I think it is a traffic_calming=* , but I have no idea a

Re: [Tagging] How to tag a "overhead electronic display" ?

I'm sure I have seen combinations as well - big black LED panels which can show information including (for example) temporary/emergency speed limits if required. Is there a need to distinguish between mechanical and electronic signs, which can only show a very limited range of signs for which

Re: [Tagging] Often seen tagging problems regarding junctions

>> >> This makes it (relatively) easy to draw a Zebra crossing, correctly >> orientated along the way. > > > I use the combination of highway =crossing and crossing=uncontrolled for > zebra crossings that are not controlled by traffic lights. On a node on the > road-highway way. > I have be

Re: [Tagging] How to tag traffic islands ?

off topic: Yes, I also learned that in Kuala Lumpur, Malaysia. Zebra crossing seem to have no meaning, red lights at pedestrian crossings are ignored as long as it possible to cross before or after the pedestrian. Sounds dangerous, but seemed to work fine for everybody ;-) I think there is a gen

Re: [Tagging] How to tag a "overhead electronic display" ?

I see no need to separate mechanical from others in the major tag like traffic_sign=*. I see no problem to add the information with another tag, maybe display_type=* Gerd Von: Colin Smale Gesendet: Montag, 2. November 2015 08:23 An: tagging@openstreetmap.org B

Re: [Tagging] How to tag a "overhead electronic display" ?

> I think the first group is not a traffic_sign=*, it is information=* Considering the sign is purely for motorist, not tourists, I think it is still very much a traffic sign. But traffic_sign has no framework for non-law signs. no one is going to go find this sign to check something - it is o

Re: [Tagging] Often seen tagging problems regarding junctions

thanks for this example. I think it illustrates my problem very well. The footways (e.g. https://www.openstreetmap.org/way/372661072) are tagged [http://www.openstreetmap.org/assets/osm_logo_256-835a859acf0d378e1d14e88b15e7b4b95211ccd41a2c061b1629cfb