Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add traffic island area preset #5562

Closed
RudyTheDev opened this issue Dec 6, 2018 · 7 comments
Closed

Add traffic island area preset #5562

RudyTheDev opened this issue Dec 6, 2018 · 7 comments
Labels
considering Not Actionable - still considering if this is something we want preset An issue with an OpenStreetMap preset or tag usability An issue with ease-of-use or design

Comments

@RudyTheDev
Copy link
Contributor

This would add rendering for traffic_calming=island (i.e. these separate areas) mapped as areas. It's used de facto quite a bit, but not as much due to mistagging and imprecise tagging mentioned below.

old
to
new

It's a typical example around my area of grassy lane-dividing traffic island with a paved pedestrian section and some railings for safety. The surface tag is what specifies the actual surface. (Notice also the poor grit box without an icon 😭)

There are also:

The islands are commonly mapped with less precision as just landuse=grass/natural=grass (which is probably where the majority of improvable uses are hiding). These are also mapped with multiple features as traffic_calming=island and landuse=grass. These are also occasionally "forced" to render with area=yes. All these sounds as mapping for renderer.

A different tagging also exists: area:highway=traffic_island. iD treats area:highway as "Road Surface". Wiki also says area:highway is for roads: lanes, but not extras, like shoulders, parking, sidewalks. In practice, it's used for separated islands too. I'm not sure if iD should have a preset for these too? This scheme doesn't have choker or chicane supported. I'm not even sure if it doesn't just mean the flush painted/marked areas.

  • area:highway=traffic_island taginfo
@bhousel bhousel added usability An issue with ease-of-use or design preset An issue with an OpenStreetMap preset or tag labels Dec 6, 2018
@bhousel
Copy link
Member

bhousel commented Dec 6, 2018

This would add rendering for traffic_calming=island (i.e. these separate areas) mapped as areas. It's used de facto quite a bit, but not as much due to mistagging and imprecise tagging mentioned below.

I like it!

The islands are commonly mapped with less precision as just landuse=grass/natural=grass (which is probably where the majority of improvable uses are hiding). These are also mapped with multiple features as traffic_calming=island and landuse=grass.

This seems ok too.

These are also occasionally "forced" to render with area=yes. All these sounds as mapping for renderer.

Aside: I wish people would stop reflexively dismissing "mapping for the renderer". Users want to be able to make maps out of this stuff, and I have tremendous sympathy for the developers who maintain the rendering software. We should try to pick tags that make their job easier. Thinking about it more, maybe landuse=grass/natural=grass is better for this.

A different tagging also exists: area:highway=traffic_island. iD treats area:highway as "Road Surface".

Oh yeah, area:highway is really for road surfaces, and for users who want to micromap the area of the pavement. It's not for obstacles like islands. If you find area:highway=traffic_island tags, please replace them with one of the other options above (and whoever feels like updating the wiki should do that too, so we can stop giving people bad advice).

@bhousel bhousel added the considering Not Actionable - still considering if this is something we want label Dec 6, 2018
@bhousel
Copy link
Member

bhousel commented Dec 9, 2018

Thinking about it more, maybe landuse=grass/natural=grass is better for this.

Yeah I thought about this even more, and I think mappers should just use other more widely used tags.

I think plain old landuse=grass is better than traffic_calming=island+surface=grass

@bhousel bhousel closed this as completed Dec 9, 2018
@RudyTheDev
Copy link
Contributor Author

What does one use when the surface isn't grass?

@bhousel
Copy link
Member

bhousel commented Dec 10, 2018

What does one use when the surface isn't grass?

I'd do this:
island

p.s. Added a generic "box" icon for the grit bin in 05c24c9

@RudyTheDev
Copy link
Contributor Author

What about:

ex

Here, it's a raised island in the middle of the road splitting lanes. It's marked off and no pedestrians are allowed. The surface is asphalt. There are reflective poles along the edges.

@bhousel
Copy link
Member

bhousel commented Dec 10, 2018

Here, it's a raised island in the middle of the road splitting lanes. It's marked off and no pedestrians are allowed. The surface is asphalt. There are reflective poles along the edges.

Ohh ok! Yeah that is a better example of a traffic_calming=island. I think the first example you gave is not really one - it's just the space between a dual carriageway, not designed to slow the cars.

So an interesting thing - the OSM wiki has a contradiction..

That's probably the reason that we don't already have a preset for a traffic calming with area=yes. But I agree now that I know what this is, we should support this.

@bhousel bhousel reopened this Dec 10, 2018
@RudyTheDev
Copy link
Contributor Author

I think the first example you gave is not really one

Yeah, my bad. That example inadvertently muddles the waters with whether the pedestrian bit is a traffic calming or not.

Here's a better real example for posterity:

ex

The left island is grass, the right one is asphalt. Both have a "pedestrian area".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
considering Not Actionable - still considering if this is something we want preset An issue with an OpenStreetMap preset or tag usability An issue with ease-of-use or design
Projects
None yet
Development

No branches or pull requests

2 participants