Talk:Proposed features/lanes sign
- Nice idea. This might be very useful for routing. Maybe you should add a "T" option for designated tun-over lanes. How would you tag intersection where you can turn half right and sharp right (or left)? I would prefer a name like "lane_directions" over "lanes_sign" because I think you want to tag the directions to which the lanes are leading and not the fact that there is an actual physical lane sign. --SnakeBDD 10:41, 31 May 2010 (UTC)
How about non-oneway roads? – Nikerabbit 12:23, 31 May 2010 (UTC) ---
- Actually, I don't care about the name at all :) It was just the first thing that came into my mind. You're right, "lane_directions" is better.
Concerning "T" option. I'm not sure it's needed, because in Ukraine if you are allowed to turn left, you are automatically allowed to make U-turn if it's not prohibited exactly here. Concerning intersections with half turns and sharp turns. The biggest problem of my proposal is that I make one sign as one jpg-file. So if you chose L_L_S, it must correspond to file L_L_S.jpg. I made signs/files with all combinations of directions for two and three lines. But try to imagine how many combinations can be on a road with 4, 5 and more lanes. Of course, it is possible to create files for all combinations, but I think it would be easier to make a script or something that will create a sign on the map using the same definition for lanes (L for left turn etc.) Unfortunately, I'm not a programmer and I don't know how to do it. Maybe, some additional keys should be made, like higway=lanes > lanes=3, then a form with multiple choice for every lane should appear, where one can chose the direction: U-turn/Left/Sharp left/Half left/Straight/Right/Sharp right/Half right.
- to Nikerabbit: It doesn't matter if a road has one-way or two-ways traffic. The tag should be placed before an intersection, so there will be no misunderstanding.
Example:
--nyoma 16:08, 31 May 2010 (UTC)
- Don't mind about that rendering issue. I don't think that this would be a big problem for programmers of a rendering engine. I think it is sufficient to provide sample images for every possible combination for one lane. A program can then put these next to each other to render the sign. Anyway, most renders will prefer a custom style for their map, so I don't think that you have to provide these images. But they are useful to demonstrate your idea in this proposal.
- Concerning the "T" option: there are few intersections here in Germany where you have designated turn-over lanes. It wouldn't hurt to allow the "T" option to map those.
- On the two-way roads issue: I understand Nikerabbit's concerns. I think you should add this tag to an existing road instead of adding a note where the physical sign is installed, what is what you want as far as I understand you, Adding an extra node just for this issue somehow doesn't feel right. You could tag only the last segment of the road in front of an intersection with this tag. In most cases It will be clear which direction is meant by the tag (the one leading to the intersection node). But we have a problem when there are two intersection nodes next to each other. In that case, we cannot tell to which direction the tag applies. A possible solution would be to add a new node between these two nodes. --SnakeBDD 13:48, 31 May 2010 (UTC)
- No problem with providing the images as well as with the "T" option. I'll do it. Concerning two-ways roads: Your ideas to place the tag on the last segment and to add one more node is good. I thought about it too. Besides, in some cases there is no need to add new node because you may use the segment between the first crossing and the next one.
For example,
- I made changes to http://wiki.openstreetmap.org/wiki/Proposed_features/lane_directions
What do you think about it?