5 ms·
As it happens, you have the choice to sense and respond to traffic, or have synchronized traffic signals in a complex grid like a city center. You can't really
by lutusp 14y ago
As it happens, you have the choice to sense and respond to traffic, or have synchronized traffic signals in a complex grid like a city center. You can't really have both.
To have synchronized signals in a city-wide two-dimensional grid of intersections, you must ignore the fact that some intersections have many cars and some have none. If you give up on the idea of synchronizing traffic, then you can have traffic sensors and working pedestrian crossing buttons.
> In the US, I can rarely tell if the buttons are just props or if they actually do anything.
It turns out that in many places, especially those that have synchronized signals, the pedestrian buttons are what might be called "placebo buttons". I'm sure you can guess what that means.
- purplelobster 14y agoIt would seem that sensors would be most useful with lower traffic volumes, and synchronization better for rush hour. Perhaps using each system at different times of the day would be theoretically optimal. Or why not incorporate sensor information into the synchronization, and continuously plan the best light cycles for any given situation?
- Anechoic 14y agocontinuously plan the best light cycles for any given situation Because there are a lot of "any given situation[s]" that might the scenario overly complex. Take a school for instance - you have students crossing the street that want pedestrian signals. The occurs twice a day (before & after school), 5 days a week, 10 months per year. Except there are holidays when there may be no activities. And there are evenings where there may be activities like sporting events, parent/teacher meetings etc. And the occasional weekend event. and so on. A city may have civic buildings, commercial plazas, construction sites, etc, where these events crop up. Plus roadways have to accommodate bus and bicycle traffic in addition to automobile traffic. Plus certain intersections may back up according to meteorological conditions (for example, blinding conditions caused by a low-setting sun that happens during certain parts of the year). Trying to synchronize to all of this, in addition to incorporating sensor information and pedestrian switching becomes very complex very quickly.
- hammock 14y ago>It would seem that sensors would be most useful with lower traffic volumes, and synchronization better for rush hour. Perhaps using each system at different times of the day would be theoretically optimal. Most cities do this. I live in chicago, that's how it works. Note that you can also combine sensors simultaneously with timing in certain cases- for example whether to allow an advance green for a left-turn lane or not (if there are cars in it, advance green, otherwise, normal green for both directions of traffic on that road. No change in when the next red comes)
- gamblor956 14y agoThe pedestrian buttons are not placebo buttons, they actually work. Generally, the pedestrian signal is set to activate in cycles of X minutes (where X is usually a multiple of 2, 3, or 5) but only if it the pedestrian button has been pressed. If the button is not pressed before the cycle begins, the pedestrian signal does not activate on that cycle but will activate on the next cycle. (For example, see dkl's comment.) In synchronized systems, the pedestrian light works the same way--this is why some intersections will sometimes have red lights for every direction of traffic even though there are no pedestrians.
- lutusp 14y ago> The pedestrian buttons are not placebo buttons, they actually work. Not if the system is grid-synchronized. In places where the system has more than one mode and adapts to the overall traffic amount, yes, but only when the system isn't in synchronize mode.