1 / 21

How to identify what resources should be considered in the SCEA

How to identify what resources should be considered in the SCEA. Surface/ Groundwater. Farmlands. Wetlands. Community. Parks. Wildlife. Cultural Resources. Overview. Scoping and initial SCEA activities Initial SCEA resource identification Data Sources.

zarifa
Download Presentation

How to identify what resources should be considered in the SCEA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. How to identify what resources should be considered in the SCEA Surface/ Groundwater Farmlands Wetlands Community Parks Wildlife Cultural Resources

  2. Overview • Scoping and initial SCEA activities • Initial SCEA resource identification • Data Sources

  3. Scoping and Initial SCEA Activities • Incorporate into project planning process during preliminary alternatives development. • Identify environmental resources and SCEA issues in the project area. (Directly impacted resources are the starting point. More resources may be identified based on secondary impacts or if new alternatives, with other/new impacts, are looked at.) • Coordinate with resource agencies to: • - obtain input on resource identification and analysis methodologies • - inform them of missing information which could become an obstacle • - seek their approval

  4. Initial SCEA Resource Identification • Identify resources directly impacted by each proposed project alternative. • Identify potential secondary impacts from project alternatives in coordination with local planners and developers.

  5. Prepare SCEA Resource Matrix for Presentation at the Interagency Field Review • Identify readily available data sources. • Create resource matrix identifying: • - each resource • - data availability • - data units • - data sources • - analysis methodology (Modules 4 & 5) Identify Direct Impacts Identify Potential Secondary Impacts Determine Data Availability Develop SCEA Resource Matrix

  6. Key Data Sources

  7. Middle River Employment Center Access Study (MRECAS)

  8. Middle River Employment Center Access Study (MRECAS) Project Purpose and Need • Purpose of the Project: • To improve access from regional transportation network to enable planned economic development. • To increase utilization of established employment areas in the Middle River Employment Center. • Need for the Project: • There is a need for a sufficient level of access and mobility for the Employment Center. • Support of economic development. • Existing roads in the study area lack the capacity and continuity to provide adequate access to the entire MREC from the existing highway network.

  9. Middle River Employment Center Access Study (MRECAS) Study Area Boundary

  10. Middle River Employment Center Access Study (MRECAS) Resource Matrix Note: Strikethroughs indicate items that are inappropriately listed as SCEA resources.

  11. Middle River Employment Center Access Study (MRECAS) Rationale for Removing Items From the SCEA Rationale for Retaining Resources in the SCEA NOTE: “Disruption to Community” as it is termed in the MRECAS environmental impact matrix, is not a resource and was not analyzed in the SCEA. However, “communities” is considered a resource and can be analyzed as such in other SCEAs.

  12. MD 5 - Hughesville Transportation Improvement Project

  13. MD 5 - Hughesville Transportation improvement Project MD 5 Location Map

  14. MD 5 - Hughesville Transportation Improvement Project MD 5 Direct Impacts Study Area

  15. MD 5 - Hughesville Transportation Improvement Project Project Purpose and Need • The purpose of the MD 5 - Hughesville Transportation Improvement Project is to alleviate congestion and to address safety hazards along MD 5 at the MD 5/MD 231 intersection in the Hughesville area. MD 5 through Hughesville experiences a high accident rate due to a constrained typical section, limited capacity at the MD 5/MD 231 intersection, and numerous driveways with direct access onto MD 5. • Traffic congestion and safety along MD 5 during morning and evening rush hours have become significant problems in recent years and conditions are expected to increase to 85 percent with the projected growth by year 2020 near Washington D.C., Lexington Park, and along the MD 5 corridor. The MD 5/MD 231 intersection currently operates at LOS "F" in the evening peak hour.

  16. MD 5 - Hughesville Transportation Improvement Project Alternatives Retained for Detailed Study No-Build - This alternative would not provide any significant improvements to MD 5 in the Hughesville area. Minor improvements would occur as part of normal maintenance and safety operations. These improvements would not measurably affect roadway capacity or reduce the accident rate. Possible minor improvements include items such as curbing, sidewalks, striping, signing, lighting, rumble strips and additional drainage.

  17. MD 5 - Hughesville Transportation Improvement Project Alternatives Retained for Detailed Study Widen Existing MD 5 - This alternative proposes widening existing MD 5 to a seven-lane curbed section, with two through lanes and an auxiliary right turn lane for both the northbound and southbound directions and a continuous center left turn lane. This alternative would have three northbound and southbound lanes near the MD 5/MD 231 intersection. The posted speed limit would be 40 miles per hour (mph), similar to existing MD 5. This alternative requires the additional widening of MD 5 at the MD 5/MD 231 intersection. The widening creates the necessary storage to efficiently move peak hour traffic through the MD 5/MD 231 intersection.

  18. MD 5 - Hughesville Transportation Improvement Project Alternatives Retained for Detailed Study Eastern Bypass - This alternative is a four-lane divided highway located east of MD 5 from south of Gallant Green Road to north of Carrico Mill Road. The Alternative 5 design speed is 60 mph. This alternative bypasses the town of Hughesville to the east. Alternative 5 is access controlled, providing only three points of access to the town of Hughesville. These points of access are at either end of the bypass and at MD 231, where a diamond interchange is proposed. The controlled-access Alternative 5 would safely and efficiently accommodate the 90 percent through traffic projected for this facility. Construction of the bypass will also safely accommodate traffic on existing in Hughesville. By intercepting the high volume of through traffic traveling between Calvert County and Lexington Park prior to Hughesville.

  19. MD 5 - Hughesville Transportation Improvement Project Summary of Direct Impacts As Presented in the EA

  20. MD 5 - Hughesville Transportation Improvement Project Summary of Direct Impacts As Presented in the EA (Not Appropriate for SCEA) Note: Strikethroughs indicate data sources that should not be included in SCEA Assessment

  21. MD 5 - Hughesville Transportation Improvement Project Rational for Including or Excluding Resources from the SCEA

More Related