Work Order Created: 16911

Work Order Acknowledged and Assigned

I was on the intersection at 1:00 p.m check vehicle detection from Edwards St side for around 45 minutes at that time traffic signal work normal and no missing any cars from that approach.Thanks for you patience.

Yet this problem has been intermittent for months. Being at the intersection for days might not see any problem, yet it happens. This is a recently installed traffic light, so perhaps it keeps some kind of diagnostic history that can be accessed? Google Maps or Wayz might give some indication of how often there's a problem.
NHPD and especially NHFD because of the Whitney Ave fire station at the bottom of Edwards can't be happy if they come up that hill to get to an incident on the other side of Prospect in a hurry, because the road is far too narrow for them to get past a long queue of stationary traffic safely at speed.

Peter, thank you for the update. We're working with our signal crew and presently exploring ways to further investigate this concern.

At 11:53, there was a queue of 18 cars at the light on Edwards. I was going the other way and it's just before lunchtime, so I can't be certain the problem was active just then, however coming from the other side of Prospect, I saw the light change to red from the bottom of the hill, I arrived, there was a pedestrian sequence, and then I was able to go almost immediately. Let me know if it's not helpful to have this kind of anecdotal data, otherwise I'll note it as I see it.

Alder from ward 21 here - any update on this issue?

I've reached out to our signal superintendent and am awaiting an update.

I've stopped using that junction whenever possible. I've started going into town along Whitney instead of down Prospect until I hear that they've determined to their satisfaction that there is or isn't a problem. The few times I haven't been able to avoid going through that light I haven't seen any problem.
My main concern is that, as I say above, given that this problem definitely happened but couldn't be investigated because it was intermittent, surely there should be a way to systematically investigate, for a new traffic light, what the exact history has been for say the last few days. If they've found a way to monitor this traffic light fairly continuously and there's been no problem for a few weeks, say, then I'm happy to see this issue closed.
Thanks for paying attention! Sorry not to be more helpful.

Doesn't the Transportation, Traffic and Parking Department utilize an ATMS (Advanced Traffic Management System)? If so, it should be easy to check the traffic signal controller data log files. The files should contain the history of exactly when a traffic signal was red and for how long. Just check the data files for January 18, 2018 from 09:45AM to 10:15AM. I'm guessing someone employed with TT&P already checked the files and found no anomalies, but if nobody did, it might be a good idea to do so. If there is anything I can do to help, just let me know.

On Monday, February 12th at 16:35, I crossed Edwards at Prospect with a pedestrian light that someone else had requested. It was approximately 3 minutes later before the light turned to green for Edwards traffic (it was about the time it took someone whose progress I watched to walk from Prospect as far as St Ronan, which appears to be approximately three minutes; I didn't measure the time using a watch). My impression was that just one green light cycle was missed for Edwards on this occasion, whereas I'm fairly sure that at least two cycles were missed on 1/18/2018 before I U-turned. [Surely Edwards isn't ever supposed to wait anywhere near 3 minutes for a green light?]
Apparently the problem can be of different durations. It seems possible, but only on the basis of this one observation, that the problem may be associated with precisely which pedestrian walk requests are placed and their timings.
More anecdotal evidence isn't what you need to resolve this, but its urgency shouldn't be in doubt.

Hi Peter,
You have a very good point and I've noticed quite a few tickets submitted via this platform claiming similar time lag issues with traffic signals at other intersections. This issue is a technical one which should easily be resolved by the IT pros in the TT&P department. While it was very admirable of someone employed with TT&P to go to the intersection and stand there for 45 minutes and watch the traffic signal intervals, we can do better than that. Let's think smarter, not harder.

Douglas Hausladen is the Director of our Transportation, Traffic and Parking Department. I have confidence he already has a plan to authenticate the claims of excessive time lags and is doing what has to be done to resolve this. Let's give him a little more time to finish working on it.

Currently, it appears the position of "Signal Superintendent" at TT&P remains vacant, but there must be someone covering those duties until someone is hired.

It would really would be great if someone at TT&P would post a comment on what else is being done to resolve this... or how statistical analysis of vehicular and pedestrian traffic dictate that nothing needs to be changed.

Hi All - I followed up with Transportation Traffic and Parking about this and they said that they believe everything is working and that the backups at this intersection are due to increased traffic volume headed towards new businesses at Science Park.

Thanks for following up, Steve. I haven't seen the problem for a while, but that may just be because I've been mostly avoiding going through the intersection from Edwards.
If they haven't diagnosed any problem and have made no changes, then I don't believe it, TBH. The last time I saw the problem was not at rush hour at all.
OTOH, if they are sure that the backups are solely because of traffic volume towards Science Park (which I can well believe has increased), then I guess they could think about setting the schedule to give slightly more priority to Edwards in the morning rush hours (though that suggestion assumes that they have hour-by-hour fine grained control, and of course the intersection is not easy to code for given its off-kilter geometry).

Thank you for letting us know; please repost if it's still an issue. TT&P has addressed;