This cannot be addressed quickly with a simple timing change alone. Working the signal manually, it is possible to overcome some of these difficulties by dynamically expanding and shrinking certain timing intervals. Key word here is dynamic. Things change rapidly from cycle to cycle. What works for one cycle would back traffic up on Battery Street needlessly for other cycles, for instance. Since these conditions can be seen and largely mitigated while standing there and working the signal manually, the diagnosis is to increase detection capability and controller flexibility to automate these timing changes in response to conditions. Except for pedestrian buttons, which give pedestrians 9 seconds of advance walk before turning College Street signals green, the signal is blind to any other conditions. Adding vehicle detection to College Street, queue detection to Battery Street, and pedestrian queue detection (# people waiting/crossing) would provide information to make timing changes on the fly. A more sophisticated controller and cabinet are necessary to make use of this information. These things are expensive. As we go down this path, it makes sense to think about a complete signal upgrade. Sharing street light poles with Burlington Electric gives us places to mount new sensors and signals, but also requires new underground conduit to run cables to these devices. A low-end estimate of a complete retrofit is about $150k. Over $200k would be a safer number to use. At this level of spending, we need to make sure that the roadway is not going to change before doing all the necessary dirt work. This project was discussed as an option in our latest round of capital signal projects earlier this year. It is currently deferred, as discussions of whether to change Battery Street are ongoing. A firm yes/no answer to the change question, plus plans of road geometry changes, if any, are needed before we can make major signal changes here. Going to mark this as a duplicate of an earlier SCF that involves these same issues.

This issue has been marked as a duplicate of issue 2765710.

If you are already receiving notifications regarding this issue,
you will now receive updates regarding issue 2765710.