Proposed features/Traffic island
From OpenStreetMap Wiki
| Traffic island | |
|---|---|
| Status: | Draft (under way) |
| Proposed by: | Lulu-Ann |
| Tagging: | landuse=traffic_island |
| Applies to: | |
| Definition: | <definition> |
| Rendered as: | <appearance> |
| Draft start: | 2010-04-08 |
| RFC start: | |
| Vote start: | |
| Vote end: | |
This proposal intends to replace the former use of crossing=uncontrolled;island/traffic_signals;island/etc by mapping traffic islands as areas - just what they are.
Contents |
prerequisites
- When there is a traffic islant, it is necessary to split up the lanes of the road.
- A traffic island has an outline.
- It is possible that footways, cycleways, or road lanes go across a traffic island.
- Traffic islands have different types of kerbs. They might be passable for wheelchair users or not, and they might be high enough to be detected by a blind person with a white cane or not.
- Traffic islands might have different surfaces.
- Traffic islands might have tactile paving.
- Traffic islands might have poles of traffic lights on them, button operated or not.
- Traffic islands can be passable for pedestrians or not. They can be middle rest of a zebra crossing, an uncontrolled crossing, a tucan crossing...
Examples with images
(planned)
Rendering
to be defined
Routing
Depends on kerb hight.
See also