AGENDA - NCITE



NCITE Traffic Control Committee Meeting MinutesSeptember 17, 2019 – 8:00 to 10:00 a.m.MnDOT Water’s EdgeFYA OperationsTopic 1: Lead/lag operations with Protected-Permissive FYA (soft trap)MnDOTWill use lead/lag, but prefers not to unless there is a real operational benefitSoft trap exists along Robert streetRemoved soft trap from a few intersections due to complaints and some drivers not paying attention to the signal head over their laneDakota CountyUses lead/lagNo complaints related to safetyPrefers lead/lead unless needed for two-way progressionDon’t have any dual left-turns so might not be as much of an issueWashington CountyHas lead/lag, but having more thoughts on it due to the national discussion on itHennepin CountyUses lead/lag when it makes sense for two-way progressionRemoved lead/lag at one intersection due to safety concernCarver CountyFollows MnDOT practices and guidelinesGeneral DiscussionLouvers can be used on signal head to block view from adjacent but might not work perfectly as the driver will notice cars slowing down. Also concern with snow build up on LEDs.Soft trap is a national discussionNebraska, Texas, Iowa use horizontal signals which can also create confusion with FYATopic 2: POOFYA practicesMnDOTMnDOT committee meeting to discuss different topics. Some warrants that has been discussed are:Omit FYA during the Walk and FDWUse on higher roadway speedUse with longer crossing distanceDon’t at smaller intersections with regular pedestrian activityMostly used at dual leftsCan’t implement POOFYA with shared left-turn/through laneWashington CountyNot using anywhere“Reverse” POOFYA at a T intersection where the arrow flashes yellow if there is a pedestrian indicationMore inclined to go with LPI over POOFYAHard to implement in the coordinated signal systemDakota CountyAdds delay to FYA to establish pedestrian in intersection rather than POOFYABloomingtonTried this with an EOS controller at an intersection and was having issuesGeneral discussionCounter measures for safetyCat tracks to have drivers focus on one part of the crossingMinneapolis is looking at hard centerlines (e.g. vertical delineators to force sharper turns – concern with plowing)The crossing conflict exists when dwelling in Phases 2 and 6, unless Ped Reservice is disabled and the ped phases aren’t displayed in the middle of the phasesTopic 3: Delay of FYAMnDOTDoesn’t delay FYAYellow arrow should be better understood than green ball and there’s not delay with green ballWashington CountyDoesn’t use, but wouldn’t think more than 2 seconds would be neededHennepin County4 secondsDakota County5 sec on mainline2 sec for minor roadLooking to reduce the delay, especially during overnight operationsBloomington4 seconds to match Hennepin CountyRound RobinTH 65/Viking Blvd signalized RCUT is operational, but can’t run FYA due to left-turn angleCoordination and standards needed between Roadway designer and signal designerMnDOT looking at utilizing safety data to help with FYA decisionsAlso looking at geometric data and implications that has to FYA operationsWhy don’t we always lag FYA by default?That’s the natural order (left-turns yield to oncoming traffic and only bring up the arrow if there aren’t gaps)With 5 signal head, lag was not possible so lead became default but this isn’t needed nowMnDOT committee is have discussion on ‘No Right turn on Red’Rural Intersection conflict warning systems report was just published ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download