132 nd street se mid block
play

132 nd Street SE Mid-Block Crossing May 14, 2019 Agenda 132 nd - PowerPoint PPT Presentation

132 nd Street SE Mid-Block Crossing May 14, 2019 Agenda 132 nd Street SE (SR96) background Engineering Options Grant Application 2 Background 3 Background Residential/Commercial uses 35,000 ADT (40,000 ADT by 2040)


  1. 132 nd Street SE Mid-Block Crossing May 14, 2019

  2. Agenda • 132 nd Street SE (SR96) background • Engineering Options • Grant Application 2

  3. Background 3

  4. Background Residential/Commercial uses • 35,000 ADT (40,000 ADT by 2040) • Four 11-foot lanes with TWLTLs and • right turn lanes 4

  5. Background MP 2.24 5

  6. Background 6

  7. Background October 2017 – WSDOT ped counts • 7

  8. Background - Crashes Since 2013, there have been seven (7) car vs. pedestrian crashes in this area: 2018 - during hours of darkness, a • vehicle hit a pedestrian crossing the road, possible injury to pedestrian 2017 – Three crashes occurred, one • during hours of darkness and two during dawn/ dusk; two serious injury & one classified as ‘unknown injury’ 8

  9. Crashes, continued… 2016 – One crash occurred during • daylight hours with possible injury 2013 – One crash occurred during • daylight hours with suspected minor injuries 9

  10. Option (Wall) 10

  11. Option (barrier) 11

  12. Option (signage) 12

  13. Option (RRFBs) 13

  14. Option (Pedestrian Signal) 14

  15. Option (HAWK Signal) 15

  16. Grant Application 2018 Pedestrian and Bicycle Program • Schedule • $675,000 Award ($75,000 match) • HAWK Signal (Pedestrian Signal) • 16

  17. 132 nd Street SE Mid-Block Crossing Questions and Comments • 17

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend