1. Context Sensitive Solutions Focus Group Session Lynn Purnell Parsons Brinckerhoff Prosperity Church Road Corridor December 8, 2005

2. Context Sensitive Solutions Context Sensitive Solutions is a collaborative, interdisciplinary approach, that involves all stakeholders to develop a transportation facility that fits its physical setting and preserves scenic, aesthetic, historic and environmental resources, while maintaining safety and mobility. FHWA CSD Website Homepage

3. What is CSS not? Not a product; it is a process Not just design Not easy

4. What does CSS look like? Understand & define the Context before design begins Engage, listen & react to communities Apply flexible designs

5. How is CSS different? Involve multi-disciplinary team early Understand valued resources before designing Involve stakeholders with open, continuous communications Balance transportation need with community values Employ roadway design that is creative, flexible and safe

6. Design Excellence-Standard Practice Safety Mobility Enhancement of the Natural Environment Preservation of Community Values

7. Qualities of Excellence in Design Satisfies purpose & need as defined by stakeholders Safe facility for user & community In harmony with the community and the natural & built environment Efficient and effective use of resources Minimal disruption to the community Lasting added value to the community

8. Every Project has a Context

9. Define the Context at beginning Transportation Context Community Context Environmental Context

10. Transportation Context Functional Classification System Context: regional or local Setting: urban, rural, suburban

11. Community Context Demographics: community or social groups Particular characteristics to be preserved or enhanced Historic features that are valued

12. Environmental Context Ecology & wetlands Cultural resources, including historic sites Farmland, parkland, etc. Noise Receptors

13. What is Purpose & Need? Seek input from technical team, public officials, focus groups & others. Seek consensus on problems and needs

14. Consensus Consensus does not mean that everyone agrees, but that groups and individuals can live with a proposal.

15. M-463, Jackson, MS Project Goals Reduce congestion Existing 2-lane volumes = 1,900 to 19,900 vpd. Projected = 9,600 to 33,300 vpd Improve safety (limited sight distance)

16. M-463 Context Commercial around interchange Suburban Rural Historic properties Scenic view- sheds Major growth potential

17. M-463 Context Constraints Development close to roadway Scenic property close to roadway Historic properties need to be avoided Historic Church congregation objects to visual impacts of an “interstate highway”

18. M-463 Existing Conditions Plan Section Church Silo Church

19. Proposed with DOT Criteria Plan Section Church Silo Lake

20. M-463 CSS Objectives Save silo and lake with narrower footprint Reduce visual impact by hiding the new lanes

21. M-463 Design Considerations Change the requirement for a 90-ft. median Change design speed Accept increased travel time

22. M-463 Design Considerations Construct the new lane at a lower elevation than the existing roadway

23. M-463 CSS Results Preserved view-shed Citizens and DOT accept increased travel time as a positive trade-off Citizens gain respect for DOT because it listened to their concerns Project moves forward at reduced cost