12.07.2015 Views

Environmental Assessment for I-90 Beck Road ... - City of Post Falls

Environmental Assessment for I-90 Beck Road ... - City of Post Falls

Environmental Assessment for I-90 Beck Road ... - City of Post Falls

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>Prepared For:Federal Highway Administration&Idaho Transportation DepartmentProject # A010(963); Key Number 010963June 2011


TABLE OF CONTENTSCHAPTER 1: PURPOSE AND NEED ........................................................................................... 1-11.1 Why Conduct an E nvironmental As ses sment? ............................................................................. 1-11.2 Project B ackground and History ..................................................................................................... 1-11.3 P roject T echnical Advis ory C ommittee .......................................................................................... 1-41.4 P roject T eam ...................................................................................................................................... 1-51.5 Project Purpose ................................................................................................................................. 1-51.6 Project Need ...................................................................................................................................... 1-51.7 Interrelated and Interdependent P rojects ....................................................................................... 1-71.7.1 Past, Planned, and On-going Projects ................................................................................................... 1-71.7.2 Local Area Development ....................................................................................................................... 1-9CHAPTER 2: DESCRIPTION OF ALTERNATIVES, INCLUDING PROPOSED ACTION ............ 2-12.1 Introduction ....................................................................................................................................... 2-12.2 Alternatives Development ................................................................................................................ 2-12.2.1 Previous Studies .................................................................................................................................... 2-12.2.2 Alternatives Evaluation .......................................................................................................................... 2-32.2.3 Summary <strong>of</strong> the Alternatives Evaluation ................................................................................................ 2-4Identification <strong>of</strong> Screening Criteria .................................................................................................. 2-4Level-I Screening Criteria ........................................................................................................ 2-4Level-II Screening Criteria ....................................................................................................... 2-42.2.4 Range <strong>of</strong> Alternatives ............................................................................................................................ 2-52.2.5 Screening <strong>of</strong> Alternatives ....................................................................................................................... 2-6Level-I Screening ........................................................................................................................... 2-6Level-II Screening .......................................................................................................................... 2-6Alternatives Eliminated ............................................................................................................ 2-6Further Analysis ...................................................................................................................... 2-8Transportation System Management ........................................................................................... 2-102.3 Alternatives Carried Forward <strong>for</strong> Detailed S tudy ......................................................................... 2-102.3.1 No-Build Alternative ............................................................................................................................. 2-122.3.2 Proposed Action (Pointe Parkway Standard Diamond Interchange Alternative) ................................. 2-12CHAPTER 3: AFFECTED ENVIRONMENT, ENVIRONMENTAL CONSEQUENCES, ANDMITIGATION ................................................................................................................................. 3-13.1 Introduction ....................................................................................................................................... 3-13.2 Cultural R esources ........................................................................................................................... 3-13.2.1 Affected Environment ............................................................................................................................ 3-1Cultural Properties .......................................................................................................................... 3-1Coeur d’Alene Tribe ....................................................................................................................... 3-43.2.2 <strong>Environmental</strong> Consequences ............................................................................................................... 3-4No-Build.......................................................................................................................................... 3-4Proposed Action ............................................................................................................................. 3-4Direct Impacts ......................................................................................................................... 3-4Indirect Impacts ....................................................................................................................... 3-5Cumulative Impacts ................................................................................................................. 3-5Mitigation ................................................................................................................................. 3-53.3 S ection 4(f) and S ection 6(f) R esources ......................................................................................... 3-53.3.1 Affected Environment ............................................................................................................................ 3-5Section 4(f) Resources ................................................................................................................... 3-5Section 6(f) Resources ................................................................................................................... 3-73.3.2 <strong>Environmental</strong> Consequences ............................................................................................................... 3-7No-Build.......................................................................................................................................... 3-7Proposed Action ............................................................................................................................. 3-73.4 Wetlands and Waters <strong>of</strong> the United S tates ..................................................................................... 3-83.4.1 Affected Environment ............................................................................................................................ 3-83.4.2 <strong>Environmental</strong> Consequences ............................................................................................................... 3-9No-Build.......................................................................................................................................... 3-9Proposed Action ............................................................................................................................. 3-9Direct Impacts ......................................................................................................................... 3-9Indirect Impacts ..................................................................................................................... 3-10Cumulative Impacts ............................................................................................................... 3-10I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>iProject No. A010(963)June 2011


Mitigation ............................................................................................................................... 3-103.5 B iological R esources ...................................................................................................................... 3-103.5.1 Affected Environment .......................................................................................................................... 3-10Vegetation .................................................................................................................................... 3-10Noxious Weeds ..................................................................................................................... 3-11Fish and Wildlife ........................................................................................................................... 3-12Species <strong>of</strong> Concern ............................................................................................................... 3-12Candidate Species ................................................................................................................ 3-12Threatened and Endangered Species .......................................................................................... 3-12Migratory Bird Act ......................................................................................................................... 3-13Bald Eagle and Golden Eagle Protection Act ............................................................................... 3-133.5.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-13No-Build........................................................................................................................................ 3-13Proposed Action ........................................................................................................................... 3-13Direct Impacts ....................................................................................................................... 3-13Indirect Impacts ..................................................................................................................... 3-15Cumulative Impacts ............................................................................................................... 3-16Mitigation ............................................................................................................................... 3-163.6 Surface Water, Floodplains, and Groundwater ............................................................................ 3-163.6.1 Affected Environment .......................................................................................................................... 3-16Surface Water .............................................................................................................................. 3-16Water Quality Documents and Permits......................................................................................... 3-17Wild and Scenic Rivers................................................................................................................. 3-19Stormwater Management ............................................................................................................. 3-19Floodplains ................................................................................................................................... 3-19Groundwater ................................................................................................................................. 3-19Spokane Valley Rathdrum Prairie Aquifer ............................................................................. 3-19Potable and Other Water Sources ................................................................................................ 3-233.6.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-25No-Build........................................................................................................................................ 3-25Proposed Action ........................................................................................................................... 3-25Direct Impacts ....................................................................................................................... 3-25Indirect Impacts ..................................................................................................................... 3-26Cumulative Impacts ............................................................................................................... 3-26Mitigation ............................................................................................................................... 3-283.7 Socioeconomics and Land Use ..................................................................................................... 3-283.7.1 Affected Environment .......................................................................................................................... 3-28Population and Economics ........................................................................................................... 3-28Community Cohesion ................................................................................................................... 3-30<strong>Environmental</strong> Justice ........................................................................................................... 3-30Public Services ............................................................................................................................. 3-30Transit ................................................................................................................................... 3-30Fire Departments................................................................................................................... 3-30Law En<strong>for</strong>cement .................................................................................................................. 3-30Schools ................................................................................................................................. 3-32Traffic, Access, and Safety ........................................................................................................... 3-33Land Use ...................................................................................................................................... 3-333.7.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-36No-Build........................................................................................................................................ 3-36Proposed Action ........................................................................................................................... 3-37Direct Impacts ....................................................................................................................... 3-37Indirect Impacts ..................................................................................................................... 3-38Cumulative Impacts ............................................................................................................... 3-39Mitigation ............................................................................................................................... 3-393.8 Nois e................................................................................................................................................. 3-403.8.1 Affected Environment .......................................................................................................................... 3-403.8.2 Existing Conditions .............................................................................................................................. 3-413.8.3 <strong>Environmental</strong> Consequences ............................................................................................................. 3-46No-Build........................................................................................................................................ 3-46Proposed Action ........................................................................................................................... 3-46Direct Impacts ....................................................................................................................... 3-46Indirect Impacts ..................................................................................................................... 3-47Cumulative Impacts ............................................................................................................... 3-47I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>iiProject No. A010(963)June 2011


Mitigation ............................................................................................................................... 3-473.9 Prime Farmland ............................................................................................................................... 3-493.9.1 Affected Environment .......................................................................................................................... 3-493.9.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-53No-Build........................................................................................................................................ 3-53Proposed Action ........................................................................................................................... 3-53Direct Impacts ....................................................................................................................... 3-53Indirect Impacts ..................................................................................................................... 3-53Cumulative Impacts ............................................................................................................... 3-53Mitigation ............................................................................................................................... 3-533.10 Air Quality ........................................................................................................................................ 3-533.10.1 Affected Environment .......................................................................................................................... 3-533.10.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-54No-Build........................................................................................................................................ 3-54Proposed Action ........................................................................................................................... 3-54Direct Impacts ....................................................................................................................... 3-54Indirect Impacts ..................................................................................................................... 3-55Cumulative Impacts ............................................................................................................... 3-55Mitigation ............................................................................................................................... 3-563.11 E arth R esources .............................................................................................................................. 3-563.11.1 Affected Environment .......................................................................................................................... 3-563.11.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-57No-Build........................................................................................................................................ 3-57Proposed Action ........................................................................................................................... 3-57Direct Impacts ....................................................................................................................... 3-57Indirect Impacts ..................................................................................................................... 3-57Cumulative Impacts ............................................................................................................... 3-57Mitigation ............................................................................................................................... 3-573.12 Hazardous Materials ....................................................................................................................... 3-573.12.1 Affected Environment .......................................................................................................................... 3-583.12.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-58No-Build........................................................................................................................................ 3-58Proposed Action ........................................................................................................................... 3-58Direct Impacts ....................................................................................................................... 3-59Indirect Impacts ..................................................................................................................... 3-59Cumulative Impacts ............................................................................................................... 3-59Mitigation ............................................................................................................................... 3-593.13 Visual R esources ............................................................................................................................ 3-603.13.1 Affected Environment .......................................................................................................................... 3-60General Landscape Character ..................................................................................................... 3-61Views from I-<strong>90</strong> and Centennial Trail ........................................................................................... 3-62Views <strong>of</strong> I-<strong>90</strong> and <strong>Beck</strong> <strong>Road</strong> ....................................................................................................... 3-643.13.2 <strong>Environmental</strong> Consequences ............................................................................................................. 3-65No-Build........................................................................................................................................ 3-65Proposed Action ........................................................................................................................... 3-65Direct Impacts ....................................................................................................................... 3-65Indirect Impacts ..................................................................................................................... 3-65Cumulative Impacts ............................................................................................................... 3-65Mitigation ............................................................................................................................... 3-65CHAPTER 4: COMMENTS AND COORDINATION...................................................................... 4-14.1 Public Open Hous e ........................................................................................................................... 4-14.1.1 Notification and Contact ........................................................................................................................ 4-14.1.2 Meeting Summary ................................................................................................................................. 4-14.2 Technical Advisory Committee Meetings ....................................................................................... 4-14.3 Agency Consultation/Coordination ................................................................................................. 4-2CHAPTER 5: DISTRIBUTION LIST .............................................................................................. 5-1CHAPTER 6: LIST OF CONTRIBUTORS AND PREPARERS ..................................................... 6-1CHAPTER 7: REFERENCES ....................................................................................................... 7-1I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>iiiProject No. A010(963)June 2011


APPENDIX A – ITD FORMS ......................................................................................................... A-1APPENDIX B – 4(F) DE MINIMIS EVALUATION ......................................................................... B-1APPENDIX C – SUPPORTING DATA .......................................................................................... C-1APPENDIX D – SCOPING RESPONSES ..................................................................................... D-1LIST OF FIGURESFigure 1-1. Project Area ..................................................................................................................................................... 1-2Figure 1-2. Aerial Photograph <strong>of</strong> Project Area ................................................................................................................... 1-3Figure 1-3. Projected Population Growth in <strong>Post</strong> <strong>Falls</strong>, 2000-2030 .................................................................................... 1-6Figure 1-4. Regional Planned Intersection and <strong>Road</strong>way Improvements ......................................................................... 1-10Figure 2-1. Alternatives Screening Process ....................................................................................................................... 2-2Figure 2-2. Alternatives Considered <strong>for</strong> Level II Screening ................................................................................................ 2-7Figure 2-3. Proposed Action: Pointe Parkway Standard Diamond Interchange Alternative ............................................. 2-11Figure 2-4. Proposed Action Interchange Detail: Pointe Parkway Standard Diamond Interchange Alternative ............... 2-14Figure 2-5. Proposed Action Typical Cross Sections: Pointe Parkway Standard Diamond Interchange Alternative ........ 2-15Figure 3-1. Area <strong>of</strong> Potential Effect .................................................................................................................................... 3-2Figure 3-2. Centennial Trail south <strong>of</strong> I-<strong>90</strong>, looking west ..................................................................................................... 3-7Figure 3-3. Jacklin Seed fire-suppression pond ................................................................................................................. 3-8Figure 3-4. Spokane River south <strong>of</strong> project area ................................................................................................................ 3-9Figure 3-5. View <strong>of</strong> Spokane River from project area just south <strong>of</strong> Jacklin Seed (looking west) ...................................... 3-16Figure 3-6. Surface Water in Project Area ....................................................................................................................... 3-18Figure 3-7. FEMA Floodplains in Project Area ................................................................................................................. 3-21Figure 3-8. Spokane Valley Rathdrum Prairie Aquifer in Relation to the Project Area ..................................................... 3-22Figure 3-9. Wells in the Project Area ................................................................................................................................ 3-24Figure 3-10. Water tower near <strong>Beck</strong> <strong>Road</strong> ....................................................................................................................... 3-25Figure 3-11. Conceptual-Level Stormwater Management <strong>for</strong> Proposed Action ............................................................... 3-27Figure 3-12. Unemployment Rates .................................................................................................................................. 3-29Figure 3-13. Neighborhood and Area Services Map ........................................................................................................ 3-31Figure 3-14. <strong>Post</strong> <strong>Falls</strong> Future Land Use Map ................................................................................................................. 3-34Figure 3-15. Kootenai County Zoning Map ...................................................................................................................... 3-35Figure 3-16. Noise Monitoring Locations and Noise Prediction (Receptor) Sites ............................................................. 3-43Figure 3-17. NRCS Soil Designations in Project Area ...................................................................................................... 3-52Figure 3-18. Waste storage at Jacklin Seed .................................................................................................................... 3-58Figure 3-19. View looking west from W. Pointe Parkway ................................................................................................. 3-62Figure 3-20. View looking east from W. Pointe Parkway .................................................................................................. 3-62Figure 3-21. Visual Resource Viewpoints ........................................................................................................................ 3-63Figure 3-22. View from Centennial Trail, looking west toward I-<strong>90</strong> .................................................................................. 3-64Figure 3-23. View from W. Pointe Parkway, looking north toward N. <strong>Beck</strong> <strong>Road</strong>............................................................. 3-64Figure 3-24. Visual Rendering Looking East .................................................................................................................... 3-66Figure 3-25. Visual Rendering Looking West ................................................................................................................... 3-67LIST OF TABLESTable 1-1. Projected 2030 LOS under No-Build Alternative ............................................................................................... 1-7Table 1-2. 2030 Regional Planned <strong>Road</strong>way Improvements ............................................................................................. 1-8Table 2-1. Planning Documents Relied Upon in the Alternatives Evaluation ..................................................................... 2-3Table 2-2. Level-I Screening Criteria .................................................................................................................................. 2-4Table 2-3. Level-II Screening Criteria ................................................................................................................................. 2-5Table 2-4. 2030 Traffic Operations Comparison <strong>of</strong> Alternatives ......................................................................................... 2-9Table 2-5. Proposed Action <strong>Road</strong>way Improvements ...................................................................................................... 2-13Table 3-1. Summary <strong>of</strong> Cultural Resources in the APE ..................................................................................................... 3-3Table 3-2. Noxious Weed Species Known or Reported to Occur in Kootenai County ..................................................... 3-11Table 3-3. Federally-listed ESA Species in Kootenai County (USFWS and NMFS) ........................................................ 3-13Table 3-4. Summary <strong>of</strong> Wells in the Project Area............................................................................................................. 3-23Table 3-5. Racial Make-up <strong>of</strong> Population in <strong>Post</strong> <strong>Falls</strong> (Census 2005-2009) ................................................................... 3-29Table 3-6. Schools, Parks, and Services near or within Proposed Project ....................................................................... 3-32Table 3-7. FHWA and ITD Noise Abatement Criteria ....................................................................................................... 3-41Table 3-8. Monitored and Predicted Noise Levels in the Project Area ............................................................................. 3-42Table 3-9. Predicted Peak Hour Sound Levels (Leq) <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange Project .................................. 3-44Table 3-10. Summary <strong>of</strong> Soils and Prime Farmland in the Project Area .......................................................................... 3-51Table 4-1. Comments Received During Scoping Period .................................................................................................... 4-4I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>ivProject No. A010(963)June 2011


ACRONYMS AND ABBREVIATIONSAASHTOAmerican Association <strong>of</strong> State Highway and Transportation OfficialsADAAmericans with Disabilities ActAPEArea <strong>of</strong> Potential EffectBMPsBest Management PracticesCFRCode <strong>of</strong> Federal RegulationsdBADecibels, A-ratedDOTU.S. Department <strong>of</strong> TransportationEA<strong>Environmental</strong> <strong>Assessment</strong>EIS<strong>Environmental</strong> Impact StatementESAEndangered Species ActFEMAFederal Emergency Management AgencyFHWAFederal Highway AdministrationFIRMsFlood Insurance Rate MapsFONSIFinding <strong>of</strong> No Significant ImpactHDRHDR Engineering, Inc.I-<strong>90</strong> Interstate <strong>90</strong>IDAPAIdaho Administrative Procedures ActIDCDCIdaho Conservation Data CenterIDEQIdaho Department <strong>of</strong> <strong>Environmental</strong> QualityIDFGIdaho Fish and GameIDWRIdaho Department <strong>of</strong> Water ResourcesIJRInterchange Justification ReportITDIdaho Transportation DepartmentKMPOKootenai Metropolitan Planning OrganizationL eqContinuous noise level during any one hour periodLOSLevel <strong>of</strong> ServiceMSATsMobile Source Air ToxicsNACNoise Abatement CriteriaNAAQSNational Ambient Air Quality StandardsNEPANational <strong>Environmental</strong> Policy ActNMFSNational Marine Fisheries ServiceNPDESNational Pollutant Discharge Elimination SystemNRCSNatural Resource Conservation ServiceNRHPNational Register <strong>of</strong> Historic PlacesPFHD<strong>Post</strong> <strong>Falls</strong> Highway DistrictSHState HighwaySHPOState Historic Preservation OfficeSRTCSpokane Regional Transportation CouncilSTARState Tax Anticipated RevenueSTIPStatewide Transportation Improvement ProgramSVRPASpokane Valley Rathdrum Prairie AquiferSWPPPStormwater Pollution Prevention PlanTACTechnical Advisory CommitteeTMDLTotal Maximum Daily LoadTNMTraffic Noise ModelTSMTransportation System ManagementUSACEU.S. Army Corps <strong>of</strong> EngineersUSEPAU.S. <strong>Environmental</strong> Protection AgencyUSFWSU.S. Fish and Wildlife ServiceWSDOTWashington State Department <strong>of</strong> TransportationI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>vProject No. A010(963)June 2011


Chapter 1: Purpose and Need1.1 Why Conduct an <strong>Environmental</strong> <strong>Assessment</strong>?This document is the <strong>Environmental</strong> <strong>Assessment</strong> (EA) <strong>for</strong> the Interstate <strong>90</strong> (I-<strong>90</strong>) <strong>Beck</strong> <strong>Road</strong> Interchangeproject in <strong>Post</strong> <strong>Falls</strong>, Idaho. As required by the National <strong>Environmental</strong> Policy Act (NEPA), this EA assessesimpacts <strong>of</strong> the Proposed Action and the No Action (also referred to as No-Build) Alternative, and cumulativeimpacts that could occur as a result <strong>of</strong> other past, on-going or planned future projects in the area. NEPAregulations apply when there is a major federal action. For this project, the major federal action is theapproval by the Federal Highway Administration (FHWA) <strong>of</strong> an interchange connecting to an interstatehighway system (I-<strong>90</strong>).This EA provides evidence and analysis <strong>for</strong> determining whether to prepare an <strong>Environmental</strong> ImpactStatement (EIS) or Finding <strong>of</strong> No Significant Impact (FONSI). It satisfies NEPA disclosure requirements andserves as the NEPA compliance document <strong>for</strong> the Proposed Action. An EIS would be required if the EAdetermines that implementing the Proposed Action would result in significant impacts.This EA is organized as follows:• Chapter 1 – Purpose and Need• Chapter 2 – Description <strong>of</strong> Alternatives, Including Proposed Action• Chapter 3 – Affected Environment, <strong>Environmental</strong> Consequences, and Mitigation• Chapter 4 – Comments and Coordination• Chapter 5 – Distribution List• Chapter 6 – List <strong>of</strong> Contributors and Preparers• Chapter 7 – References1.2 Project Background and HistoryThe I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project (Idaho Transportation Department Project No. A010 (963),Key No. 010963) is located at the west end <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>, Idaho (Figure 1-1). An aerial photograph thatillustrates the location <strong>of</strong> the proposed interchange and its proximity to existing interchanges along I-<strong>90</strong> isshown in Figure 1-2. The project site is located approximately 1.2 miles west <strong>of</strong> the Pleasant View <strong>Road</strong>Interchange and approximately 1.2 miles east <strong>of</strong> the State Line <strong>Road</strong> Interchange. For purposes <strong>of</strong> this EA, the“project area” is defined as the Pleasant View <strong>Road</strong> Interchange to the east, the State Line <strong>Road</strong> Interchangeto the west, the Spokane River to the south and W. Seltice Way to the north (Figure 1-2). The ‘project site’refers to the proposed interchange location, which is further defined in Chapter 2.Regionally, I-<strong>90</strong> connects Kootenai County in Idaho andSpokane County in Washington. The stretch <strong>of</strong> I-<strong>90</strong> inthe project area is a four-lane highway. N. <strong>Beck</strong> <strong>Road</strong>south <strong>of</strong> W. Seltice Way is a north-south unpaved roadclassified by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> as a future minorarterial road (see box <strong>for</strong> definitions <strong>of</strong> roadclassifications). North <strong>of</strong> W. Seltice Way, N. <strong>Beck</strong> <strong>Road</strong>is a paved two-lane road with a rural classification as amajor collector. N. <strong>Beck</strong> <strong>Road</strong> is maintained by the <strong>Post</strong><strong>Falls</strong> Highway District (PFHD). W. Pointe Parkway, aneast-west road classified as a proposed minor arterial,provides access between the existing developments inthe project area and would connect to N. <strong>Beck</strong> <strong>Road</strong>.<strong>Road</strong> ClassificationsMajor Collector <strong>Road</strong> – Designed to collecttraffic from local roads and minor collectors totransmit that traffic onto arterials or the interstate.Major collectors should exhibit moderate speeds,carry between 2,000 and 5,000 vehicles per dayand have low accessibility.Minor Arterial <strong>Road</strong> – Serve higher trafficvolumes, with increased speeds and lowaccessibility. They should move traffic fromcollector streets, between areas and across acity or region, and are intended to carry between5,000 and 10,000 vehicles per day.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-1Project No. A010(963)June 2011


The area north and south <strong>of</strong> I-<strong>90</strong> near N. <strong>Beck</strong> <strong>Road</strong> is currently designated as industrial, but is identified as afuture commercial area in the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>’ Comprehensive Plan, which emphasizes major employmentcenters in the project area. Future commercial land uses are anticipated to extend along I-<strong>90</strong> from the stateboundary to the Pleasant View <strong>Road</strong> Interchange. This planned commercial use, along with regionalemployment and population growth would generate increased demand <strong>for</strong> access to and from I-<strong>90</strong>.Topography and the Spokane River limit development south <strong>of</strong> I-<strong>90</strong>. The proposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project would connect to public roads on both the north and south sides <strong>of</strong> I-<strong>90</strong>.An interchange in the N. <strong>Beck</strong> <strong>Road</strong> area at I-<strong>90</strong> is consistent with local and regional plans including:• <strong>Post</strong> <strong>Falls</strong> Transportation Master Plan, 2004• <strong>Post</strong> <strong>Falls</strong> Comprehensive Plan, 2010• Kootenai Metropolitan Area Transportation Plan, 2007-2030• Idaho Statewide Transportation Improvement Program (STIP), FY 2010-2013The project would initially be privately funded by the Pointe LLC, developer <strong>of</strong> The Pointe at <strong>Post</strong> <strong>Falls</strong>, acommercial development on the north side <strong>of</strong> I-<strong>90</strong> in the area <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> and W. Pointe Parkway. Underthe State Tax Anticipated Revenue (STAR) Legislation approved by the Idaho legislature in 2007, the privatecompany would be eligible <strong>for</strong> reimbursement <strong>of</strong> up to $35 million <strong>of</strong> project expenses <strong>for</strong> approvedtransportation improvements using sales tax reimbursements from retail development within the project area.The project is the first in Idaho to utilize the STAR Legislation, and would be the first to benefit from thepublic/private relationship authorized by the legislation.An interchange connecting to an interstatehighway system must obtain federal approvalthrough a needs assessment, as required by theFHWA (see box <strong>for</strong> explanation <strong>of</strong> policyrequirements). The I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> InterchangeJustification Report (IJR), which was completedin October 2010 (HDR 2010), concluded thatthere is sufficient justification <strong>for</strong> a newinterchange that would connect W. PointeParkway (north <strong>of</strong> I-<strong>90</strong>) to W. RiverbendAvenue (south <strong>of</strong> I-<strong>90</strong>). The IJR alsorecommended a standard diamond interchangeon the W. Pointe Parkway alignment thatincludes related improvements to W. RiverbendAvenue, N. <strong>Beck</strong> <strong>Road</strong>, and W. Pointe Parkway.Policy on Access to Interstate SystemThis FHWA policy outlines the justification anddocumentation necessary to substantiate anyproposed changes in access to the interstate system.A new interchange connecting to I-<strong>90</strong> must beapproved by FHWA and developed in accordance withfederal laws and regulations as specified in 23 U.S.C.109 and 111, 23 C.F.R. 625.4, and 49 C.F.R.1.48(b)(1). FHWA’s policy can be found at:http://www.fhwa.dot.gov/programadmin/fraccess.cfmThe supporting document <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project is the Interstate JustificationReport.The alternatives screening process used in the IJR is described in Chapter 2 <strong>of</strong> this EA. The FHWA acceptedthe standard diamond interchange on the W. Pointe Parkway alignment, subject to successful completion <strong>of</strong>the NEPA process.1.3 Project Technical Advisory CommitteeThe alternatives <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project were developed and screened with the guidance<strong>of</strong> a Technical Advisory Committee (TAC) representing a cross-section <strong>of</strong> local, state, and federal agenciesand regional stakeholders. The TAC provided valuable knowledge and input into the development <strong>of</strong> the IJRand helped to define the project purpose and need. The TAC members included representatives from thefollowing entities:• FHWA - Idaho• FHWA - Washington• Idaho Transportation Department (ITD)• Washington State Department <strong>of</strong> Transportation (WSDOT)I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-4Project No. A010(963)June 2011


• Kootenai Metropolitan Planning Organization (KMPO)• Spokane Regional Transportation Council (SRTC)• PFHD• Spokane County• <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>1.4 Project TeamThe project team, consisting <strong>of</strong> staff from HDR Engineering, Inc. (HDR) and the Pointe LLC, was alsocrucial in shaping and analyzing the alternatives created <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Theproject team facilitated the decision-making process and provided input throughout the planning and analysisphase.1.5 Project PurposeThe project purpose and need were developed with guidance from the IJR, the TAC, and local and regionaltransportation and land-use plans.The purpose <strong>of</strong> this project is to:Improve regional traffic operations to and from I-<strong>90</strong>, between and including the Pleasant View <strong>Road</strong>/I-<strong>90</strong> andState Line <strong>Road</strong>/I-<strong>90</strong> interchanges.1.6 Project NeedThe need <strong>for</strong> this project is based upon the following factor:• Inability <strong>of</strong> the existing interchanges with I-<strong>90</strong> at Pleasant View <strong>Road</strong> and State Line <strong>Road</strong> toadequately serve future access and regional connectivity demands.Evidence <strong>for</strong> defining the need, based on projected population and planned land-use growth, is outlined in theIJR and summarized below.Considerable population growth has occurred in Kootenai County, Idaho over the past decades, with growthin and around the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> steadily increasing over the last 20 years. Much <strong>of</strong> the recent growth in<strong>Post</strong> <strong>Falls</strong> is focused largely in the western area. <strong>Post</strong> <strong>Falls</strong> has grown from 7,350 residents in 19<strong>90</strong> to almost27,000 in 2009. This growth is projected to continue with an estimated 34,000 residents by 2030(Figure 1-3). This population increase correlates with increases in employment in the region and in retailbusinesses to provide goods and services to the population and business community.The increased growth will result in increased pressure on the regional transportation system, including ademand <strong>for</strong> access to and from I-<strong>90</strong> in the project area. A new interchange in this location would also provideregional connectivity via N. <strong>Beck</strong> <strong>Road</strong> from W. Seltice Way to State Highway 53 (SH-53) as this areatransitions from rural development to urban including annexation to the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> (KMPO 2010) 1 .1 The regional future <strong>for</strong> N. <strong>Beck</strong> <strong>Road</strong> was affirmed in communication with the KMPO (Glenn Miles) dated May 25, 2010 andincluded in Appendix AH <strong>of</strong> the IJR.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-5Project No. A010(963)June 2011


Figure 1-3. Projected Population Growth in <strong>Post</strong> <strong>Falls</strong>, 2000-2030Population35,00033,00031,00029,00027,00025,00023,00021,00019,00017,00015,0002000200120022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027202820292030YearSource: 2000-2009 data from U.S. Census Bureau; 2010-2030 projections provided by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> (Melvin 2011).The local roads and their intersections with the two existing interchanges would operate at levels <strong>of</strong> service(LOS) “F” under the No-Build condition in 2030 (Table 1-1) (see box <strong>for</strong> explanation <strong>of</strong> LOS). The PFHDand the KMPO consider an LOS <strong>of</strong> E or F to be undesirable <strong>for</strong> transportation planning. The No-Buildcondition refers to no new interchange or no improvements to the existing interchanges (see Chapter 2).Level <strong>of</strong> Service Rating StandardsLevel <strong>of</strong> Service (LOS) is a measure used by traffic engineers to describe the quality <strong>of</strong> service to theroad user in terms <strong>of</strong> driver discom<strong>for</strong>t, frustration, fuel consumption and travel time. LOS at signalizedintersections is directly related to average delay time. LOS standards consist <strong>of</strong> the following:LOS A – Free flowing, low traffic densityLOS B – Minimum delay, stable traffic flowLOS C – Stable condition, movements somewhat restricted due to higher volumes, but not objectionable<strong>for</strong> motoristLOS D – Movements more restricted, delay may occur during short peaks, but lower demands occur <strong>of</strong>tenenough to permit clearing, preventing excessive backupsLOS E – Actual capacity <strong>of</strong> the roadway involves delay to all motorists due to congestionLOS F – Demand volumes greater than capacity, resulting in complete congestionIn addition to the terminal ramps at the interchanges presented in Table 1-1, other intersections in the projectarea were evaluated <strong>for</strong> traffic effectiveness in 2030 under No-Build conditions (See IJR, Section 1.2, HDR2010). Of the eight signalized intersections in the project area, seven exhibit LOS E or F <strong>for</strong> the 2030 designyear. Generally, the local roadway facilities and their intersections with the interstate system would operate atunacceptable LOS under the future No-Build condition.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-6Project No. A010(963)June 2011


Table 1-1. Projected 2030 LOS under No-Build AlternativeIntersectionLOSCurrent Condition (2007) 2030Pleasant View <strong>Road</strong>/I-<strong>90</strong> West Bound Ramp Terminal B FPleasant View <strong>Road</strong>/I-<strong>90</strong> East Bound Ramp Terminal B FState Line <strong>Road</strong>/I-<strong>90</strong> West Bound Ramp Terminal F FState Line <strong>Road</strong>/I-<strong>90</strong> East Bound Ramp Terminal C FSource: I-<strong>90</strong> IJR, Appendix AA (HDR 2010); LOS is based on PM (afternoon) peak conditions.1.7 Interrelated and Interdependent ProjectsThis section describes projects that could cause cumulativeeffects (see box <strong>for</strong> definitions <strong>of</strong> types <strong>of</strong> impacts) inconjunction with the construction and operation <strong>of</strong> the ProposedAction. Federal agencies are required to consider the cumulativeimpacts <strong>of</strong> their actions through NEPA and the Council on<strong>Environmental</strong> Quality Regulations <strong>for</strong> Implementing theProcedural Provisions <strong>of</strong> NEPA (Code <strong>of</strong> Federal Regulations(CFR), Title 40, Parts 1500-1508). Cumulative effects aredefined as the incremental impacts <strong>of</strong> the action when added topast, on-going, and planned future actions, regardless <strong>of</strong> whatagency (federal or non-federal) or person undertakes suchactions. Cumulative impacts can result from actions that areindividually minor but collectively significant over a period <strong>of</strong>time (40 CFR 1508.7).Cumulative impacts are based on the net impacts (i.e. impacts remaining after mitigation has been applied),not gross impacts. If the cumulative impact analysis was based on gross impacts, the actual cumulative impactwould be misrepresented. If the Proposed Action did not impact a resource, there would be no potential <strong>for</strong>measuring cumulative impacts.1.7.1 Past, Planned, and On-going ProjectsTypes <strong>of</strong> ImpactsDirect Impacts – Impacts caused bythe action and occurring at the sametime and place.Indirect Impacts – Impacts caused bythe action and occurring later in time orfarther removed in distance, but stillreasonably <strong>for</strong>eseeable.Cumulative Impacts – Impacts thatresult from incremental impact <strong>of</strong> thePreferred Alternative when added toother past, present and reasonably<strong>for</strong>eseeable future actions.Past projects include the building <strong>of</strong> roadway systems in the <strong>Post</strong> <strong>Falls</strong> area; residential, commercial andagricultural development; and the construction <strong>of</strong> I-<strong>90</strong>. The 2009 aerial photograph in Figure 1-2 provides asnapshot <strong>of</strong> existing roadways and development.Long-range transportation improvements (beyond 2011) identified <strong>for</strong> the Kootenai County area are identifiedin the following documents:• Kootenai Metropolitan Area Transportation Plan, 2007-2030• Idaho STIP, FY 2010-2013• Washington State Department <strong>of</strong> Transportation Capitol Improvements and Preservation Program,FY 2009-2011• <strong>Post</strong> <strong>Falls</strong> Transportation Master Plan, 2004These documents identify roadway improvements needed to support planned land uses in the study area.Table 1-2 summarizes planned roadway improvements in the study area by 2030. These improvements, alongwith intersection improvements, are illustrated in Figure 1-4.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-7Project No. A010(963)June 2011


Table 1-2. 2030 Regional Planned <strong>Road</strong>way ImprovementsJurisdiction Project Transportation Improvement AssumptionsWSDOTITDProject areaI-<strong>90</strong>: Harvard <strong>Road</strong> to State Line <strong>Road</strong>(improvement extends outside <strong>of</strong> the projectarea)I-<strong>90</strong>: State Line <strong>Road</strong> to Government Way,four to six lanes (improvement extendsoutside <strong>of</strong> the project area)Six lanesSix lanes<strong>Post</strong> <strong>Falls</strong> N. <strong>Beck</strong> <strong>Road</strong>: W. Seltice Way to SH 53* Four to five LanesPFHD<strong>Post</strong> <strong>Falls</strong>, PFHD<strong>Post</strong> <strong>Falls</strong><strong>Post</strong> <strong>Falls</strong><strong>Post</strong> <strong>Falls</strong>, PFHDITD, PFHD<strong>Post</strong> <strong>Falls</strong>, PFHD<strong>Post</strong> <strong>Falls</strong><strong>Post</strong> <strong>Falls</strong><strong>Post</strong> <strong>Falls</strong>, PFHD<strong>Post</strong> <strong>Falls</strong>PFHDPFHDITDBNSF Railroad Main Line Rail Crossing atPrairie Avenue**Chase <strong>Road</strong>: W. Seltice Way to PrairieAvenueEmpire Center: W. Seltice Way to PolelineAvenueExpo Parkway: Baugh Way to W. PleasantView <strong>Road</strong>McGuire <strong>Road</strong>: W. Seltice Way to PrairieAvenueN. Pleasant View <strong>Road</strong>/SH 53 Interchange***N. Pleasant View <strong>Road</strong>: W. RiverbendAvenue to Prairie AvenuePoleline Avenue: McGuire <strong>Road</strong> to Chase<strong>Road</strong>Jacklin <strong>Road</strong>: N. <strong>Beck</strong> <strong>Road</strong> to W. ExpoParkwayW. Riverbend Avenue: N. <strong>Beck</strong> <strong>Road</strong> to S.Pleasant View <strong>Road</strong>W. Riverbend Avenue: S. Pleasant View<strong>Road</strong> to McGuire <strong>Road</strong>Prairie Avenue: S. Pleasant View <strong>Road</strong> to SH41 (improvement extends outside <strong>of</strong> theproject area)Prairie Avenue: N. <strong>Beck</strong> <strong>Road</strong> to N. PleasantView <strong>Road</strong>SH53: State Line <strong>Road</strong> to Rathdrum(improvement extends outside <strong>of</strong> the projectarea)Close at-grade crossingThree lanesThree lanesNew five-lane segmentThree lanesGrade-separated interchange, replacement <strong>of</strong>at-grade rail crossing and intersectionFive lanes on Pleasant View <strong>Road</strong> from SelticeWay to Prairie AvenueThree lanesThree lanesFive lanesThree lanesFive lanesFive lanesFour lanes<strong>Post</strong> <strong>Falls</strong> Spokane St: 15th Avenue to Prairie Avenue Three lanes<strong>Post</strong> <strong>Falls</strong> Spokane St: 2nd Avenue to 4th Avenue Five lanesSource: I-<strong>90</strong> IJR, Appendix C (HDR 2010);*This improvement is anticipated as this area transitions from rural development to urban and is annexed into the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>(KMPO 2010);** Shown as intersection #22 in Figure 1-4;***Shown as intersection #21 in Figure 1-4.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-8Project No. A010(963)June 2011


In addition to the planned roadway improvements listed above, other on-going and future projects near theI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project include:• I-<strong>90</strong> Washington State Line to Sherman Avenue in Coeur D’Alene (ITD Key # 8651) – Conduct acorridor study to identify existing deficiencies and improvements required to handle future growth.The objective is to plan an infrastructure system in coordination with local and regional planningentities. This study includes the project area <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. This corridorstudy is planned <strong>for</strong> 11 to 15 years out on ITD’s Long-Range Capital Improvement Program.• I-<strong>90</strong> <strong>Post</strong> <strong>Falls</strong> Access Improvement Project (ITD) – This on-going project is exploring improvementsto I-<strong>90</strong> that would enhance access and mobility in <strong>Post</strong> <strong>Falls</strong>. The study area is approximately 3 mileslong and extends from the west terminus <strong>of</strong> the Spokane Street Interchange to the east terminus <strong>of</strong> theState Highway (SH) 41 interchange, which constitutes the urbanized area <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>. The Draft EISwas published in 2008. A Final EIS is being finalized.The 2007 KMPO Transportation Improvement Plan identifies the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange under ITDjurisdiction on its short-term improvements project list. Also, N. <strong>Beck</strong> <strong>Road</strong> is identified <strong>for</strong> widening to fivelanes from I-<strong>90</strong> to W. Seltice Way in the short-term improvements project list designated under the <strong>City</strong> <strong>of</strong><strong>Post</strong> <strong>Falls</strong> jurisdiction. These improvements would be constructed as part <strong>of</strong> the Proposed Action described inChapter 2.In addition to the future or on-going transportation projects listed above, the project area is undergoingresidential and commercial development, which is further described below.1.7.2 Local Area DevelopmentThe growth <strong>of</strong> the area in and around the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> has been steadily increasing over the last 20 years,with recent growth focused largely in the western area.Figure 1-3 illustrates measured population growth from 19<strong>90</strong> to 2009 and projected growth through 2030. Tosupport future growth, the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and the KMPO are considering infrastructure and capacityrelatedimprovements that will benefit and support future populations.Future land-use plans identified in the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Comprehensive Plan will help facilitate projectedpopulation and employment growth in the <strong>Post</strong> <strong>Falls</strong> area. The plan identifies considerable commercial andindustrial growth in the project area (Figure 3-14) along the I-<strong>90</strong> corridor and also recognizes the need <strong>for</strong>regional connectivity through quick and easy access to the interstate. According to future employmentdensity projections by the KMPO:• More than 20,000 people are expected to be working in the <strong>Post</strong> <strong>Falls</strong> area by 2030, a 157 percentincrease over 2005. Approximately 5,000 new jobs are anticipated in western <strong>Post</strong> <strong>Falls</strong> by 2030 (inthe general project area).• Residential units are expected to increase by 172 percent, to 11,077, in the west <strong>Post</strong> <strong>Falls</strong> area by2030.This level <strong>of</strong> growth will result in increased demand <strong>for</strong> regional access to and from I-<strong>90</strong> in the area and willcause increased traffic pressure on the existing interchanges.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>1-9Project No. A010(963)June 2011


Chapter 2: Description <strong>of</strong> Alternatives, Including Proposed Action2.1 IntroductionInterchange JustificationReport Open HouseAn I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchangepublic open house was held onJanuary 14, 2009, at the <strong>Post</strong><strong>Falls</strong> <strong>City</strong> Hall. The purpose <strong>of</strong>this meeting was to gather publicinput on alternatives beingevaluated in the IJR process. Formore in<strong>for</strong>mation on the openhouse, see Chapter 4.The alternatives described in this chapter include a range <strong>of</strong>reasonable actions considered by the TAC and the public during theIJR and scoping processes (further described in Chapter 4). TACmembers representing local, state, and federal agencies and regionalstakeholders provided valuable knowledge and input. Alternativeswere developed through a collaborative process between TACmembers and the project team. A public meeting was held during theIJR process to seek input on alternatives being evaluated and toidentify issues and concerns by the public on the proposed project(see box).To initiate the alternatives development process, the TAC and theproject team first came to a consensus on how to evaluate thealternatives. To ensure that a range <strong>of</strong> reasonable alternatives was considered and documented, the evaluationwas conducted in two screening levels. The alternatives that met initial (level-I) screening criteria were<strong>for</strong>warded to a level-II analysis (Figure 2-1). The screening criteria and the screening results are described inSection 2.2.2.2 Alternatives Development2.2.1 Previous StudiesAlternatives developed and screened as part <strong>of</strong> the IJR process relied on a number <strong>of</strong> regional and localplanning documents (Table 2-1). In addition, the level-II screening process included the 2030 regionalnetwork travel demand modeling by the SRTC and KMPO, as well as operational traffic analysis <strong>of</strong> the localnetwork by the project team. Details on the traffic modeling approach are presented in Section 1.2 <strong>of</strong> the IJR(HDR 2010).Additional documents referenced <strong>for</strong> development <strong>of</strong> this EA are cited in Chapter 7. A summary <strong>of</strong> thealternatives evaluation process is presented below. See Section 2.3 <strong>of</strong> the IJR (HDR 2010) <strong>for</strong> details on theevaluation process and results.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-1Project No. A010(963)June 2011


Table 2-1. Planning Documents Relied Upon in the Alternatives EvaluationPlanning DocumentDocumentPrepared <strong>for</strong>:Regional Planning Documents<strong>Post</strong> <strong>Falls</strong> Transportation Master Plan, May 2004. Availableat:http://www.postfallsidaho.org/PZDept/pz<strong>for</strong>ms/TransportationMasterPlan2004.pdfKootenai Metropolitan Area Transportation Plan, 2007-2030.Available at: http://www.kmpo.net/mtp-page.htmlIdaho STIP, FY 2010-2013. Available at:http://itd.idaho.gov/planning/stip/stip2010/Draft%20FY2010%20STIP%20Document%20SLF.pdfI-<strong>90</strong> <strong>Post</strong> <strong>Falls</strong> Access Improvements Project, Draft EIS.Available at:http://www.postfallsidaho.org/pzdept/Engineering/EngProjects/I_<strong>90</strong>Impact/Start.pdf<strong>City</strong> <strong>of</strong> <strong>Post</strong><strong>Falls</strong>KootenaiCountyITDITDProject-Specific Documents Prepared by Project TeamI-<strong>90</strong> Interchange Justification Report. Project No. A010(963).Key No. 010963. October 2010.<strong>Environmental</strong> Scan, I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange Project No.A010(963). Key No. 010963. Updated January 2011.2.2.2 Alternatives EvaluationThe project team developed alternatives based on:FHWA/ITD• NEPA requirements, including advancing the No-Build Alternative• Regional planning documents (Table 2-1)• Input from TAC members, stakeholders, and agencies• Engineering and environmental considerationsITDDescriptionIdentifies N. <strong>Beck</strong> <strong>Road</strong> as a logicallocation <strong>for</strong> a new interchange to servegrowing development in west <strong>Post</strong><strong>Falls</strong>.Identifies I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchangeas a programmed project in KootenaiCounty.Cites I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange as aregionally significant transportationproject.Outlines environmental conditionsalong the I-<strong>90</strong> corridor near N. <strong>Beck</strong><strong>Road</strong> and cites improvements toadjacent interchanges.Assesses impacts associated with theaddition <strong>of</strong> a new interchange on I-<strong>90</strong>near N. <strong>Beck</strong> <strong>Road</strong>.Preliminary assessment <strong>of</strong>environmental issues <strong>for</strong> a potentialinterchange near N. <strong>Beck</strong> <strong>Road</strong> and I-<strong>90</strong>.As per FHWA guidance, consideration <strong>of</strong> alternatives includes:• No-Build Alternative• Transportation System Management (TSM) and Mass Transit• Build AlternativesThe process <strong>for</strong> alternatives screening included (Figure 2-1):1. Identification <strong>of</strong> alternative screening criteria2. Identification <strong>of</strong> alternatives3. Level-I screening4. Level-II screeningI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-3Project No. A010(963)June 2011


2.2.3 Summary <strong>of</strong> the Alternatives EvaluationIdentification <strong>of</strong> Screening CriteriaThe approach used <strong>for</strong> assessing alternatives during the IJR process involved level-I and level-II screeningcriteria as described below.Level-I Screening CriteriaLevel-I screening was designed to advance alternatives that met general criteria defined during the IJRprocess (Table 2-2). Alternatives that were not screened out in the level-I analysis were moved <strong>for</strong>ward <strong>for</strong>consideration in the level-II evaluation.Table 2-2. Level-I Screening CriteriaCriteriaGeneral Compliance withFHWA StandardsGeneral Compliance withITD / WSDOT StandardsHighway Operational andSafety ImpactsImpacts on Local<strong>Road</strong>waysLocal Plan ConsistencyNatural EnvironmentConcernsSocioeconomic ConcernsCultural ResourceConcernsExplanationDoes the alternative appear capable <strong>of</strong> meeting the FHWA standards <strong>for</strong> access? Is thereanything that would clearly require a deviation from those standards?Does the alternative appear capable <strong>of</strong> meeting the ITD / WSDOT design standards <strong>for</strong>interchanges? Is there anything that would clearly require a deviation from those standards?Does the interchange concept allow feasible highway operations? Does the interchangeconcept address existing safety concern? Does the interchange concept present thepotential <strong>of</strong> creating a future safety concern?Does the alternative create negative impacts <strong>for</strong> the local roadway system or relieve existingimpacts? Does the alternative fail to enhance local connectivity?Does the alternative appear compatible with the local transportation and land-use plans?Does the alternative appear to have impacts on the natural environment that would need tobe mitigated?Would the alternative appear to involve displacements <strong>of</strong> people or businesses? Would thealternative substantially change the character <strong>of</strong> established business or residential areas? Ifthere are possible displacements, do those displacements disproportionately affectresidential or business areas providing <strong>for</strong> low-income or minority populations(“environmental justice”)?Does the alternative have the potential to adversely affect known national register-eligibleresources?ConstructabilityDoes an alternative appear to be constructible?Source: I-<strong>90</strong> IJR, Appendix H (HDR 2010)Level-II Screening CriteriaThe level-II screening criteria (Table 2-3) provided a more detailed evaluation based on FHWA interstateaccess policy guidelines (see box on Page 1-4) and other considerations identified by TAC members. Thisstep in the screening process required technical analysis, including an evaluation <strong>of</strong> future traffic operations.From the level-II screening, the recommended operationally acceptable alternative (preferred alternative) wasdetermined.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-4Project No. A010(963)June 2011


Category <strong>of</strong>EvaluationEvaluation CriteriaTable 2-3. Level-II Screening CriteriaExplanationAccess PointDecision CriteriaOtherConsiderationsConsistency with interstate networkplanningState and local land-use andtransportation plan consistencyService <strong>for</strong> regional trip purposesCompliance with interstategeometric standardsOperational capability (opening dayand 20-year horizon) <strong>of</strong> local streetsystem, interchange ramps(existing and proposed), andinterstate mainline *Local system supportLocal connectivityLand-use compatibility and impactsSocioeconomic impactsRight-<strong>of</strong>-wayNatural environment impactExamination <strong>of</strong> whether proposed access is recognized on theinterstate network plans.Is the proposed access recognized on local land-use andtransportation plans as a future improvement?Would the new access be used <strong>for</strong> regional trip purposes (longdistancetrips) versus allowing use <strong>of</strong> the interstate as a “superarterial”<strong>for</strong> local trips?Does the alternative appear capable <strong>of</strong> meeting interstategeometric standards?Does the alternative maintain or improve traffic operations onthe local street system, the interchange ramps, or the interstatemainline? Does the alternative address an existing safetyconcern?Will the local components <strong>of</strong> the alternative be “delivered”concurrent with the interstate components?Does the alternative improve/restore local street connections?Is the zoning in the immediate area <strong>of</strong> the alternative consistentwith that alternative?Would the alternative have negative or positive socioeconomicimpacts?Could the alternative be constructed within existing right-<strong>of</strong>way?What additional right-<strong>of</strong>-way is required <strong>for</strong> alternative?Does the alternative involve a greater potential <strong>of</strong> wetland,stream bank or habitat impacts?Cultural environment impactAre there cultural resources or public facilities (archeology,historic, parks, etc.) that could be affected by the alternative?Can the alternative be constructed utilizing temporary workConstructabilityzone traffic-control strategies that will not significantly delaytravel?Source: I-<strong>90</strong> IJR, Appendix H (HDR 2010); * The interstate mainline refers to the principal travel section <strong>of</strong> I-<strong>90</strong> in the study area.2.2.4 Range <strong>of</strong> AlternativesThe project team and the TAC met in May 2008 to begin <strong>for</strong>mulating alternatives that would be measuredagainst the screening criteria. Detailed in<strong>for</strong>mation on alternatives development is provided in Appendix I <strong>of</strong>the IJR (HDR 2010). From this meeting and follow-up discussions, 22 build alternatives emerged <strong>for</strong> level-1screening in the following categories:• Three were improvements at the adjacent State Line <strong>Road</strong> Interchange or the Pleasant View <strong>Road</strong>Interchange• Seven included modifications to existing interchanges with partial or new interstate accessimprovements• Twelve were various <strong>for</strong>ms <strong>of</strong> a new interchange, using either N. <strong>Beck</strong> <strong>Road</strong> or W. Pointe ParkwayI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-5Project No. A010(963)June 2011


The No-Build Alternative was carried <strong>for</strong>ward throughout the process. A Local Improvement Alternative(further defined in Section 2.2.5) that was added shortly after the level-II screening process was incorporatedinto the IJR.2.2.5 Screening <strong>of</strong> AlternativesLevel-I ScreeningThe initial 22 build alternatives described above were screened using the criteria outlined in Table 2-2. Level-I Screening Criteria as well as details on the level-I screening process, including rationale <strong>for</strong> eliminatingalternatives, are provided in Appendix J <strong>of</strong> the IJR (HDR 2010). The level-I screening process assigned scoresto each <strong>of</strong> the alternatives based on the criteria listed in Table 2-2. Based on the screening process and inputprovided by TAC and the project team, the following alternatives were advanced <strong>for</strong> level-II screening(Figure 2-2):• Existing Interchange Improvement Alternatives:• New <strong>Road</strong> Overcrossing Connecting to Expo Parkway with Improvements to Pleasant View<strong>Road</strong> Interchange• State Line <strong>Road</strong> Improvements + New <strong>Road</strong> Overcrossing Connecting to Expo Parkway +Improvements to Pleasant View <strong>Road</strong> Interchange• New Interchange Alternatives:• Pointe Parkway Standard Diamond Interchange• Pointe Parkway Roundabout Diamond Interchange• Pointe Parkway Single Point Urban Interchange• <strong>Beck</strong> <strong>Road</strong> Single Point Urban InterchangeLevel-II ScreeningAlternatives EliminatedAs a first step in the level-II screening, the six alternatives were screened based on their qualitative measures,which resulted in the following alternatives being eliminated:New <strong>Road</strong> Overcrossing Connecting to Expo Parkway with Improvements to Pleasant View <strong>Road</strong>Interchange – This alternative includes reorganization and rerouting <strong>of</strong> the existing and planned localroadway system. Many <strong>of</strong> these changes make this alternative inconsistent with the local adoptedtransportation plan. The restriction <strong>of</strong> intersections on N. Pleasant View <strong>Road</strong> to right-in/right-out movementscould cause multiple business displacements or disruptions through associated access measures. Moreover,the proposed overcrossing road and its connection south <strong>of</strong> W. Riverbend <strong>Road</strong> to Pleasant View <strong>Road</strong> andthe rest <strong>of</strong> the transportation system had the potential <strong>of</strong> causing multiple industrial employmentdisplacements.State Line <strong>Road</strong> Improvements + New <strong>Road</strong> Overcrossing Connecting to Expo Parkway +Improvements to Pleasant View <strong>Road</strong> Interchange – This alternative, which combines the overcrossingalternative described above with major improvements to the State Line Interchange, was eliminated <strong>for</strong> thesame reasons described above.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-6Project No. A010(963)June 2011


Further AnalysisAfter the first two alternatives were eliminated from further consideration, a detailed traffic operation andtraffic service analysis was conducted to analyze the remaining alternatives. This included travel demandmodeling <strong>of</strong> the SRTC/KMPO 2030 regional network and operational traffic analysis <strong>of</strong> the local network.This level <strong>of</strong> analysis allowed an understanding <strong>of</strong> future traffic operations, including LOS at localintersections and vehicle travel time and miles traveled <strong>for</strong> each alternative <strong>for</strong> the planning year 2030. It alsoprovided valuable input into traffic-related benefits that could result from any <strong>of</strong> the remaining improvementalternatives. For additional in<strong>for</strong>mation on travel demand model <strong>for</strong>ecasting and adjustments, see the TravelDemand Model Forecast Procedures Memorandum dated May 21, 2010 (Appendix D in the IJR, HDR 2010).During the development <strong>of</strong> the IJR, and the ongoing level-II screening, discussions with ITD and FHWA ledto development <strong>of</strong> a Local Improvement Alternative that would function as a possible substitute <strong>for</strong> aninterchange build alternative. The Local Improvement Alternative would include improvements to thePleasant View <strong>Road</strong> Interchange, optimization <strong>of</strong> traffic signal timing, and improvements on N. and S.Pleasant View <strong>Road</strong> to interconnect and coordinate traffic operations.The project team completed traffic <strong>for</strong>ecasts and operational analysis <strong>for</strong> signalized and unsignalizedintersections in the project area <strong>for</strong> the four remaining interchange alternatives and the Local ImprovementAlternative. This ef<strong>for</strong>t included a traffic capacity analysis <strong>for</strong> I-<strong>90</strong> and the merging and diverging ramp areason the State Line <strong>Road</strong> and Pleasant View <strong>Road</strong> interchanges. The results <strong>of</strong> this analysis are presented inSection 2 <strong>of</strong> the IJR (HDR 2010) and are summarized in the following text.Table 2-4 summarizes the traffic analysis that compares these alternatives and the No-Build Alternative. Asshown in the table, the build alternatives that add access to I-<strong>90</strong> enhance the local transportation system byimproving traffic conditions at signalized and unsignalized intersections in the project area. For example,87.5 percent <strong>of</strong> the signalized intersections in the project area would operate at LOS E or F under the No-Build Alternative compared to 0 percent with the four new interchange alternatives (all operated at LOS D orbetter). The four interchange alternatives also provide more improved traffic operations compared to theLocal Improvement Alternative.The LOS <strong>for</strong> the I-<strong>90</strong> mainline (the principal travel section <strong>of</strong> I-<strong>90</strong>) between the new interchange and thePleasant View <strong>Road</strong> Interchange is reduced from LOS C in the No-Build to LOS D <strong>for</strong> the build alternatives.As part <strong>of</strong> the IJR process, ITD accepted a request from the project team to use LOS D as the minimumdesign threshold <strong>for</strong> the I-<strong>90</strong> mainline, since it is in an urban area (ITD 2010). The ITD approval letter <strong>for</strong> theI-<strong>90</strong> mainline LOS is provided in Appendix Y <strong>of</strong> the IJR.The effects <strong>of</strong> a new interchange on traffic conditions were analyzed with and without traffic signals on theramp terminus intersections at the existing State Line <strong>Road</strong> Interchange. These intersections are currentlyunsignalized. As unsignalized intersections, both ramps are predicted to per<strong>for</strong>m poorly (LOS F) under<strong>for</strong>ecasted 2030 peak-hour conditions, with or without the build alternatives. By assuming signalization, thefour new interchange alternatives would improve conditions at the State Line <strong>Road</strong> Interchange from LOS Fto LOS C or LOS B.The SRTC Metropolitan Transportation Plan identifies these ramp terminus intersections as unfundeddeficiencies in the planning year 2015. Even without signalized intersections, the new interchange alternativeswould delay the urgency <strong>of</strong> this deficiency beyond the projected 2015 horizon year (it delays the need <strong>for</strong>signalization). That additional time would allow the SRTC and its regional partners to find an appropriatefunded solution to this recognized deficiency (See page 3-11 <strong>of</strong> the IJR, HDR 2010). The acceptableoperation <strong>of</strong> the interchange alternatives is not dependent upon the provision <strong>of</strong> improvements at the StateLine <strong>Road</strong> Interchange and improvements to the State Line <strong>Road</strong> Interchange are not included in thecommitted improvements <strong>for</strong> opening day.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-8Project No. A010(963)June 2011


Table 2-4. 2030 Traffic Operations Comparison <strong>of</strong> AlternativesSignalized Intersections Unsignalized Intersections Freeway ComponentsNo-BuildAlternativeTotal(%)8(100%)LOS C*or better(%)0(0%)LOS D(%)1(12.5%)LOS E orF(%)7(87.5%)Total(%)3(100%)LOS C orbetter(%)1(33.3%)LOS D(%)0(0%)LOS E orF(%)2(66.7%)Total(%)16(100%)LOS C orbetter(%)16(100%)LOS D(%)0(0%)LOS E orF(%)0(0%)Local ImprovementAlternative8(100%)4(50%)2(25%)2(25%)3(100%)1(33.3%)0(0%)2(66.7%)16(100%)16(100%)0(0%)0(0%)Pointe ParkwayStandard Diamond12(100%)11(91.7%)1(8.3%)0(0%)4(100%)2(50%)0(0%)2(50%)20(100%)17(85%)3(15%)0(0%)Pointe ParkwayRoundaboutDiamond12(100%)10(83.3%)2(16.7%)0(0%)4(100%)2(50%)0(0%)2(50%)20(100%)17(85%)3(15%)0(0%)Pointe ParkwaySingle Point UrbanInterchange11(100%)10(<strong>90</strong>.9%)1(9.1%)0(0%)4(100%)2(50%)0(0%)2(50%)20(100%)17(85%)3(15%)0(0%)<strong>Beck</strong> <strong>Road</strong> SinglePoint UrbanInterchange12(100%)11(91.7%)1(8.3%)0(0%)2(100%)0 02(100%)20(100%)17(85%)3(15%)0(0%)Source: I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> IJR, Table 27 (HDR 2010)* LOS is based on PM peak hour conditions.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong> 2-9Project No. A010(963)June 2011


The four new interchange alternatives listed in Table 2-4 have similar traffic operation effectiveness and allfour provide greater traffic flow benefits compared to the Local Improvement Alternative. The PointeParkway Standard Diamond was recommended in the IJR as the preferred alternative <strong>for</strong> the followingreasons:• Providing a new interchange is in direct response to predicted regional travel demand from the west<strong>Post</strong> <strong>Falls</strong> area, which is expected to grow by nearly 11,077 residential units and over 5,000employees by 2030.• A new interchange in the N. <strong>Beck</strong> <strong>Road</strong> vicinity is supported in the regional and local land-use andtransportation plans.• The proposed interchange improves traffic operations over the projected 2030 No-Build Alternativewith 92 percent <strong>of</strong> the signalized intersections projected at LOS C or better, compared to allsignalized intersections at LOS D or F <strong>for</strong> the No-Build Alternative.• The standard diamond design can accommodate vehicle, bicycle and pedestrians effectively while<strong>of</strong>fering ease <strong>of</strong> construction and future expandability. The Pointe Parkway design follows generallyaccepted engineering practices <strong>for</strong> an urban roadway where speeds are controlled by signalizedintersections.• The location on the Pointe Parkway alignment provides increased distance from the Spokane Rivercompared to the <strong>Beck</strong> <strong>Road</strong> alignments.Transportation System ManagementTSM refers to a wide-range <strong>of</strong> traffic engineering measures that can increase the capacity <strong>of</strong> the existingroadway system. Examples <strong>of</strong> TSM include improving signal timing, changing lane configurations, rampmetering (the use <strong>of</strong> traffic signals at interstate on-ramps to manage the rate <strong>of</strong> automobiles entering theinterstate), carpooling, and mass transit options. Mass transit would consist <strong>of</strong> providing bus, light rail orother transit options. FHWA guidelines require that TSM is considered in highly urbanized areas be<strong>for</strong>e largescalecapital improvements are made.FHWA’s Technical Advisory T6640.8A indicates that alternate means <strong>of</strong> meeting the project purpose andneed (such as TSM measures) is usually relevant only <strong>for</strong> major projects proposed in urban areas with apopulation over 200,000. According to <strong>of</strong>ficial population <strong>for</strong>ecasts published by the KMPO, the entire <strong>Post</strong><strong>Falls</strong> Highway District is expected to have a population <strong>of</strong> just over 100,000 by 2030. Since this is only half<strong>of</strong> the cited threshold, TSM measures are not likely to be an effective replacement <strong>for</strong> additional access toI-<strong>90</strong>. Various local improvement alternatives were evaluated in the IJR that included TSM measures such astraffic signal optimization and changing lane configurations. None <strong>of</strong> these alternatives met the traffic needs<strong>for</strong> the study area in 2030. Refer to Section 2.2 <strong>of</strong> the IJR <strong>for</strong> additional in<strong>for</strong>mation on TSM.2.3 Alternatives Carried Forward <strong>for</strong> Detailed StudyBased on the screening <strong>of</strong> a range <strong>of</strong> alternatives, the project team with input from ITD and FHWArecommended the Pointe Parkway Standard Diamond Interchange Alternative (Figure 2-3) as the ProposedAction. This alternative meets the project purpose and need, it provides favorable traffic effectivenesscompared to other alternatives evaluated, and is compatible with regional plans and the transportation networkin the project area. The No-Build Alternative is required to be evaluated under NEPA.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-10Project No. A010(963)June 2011


2.3.1 No-Build AlternativeNo interchange would be built under the No-Build Alternative, which provides a basis <strong>for</strong> comparing the prosand cons <strong>of</strong> the Proposed Action. The No-Build Alternative would retain the current W. Pointe Parkway andN. <strong>Beck</strong> <strong>Road</strong> configurations without access to I-<strong>90</strong> in the N. <strong>Beck</strong> <strong>Road</strong> area. Traffic in the project areawould continue to access I-<strong>90</strong> via the State Line <strong>Road</strong> and Pleasant View <strong>Road</strong> interchanges. Other projectsand local development included in the regional long-range transportation and comprehensive plans would beconstructed (see Section 1.7.1 <strong>for</strong> a description <strong>of</strong> these projects).2.3.2 Proposed Action (Pointe Parkway Standard Diamond InterchangeAlternative)The Proposed Action would be connected to the regional roadway system by W. Pointe Parkway and N. <strong>Beck</strong><strong>Road</strong> to the north <strong>of</strong> I-<strong>90</strong> and by W. Riverbend Avenue to the south <strong>of</strong> I-<strong>90</strong>. Logical beginning and endingpoints <strong>for</strong> the environmental evaluation <strong>of</strong> the Proposed Action are (Figure 2-3):• Begin Project Terminus: The project begins at the connection <strong>of</strong> the interchange to W. RiverbendAvenue south <strong>of</strong> I-<strong>90</strong>. The terminus would allow <strong>for</strong> the realignment <strong>of</strong> W. Riverbend Avenue tothis new intersection and construction <strong>of</strong> an extension from W. Riverbend Avenue to connectwith properties west <strong>of</strong> the interchange. This terminus would also provide necessaryimprovements to the North Idaho Centennial Trail (Centennial Trail) multi-use recreational trailsystem, to allow trail users to access the interchange crossing while maintaining uninterruptedtravel along the trail system.• End Project Terminus: The project ends north <strong>of</strong> I-<strong>90</strong> at the intersection <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> andW. Seltice Way. This terminus would include improvements to N. <strong>Beck</strong> <strong>Road</strong> and the intersectionat N. <strong>Beck</strong> <strong>Road</strong> and W. Seltice Way to meet <strong>for</strong>ecasted traffic demand.• The project also includes ramps accessing and exiting I-<strong>90</strong> <strong>for</strong> both directions <strong>of</strong> travel at theproject location.The Pointe Parkway Standard Diamond Interchange and its ramps would be part <strong>of</strong> the National HighwaySystem when completed. The proposed improvements would be designed according to American Association<strong>of</strong> State Highway and Transportation Officials (AASHTO) guidelines and would meet or exceed ITD andFHWA standards. The concept design has been discussed with the governing agencies (ITD and <strong>City</strong> <strong>of</strong> <strong>Post</strong><strong>Falls</strong>) as part <strong>of</strong> the IJR process. Both agencies are supportive <strong>of</strong> the design concepts.Interstate ramps are designed to meet the required acceleration/deceleration lengths and provide necessaryspacing <strong>for</strong> merge and diverge actions between adjacent (existing) interchanges. Local roads and theintersection at N. <strong>Beck</strong> <strong>Road</strong> and W. Seltice Way to be improved as part <strong>of</strong> the Proposed Action would bedesigned in accordance with <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>, PFHD, Kootenai County, or ITD published standards, asapplicable <strong>for</strong> the appropriate road jurisdiction.Based on the opening-day analysis, construction <strong>of</strong> the interchange assumes associated improvements thatwould be in place concurrent with the opening <strong>of</strong> the interchange. This in<strong>for</strong>mation is summarized in thedesign features <strong>for</strong> the Proposed Action in Table 2-5.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-12Project No. A010(963)June 2011


Table 2-5. Proposed Action <strong>Road</strong>way ImprovementsLocationI-<strong>90</strong>/W. Pointe ParkwayW. Pointe Parkway(I-<strong>90</strong> to N. <strong>Beck</strong> <strong>Road</strong>)W. Pointe Parkway(I-<strong>90</strong> to W. RiverbendAvenue)W. Riverbend Avenue(Existing alignment toPointe Parkway)W. Riverbend AvenueExtensionN. <strong>Beck</strong> <strong>Road</strong> (W.Pointe Parkway to W.Seltice Way)Diamond interchange with rampsDescriptionFour-lane minor arterial roadway with bike lanes and sidewalks, turnlanes at ramps and N. <strong>Beck</strong> <strong>Road</strong> intersectionFour-lane minor arterial roadway with bike lanes and sidewalks, turnlanes at ramps and the W. Riverbend Avenue intersectionRealign as a two-lane collector road with bike lanes and sidewalks,turn lanes at intersectionsTwo-lane collector road with sidewalk on south side, CentennialTrail on north side, a two-way left-turn lane west <strong>of</strong> gradeseparation,and turn lanes at intersectionsFive-lane minor arterial roadway with bike lanes and sidewalks, turnlanes at intersectionsNOTE: Pointe LLC, the proponent <strong>of</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project, has committed to completingthe improvements listed in this table concurrent with the opening <strong>of</strong> the project. See Figures 2-4 and 2-5 <strong>for</strong>Proposed Action layout and typical cross sections, respectively.The design speeds <strong>for</strong> the new roads are based on adjacent roadways. N. <strong>Beck</strong> <strong>Road</strong> and W. Pointe Parkwaywould be designed as minor arterials, with a design speed <strong>of</strong> 35 mph (posted speed 25 mph) and signalizedintersections. W. Riverbend Avenue would be designed as a collector road with a design speed that increasesfrom 25 mph at the W. Pointe Parkway intersection to 35 mph at its connection with the existing alignment(posted speed 25 mph). The W. Riverbend Avenue extension to the west would have a design speed <strong>of</strong> 35mph (posted speed 25 mph).The Proposed Action interchange detail concept is shown in Figure 2-4. Typical sections are illustrated inFigure 2-5. The proposed interchange concept would include provisions <strong>for</strong> bicycles and pedestrians. TheCentennial Trail, which runs parallel to I-<strong>90</strong> on the south side, would be continued through the interchangearea adjacent to the proposed W. Riverbend Avenue extension that would be grade-separated from the PointeParkway interchange cross-road. The trail would not have any at-grade roadway crossings after construction<strong>of</strong> the interchange is complete. Conceptual right-<strong>of</strong>-way estimates anticipate approximately 15 to 20 acres <strong>of</strong>new right-<strong>of</strong>-way <strong>for</strong> the interchange footprint. The right-<strong>of</strong>-way <strong>for</strong> N. <strong>Beck</strong> <strong>Road</strong> is not included in thismeasurement because it has already been dedicated to the <strong>City</strong>.Construction requirements <strong>for</strong> the Centennial Trail would be consistent with <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> designstandards (12-foot paved, multi-use trail with Americans with Disabilities Act (ADA) - compliant grades). Aconnection between the Centennial Trail and the sidewalk and bike lanes would be constructed onW. Riverbend Avenue and W. Pointe Parkway <strong>for</strong> non-trail access across I-<strong>90</strong>. To provide continuousoperation <strong>of</strong> the Centennial Trail during construction, plans would indicate where temporary connectionswould be constructed.The design concept drawing shown in Figure 2-4 illustrates the conceptual provisions <strong>for</strong> bicycle andpedestrian facilities. Where possible, pedestrian sidewalks would be 6 feet wide and detached from theroadway. Where right-<strong>of</strong>-way or other constraints preclude a detached sidewalk, pedestrian sidewalks wouldbe attached to the roadway section. Bicycle travel would be accommodated with 5-foot, on-street bicyclelanes. For both the multi-use trail and sidewalks, ADA-accessible ramps would be provided at all crossings.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>2-13Project No. A010(963)June 2011


Chapter 3: Affected Environment, <strong>Environmental</strong> Consequences,and Mitigation3.1 IntroductionThis chapter describes the affected human environment (baseline conditions) that could be affected byconstruction, operation and maintenance <strong>of</strong> the Proposed Action (Pointe Parkway Standard DiamondInterchange Alternative). It also documents the environmental consequences (impacts) <strong>of</strong> the Proposed Actionon the quality <strong>of</strong> the human environment.The “affected environment” describes the existing physical status <strong>of</strong> the resources in the area influenced bythe project. The “human environment” is defined in this study as all the environmental resources, includingphysical, biological, social, and economic conditions occurring in the project area.This chapter focuses on the environmental elements that are expected to be directly or indirectly andindividually or cumulatively affected by the project.3.2 Cultural ResourcesThis section summarizes compliance with requirements <strong>of</strong> Section 106 <strong>of</strong> the National Historic PreservationAct related to baseline conditions and potential effects on cultural resources. This section is based on thefindings presented in the documents, I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange Cultural Resources Survey (ITD 2008) andArchaeological and Historic Survey Report, I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Area Interchange Project (TAG 2011). Bothdocuments are available from ITD District 1 upon request.3.2.1 Affected EnvironmentCultural PropertiesSection 106 <strong>of</strong> the National Historic Preservation Act, as amended, requires that federal agencies identify andassess the effects <strong>of</strong> federally-assisted undertakings on historic resources, archaeological sites, and traditionalcultural properties and consult with others to find acceptable ways to avoid or mitigate adverse effects.Resources protected under Section 106 are those that are listed or eligible <strong>for</strong> listing on the National Register<strong>of</strong> Historic Places (NRHP). Eligible properties generally must be at least 50 years old, possess integrity <strong>of</strong>physical characteristics, and are described as follows:The quality <strong>of</strong> significance in American history, architecture, archeology, engineering, andculture is present in districts, sites, buildings, structures, and objects that possess integrity <strong>of</strong>location, design, setting, materials, workmanship, feeling, and association.Eligible properties must also meet at least one <strong>of</strong> four criteria <strong>of</strong> significance:1. Association with a significant historic event2. Association with any significant person3. Architectural significance4. Likelihood to yield in<strong>for</strong>mation important to historyThe Area <strong>of</strong> Potential Effect (APE) is the term used in cultural resource surveys to define the area <strong>of</strong> detailedstudy. For the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project, the APE is the area <strong>of</strong> the Proposed Action and adjacentproperty as shown in Figure 3-1.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-1Project No. A010(963)June 2011


Two levels <strong>of</strong> cultural resource surveys were conducted <strong>for</strong> this project as described below.Cursory-level Survey – The first was a cursory-level survey conducted in 2008 by ITD (ITD 2008) to locatesites and determine probable eligibility <strong>for</strong> the NRHP. This in<strong>for</strong>mation was used to support alternativesevaluation activities <strong>for</strong> the IJR (HDR 2010). The area surveyed encompassed the entire project area: PleasantView <strong>Road</strong> Interchange to the east, State Line <strong>Road</strong> Interchange to the west, W. Seltice Way to the north, andthe Spokane River to the south.This initial survey identified thirteen properties within or near the project area as potentially historic structures(no archaeological sites were identified). Six <strong>of</strong> the thirteen sites were considered probably eligible <strong>for</strong> theNRHP. One <strong>of</strong> those six sites, the Old I-<strong>90</strong> Bridge that crossed the Spokane River at Appleway Avenue inSpokane County, Washington, was demolished in 2010 due to safety concerns (see Figure 3-1 <strong>for</strong> location).This bridge is currently being reconstructed by Spokane County. The demolition and reconstruction <strong>of</strong> thisbridge would change the eligibility <strong>of</strong> this site. Of the 13 sites, only the Jacklin Seed Company facility islocated within the APE. Refer to the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange <strong>Environmental</strong> Scan (HDR 2010) <strong>for</strong> the 13potential NRHP sites within or adjacent to the project area.Section 106 Cultural Resources Survey – The second survey was completed after the selection <strong>of</strong> theProposed Action and is the detailed Section 106 cultural resource survey <strong>for</strong> the APE (TAG 2011). Thissurvey was conducted in January 2011 to locate, record, and assess any prehistoric and historic or culturalresources. It identified two potentially historic sites within the APE (Figure 3-1):• Coeur d’Alene-Spokane Electric Interurban Railway (currently the Centennial Trail): This siteconsists <strong>of</strong> an old alignment <strong>of</strong> the railroad that is now a paved and graded pedestrian and bicyclethoroughfare within the APE. The Coeur d’Alene Spokane Electric Interurban railroad was built in1<strong>90</strong>3, and in 1<strong>90</strong>6 merged with another company to <strong>for</strong>m the Spokane and Inland Empire RailwayCompany. The Interurban line ran between Spokane and Hayden Lake, Idaho, via <strong>Post</strong> <strong>Falls</strong>, Gibbs,Coeur d’Alene and Dalton. The 37-mile trail begins in Spokane, where it is known as the SpokaneRiver Centennial Trail. When the trail crosses the Idaho border it becomes the North IdahoCentennial Trail, ending at Coeur d’Alene.The railroad alignment has been recommended eligible <strong>for</strong> inclusion in the NRHP under Criterion A<strong>for</strong> its association with events significant to local, regional and national history. However, thesegment within the APE has been paved. No rails, ties, or other railroad-related features wereobserved within or adjacent to the APE. As a result <strong>of</strong> the disturbance to this segment, it is likelynoncontributing, and would not be eligible <strong>for</strong> the NRHP (Table 3-1).• Jacklin Seed Company: This site at 5300 W. Riverbend Avenue is associated with Jacklin SeedCompany, which is world-renowned <strong>for</strong> grass-seed research and production and an important aspect<strong>of</strong> Kootenai County’s economy in the late twentieth century. The complex is comprised <strong>of</strong> 22buildings with two buildings more than 50 years old (a cabin and an outhouse are circa 1956). Whilethese two buildings meet the age criteria, they lack integrity <strong>of</strong> design, workmanship and materials.The site is not significant architecturally and is not eligible <strong>for</strong> inclusion in the NRHP (Table 3-1).Table 3-1. Summary <strong>of</strong> Cultural Resources in the APESite (Site ID No.) Eligible? Proposed ActionCoeur d’Alene-Spokane Electric Interurban Railway –currently the Centennial Trail (10KA392)NoNo EffectJacklin Seed Company (JA001) No No EffectI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-3Project No. A010(963)June 2011


Coeur d’Alene TribeThe project area is in the traditional territory <strong>of</strong> the Coeur d’Alene Tribe who occupied an area <strong>of</strong> at least6,200 square miles centered on Lake Coeur d’Alene, its major tributaries, and the Spokane River. Coeurd’Alene villages were <strong>for</strong>mally grouped into three bands: one on the Spokane River, a second on the Coeurd’Alene River, and a third on the St. Joe River. Reportedly the largest Coeur d’Alene village was at the outlet<strong>of</strong> Lake Coeur d’Alene where the Spokane River begins. Another village at <strong>Post</strong> <strong>Falls</strong> was called “Q’emiln,”meaning “throat <strong>of</strong> the river” (TAG 2011).During the winter, the Coeur d’Alene remained in their villages along the major water sources, subsisting ontrout and whitefish, deer, elk, moose, and small animals from the surrounding <strong>for</strong>ests, and roots crops andberries they collected the previous summer. When spring arrived, members <strong>of</strong> the winter villages set out <strong>for</strong>the outlying prairies to gather the root crops, including camas, bitterroot, and cous. By mid-summer and intoearly fall the last <strong>of</strong> the camas would have been harvested and berry picking would begin.The Coeur d’Alene trekked higher into the hills along the mountain streams to collect well over a dozendifferent types <strong>of</strong> berries – the most popular being huckleberries, serviceberries, and chokecherries. In latefall, the “water potato” (broad-leafed arrowhead) would be collected from the marshes around Lake Coeurd’Alene. This practice was unique to the Coeur d’Alene Tribe (Frey n.d.). When winter began to set in, theCoeur d’Alene returned to their houses along the lake shores and river banks.Coeur d’Alene housing consisted <strong>of</strong> long communal houses that were essentially lean-to structures up to <strong>90</strong>feet long and constructed with poles covered with tulle woven into mats. Each family within the communallodge had their own fire pit. The Coeur d’Alene also occupied cone-shaped, tulle-covered lodges.Lewis and Clark recorded a meeting between traders and the Coeur d’Alene at a Nez Perce camp during the1805 expedition. In 1842 Jesuit missionaries met with the Coeur d’Alene Tribe and founded a settlement atthe south end <strong>of</strong> Lake Coeur d’Alene. In response to Euro-American mining pressures and land reduction <strong>of</strong>the reservation by treaties, the mission was moved twice be<strong>for</strong>e being established at DeSmet, Idaho, in the1870s. The Coeur d’Alene Reservation was established in 1873, and opened to non-tribal settlement in 1<strong>90</strong>9.Coeur d’Alene Tribe testimony indicates that the general area (I-<strong>90</strong> corridor west <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>) may havebeen used <strong>for</strong> horse racing. Likely cultural resources associated with this activity might include gamingmarkers, or those associated with camping, or food processing.3.2.2 <strong>Environmental</strong> ConsequencesNo-BuildThere would be no impacts on cultural resources under the No-Build Alternative.Proposed ActionDirect ImpactsTwo sites identified in the APE <strong>for</strong> this project, the Coeur d’Alene-Spokane Electric Interurban Railway andthe Jacklin Seed Company, are not eligible <strong>for</strong> listing on the NRHP. Thus, under Section 106 criteria, thereare no effects to cultural resource sites under the Proposed Action. The Idaho State Historic PreservationOffice (SHPO) approved these findings by signing the ITD <strong>for</strong>m 1502 - Determination <strong>of</strong> Significance andEffect included in Appendix A.There are no known prehistoric sites adjacent to or within the APE based on review <strong>of</strong> documents andinterviews with the Coeur d’Alene Tribe. Tribal testimony indicates that there may have been horse racing inthe general area. This activity may include cultural resources such as gaming markers, or items associatedwith camping sites or food preparation areas. The Proposed Action does not encroach on the banks <strong>of</strong> theI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-4Project No. A010(963)June 2011


Spokane River, where potential prehistoric sites could be found. However, construction activities may resultin the unexpected discovery <strong>of</strong> buried archaeological or paleontological resources or artifacts. Constructionactivities would be stopped following any such discovery, and the ITD cultural resources staff notified.Consultation with SHPO and the Coeur d’Alene Tribe would be conducted prior to resuming construction.Indirect ImpactsThe National Historic Preservation Act Section 106 applies to federal actions, such as the Proposed Action,but does not apply to private development. Thus, potential impacts to historic structures, such as demolition<strong>of</strong> buildings, could occur from interrelated and interdependent development, since there would not be thesame level <strong>of</strong> protection as with federal projects. The Proposed Action would likely accelerate development(see Section 3.7 <strong>for</strong> discussion <strong>of</strong> induced development); however, it is likely that the area would ultimatelybe developed with or without the Proposed Action. Thus, impacts to historic structures (e.g. removing <strong>of</strong> ahistoric building <strong>for</strong> a residential development) would likely occur regardless <strong>of</strong> the Proposed Action.Cumulative ImpactsAs defined in Chapter 2, cumulative impacts are impacts on the environment that result from the incrementalimpact <strong>of</strong> the Proposed Action when added to other past, present, and reasonably <strong>for</strong>eseeable future actions,regardless <strong>of</strong> what agency or person undertakes them. Cumulative impacts on cultural resources areanticipated with planned area-wide development. However, as described above, National HistoricPreservation Act Section 106 does not provide the same level <strong>of</strong> protection (required mitigation) <strong>for</strong> privatedevelopment compared to federal projects. While overall development in the area (past, present and<strong>for</strong>eseeable) may result in impacts to historic properties such as historic buildings (e.g., removing <strong>of</strong> a historicbuilding <strong>for</strong> a residential development), it would likely occur regardless <strong>of</strong> the Proposed Action.MitigationThe Proposed Action would have no effects on NRHP eligible properties. Coeur d’Alene Tribal testimonyindicates that there is potential <strong>for</strong> tribal related cultural resources in the project area related to horse racing.Likely cultural resources associated with this activity might include gaming markers, or those associated withcamping, or food processing. Because <strong>of</strong> the potential <strong>for</strong> tribal cultural resources in the project area, and atthe request <strong>of</strong> the Tribe, a qualified archeologist will be on-site during project geotechnical soil samplingactivities. The archeologist will evaluate the soil samples on-site <strong>for</strong> evidence <strong>of</strong> archaeological orpaleontological artifacts. If artifacts are found, ITD cultural resource staff will be notified. In addition, duringconstruction, if evidence <strong>of</strong> archeological or paleontological artifacts is discovered, ITD cultural resource staffwill be notified. ITD staff will be responsible <strong>for</strong> notifying the Coeur d’Alene Tribe and SHPO. The Coeurd’Alene Tribe and ITD will be provided the construction schedule at least 15-days prior to initiation <strong>of</strong> fieldconstruction activities. In addition, key field personnel <strong>for</strong> the contractor will participate in a 1- hour culturalresource awareness training conducted by the Coeur d’Alene Tribe.3.3 Section 4(f) and Section 6(f) Resources3.3.1 Affected EnvironmentSection 4(f) ResourcesThe Department <strong>of</strong> Transportation Act <strong>of</strong> 1966 included a special provision – Section 4(f) – which stipulatedthat the FHWA and other U.S. Department <strong>of</strong> Transportation (DOT) agencies cannot use land from publiclyowned parks, recreational areas, wildlife and waterfowl refuges, or public and private historical sites unlessthe following conditions apply:There is no feasible and prudent alternative to the use <strong>of</strong> landI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-5Project No. A010(963)June 2011


• The action includes all possible planning to minimize harm to the property resulting from useWhile a Section 4(f) evaluation is a separate and distinct legal requirement, FHWA incorporates the 4(f)evaluation into its environmental documents as required by federal regulations (23 CFR §§ 771.105(a) and771.135(i)).Section 4(f) resources can include publicly owned land from a public park, recreation area, or wildlife refuge,or any land <strong>of</strong> historic significance. Potential 4(f) sites were considered when defining and evaluatingalternatives <strong>for</strong> the project. Federal code defines several uses <strong>of</strong> land or resources that may be subject toSection 4(f) requirements. They include:• A use that can occur when land is permanently incorporated into a transportation facility or whenthere is a temporary occupancy <strong>of</strong> the land that is adverse to a 4(f) resource.• A use that can also occur (called a “constructive use”) when a project’s proximity impacts are sosevere that the protected activities, features, or attributes that qualify a resource <strong>for</strong> protection under4(f) are “substantially impacted” (e.g., by noise, aesthetic impairment, diminished wildlife habitat)Under Section 4(f), a feasible and prudent alternative that avoids the use <strong>of</strong> Section 4(f) resources must besought. If such an alternative cannot be developed, the alternative that does the least harm to Section 4(f)resources must be chosen. To choose this alternative, an evaluation <strong>of</strong> the relative importance <strong>of</strong> the resourcesbeing used and the relative severity <strong>of</strong> the uses is required.In August 2005, Section 6009(a) <strong>of</strong> the Safe, Accountable, Flexible, and Efficient Transportation Equity Act:A Legacy <strong>for</strong> Users was the first substantive revision to Section 4(f) since 1966. Section 6009, whichamended existing Section 4(f) legislation at both Title 49 U.S. Code Section 303 and Title 23 U.S. CodeSection 138, simplified the process and approval <strong>of</strong> projects that have only de minimis (insignificant) impactson lands impacted by Section 4(f).Under the new provisions, once the DOT determines that a transportation use <strong>of</strong> Section 4(f) property resultsin an insignificant impact, analysis <strong>of</strong> avoidance alternatives is not required and the Section 4(f) evaluationprocess is complete. On March 12, 2008 FHWA issued a Final Rule on Section 4(f) that clarifies the 4(f)approval process and simplifies its regulatory requirements, and provides guidance <strong>for</strong> determining deminimis impacts. The Final Rule also moved the Section 4(f) regulation to 23 CFR 774. The de minimiscriteria <strong>for</strong> parks, recreation areas and wildlife and waterfowl refuges are met when:1. The transportation use <strong>of</strong> the Section 4(f) resource, together with any impact avoidance,minimization, and mitigation or enhancement measures incorporated into the project, does notadversely affect the activities, features, and attributes that qualify the resource <strong>for</strong> protection underSection 4(f);2. The <strong>of</strong>ficial(s) with jurisdiction over the property are in<strong>for</strong>med <strong>of</strong> FHWA’s intent to make the deminimis impact finding based on their written concurrence that the project will not adversely affectthe activities, features, and attributes that qualify the property <strong>for</strong> protection under Section 4(f); and3. The public has been af<strong>for</strong>ded an opportunity to review and comment on the effects <strong>of</strong> the project onthe protected activities, features, and attributes <strong>of</strong> the Section 4(f) resource.The project team conducted land-use reviews to determine the presence <strong>of</strong> potential protected Section 4(f)resources within the project area. The land-use review consisted <strong>of</strong> field observations <strong>for</strong> parks, recreationareas and wildlife and waterfowl refuges and a Section 106 cultural resources survey.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-6Project No. A010(963)June 2011


The Centennial Trail (Figure 3-2), located on the south side<strong>of</strong> I-<strong>90</strong>, is the only 4(f) property within the footprint <strong>of</strong> oradjacent to the Proposed Action. The portion <strong>of</strong> the trail in thearea <strong>of</strong> the Proposed Action is managed by Kootenai CountyParks and Recreation and is considered a recreationalresource. The trail is a non-motorized, multi-use recreationaltrail, which starts at Higgins Point (adjacent to Lake Coeurd’Alene Idaho) and meanders <strong>for</strong> 24 miles to theIdaho/Washington state line. The trail continues another 37miles into Washington to Nine Mile <strong>Falls</strong>.The Centennial Trail is ADA-compliant. The trail attractsmany recreationists, including in the late fall and early winter<strong>for</strong> those hoping to view bald eagles as they migrate south.The trail, which was built by dedicated public funds, hasreceived national acclaim and was designated a MillenniumTrail by Hillary Clinton in 1999. The portion <strong>of</strong> the trail in theproject area is paved and follows the south side <strong>of</strong> I-<strong>90</strong>.Figure 3-2. Centennial Trail south <strong>of</strong> I-<strong>90</strong>,looking westSection 6(f) ResourcesSection 6(f) <strong>of</strong> the Land and Water Conservation Funds Act applies to all projects that impact recreationallands purchased or improved with land and water conservation funds. The Secretary <strong>of</strong> the Interior mustapprove any conversion <strong>of</strong> property acquired or developed with assistance under this act to other than public,outdoor recreation use (ITD 2011). No Section 6(f) resources occur in the project area.3.3.2 <strong>Environmental</strong> ConsequencesNo-BuildThere would be no impacts on Section 4(f) or Section 6(f) resources under the No-Build Alternative becausethe Centennial Trail would continue to function as it does today.Proposed ActionThe Proposed Action would include the re-alignment <strong>of</strong> the Centennial Trail where the interchange connectsto W. Riverbend Avenue (Figure 2-4). At the interchange, the trail would be diverted to the south where itwould pass under the interchange structure (undercrossing) and then be diverted back to the original pathparallel with I-<strong>90</strong>. The trail also would be connected to a shared-use sidewalk that provides direct access tothe interchange and W. Pointe Parkway and N. <strong>Beck</strong> <strong>Road</strong> north <strong>of</strong> I-<strong>90</strong>.The proposed Centennial Trail re-alignment would not cross any roads and does not impact the continuity <strong>of</strong>the trail <strong>for</strong> users (e.g., there would be no stop signs or at grade road crossings). The re-alignment <strong>of</strong> the trailwould be consistent with the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and Kootenai County design standards (12-foot, paved, multiusetrail with ADA-compliant grades). The Centennial Trail will remain open during construction, but somedisruption <strong>of</strong> trail access such as temporary detours, gravel/dirt resurfacing and flagging could occur. Everyattempt would be made to minimize disruption, and construction plans would clearly indicate locations <strong>for</strong>temporary connections. The activities, features, and attributes <strong>of</strong> the current trail system that qualify thisresource <strong>for</strong> protection under Section 4(f) would be restored once construction is complete.Kootenai County and the North Idaho Centennial Trail Foundation, which have jurisdiction over theCentennial Trail in the project area, have both concurred in writing that the Proposed Action would notadversely affect the activities, features or attributes <strong>of</strong> the trail that qualify it as a 4(f) resource. Furthermore,I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-7Project No. A010(963)June 2011


the connection <strong>of</strong> the trail system to the proposed interchange is viewed as an enhancement that provides trailusers access to and from areas north <strong>of</strong> I-<strong>90</strong>. County and foundation <strong>of</strong>ficials were notified that, based on thatconcurrence, FHWA intends to make a finding <strong>of</strong> de minimis impact (no adverse impact) on the trail. A 4(f)de minimis finding that further describes these conclusions is presented in Appendix B.Since no Section 6(f) resources are present in the project area, the Proposed Action would have no impact onthese resources.3.4 Wetlands and Waters <strong>of</strong> the United StatesThis section describes existing wetlands and open waters and evaluates impacts <strong>of</strong> the Proposed Action onthese resources.3.4.1 Affected Environment<strong>Assessment</strong>s <strong>of</strong> the Waters <strong>of</strong> the U.S. and associated wetlands were conducted by the project team in 2007and 2011 in accordance with the U.S. Army Corps <strong>of</strong> Engineers (USACE) 1987 Wetlands DelineationManual. The requirements <strong>for</strong> such delineation are contained in Section 404 <strong>of</strong> the Clean Water Act, whichrequires authorization through the USACE <strong>for</strong> the discharge <strong>of</strong> dredged or fill material into all Waters <strong>of</strong> theU.S., including wetlands. Waters <strong>of</strong> the U.S. is defined by U.S. <strong>Environmental</strong> Protection Agency (USEPA)on their website: http://www.epa.gov/owow_keep/wetlands/guidance/CWAwaters.html.In addition to the USACE regulations, Executive Order 119<strong>90</strong> (applies to all federal agencies) and 23 CFR777 (applies to FHWA projects) requires that agencies, to the extent permitted by law, shall avoid undertakingor providing assistance <strong>for</strong> new construction located in wetlands (both jurisdictional and non-jurisdictionalwetlands) unless the head <strong>of</strong> the agency finds (1) that there is no practicable alternative to such construction,and (2) that the Proposed Action includes all practicable measures to minimize harm to wetlands that mayresult from such use.The project team conducted field surveys to identify and assess Waters <strong>of</strong> the U.S. and associated specialaquatic sites within the area that would be potentially impacted by the Proposed Action. Identified waters inthe project area have been divided into two categories: natural waters and stormwater-related waters.The 2007 and 2011 field surveys were conducted in the area <strong>of</strong> the Proposed Action (same general footprintas presented <strong>for</strong> the cultural resource APE in Figure 3-1) to assess the presence <strong>of</strong> wetlands. No evidence wasfound <strong>of</strong> wetland vegetation and/or saturated soils that could support wetlands. The area north <strong>of</strong> I-<strong>90</strong>, whichhad been in agricultural production, was re-graded in recent years <strong>for</strong> commercial and industrial development,including stormwater controls. The area south <strong>of</strong> I-<strong>90</strong> isdeveloped with roads, parking areas, and buildings.Stormwater drainages north <strong>of</strong> I-<strong>90</strong> are localized (they do notcross south <strong>of</strong> I-<strong>90</strong>) and there is no evidence that they leaddirectly to the Spokane River in the area <strong>of</strong> the ProposedAction. USACE verified in a letter dated May 17, 2011 thatthe project site does not contain wetlands or waters <strong>of</strong> theU.S. A copy <strong>of</strong> the letter is presented in Appendix D.Figure 3-3. Jacklin Seed fire-suppressionpondI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>A man-made fire-suppression pond is located on the JacklinSeed Company property south <strong>of</strong> I-<strong>90</strong> within the footprint <strong>of</strong>the Proposed Action (Figure 3-3 and Figure 3-6). Thegeotextile-lined pond is about 530 feet from the SpokaneRiver and is not hydrologically connected. It has novegetation on or near its banks and there is no evidence <strong>of</strong>seepage. The area surrounding the pond has been graded andis largely disturbed by operations <strong>of</strong> the adjacent commercial3-8Project No. A010(963)June 2011


facilities.Officials with the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and Jacklin Seed indicated that the pond is no longer in use. Jacklin hadconstructed the pond be<strong>for</strong>e it was served by the city’s potable water system, and needed a water supply <strong>for</strong>fire protection. A pump station associated with the pond isbeing dismantled by Jacklin Seed.The Spokane River flows from east to west on the south side<strong>of</strong> the project area and is the only natural drainage in theproject area (Figure 3-4 and Figure 3-6). The river isapproximately 100 miles long, beginning as the outlet <strong>for</strong>Lake Coeur d’Alene and ending as a tributary to theColumbia River. The River drains from the northwest corner<strong>of</strong> Lake Coeur d’Alene near the <strong>City</strong> <strong>of</strong> Coeur d'Alene andflows west approximately 25 miles into east centralWashington through the suburban Spokane Valley toSpokane. The Spokane River is a Water <strong>of</strong> the U.S. and anywetlands or waters hydraulically connected to the river arealso Waters <strong>of</strong> the U.S. Additional in<strong>for</strong>mation on theSpokane River is provided in Section 3.6 <strong>of</strong> this report.The southernmost boundary <strong>of</strong> the Proposed Action is a driveway that is proposed to connect the interchangeto the Jacklin Seed property (Figure 2-4). The gravel driveway is approximately <strong>90</strong> feet from the banks <strong>of</strong> theSpokane River and is approximately 60 feet higher in elevation. Jacklin Seed uses this area <strong>for</strong> parking andstorage.3.4.2 <strong>Environmental</strong> ConsequencesNo-BuildThere would be no direct or indirect impacts on open water or wetlands under the No-Build Alternative.Future open water and wetland conditions in the project area would remain largely the same as today. Therecould be impacts associated with development, which is expected to continue under the No-Build Alternative.Developers would be required to follow the Clean Water Act requirements <strong>for</strong> wetlands and waters underU.S. protection.Proposed ActionDirect ImpactsFigure 3-4. Spokane River south <strong>of</strong>project areaStormwater run<strong>of</strong>f from the construction and operation <strong>of</strong> the Proposed Action would be designed to beretained on-site. No direct stormwater discharge from the Proposed Action to the river would occur. Forconstruction, the project would obtain a stormwater permit and develop and implement a StormwaterPollution Prevention Plan (SWPPP). Final design specifications would include necessary stormwater andemergency response permits and programs. With stormwater retention on-site, implementation <strong>of</strong> stormwaterBest Management Practices (BMPs), including filtering <strong>of</strong> sediment, direct impacts to the Spokane Riverwould not occur under the Proposed Action.There would be no direct wetland impacts in the area <strong>of</strong> the Proposed Action because there are no wetlands.The Proposed Action would have a direct impact on the fire-suppression pond at the Jacklin Seed facility.However, this lined, man-made pond has no hydraulic connection to the Spokane River, and has novegetation. Since the pond is no longer in use or required by facilities on W. Riverbend Avenue, it would notbe replaced.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-9Project No. A010(963)June 2011


Indirect ImpactsThe Proposed Action would likely accelerate development in the area, but the area is expected to ultimatelybe developed with or without the Proposed Action. Development could result in the loss <strong>of</strong> wetlands and openwater. However, all construction projects (private or federal actions) would be required to obtain a Section404 permit <strong>for</strong> the discharge <strong>of</strong> dredged or fill material into all Waters <strong>of</strong> the U.S., including wetlands. Such apermit would address minimizing impacts and mitigation if impacts occur.A National Pollutant Discharge Elimination System (NPDES) Construction General Permit is required <strong>for</strong>projects that disturb more than 1 acre <strong>of</strong> soil and could have the potential to discharge stormwater to Waters<strong>of</strong> the U.S. This permit will address controlling stormwater run<strong>of</strong>f from construction activities. Withappropriate design specifications, on-site stormwater retention, stormwater and emergency response permitsand programs, and implementation <strong>of</strong> stormwater BMPs, there would be no indirect impacts to the SpokaneRiver.Cumulative ImpactsThere would be no cumulative impacts <strong>for</strong> wetlands or Waters <strong>of</strong> the U.S. because the Proposed Action doesnot disturb these resources. While the fire-suppression pond would be impacted by the Proposed Action, thisfeature is neither a wetland nor a Water <strong>of</strong> the U.S. Additionally, development in the area would be requiredto comply with Section 404 <strong>of</strong> the Clean Water Act and mitigate <strong>for</strong> any wetlands or Waters <strong>of</strong> the U.S.impacts.MitigationNo direct impacts on wetlands or Waters <strong>of</strong> the U.S. would occur under the Proposed Action. No mitigationwould be required <strong>for</strong> the fire-suppression pond at Jacklin Seed because it is no longer in use or required, and<strong>of</strong>ficials with the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and Jacklin Seed have confirmed that no mitigation would be required.For construction practices, measures to minimize potential secondary impacts on the Spokane River are asfollows:• Procedures to protect the Spokane River and adjacent properties during construction will be addressedin the Construction General Permit, local stormwater permits and the SWPPP.3.5 Biological ResourcesThis section describes the affected biological environment and evaluates impacts on vegetation, fish, andwildlife, including threatened and endangered species under the Proposed Action. The biological reviewconsisted <strong>of</strong> a request <strong>for</strong> in<strong>for</strong>mation from the Idaho Conservation Data Center (IDCDC), a review <strong>of</strong> thelatest threatened and endangered species lists from the U.S. Fish and Wildlife Service (USFWS) and theNational Marine Fisheries Service (NMFS), and a review <strong>of</strong> pertinent species in<strong>for</strong>mation <strong>for</strong> the area.3.5.1 Affected EnvironmentVegetationThe land surface in the area <strong>of</strong> the Proposed Action has been mostly disturbed (Figure 1-2). Vegetation north<strong>of</strong> I-<strong>90</strong> is mostly weed species with some native grasses and <strong>for</strong>bs. This area was once under agriculturalproduction, but is now being developed and much <strong>of</strong> the ground surface has been graded (re-sloped). South <strong>of</strong>I-<strong>90</strong>, the project area is developed into roads, parking lots, and buildings with some landscaping. No naturalvegetation is present. Some wetland vegetation occurs near the edges <strong>of</strong> the Spokane River.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-10Project No. A010(963)June 2011


Noxious WeedsNoxious weeds degrade natural habitat, choke streams, crowd native plants, create fire hazards, poison andinjure livestock and humans, and foul recreation sites. Areas that have been disturbed are at particular risk <strong>of</strong>weed encroachment. In<strong>for</strong>mation on Idaho’s noxious weed <strong>for</strong> Kootenai County is available on their website.According to the Idaho State Department <strong>of</strong> Agriculture, Idaho has 64 species <strong>of</strong> weeds that are designatednoxious by state law. The Kootenai County Noxious Weed Control Department reports 23 noxious weeds, 20<strong>of</strong> which are also on the state list. Table 3-2 lists the noxious weed species that are known or reported tooccur in Kootenai County.Table 3-2. Noxious Weed Species Known or Reported to Occur in Kootenai CountyCommonSpecies NameScientificWeed List SourceBlueweed Echium vulgare Kootenai County/State <strong>of</strong> IdahoCommon tansy Tanacetum vulgare Kootenai CountyEurasian watermilfoil Myriophyllum spicatu Kootenai County/State <strong>of</strong> IdahoField bindweed Convolvulus arvensis Kootenai County/State <strong>of</strong> IdahoOrange hawkweed Hieracium aurantiacu Kootenai County/State <strong>of</strong> IdahoYellow hawkweed Hieracium pratense Kootenai County/State <strong>of</strong> IdahoHoundstongue Sismgrium altissimum Kootenai County/State <strong>of</strong> IdahoSpotted knapweed Centaurea maculosa Kootenai County/State <strong>of</strong> IdahoJapanese knotweed Polygonum cuspidatum Kootenai County/State <strong>of</strong> IdahoKochia Kochia scoparia Kootenai CountyLeafy spurge Euphorbia esula Kootenai County/State <strong>of</strong> IdahoOxeye daisy Chrysantemum leucant Kootenai County/State <strong>of</strong> IdahoPoison hemlock Conium maculatum Kootenai County/State <strong>of</strong> IdahoPurple loosestrife Lythrum salicara Kootenai County/State <strong>of</strong> IdahoRush skeletonweed Chondrilla juncea Kootenai County/State <strong>of</strong> IdahoScotch broom Cytisus scoparius Kootenai County/State <strong>of</strong> IdahoSt. Johnswort Hypericum per<strong>for</strong>atum Kootenai CountyTansy Ragwort Senecio jacobaea Kootenai County/State <strong>of</strong> IdahoCanada thistle Cirsium arvense Kootenai County/State <strong>of</strong> IdahoScotch thistle Onopordum acanthium Kootenai County/State <strong>of</strong> IdahoDalmatian toadflax Linaria damartica Kootenai County/State <strong>of</strong> IdahoYellow toadflax Linaria vulgaris Kootenai County/State <strong>of</strong> IdahoYellow starthistle Centaurea solstitias Kootenai County/State <strong>of</strong> IdahoI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-11Project No. A010(963)June 2011


Fish and WildlifeSpecies <strong>of</strong> ConcernSpecies <strong>of</strong> concern are native species that are not listed as threatened or endangered but have been identifiedby IDCDC as being low in numbers, limited in distribution, or having suffered habitat loss. IDCDC lists thefollowing aquatic species <strong>of</strong> concern <strong>for</strong> the segment <strong>of</strong> the Spokane River adjacent to the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project:• Brook trout• Rainbow trout• Brown trout• Cutthroat trout• Pumpkinseed sunfish• Yellow perch• Largemouth bass• Dace (small fish)• Speckled DaceCandidate SpeciesCandidate species are plants and animals <strong>for</strong> which the USFWS has sufficient in<strong>for</strong>mation on their biologicalstatus and threats to propose them as endangered or threatened under the Endangered Species Act (ESA), but<strong>for</strong> which development <strong>of</strong> a proposed listing regulation is precluded by other higher priority listing activities.Categorization <strong>of</strong> a species as a candidate is strong evidence that the species is <strong>of</strong> special concern, and may besubject to the full protection <strong>of</strong> the listing process in the future. No consultation or conference is required <strong>for</strong>candidate species. If a candidate species becomes listed be<strong>for</strong>e or during construction, biological evaluationand determination <strong>of</strong> effect would be necessary be<strong>for</strong>e construction could proceed.Appendix C presents Idaho’s ESA-listed species under USFWS jurisdiction (dated May 5, 2011), includingcandidate species. The following candidate species are listed by USFWS in Kootenai County:• Yellow-billed cuckoo (Coccyzus americanus)• Wolverine (Gulo gulo)Threatened and Endangered SpeciesThe threatened and endangered species literature resource review included the USFWS list <strong>of</strong> threatened andendangered species that receive protection under the ESA. An endangered species is one that is in danger <strong>of</strong>extinction throughout all or a significant portion <strong>of</strong> its range. A threatened species is one that is likely tobecome endangered in the <strong>for</strong>eseeable future.Appendix C presents Idaho’s ESA-listed species under USFWS jurisdiction (dated May 5, 2011) and byNMFS (dated July 1, 2009), which is summarized in Table 3-3. This table shows federally-listed endangeredand threatened species <strong>for</strong> Kootenai County, followed by a summary <strong>of</strong> each species’ status.NMFS lists anadromous fish species by river basin. No ESA federally-listed anadromous fish species underNMFS jurisdiction are listed <strong>for</strong> the Spokane River, the only natural drainage in the project area.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-12Project No. A010(963)June 2011


Table 3-3. Federally-listed ESA Species in Kootenai County (USFWS and NMFS)Scientific Name Common Name StatusLynx Canadensis Canada Lynx Listed ThreatenedSalvelinus confluentus Bull Trout Listed Threatened, Designated Critical HabitatHowellia aquatilis Water Howellia Listed ThreatenedSilene spaldingii Spalding’s Catchfly Listed ThreatenedMigratory Bird ActThis federal law, administered by the USFWS, makes it unlawful to take, import, export, possess, sell,purchase, or barter any migratory bird, with the exception <strong>of</strong> the taking <strong>of</strong> game birds during establishedhunting seasons. The law also applies to feathers, eggs, nests, and products made from migratory birds. Fortransportation projects, this law can be a concern when the project disturbs migratory bird nests such asremoving nests or disturbing nesting habitats (e.g., vibration noise from machinery).Migratory birds are found in the project area, especially given the proximately <strong>of</strong> the Spokane River, whichwould attract water fowl, and the availability <strong>of</strong> food (e.g., rodents) associated with fields, which wouldattract birds <strong>of</strong> prey. During site surveys, no bird nests (ground or in trees) were observed in the footprint oradjacent to the Proposed Action.Bald Eagle and Golden Eagle Protection ActThis federal law, administered by the USFWS, makes it unlawful to take, import, export, sell, purchase, orbarter any bald or golden eagle, their parts, products, nests, or eggs. Take includes pursuing, shooting,poisoning, wounding, killing, capturing, trapping, collecting, molesting, or disturbing the eagles. Fortransportation projects, the law can be a concern when eagle nests are near projects sites and constructionactivities or the built project disturbs the nesting habits <strong>of</strong> the eagles.During site surveys, no large bird nests were observed in the project area, though bald eagles likely perchalong the Spokane River during the winter months in the project area.3.5.2 <strong>Environmental</strong> ConsequencesNo-BuildUnder the No-Build Alternative, impacts on biological resources in the project area would be limited tocontinued development, periodic herbicide applications, mowing, and surface-water run<strong>of</strong>f from developmentand roads.Proposed ActionConsequences to biological resources under the Proposed Action are described in the following sections.Direct ImpactsPotential impacts to vegetation could result from habitat loss or from disturbance during construction <strong>of</strong> theroadway. Based on preliminary design estimates, construction <strong>of</strong> the Proposed Action would cover about 17acres <strong>of</strong> land with pavement (impervious surfaces). Additional areas that would be disturbed fromconstruction activities would be re-vegetated. The areas that would be permanently disturbed adjacent to W.Pointe Parkway and N. <strong>Beck</strong> <strong>Road</strong> are already disturbed by grading <strong>of</strong> development sites. Land south <strong>of</strong> I-<strong>90</strong>is developed, with little to no remaining natural vegetation or habitat.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-13Project No. A010(963)June 2011


Potential impacts on fish and wildlife in the project area could result from habitat loss or from disturbance,injury, or mortality during construction and use <strong>of</strong> the roadway. Construction activities have the potential todisturb or destroy individual passerine (perching and song birds), small mammal, reptile, and amphibian nestsites or dens and less mobile animals unable to escape the path <strong>of</strong> construction equipment. Other temporaryconstruction-related effects include the disruption <strong>of</strong> normal wildlife activities because <strong>of</strong> construction noise,presence <strong>of</strong> personnel, and heavy equipment operations. During construction, upland game birds wouldmainly disperse to nearby habitat, leading to increased competition <strong>for</strong> resources and the possible permanentdisplacement <strong>of</strong> some individuals. The net effects <strong>of</strong> such activities are not considered to be significant at thepopulation level anticipated in the project area.The IDCDC list <strong>of</strong> Idaho species <strong>of</strong> concern was reviewed to determine if the Proposed Action posed any riskto these species. Species <strong>of</strong> concern in the project area were limited to aquatic species in the Spokane River.The project would have no direct impacts on the Spokane River and would there<strong>for</strong>e have no impact onaquatic species.The potential impacts <strong>of</strong> the Proposed Action on candidate species are as follows:Yellow-billed Cuckoo. The yellow-billed cuckoo is a long-distance migrant. Breeding habitat includes openwoodland, parks, deciduous riparian woodland, tall cottonwood and willow riparian woodland, deciduouswoodlands, moist thickets, orchards, and overgrown pastures. Non-breeding habitat includes <strong>for</strong>est,woodland, and scrub. The yellow-billed cuckoo eats mainly caterpillars. Other food sources include otherinsects, some fruits, small lizards, frogs, and bird eggs (IDFG 2005). Given its habitat preferences, it isunlikely the yellow-billed cuckoo would be found in the project area. There<strong>for</strong>e, the Proposed Action wouldhave no impact on the yellow-billed cuckoo.Wolverine. Wolverine populations in Idaho are centered in the Selkirk Mountains, Lochsa and Kelly Creekdrainages, and the Smoky Mountain complex <strong>of</strong> the Sawtooth Mountains (IDFG 2005). A September 2005IDCDC map shows a small predicted distribution area <strong>for</strong> wolverines approximately 5 miles south <strong>of</strong> theproject area. The nearest point location, or confirmed sighting, is greater than 10 miles north <strong>of</strong> the projectarea. Studies suggest that wolverines are sensitive to human disturbance. It is expected that no wolverineswould use the project area given the developed nature <strong>of</strong> the area and the presence <strong>of</strong> I-<strong>90</strong>. Due to thesensitivity to human disturbance and lack <strong>of</strong> habitat in the project area, the Proposed Action would have noimpact on the wolverine.The status <strong>of</strong> USFWS federally-listed endangered and threatened species in Kootenai County and thepotential effects <strong>of</strong> the Proposed Action on those species are presented below.Canada Lynx. Canada lynx, west <strong>of</strong> the Continental Divide, generally occur in sub-alpine <strong>for</strong>ests between4,000 and 7,050 feet in elevation in stands composed <strong>of</strong> pure lodgepole pine, but also mixed stands <strong>of</strong>subalpine fir, lodgepole pine, Douglas fir, grand fir, western larch and hardwoods. They typically avoid largeopenings, but <strong>of</strong>ten hunt along edges <strong>of</strong> areas <strong>of</strong> dense cover. Habitat <strong>for</strong> the Canada lynx is not present in theproject area due to lack <strong>of</strong> sub-alpine <strong>for</strong>est (IDFG 2005). There<strong>for</strong>e, this species is considered absent and theProposed Action would have no effect on the Canada lynx.Bull Trout. Bull trout normally prefer temperatures <strong>of</strong> less than 54 degrees F (IDFG 2005). Juveniles useruns, riffles and pocket water, but fish over a year old generally select deeper pools while resting. In<strong>for</strong>mationfrom the IDCDC indicates that bull trout are present in the segment <strong>of</strong> the Spokane River south <strong>of</strong> the projectarea. While critical habitat has been designated <strong>for</strong> bull trout in Kootenai County, it does not include theSpokane River, and there are no other natural drainages in the project area. The Proposed Action would haveno direct or indirect impacts on the Spokane River. Stormwater from construction and operation <strong>of</strong> theProposed Action would be contained and managed without discharge to the river. In addition, timber alongthe river banks that may provide shady habitat <strong>for</strong> fish in the river would not be impacted by the ProposedAction (there are few trees along the banks <strong>of</strong> the river in the project area). There<strong>for</strong>e, the Proposed ActionI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-14Project No. A010(963)June 2011


would have no effect on bull trout. Personal communication with Bob Kibler, a biologist with the USFWS onFebruary 7, 2011, supported this determination.Water Howellia. Water howellia is a winter annual aquatic plant that grows 4 to 24 inches high. It is limitedto six clusters <strong>of</strong> populations in Cali<strong>for</strong>nia, Washington, Idaho and Montana. The entire species occupies atotal area <strong>of</strong> less than 200 acres, with most sites less than 1 acre (USFWS 2006). The species is distinctiveenough that it is the only member <strong>of</strong> its genus. Water howellia is restricted to small pothole ponds ororphaned river oxbows. Ponds are almost always surrounded by broadleaf deciduous trees. Since seedsgerminate in the fall and overwinter as seedlings, the species only grows in zones within wetlands that areseasonally inundated, yet dry out in late summer or early fall. Habitat <strong>for</strong> the water howellia is not present inthe project area, and the species is considered absent. There<strong>for</strong>e, the Proposed Action would have no effect onwater howellia.Spalding’s Catchfly. Spalding’s catchfly is a leafy, perennial plant that is endemic to mesic grasslands <strong>of</strong> thePalouse Prairie region in eastern Washington and adjacent portions <strong>of</strong> northeastern Oregon and north-centralIdaho. Throughout its range, much <strong>of</strong> the Palouse Prairie grassland habitat <strong>of</strong> Silene spaldingii has beenconverted to crop agriculture or pastureland. In Idaho, it is associated with relatively undisturbed slopes orflats in swales and drainages, upper canyon slopes, and in small strips <strong>of</strong> native vegetation surrounded bycultivated fields. Sites <strong>of</strong>ten occur near lower treeline or scattered ponderosa trees. There are only 10 knownoccurrences in Idaho. Since the area within the footprint <strong>of</strong> the Proposed Action is disturbed with no nativevegetation, habitat <strong>for</strong> the Spalding’s catchfly does not exist. It may be possible <strong>for</strong> Spalding’s catchfly toexist in undisturbed areas <strong>of</strong> grasslands along the banks <strong>of</strong> the Spokane River south <strong>of</strong> Jacklin Seed outside <strong>of</strong>the Proposed Action footprint (IDFG 2007). However, the Proposed Action would have no direct impacts onthe Spokane River, its banks, or the area south <strong>of</strong> the river. There<strong>for</strong>e, the Proposed Action would have noeffect on the Spalding’s catchfly. Personal communication with Bob Kibler, a biologist with the USFWS onFebruary 7, 2011, supported this determination.During site surveys, no bird nests were observed within the footprint <strong>of</strong>, or adjacent to, the Proposed Action.Furthermore, no eagle nests are found in the project area. Thus, the Proposed Action meets the conditions <strong>of</strong>the Migratory Bird Act and the Bald Eagle and Golden Eagle Protection Act.Indirect ImpactsThe Proposed Action has the potential to indirectly impact existing vegetation and wildlife habitat by theintroduction and invasion <strong>of</strong> noxious weed species. Invasive plant species, including weeds, have the potentialto overrun more desirable species and can significantly reduce the productivity <strong>of</strong> croplands and wildlifehabitats. Disturbance associated with construction can create conditions favorable to the establishment <strong>of</strong>weed populations that are in the area and have potential <strong>for</strong> invasion. In addition, construction vehicles andpersonnel can inadvertently bring weed seeds and other weed parts into the area, assisting in their spread.Since a weed-control plan would be developed as part <strong>of</strong> the design and implemented during construction andduring vegetation establishment <strong>of</strong> disturbed areas, the invasion <strong>of</strong> noxious weeds should be minimal. Thedisturbed areas north <strong>of</strong> I-<strong>90</strong> are currently covered by potentially invasive weed species. By re-seeding orlandscaping these disturbed areas as development occurs, the natural vegetation habitat would be improved.The listed species <strong>of</strong> concern in the project area are aquatic species in the Spokane River. The ProposedAction would not have direct impacts on the Spokane River. As described in Section 3.6, measures would betaken to manage stormwater run<strong>of</strong>f during construction, contain stormwater on-site, and have sufficientstormwater control to prevent impacts on the river.No impacts to threatened and endangered species would occur. Interrelated and interdependent actions areassociated with this project that could result in indirect impacts to fish, wildlife and associated habitat.Potential impacts from development could include removal or disturbance <strong>of</strong> vegetation and loss <strong>of</strong> wildlifehabitat. The sponsors <strong>of</strong> these development projects are responsible <strong>for</strong> complying with environmentalresource regulations, which includes the Migratory Bird Treaty Act, the Bald Eagle and Golden EagleI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-15Project No. A010(963)June 2011


Protection Act, ESA, and the Clean Water Act 404 permitting. The sponsor would be required to mitigate ifadverse impacts occur.Cumulative ImpactsMeasures <strong>of</strong> cumulative impacts <strong>for</strong> wildlife in the area include loss <strong>of</strong> habitat, loss <strong>of</strong> function, and changesin the distribution <strong>of</strong> habitat. Within the general area, habitat has been diminishing due to historic activities(within the past 100 years), including clearing <strong>of</strong> vegetation <strong>for</strong> agriculture and construction <strong>of</strong> roads. Morerecently, habitat has been affected due to residential and commercial development, which can produce anindirect effect <strong>of</strong> introducing more people into the area. Since the Proposed Action would have no impact onthreatened and endangered species, no cumulative impacts on threatened and endangered species wouldoccur.MitigationDisturbed vegetated areas that are not covered by the roadway or interchange will be re-seeded with weedfreevegetation. In addition, a weed control plan will be developed by the contractor that addressesminimizing introduction and spreading <strong>of</strong> noxious weeds. Off-site use areas such as source, waste, andstaging sites will be reviewed <strong>for</strong> threatened and endangered species. If potential effects are identified,consultation will be coordinated with USFWS.3.6 Surface Water, Floodplains, and GroundwaterThis section describes the affected environment and evaluates impacts on surface water, floodplains, andgroundwater.3.6.1 Affected EnvironmentSurface WaterThe surface-water resource review consisted <strong>of</strong> a site visit, a request <strong>for</strong> in<strong>for</strong>mation from the IdahoDepartment <strong>of</strong> <strong>Environmental</strong> Quality (IDEQ) and USEPA, and a review <strong>of</strong> pertinent water qualitydocuments (cited below) <strong>for</strong> the Spokane River. As discussed in Section 3.4, the Spokane River is the onlywaterway in the project area.Figure 3-5. View <strong>of</strong> Spokane River from projectarea just south <strong>of</strong> Jacklin Seed (looking west)The Spokane River flows east to west on the southside <strong>of</strong> the project area (Figure 3-5). The river isabout 100 miles long, beginning as the outlet <strong>for</strong> LakeCoeur d’Alene, and ending as a tributary to theColumbia River. It is the only watercourse over theSpokane Valley Rathdrum Prairie Aquifer (SVRPA)that remains on the surface <strong>for</strong> an extended distance.The Jacklin Seed fire suppression pond described inSection 3.4.1 is located on the Jacklin Seed Companyproperty south <strong>of</strong> I-<strong>90</strong> within the footprint <strong>of</strong> theProposed Action. Additional surface water featuresin the project area include Skalan Creek and CableCreek, which are both located south <strong>of</strong> the SpokaneRiver. A large pond area is also identified south <strong>of</strong> the Spokane River, just northwest <strong>of</strong> W. Laura Lane(Figure 3-6).The flow <strong>of</strong> the Spokane River is regulated by the <strong>Post</strong> <strong>Falls</strong> Dam, a hydroelectric development located near<strong>Post</strong> <strong>Falls</strong> (just east <strong>of</strong> Spokane Street south <strong>of</strong> I-<strong>90</strong>) where the Spokane River divides and flows through threeI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-16Project No. A010(963)June 2011


edrock channels. Each channel contains a dam. The <strong>Post</strong> <strong>Falls</strong> Dam began operating between 1<strong>90</strong>6 and 1<strong>90</strong>8and generates electricity while helping to regulate flooding, store irrigation water, and provide waterrecreation. During most years, the dam gates are left open from December through June, and the flow <strong>of</strong>tenmimics inflows into the Coeur d’Alene Lake from snowmelt run<strong>of</strong>f. During most <strong>of</strong> the summer, however,the gates are set to maintain specific water levels in Coeur d’Alene Lake (Hortness 2005).Water Quality Documents and PermitsSection 303(d) <strong>of</strong> the federal Clean Water Act requires Idaho to develop a list <strong>of</strong> water bodies, subject toUSEPA approval, that do not meet water quality standards. States and tribes must periodically publish apriority list <strong>of</strong> impaired waters, currently every two years. When water quality fails to meet state water qualitystandards, IDEQ determines the causes and sources <strong>of</strong> pollutants in a subbasin assessment and sets maximumpollutant levels called total maximum daily loads (TMDL). For waters identified on this list, states and tribesmust develop water quality improvement plans <strong>for</strong> TMDLs that establish allowable pollutant loads set atlevels to achieve water quality standards.A TMDL sets maximum pollutant levels in a watershed and becomes the basis <strong>for</strong> implementation plans torestore water quality to a level that supports its designated beneficial uses. The implementation plans identifyand describe pollutant controls and management measures (such as BMPs), the mechanisms by which theselected measures would be put into action, and the individuals and entities responsible <strong>for</strong> implementationprojects.IDEQ’s 2008 Integrated 303(d)/305(b) Report <strong>for</strong> Idaho lists the Spokane River watershed from the <strong>Post</strong> <strong>Falls</strong>Dam to the Washington state line (5.67 miles), which includes the portion <strong>of</strong> the river that passes south <strong>of</strong> theproject area. This segment is listed as impaired <strong>for</strong> exceedance <strong>of</strong> water quality criteria <strong>for</strong> cadmium, lead,zinc, and total phosphorus. The presence <strong>of</strong> the cadmium, lead, and zinc in this section <strong>of</strong> the river isattributed to sediment washed down from upstream historic mining operations in the Silver Valley area.Phosphorus is attributed to non-point sources such as agriculture, septic tanks, and point discharges such asthe <strong>City</strong> <strong>of</strong> Coeur d’Alene wastewater treatment plant.A TMDL <strong>for</strong> total phosphorus was developed <strong>for</strong> the upper Spokane River and approved by USEPA inJanuary 2001. An implementation plan is under development, and construction practices would have tocomply with requirements <strong>of</strong> an implementation plan if put in place. A TMDL <strong>for</strong> metals is also beingdeveloped.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-17Project No. A010(963)June 2011


Wild and Scenic RiversRiver systems were also reviewed to determine whether they were eligible <strong>for</strong> protection under the Wild andScenic Rivers Act. Created by Congress in 1968, this law provides protection <strong>of</strong> selected rivers and theirimmediate environments if they possess outstandingly remarkable scenic, recreational, geologic, fish andwildlife, historic, cultural, or other similar values. A Wild and Scenic River status has not been designated <strong>for</strong>the Spokane River (NPS 2007).Stormwater ManagementThe NPDES program regulates discharge <strong>of</strong> stormwater into surface waters. An NPDES Construction GeneralPermit is required <strong>for</strong> projects that disturb more than 1 acre <strong>of</strong> soil and could have the potential to dischargestormwater to Waters <strong>of</strong> the U.S.Current roadway drainages in the area <strong>of</strong> the Proposed Action infiltrate into soils along roadside ditches andswales with little evidence <strong>of</strong> conveyance <strong>of</strong> stormwater. While the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange projectwould not encroach on the Spokane River, stormwater control <strong>for</strong> surface-water protection would be animportant consideration <strong>for</strong> this project. Concept-level design <strong>for</strong> stormwater management under the ProposedAction is further discussed under <strong>Environmental</strong> Consequences (Section 3.6.2).FloodplainsFloodplains are land areas adjacent to rivers and streams that are subject to recurring inundation. Because <strong>of</strong>their connection to river systems, floodplains <strong>of</strong>ten contain wetlands and other areas vital to a diverse andhealthy ecosystem. Floodways are channels <strong>of</strong> a river or watercourse and the adjacent land areas that must bereserved to discharge the 100-year flood without cumulatively increasing the water surface elevation morethan 1 foot. Floodways are only delineated in communities where detailed hydraulic analyses have beencompleted. The floodway is contained within the floodplain.The Federal Emergency Management Agency (FEMA) Flood Insurance Rate Maps (FIRMs) define theregulatory boundaries <strong>of</strong> floodplains along rivers or streams where FIRM studies have been conducted. Thesestudies are maintained by FEMA to determine the “existence and severity <strong>of</strong> flood hazards” and helpadminister the National Flood Insurance Act <strong>of</strong> 1968 and the Flood Disaster Protection Act <strong>of</strong> 1973.FIRMs identify several types <strong>of</strong> flood zones in the project area (Figure 3-7). The floodplain associated withthe Spokane River is designated Zone A5, which means it is an area inundated by 100-year flooding, but nobase flood elevations have been established. The river is located down a steep grade on the south side <strong>of</strong> theproposed interchange. The footprint <strong>of</strong> the Proposed Action is outside the 100-year floodplain.GroundwaterSpokane Valley Rathdrum Prairie AquiferThe project area overlies the SVRPA, which is a designated sole-source aquifer. Sole-source aquiferdesignations are used to identify aquifers that should receive special protection because they are a drinkingwater supply in areas with few or no alternative sources to groundwater, and where using an alternativesource would be extremely expensive if the aquifer were contaminated. The USEPA administers the SoleSource Aquifer Protection Program under the authority <strong>of</strong> the Safe Drinking Water Act. The USEPA definesa sole- or principal-source aquifer as one that supplies at least 50 percent <strong>of</strong> the drinking water consumed inthe area overlying the aquifer.The SVRPA provides the sole source <strong>of</strong> water <strong>for</strong> most <strong>of</strong> Spokane County, Washington, and KootenaiCounty, Idaho. It extends south from the Bonner-Kootenai County boundary toward the cities <strong>of</strong> Coeurd'Alene and <strong>Post</strong> <strong>Falls</strong> and west into Washington to Spokane Lake (Figure 3-8). At least 500,000 peopleI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-19Project No. A010(963)June 2011


depend on the aquifer <strong>for</strong> potable water supply. It covers 370 square miles and has one <strong>of</strong> the fastest flowrates in the nation, flowing as much as 60 feet per day in some areas (compared to a typical daily flow rate <strong>of</strong>a quarter inch to 5 feet <strong>for</strong> most aquifers). The SVRPA is comprised <strong>of</strong> highly permeable boulders, gravel,and sands, overlain by permeable soils, which makes the aquifer susceptible to contamination from thesurface. Water recharges the SVRPA through precipitation, run<strong>of</strong>f from the surrounding upland areas, andleakage from surrounding lakes (IDEQ 2011).As the population <strong>of</strong> the area grows, groundwater in the SVRPA is used more <strong>for</strong> domestic supply andindustry, with less agriculture use. Not only are populations growing, but the economic focus <strong>of</strong> communitiesin the area is becoming less agricultural, which means less water is needed <strong>for</strong> irrigation. This is changing thewater quality in the SVRPA.While there is some evidence <strong>of</strong> contamination, mainly in the top few feet <strong>of</strong> the SVRPA from industrial,agricultural, and domestic sewage sources, the water quality is generally considered to be in good condition.Risks to the aquifer include untreated stormwater, septic tank leachate, fertilizer leachate, and leakingunderground storage tanks (MacInnis et. al., 2004).According to the 2000 Spokane Valley Rathdrum Prairie Aquifer Atlas (MacInnis et. al., 2004):“The aquifer is highly vulnerable to contamination from activities on the ground surface. Unlikemany other aquifers, the aquifer does not have protective layers <strong>of</strong> clay to deter infiltration <strong>of</strong>surface contaminants. The soil layer on top <strong>of</strong> the aquifer is relatively thin in most areas, andfluids readily infiltrate into the porous sands and gravel that comprise the aquifer soils. Potentialcontamination is perhaps the most important aquifer issue that must be addressed in order topreserve and maintain the aquifer as a regional drinking water resource.”Because the project area overlays the SVRPA, stormwater control <strong>for</strong> groundwater protection is an importantconsideration <strong>for</strong> this project.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-20Project No. A010(963)June 2011


Potable and Other Water SourcesThe Idaho Department <strong>of</strong> Water Resources (IDWR) database <strong>for</strong> driller wells logs was reviewed <strong>for</strong> theproject area. The well search is summarized in Table 3-4 and Figure 3-9.WellNo.160203272758272841273635273847274339Table 3-4. Summary <strong>of</strong> Wells in the Project AreaLocation Owner UseWest <strong>of</strong> Cabela’s,on north side <strong>of</strong> riverCentennial Trail atstate lineNorth side <strong>of</strong> river,near state lineNorth side <strong>of</strong>highwayN. Pleasant View<strong>Road</strong>5300 W. RiverbendAvenueWA State Dept <strong>of</strong>HwysKootenai CountyStatic WaterLevel (feet belowground surface)YearConstructedUnknown Unknown UnknownDomestic(Trail rest stop)95 1995Bruce Jenson Domestic <strong>90</strong> 1995Jacklin Land Co LtdPartnershipIrrigation Unknown 1992Larry Gutzmer Domestic 47 1993Jacklin Seed Co Commercial Unknown Unknown275030 S. Clearwater Loop Jacklin Seed Co Commercial 139 1988275031 Expo Building Jacklin Seed Co Domestic 139 1988275412 S. Clearwater Loop Mike R Ward Domestic 50 1984276680 W. Pointe Parkway Jacklin Seed Co Domestic 131 1952276687North side <strong>of</strong>highwayOwen F Jacklin Irrigation 128 1957276801N. Pleasant View<strong>Road</strong>Larry Easterly Domestic 60 1996276862N. Pleasant View<strong>Road</strong>Elmer L Pierson Domestic 89 19693351833351863351<strong>90</strong>335192337570338597S. Clearwater LoopBldg 104S. Clearwater LoopBldg 104S. Clearwater LoopBldg 104S. Clearwater LoopBldg 104S. Pleasant View<strong>Road</strong>S. Pleasant View<strong>Road</strong>AvistaCommunicationsAvistaCommunicationsAvistaCommunicationsAvistaCommunicationsUniversity <strong>of</strong> IDResearch ParkUniversity <strong>of</strong> IDResearch ParkCathodic Protection Unknown 2000Unknown Unknown 2000Cathodic Protection Unknown 2000Cathodic Protection Unknown 2000Monitoring Unknown 2000Monitoring 32 2000418258 SYSCO Building <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Test 160 20074233986<strong>90</strong>2 W. SelticeWayCab Inc Monitoring 115 2008427588 SYSCO Building <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Municipal 150 2007I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-23Project No. A010(963)June 2011


One <strong>of</strong> the wells in the project area listed in Table 3-4 is located near the footprint <strong>of</strong> the Proposed Action(Well # 276680 in Figure 3-9). This well is owned by JacklinSeed Company and is located just south <strong>of</strong> the existingW. Pointe Parkway alignment, slightly west <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong>.The well is 16 inches in diameter and approximately 168 feetdeep; static water is reported at 131 feet below ground surface.Since the Proposed Action is located along the current W.Pointe Parkway alignment, it is not anticipated this well wouldbe impacted. The well would be identified in construction plansand contractors instructed to avoid disturbing it or storingconstruction materials within 100 feet <strong>of</strong> it.A large water tower, part <strong>of</strong> the <strong>Post</strong> <strong>Falls</strong> water system, islocated on the south side <strong>of</strong> W. Seltice Way, west <strong>of</strong> N. <strong>Beck</strong><strong>Road</strong> in the project area (Figure 3-10). The water tower islocated approximately 500 feet west <strong>of</strong> the Proposed Actionright-<strong>of</strong>-way <strong>for</strong> N. <strong>Beck</strong> <strong>Road</strong>.3.6.2 <strong>Environmental</strong> ConsequencesNo-BuildThe area would continue to develop under the No-Build Alternative, which could impact surface water andthe aquifer associated with such development. Developers would be required to comply with the Clean WaterAct or other federal, state, or local water resource protection rules.Proposed ActionDirect ImpactsFigure 3-10. Water tower near <strong>Beck</strong><strong>Road</strong>Increases in impervious surface and clearing <strong>of</strong> vegetation are the two most prominent actions that couldaffect water quality under the Proposed Action. Widening and paving N. <strong>Beck</strong> <strong>Road</strong>, constructing aninterchange and associated ramps, and improvements to W. Riverside Avenue would increase impervioussurfaces and stormwater run<strong>of</strong>f quantity. Construction would require an NPDES Construction General Permit,development <strong>of</strong> a SWPPP, and implementation <strong>of</strong> BMPs to control stormwater run<strong>of</strong>f and sediment erosion.Run<strong>of</strong>f from the interchange and local roads in the area would be directed to stormwater swales and otherretention structures along both sides <strong>of</strong> the roadways <strong>for</strong> stormwater treatment (Figure 3-11). In the northernportion <strong>of</strong> the project area, the paving and widening <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> would use low-impact stormwatermanagement systems consisting <strong>of</strong> vegetated swales or vegetated filter strips to treat roadway drainage. Avegetated swale is a broad, shallow channel with a dense stand <strong>of</strong> vegetation covering the side slopes andbottom. Swales can be natural or manmade, and are designed to trap particulate pollutants (suspended solidsand trace metals), promote infiltration, and reduce the flow velocity <strong>of</strong> stormwater run<strong>of</strong>f.A vegetated filter strip is an area <strong>of</strong> planted vegetation, typically grass, and a flat cross slope to maintain sheetflow and remove particulate pollutants from run<strong>of</strong>f coming directly <strong>of</strong>f pavement. In the southern portion <strong>of</strong>the project area, a stormwater retention pond would collect stormwater from the interchange and W. RiversideAvenue (Figure 3-11).Pollutants in stormwater associated with construction activities and transportation facilities could includegasoline, oil, hydraulic fluids, tire and brake particulates (including metals), litter, non-airborne vehicleexhaust particles, dust, salt, sand, and de-icing chemicals associated with general winter road maintenance. Ifnot captured and treated through stormwater BMPs, these constituents could contribute to water qualityI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-25Project No. A010(963)June 2011


degradation to surface and/or groundwater. With the addition <strong>of</strong> an interchange and associated ramps andconnecting facilities, there is a greater potential risk <strong>of</strong> hazardous materials accidents and spills from vehicles.The USEPA is required to review projects located above sole-source aquifers <strong>for</strong> groundwater protection ifthe project receives federal financial assistance (USEPA 2010). Federal funds would not be used <strong>for</strong> the I-<strong>90</strong><strong>Beck</strong> <strong>Road</strong> Interchange project. As described in Chapter 1, construction would be funded by a privatedeveloper, who would be repaid through the STAR program, using sales tax reimbursements from retaildevelopment within the project area. There<strong>for</strong>e, USEPA’s review <strong>of</strong> the project under sole-source aquiferregulations is not required. Susan Ennes <strong>of</strong> USEPA Region 10 confirmed that no review was necessary viapersonal communication January 27, 2011, and February 2, 2011. Nonetheless, aquifer protection would be apriority <strong>for</strong> this project and stormwater BMPs would be implemented to provide aquifer protection.The Panhandle Health District also protects groundwater resources in the project area. Jay Loveland <strong>of</strong> thePanhandle Health District confirmed that the project would require their involvement if shallow injectionwells were constructed (e.g., as part <strong>of</strong> stormwater management system). According to Idaho AdministrativeProcedures Act (IDAPA) 37.03.03, Rules and Minimum Standards <strong>for</strong> the Construction and Use <strong>of</strong> InjectionWells, an injection well is defined as any excavation or artificial opening into the ground that meets thefollowing three criteria:a. It is a bored, drilled, or dug hole, or is a driven mine shaft or a driven well pointb. It is deeper than its largest straight-line surface dimensionc. It is used <strong>for</strong> or intended to be used <strong>for</strong> injectionShallow injection wells are less than or equal to 18 feet in vertical depth below land surface.<strong>Post</strong> <strong>Falls</strong> <strong>City</strong> Ordinance 17.28.070, Storm Drainage, specifies requirements <strong>for</strong> stormwater management <strong>for</strong>developments in <strong>Post</strong> <strong>Falls</strong>. Per the ordinance, stormwater management must comply with IDEQ BMPs <strong>for</strong>the SVRPA, primarily by using grassy swales designed to overflow into shallow injection wells. If shallowinjection wells were to be used <strong>for</strong> the Proposed Action to control stormwater, proper design and permittingrequirements would be followed under the jurisdiction <strong>of</strong> the Panhandle Health District. In addition, theKootenai County Stormwater Technical Advisory Committee developed a swale BMP <strong>for</strong> the SVRPA. TheBMP was completed in December 2000 <strong>for</strong> inclusion in the Catalog <strong>of</strong> Best Management Practices <strong>for</strong> IdahoCities and Counties (BMP 2 – Bioinfiltration Swale).The project would avoid disturbing identified wells in the project area. If the Proposed Action requiresdisplacement <strong>of</strong> any wells, they would be closed according to applicable regulations and replaced. The watertower located approximately 500 feet west <strong>of</strong> the Proposed Action right-<strong>of</strong>-way <strong>for</strong> N. <strong>Beck</strong> <strong>Road</strong> would notbe impacted by the project.Indirect ImpactsIndirect impacts would include potential sediment deposition from construction and sanding operations. Inaddition, construction <strong>of</strong> the roadway has the potential to alter drainage patterns by changing flow patterns inthe area. The Proposed Action would likely accelerate development in the area, but the area is expected toultimately be developed with or without the Proposed Action. Development in the area would be required tocomply with federal and local regulations pertaining to stormwater management, including the development<strong>of</strong> SWPPP and BMPs.Cumulative ImpactsWater quality could be affected with changes in human activity in the west <strong>Post</strong> <strong>Falls</strong> area. Severalintersection and roadway improvements are planned by the PFHD in the area that could help improve waterquality through additional stormwater management.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-26Project No. A010(963)June 2011


MitigationWith implementation <strong>of</strong> the SWPPP, BMPs, and controls, no short-term or long-term impacts on waterquality are anticipated. Specific provisions are as follows:• The contractor will be required to obtain a stormwater Construction General Permit that includes thedevelopment <strong>of</strong> a SWPPP.• Erosion-control BMPs will be implemented in areas disturbed during construction <strong>of</strong> project features.ITD’s specifications and policies <strong>for</strong> BMPs will be followed including timelines <strong>for</strong> implementingsuch actions. The contractor will be required to restore disturbed surfaces, through seeding, applyingsoil stabilizers, or other means to avoid and minimize erosion. Areas waiting to be seeded will bemaintained to prevent weed invasion.• Prior to construction, sediment controls will be installed along the edge <strong>of</strong> disturbed areas where<strong>of</strong>fsite stormwater run<strong>of</strong>f is possible• Run<strong>of</strong>f from the road will be directed into roadside ditches and stormwater retention structures wherethe water can be retained and treated (Figure 3-11).• Any drainage easements or co-mingling <strong>of</strong> stormwater within PFHD right-<strong>of</strong>-way would requireagreements with the District regarding maintenance and control.• Refueling areas will be identified in the SWPPP and containment systems will be implemented tominimize risk <strong>of</strong> contaminating surface waters. Fueling and maintenance <strong>of</strong> equipment will occurmore than 100 feet from the Spokane River.• Well 276680 (Figure 3-9) will be protected by placing a protective crash barrier around the well headand also ensuring that stormwater from construction activities is conveyed away from the wellheadarea. Refueling areas will be kept a minimum <strong>of</strong> 100 feet from the wellhead.• A consent decree issued by the U.S. District Court <strong>of</strong> Idaho in 2006 states specific environmentalregulatory requirements regarding stormwater discharge <strong>for</strong> ITD construction projects. Because the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project is privately funded and constructed, the conditions <strong>of</strong> the consentdecree do not apply to this project.3.7 Socioeconomics and Land UseThis section describes the affected environment andevaluates impacts <strong>of</strong> the Proposed Action on socioeconomicsand land use, including community cohesion, economicvitality, displacements, environmental justice, safety andtraffic, and con<strong>for</strong>mity to regional and local planningdocuments.3.7.1 Affected EnvironmentPopulation and EconomicsIdaho has experienced rapid population growth in recentdecades. Growth in and around the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> has alsobeen steadily increasing over the last 20 years, with recentSocioeconomics and Land UseDefinitionsSocioeconomics generally deals witheconomics, emergency vehicle access,community cohesiveness, safety andtraffic, displacements, relocation anddisadvantaged groups.Land Use focuses on consistency <strong>of</strong> theProposed Action with transportationplans and comprehensive plans adopted<strong>for</strong> the area. It also addresses induceddevelopment as a secondary impact.growth focused largely in the west side <strong>of</strong> the city, including the project area. The city has grown from 7,350residents in 19<strong>90</strong> to almost 27,000 residents in 2009. The population is projected to be more than 34,000 in2030, a nearly <strong>90</strong> percent increase over 19<strong>90</strong> (Figure 1-3).I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-28Project No. A010(963)June 2011


The <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> annual unemployment rate <strong>for</strong> 2009 was 9.7 percent compared to 8.0 percent <strong>for</strong> theState <strong>of</strong> Idaho. As <strong>of</strong> November 2010, the city’s unemployment rate was 11.5 percent, more than 2 percenthigher than the state unemployment rate <strong>of</strong> 9.4 percent (Figure 3-12).The KMPO projects that about 5,000 new jobs would be created in the project area by 2030. To supportfuture growth in population and employment, the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and the KMPO are consideringinfrastructure and capacity-related improvements that would benefit and support economic development.1211Figure 3-12. Unemployment RatesUnemployment Rate1098765200920104State <strong>of</strong> Idaho Kootenai County <strong>Post</strong> <strong>Falls</strong>Source: Idaho Department <strong>of</strong> Labor, 2010The median household income based on Census data collected from 2005 to 2009 was $45,994 compared tothe national average <strong>of</strong> $51,425. As <strong>of</strong> 2005, the industries in <strong>Post</strong> <strong>Falls</strong> with the most employment were salesand <strong>of</strong>fice-related occupations at 30.1 percent, management and pr<strong>of</strong>essional occupations at 25.7 percent,service occupations at 15.9 percent and product transportation and material moving occupations at 15.1percent.Minority populations in Idaho are lower than the national average. The racial make-up <strong>of</strong> the population in<strong>Post</strong> <strong>Falls</strong> based on Census data collected from 2005-2009 is shown in Table 3-5.Table 3-5. Racial Make-up <strong>of</strong> Population in <strong>Post</strong> <strong>Falls</strong> (Census 2005-2009)Race Population in <strong>Post</strong> <strong>Falls</strong> (%)White 95.7%Black or African American 0.3%Asian 0.5%American Indian and Alaskan Native 0.2%Other 0.5%Two or more races 2.8%Source: U.S. Census Bureau, population data collected from 2005-2009In 2008, Kootenai County’s poverty rate was 9.4 percent, compared to 12.5 percent statewide and 13.2nationally. While the national poverty rates <strong>for</strong> 2009 are not yet available, Kootenai County’s 2009 povertyrate has been estimated at 13.8 percent, compared to 14.4 percent statewide. The increase from 9.4 to 13.8percent between 2008 and 2009 is attributed to the economic downturn during that time period.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-29Project No. A010(963)June 2011


Community CohesionTwo neighborhoods lie within the project area (Figure 3-13). The Woodbridge Park residential neighborhoodis in the northeast portion <strong>of</strong> the project area (south <strong>of</strong> W. Seltice Way) about 620 feet east <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong>.This subdivision has about 275 single-family homes and was platted between 2001 and 2004. In 2010, theaverage assessed value <strong>of</strong> homes in the subdivision was approximately $142,000.The Eastland subdivision, located in Spokane County immediately west <strong>of</strong> State Line <strong>Road</strong>, is about 1 milewest <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> (Figure 3-13). The subdivision has 107 single family homes and was platted in theearly 1970s. The average assessed value <strong>of</strong> homes in 2010 was about $135,000.<strong>Environmental</strong> JusticeExecutive Order 12898, Federal Actions to Address <strong>Environmental</strong> Justice in Minority Populations and Low-Income Populations, signed by the President on February 11, 1994, directs federal agencies to identify andaddress disproportionately high and adverse human health and environmental effects, including theinterrelated and social and economic effects <strong>of</strong> their programs, policies and activities on minority and lowincomepopulations in the United States. The Proposed Action is in a commercial/industrial area and there areno residents within or adjacent to the project footprint. The closest residents are in the Woodbridge Park andEastland Subdivisions.Public ServicesMost public services provided by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> are located east <strong>of</strong> the project area, near SpokaneStreet and the city center. The city center area includes a public library, elementary schools, middle schools,high schools, and two branches <strong>of</strong> the Northwest Specialty Hospital east <strong>of</strong> Spokane Street.Transit<strong>City</strong>link transit, launched in 2005, provides public bus service to Kootenai and Benewah counties on fiveroutes, 22 hours a day, seven days a week. The <strong>City</strong>link Red A-Line bus is an express service via I-<strong>90</strong> to thepark-n-ride facility at W. Pointe Parkway. The route takes W. Seltice Way to Bay Street east <strong>of</strong> the projectarea, where a rider can transfer to a bus service bound <strong>for</strong> Hayden, Idaho (north <strong>of</strong> the project area).The short-range transportation plans <strong>of</strong> the two metropolitan planning organizations <strong>of</strong> the region (SRTC andKMPO) have identified a project to develop transit service between Spokane and Coeur d’Alene. The natureand service provider has not been determined, but initial consideration has suggested it would start with anexpress commuter service that would likely include a Park-n-Ride lot near the intersection <strong>of</strong> N. PleasantView <strong>Road</strong> and I-<strong>90</strong>.Fire DepartmentsThe Kootenai County Fire and Rescue Department provides fire protection and emergency services to the<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and Kootenai County. Fire stations within or adjacent to the project area are illustrated inFigure 3-13. The closest fire station to the Proposed Action is Station 2, located on W. Seltice Way.Law En<strong>for</strong>cementThe <strong>Post</strong> <strong>Falls</strong> police station is located east <strong>of</strong> Spokane Street near the city center. The Idaho State Police,Region 1, located in Coeur d’Alene, is responsible <strong>for</strong> patrolling I-<strong>90</strong> and major crime investigations and<strong>for</strong>ensic services in the region.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-30Project No. A010(963)June 2011


SchoolsThe project area is located in the <strong>Post</strong> <strong>Falls</strong> School District in Idaho and the East Valley School District inWashington. <strong>Post</strong> <strong>Falls</strong> School District enrollment reached 5,620 students in 2010, an increase <strong>of</strong> 1,164students over 2000. East Valley enrollment dropped from 4,837 students in 2000 to 4,486 in 2010. TheRiverbend Pr<strong>of</strong>essional Technical Academy is the only school located within the project area (Figure 3-13).Our Lady Victory School, a private catholic school, is located south <strong>of</strong> I-<strong>90</strong> close to the Pleasant View <strong>Road</strong>Interchange.Table 3-6 lists schools, parks, and services in the vicinity <strong>of</strong> the proposed interchange. This list was compiledusing current in<strong>for</strong>mation from the Chamber <strong>of</strong> Commerce, school districts, <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>, and the IdahoDepartment <strong>of</strong> Commerce and Labor.Table 3-6. Schools, Parks, and Services near or within Proposed ProjectSchoolsAddressSchools near Project AreaRiverbend Pr<strong>of</strong>essional Technical Academy525 S. Clearwater Loop, <strong>Post</strong> <strong>Falls</strong>, IDOur Lady <strong>of</strong> Victory (St Michael) School421 S. Lochsa St., <strong>Post</strong> <strong>Falls</strong>, IDSchools in the General Project VicinitySeltice ElementaryPrairie View Elementary<strong>Post</strong> <strong>Falls</strong> Middle SchoolNew Vision High SchoolMullan Trail ElementaryRiver <strong>City</strong> Middle School<strong>Post</strong> <strong>Falls</strong> High SchoolEast Farms ElementaryMountain View Middle and Junior HighParksGateway Conservation AreaGateway Regional ParkWoodbridge ParkPublic ServicesKootenai Co. Fire and Rescue Department – Station 2<strong>City</strong>link Bus Service<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Public Services Department<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Water Division<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Water Reclamation DivisionCoeur d'Alene Garbage Service/<strong>Post</strong> <strong>Falls</strong> Sanitation<strong>Post</strong> <strong>Falls</strong> Police Department1101 N. Chase <strong>Road</strong>, <strong>Post</strong> <strong>Falls</strong>, ID2478 E. Poleline Avenue, <strong>Post</strong> <strong>Falls</strong>, ID301 E. 16th Avenue, <strong>Post</strong> <strong>Falls</strong>, ID201 W. Mullan Avenue, <strong>Post</strong> <strong>Falls</strong>, ID300 W. Cherry Avenue, <strong>Post</strong> <strong>Falls</strong>, ID1505 N. Fir St., <strong>Post</strong> <strong>Falls</strong>, ID2832 E. Poleline <strong>Road</strong>, <strong>Post</strong> <strong>Falls</strong>, IDE. 26203 Rowan Avenue, Newman Lake, WA6011 N. Chase <strong>Road</strong>, Newman Lake, WAAddressBetween State Line <strong>Road</strong> Interchange and the SpokaneRiverBetween State Line <strong>Road</strong> Interchange and the SpokaneRiverW. Seltice Way and Silkwood DriveAddress4320 W. Seltice Way, <strong>Post</strong> <strong>Falls</strong>, IDVaries408 N. Spokane St., <strong>Post</strong> <strong>Falls</strong>, ID2002 W. Seltice Way, <strong>Post</strong> <strong>Falls</strong>, ID2002 W. Seltice Way, <strong>Post</strong> <strong>Falls</strong>, ID1820 N. Highway 41, <strong>Post</strong> <strong>Falls</strong>, ID1717 E. Polston Avenue, <strong>Post</strong> <strong>Falls</strong>, IDI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-32Project No. A010(963)June 2011


Traffic, Access, and SafetyThe SRTC developed and modeled future traffic scenarios <strong>for</strong> alternatives developed <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project. The baseline travel demand model was used to <strong>for</strong>ecast traffic volumes <strong>for</strong> 2012 (openingday <strong>of</strong> a new interchange) and the 2030 design year. This model was modified to <strong>for</strong>ecast volumes <strong>for</strong> thefollowing traffic scenarios:• 2012 Opening Day <strong>of</strong> New Interchange• 2030 No-Build• 2030 Local Improvements Only• 2030 Existing Interchange Modifications• 2030 New Interchange AlternativesThe <strong>for</strong>ecast results were used to support the IJR analysis, project purpose and need (Chapter 1), and design<strong>of</strong> intersections and roadways under the Proposed Action. Details on model assumptions and results arepresented in Appendix D <strong>of</strong> the IJR (HDR 2010).The Centennial Trail occurs south <strong>of</strong> I-<strong>90</strong>, which provides non-motorized transportation access to the area.The trail is detached from W. Riverbend Avenue and provides a safe travel route <strong>for</strong> pedestrians andbicyclists on the path.Land UseThe land use evaluation focuses on the consistency <strong>of</strong> the Proposed Action with local and regionaltransportation plans and comprehensive plans. As described in Chapter 2, several transportation andcomprehensive plans identified the need <strong>for</strong> an interchange near N. <strong>Beck</strong> <strong>Road</strong>. Current <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>zoning <strong>for</strong> the area identifies the land surrounding N. <strong>Beck</strong> <strong>Road</strong> south <strong>of</strong> W. Seltice Way as industrial andCommunity Commercial Services. The Community Commercial Services zone supports uses that includeretail sales or per<strong>for</strong>mance <strong>of</strong> consumer services and permits a variety <strong>of</strong> retail, pr<strong>of</strong>essional, or servicebusinesses. Similar to other commercial zoned designations, residential uses can be incorporated into aCommunity and Commercial Services zone only by a special use permit granted by the <strong>City</strong>. The <strong>City</strong>granted a special use permit <strong>for</strong> the N. <strong>Beck</strong> <strong>Road</strong> area that would allow <strong>for</strong> the use <strong>of</strong> mixed use includingresidential. While a permit has been issued, according to the <strong>City</strong> no plans have been submitted <strong>for</strong> this area,as the permit was requested as a future development option. Kootenai County has the area south <strong>of</strong> I-<strong>90</strong>zoned <strong>for</strong> industrial uses.The <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> has recognized the need <strong>for</strong> planning near N. <strong>Beck</strong> <strong>Road</strong> by adopting the followingpolicy in its comprehensive plan:“The city will work with ITD and other agencies on providing new interchanges along I-<strong>90</strong> atGreensferry and <strong>Beck</strong> <strong>Road</strong>, as well as maintaining and expanding the I-<strong>90</strong> corridorincluding interchanges.” (<strong>Post</strong> <strong>Falls</strong> Comprehensive Plan 2010).Future land-use designations in the <strong>Post</strong> <strong>Falls</strong> Comprehensive Plan identify commercial and industrial landuses in the project area (Figure 3-14) along the I-<strong>90</strong> corridor to manage high traffic volumes and <strong>of</strong>fer quickand easy access onto the interstate <strong>for</strong> regional connectivity.The area north <strong>of</strong> W. Seltice Way is currently under Kootenai County jurisdiction. The county’s zoningregulation designates the area along N. <strong>Beck</strong> <strong>Road</strong> north <strong>of</strong> W. Seltice Way as industrial land (Figure 3-15).This classification extends from W. Seltice Way <strong>for</strong> about 1.5 miles along N. <strong>Beck</strong> <strong>Road</strong> to about 1,000 feetsouth <strong>of</strong> Poleline Avenue.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-33Project No. A010(963)June 2011


Potential new development and associated travel would be a secondary impact <strong>of</strong> a new interchange. To betterunderstand land-use and development impacts <strong>of</strong> the Proposed Action, the project team interviewed the <strong>City</strong><strong>of</strong> <strong>Post</strong> <strong>Falls</strong> planner and public works director on February 2, 2011. The following questions were presentedto the city staff:• Is the Proposed Action consistent with local land-use plans and zoning regulations?• How would the Proposed Action affect the location, patterns and pace <strong>of</strong> residential, commercial, andindustrial development in the project area, especially north <strong>of</strong> W. Seltice Way (a largely undevelopedarea)?• How would land-use development and traffic patterns change with or without the interchange?The responses from city staff are captured in the environmental consequences section that follows.3.7.2 <strong>Environmental</strong> ConsequencesNo-BuildA proposed interchange is part <strong>of</strong> the <strong>Post</strong> <strong>Falls</strong> Comprehensive Plan and Transportation Master Plan, theKMPO Metropolitan Transportation Plan, and is cited in the ITD STIP 2010-2013. Thus, if the project werenot built, there would be a negative impact on the planned community vision, economic growth, publicservices, and overall land use in the project area.The local and regional planning documents noted above recognize the need <strong>for</strong> an interchange to meet traveldemands associated with current and projected development in the project area and overall regionalpopulation and employment growth. The <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> would be responsible <strong>for</strong> considering andapproving development in the area consistent with the city’s plans and requirements. It is possible that certaintypes <strong>of</strong> developments would not occur due to inadequate transportation facilities if the interchange were notbuilt. While the anticipated land uses would likely occur over time without a new interchange, particularlygiven the existence <strong>of</strong> anchor stores in the project area, such development would take longer and possibly bedeveloped at a lower density (Melvin 2011).Furthermore, if the No-Build Alternative is chosen, property values in the project area could decline asproperty would revert from the more valuable commercial and higher-end industrial development to lowintensityindustrial and commercial development.Under the No-Build Alternative, no adverse effects would occur on minority or low income populations perExecutive Order 12898.The proposed interchange provides additional options <strong>for</strong> emergency vehicles to access local roads from theinterchange and to respond to Interstate accidents. Without additional access to I-<strong>90</strong> near N. <strong>Beck</strong> <strong>Road</strong>,emergency services responders would be limited to existing local roads and access at adjacent interchanges,which would be more congested compared to the Proposed Action.Under the No-Build Alternative, travel patterns would continue to access I-<strong>90</strong> at adjacent interchanges. Thewestbound ramp terminal at the State Line <strong>Road</strong> interchange currently operates at LOS F (Table 1-1).UnderNo-Build conditions, both existing interchange terminal ramps (Pleasant View <strong>Road</strong> and State Line <strong>Road</strong>)would operate at LOS F by 2030. An additional five intersections in the project area would also exhibitunacceptable LOS E or F, including those near the existing Pleasant View <strong>Road</strong> Interchange. The CentennialTrail would continue to operate in its current condition without improvements or without connections acrossI-<strong>90</strong>.The No-Build Alternative would not be consistent with area-wide planning documents. <strong>Post</strong> <strong>Falls</strong> and thecounty would need to adjust land-use plans to reflect the absence <strong>of</strong> the planned interchange, includingadjusting development density in response to traffic-volume concerns on local roads and the existingI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-36Project No. A010(963)June 2011


interchanges. The project team conducted interviews with <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> <strong>of</strong>ficials to assess socioeconomicimpacts and the potential <strong>for</strong> induced development associated with the project (Melvin 2011). For the No-Build Alternative, the findings included:• If the interchange were not built: 1) the zoning <strong>of</strong> this area would remain the same and the areawould likely develop, but at a slower pace, 2) the type <strong>of</strong> businesses and industry might change; <strong>for</strong>example, a business that depends on high truck-traffic volume may not choose to locate in this area ifthere was not easy access to and from the Interstate, 3) the density <strong>of</strong> development may change in thearea due to traffic congestion concerns.• If the interchange were not built, land-use development patterns north <strong>of</strong> W. Seltice Way wouldlikely not change, but the pace <strong>of</strong> development might be slowed.Proposed ActionDirect ImpactsThe Proposed Action would have a direct impact on area economics by creating construction jobs andinterrelated and interdependent development. No minority or low-income populations have been identifiedthat would be adversely impacted by the Proposed Action. There<strong>for</strong>e, this project will not havedisproportionately high or adverse effects on minority or low income populations per Executive Order 12898.The <strong>Post</strong> <strong>Falls</strong> Comprehensive Plan identifies the area north <strong>of</strong> I-<strong>90</strong> in the project area <strong>for</strong> current and futurecommercial and industrial uses. Development is already underway with Cabela’s and Walmart retail facilities,which are considered anchor stores <strong>for</strong> future commercial developments. Easy access to and from I-<strong>90</strong> underthe Proposed Action would benefit current and future businesses in the project area and provide greaterregional connectivity to neighborhoods as well as commercial and industrial properties.N. <strong>Beck</strong> <strong>Road</strong> between the proposed interchange and W. Seltice Way would be a five-lane, minor arterialroad that would provide improved access to W. Seltice Way and areas north. The PFHD’s long-range plansinclude improvements to N. <strong>Beck</strong> <strong>Road</strong> north <strong>of</strong> W. Seltice Way, which would provide greater regionalconnectivity north toward SH-53.Existing businesses south <strong>of</strong> I-<strong>90</strong>, including Jacklin Seed and the Greyhound Park and Event Center, would beimpacted during construction activities that might include access delays. Portions <strong>of</strong> both properties would beobtained <strong>for</strong> project right-<strong>of</strong>-way, but permanent access would be maintained (Figure 2-4). Current access toboth businesses is via W. Riverbend Avenue to the Pleasant View <strong>Road</strong> Interchange. With the newinterchange, both would have close and easy access to I-<strong>90</strong>.The project would not cause any displacements. The Centennial Trail would continue through the interchangeparallel to I-<strong>90</strong> on the proposed W. Riverbend Avenue extension and would remain open throughout theconstruction period. Construction impacts associated with the Centennial Trail are provided in Section 3.3.2<strong>of</strong> this EA. After construction, the trail would be continuous and have no at-grade crossings. A connectionbetween the Centennial Trail and the sidewalk and bike lanes would be constructed on W. Riverbend Avenueand W. Pointe Parkway <strong>for</strong> non-trail access across I-<strong>90</strong>. The two neighborhoods in the project area would notbe directly affected by the Proposed Action, though residents <strong>of</strong> both neighborhoods would benefit by havingimproved access to I-<strong>90</strong>.The Proposed Action is expected to provide improved response times <strong>for</strong> emergency vehicles through greateraccess to and from I-<strong>90</strong>. Kootenai County Fire and Rescue indicated that a new interchange would enhanceaccess to commercial and industrial areas <strong>for</strong> emergency responses.The Proposed Action would improve access to I-<strong>90</strong> and reduce delays at the Pleasant View <strong>Road</strong> Interchangeand a number <strong>of</strong> local intersections. As described in Chapter 2, the traffic service levels <strong>of</strong> the interstate in theI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-37Project No. A010(963)June 2011


project area would be reduced from LOS C to LOS D, which has been deemed acceptable by ITD (ITD 2010).The project would accommodate anticipated travel demand through the year 2030.Direct access would be provided to the Jacklin Seed property via the W. Riverbend Avenue extension and atthe W. Riverbend Avenue and W. Pointe Parkway intersection. Jacklin Seed’s signage would be impacted bythe W. Riverbend Avenue extension. The Greyhound Park and Event Center currently has three accesses ontoW. Riverbend Avenue. The westernmost access to the Greyhound Park and Event Center would need to beclosed after construction is complete to support connectivity and required design queue lengths <strong>for</strong> theproposed Pointe Parkway and W. Riverbend Avenue intersection south <strong>of</strong> the interchange (Figure 2-4). TheGreyhound Park and Event Center parking lot and business signage would be impacted by the W. RiverbendAvenue extension. The interchange would provide access to commercial and industrial businesses north <strong>of</strong> I-<strong>90</strong>, including Cabela’s, Walmart, and Sysco Foods as well as to future commercial and industrial businesseszoned in this area.The Proposed Action is consistent with local and regional planning documents. The Proposed Action wouldserve planned development north and south <strong>of</strong> I-<strong>90</strong>, including providing regional connectivity via N. <strong>Beck</strong><strong>Road</strong> north <strong>of</strong> W. Seltice Way to SH-53. Such connectivity supports the regional benefits <strong>of</strong> the ProposedProject and is consistent with land use jurisdiction plans <strong>for</strong> future development in the area.Indirect ImpactsBesides the direct economic benefits <strong>of</strong> the Proposed Action described above, interrelated and interdependentprojects in the area would provide economic benefits to the area through construction jobs and permanentjobs. These jobs, along with new businesses in the area, would bring increased tax revenue to the area tosupport community needs such as schools and emergency services.While some area roads would experience increased traffic volumes after construction (e.g., N. <strong>Beck</strong> <strong>Road</strong> thatis currently unpaved), none <strong>of</strong> this would be through-traffic in residential neighborhoods. Enhanced regionalconnectivity would provide better access to the Interstate <strong>for</strong> local and regional travel and improve overalltraffic conditions compared to the No-Build Alternative.The planned developments in the project area would potentially require increased law en<strong>for</strong>cement presenceand fire protection in the project area. As the population <strong>of</strong> the area grows, the fire department woulddetermine if and where new emergency response centers would be needed to maintain adequate responsetimes.Compared to the No-Build Alternative, the Proposed Action provides <strong>for</strong> overall improvements in trafficeffectiveness <strong>for</strong> the region (see discussion in Chapter 2). The Proposed Action would not result in anychange in safety <strong>for</strong> the Centennial Trail, which provides non-motorized access to the area. The ProposedAction would provide uninterrupted travel through the interchange area and provides connectivity north <strong>of</strong> I-<strong>90</strong>.The project team conducted interviews with <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> <strong>of</strong>ficials to assess induced developmentassociated with the project (Melvin 2011). A summary <strong>of</strong> findings is presented below:• The <strong>City</strong> representatives verified that the Proposed Action is consistent with land-use and zoningregulation and that the need <strong>for</strong> an interchange has been identified in numerous planning documents.• The area north <strong>of</strong> I-<strong>90</strong> and south <strong>of</strong> W. Seltice Way is zoned Community Commercial Services. Theinterchange is an important planned element in providing access to these developments. The localroadway jurisdiction has long-range plans <strong>for</strong> improving N. <strong>Beck</strong> <strong>Road</strong> north <strong>of</strong> W. Seltice Way toSH-53 as the area transitions from rural to urban and is annexed to the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> (KMPO2010). The current industrial zoning <strong>for</strong> the area north <strong>of</strong> W. Seltice Way along N. <strong>Beck</strong> <strong>Road</strong> is notanticipated to change. Zoning <strong>for</strong> areas further north are currently rural and outside the <strong>City</strong> <strong>of</strong> <strong>Post</strong><strong>Falls</strong> limits. The Proposed Action is not anticipated to change the industrial land-use zoning <strong>for</strong> thisI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-38Project No. A010(963)June 2011


area. The viability <strong>of</strong> commercial use on the north side <strong>of</strong> the W. Seltice Way and N. <strong>Beck</strong> <strong>Road</strong>intersection is restricted by a steep grade.Logical beginning and ending points (termini) <strong>for</strong> the Proposed Action, which are defined in Chapter 1,should ensure the “independent utility” <strong>of</strong> the project. The project must “stand alone” and should not triggeran immediate need <strong>for</strong> additional improvements elsewhere. If the project triggers an immediate need <strong>for</strong>improvements elsewhere, the logical termini were not defined correctly and the Proposed Action shouldaddress these needed improvements.Future traffic was modeled <strong>for</strong> project alternatives to evaluate if building an I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchangeproject would trigger the immediate need <strong>for</strong> transportation improvements beyond the defined logical termini.The traffic was modeled <strong>for</strong> the year 2012, the assumed construction completion year <strong>for</strong> the project. Thetraffic model shows no additional road improvements would be needed in 2012, including roads north <strong>of</strong> W.Seltice Way on N. <strong>Beck</strong> <strong>Road</strong>, in response to the Proposed Action. As a result, the project has independentutility.Correspondence with KMPO staff, who maintains the regional traffic model, verified that N. <strong>Beck</strong> <strong>Road</strong>,north <strong>of</strong> W. Seltice Way would be expanded by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> as the areas transitions from urban torural development and is annexed into the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> (KMPO 2010). This need is projected to be 20 to30 years out.Cumulative ImpactsCumulative impacts are similar to secondary impacts in that the accumulation <strong>of</strong> projects would result inincreased population, need <strong>for</strong> greater services, increased economic development, and subsequent increases inemployment.The PFHD has projects planned <strong>for</strong> the area <strong>of</strong> the proposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange, which, whencombined with the Proposed Action, would improve traffic movement in the area. Many <strong>of</strong> the projectsinclude pedestrian and bicycle facilities that would improve movement and safety throughout the area.MitigationBicycle and pedestrian connectivity will be maintained through the project area by providing an uninterruptedCentennial Trail (both during and after construction). The Centennial Trail would be impacted byconstruction activities <strong>of</strong> the interchange, but will remain open. During construction, access to the CentennialTrail could be disrupted and pedestrian or bicyclists may have to travel through unpaved areas or temporarilywait <strong>for</strong> passage through the construction area. Where feasible, temporary detours will be identified t<strong>of</strong>acilitate connectivity <strong>of</strong> the trail during construction.After construction, the Centennial Trail will have connectivity to the developed areas north <strong>of</strong> I-<strong>90</strong>, byproviding bike lanes or multi-use paths as appropriate on the proposed roadways.It is anticipated that construction <strong>of</strong> the new interchange would require temporary lane closure and possiblytemporary detours. N. <strong>Beck</strong> <strong>Road</strong> will not be disrupted during construction since it is currently unpaved andnot used as an everyday transportation facility. I-<strong>90</strong> and W. Riverbend Avenue would be impacted duringconstruction. During final design, project-specific traffic-control plans and special provisions would bedeveloped in con<strong>for</strong>mance with ITD standards, <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> requirements, and the Manual on Uni<strong>for</strong>mTraffic Control Devices <strong>for</strong> Streets and Highways. Along with the ITD standard plans and specifications, thetraffic-control plans would provide the contractor with the minimum standards <strong>for</strong> maintaining traffic.Anticipated property impacts that will occur to the Jacklin Seed and Greyhound Parks and Event Centerfacilities have been discussed with property owners. Property agreements will be negotiated with propertyowners subject to final design requirements <strong>of</strong> the project. Detailed design issues will be discussed withI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-39Project No. A010(963)June 2011


property owners as part <strong>of</strong> right-<strong>of</strong>-way negotiations. These agreements will address right-<strong>of</strong>-way andcompensation, easements, liability, business impacts and signage, and local connectivity.3.8 NoiseThis section describes the affected environment and evaluates noise impacts from the Proposed Action.3.8.1 Affected EnvironmentA Noise <strong>Assessment</strong> Technical Report was completed <strong>for</strong> theproject to identify existing and future predicted traffic noiselevels (HDR 2011a). The noise analysis was completed priorto the adoption <strong>of</strong> ITD’s 2011 Traffic Noise Policy, but wasrevisited to verify compliance with the updated policy. TheWhat is Noise?Noise is an unwanted sound and ismeasured in A-weighted decibels(dBA).The decibel scale corresponds tothe sensitivity range <strong>for</strong> human hearing.noise analysis remains valid and complies with the 2011 ITD Traffic Noise Policy. The updated NoiseAbatement checklists were utilized <strong>for</strong> the analysis.Noise studies must be prepared <strong>for</strong> all federal-aid highway construction projects that construct new highwaysor reconstruct existing highways by significantly changing either the horizontal or vertical alignment or byincreasing the number <strong>of</strong> through travel lanes (designated as “Type 1” projects by FHWA). All federal-aidhighway noise analyses must be prepared in con<strong>for</strong>mance with FHWA Procedures <strong>for</strong> Abatement <strong>of</strong> HighwayTraffic Noise and Construction Noise (23 CFR Part 772). The I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project results innew highway construction and significant changes in horizontal and vertical alignments and, as a result,triggers the requirement <strong>for</strong> a detailed traffic noise analysis.The project study area <strong>for</strong> this noise analysis encompassed the area north and south <strong>of</strong> I-<strong>90</strong> where the newinterchange would be constructed, the area adjacent to the new connection between the proposed interchangeand the intersection with W. Pointe Parkway, and the area adjacent to N. <strong>Beck</strong> <strong>Road</strong> between the intersectionwith W. Pointe Parkway and the intersection with W. Seltice Way.FHWA noise criteria and standards, called noise abatement criteria (NAC) are shown in Table 3-7. TheseNAC represent the maximum traffic noise levels that allow uninterrupted use within each activity category.The land use categories included in the FHWA NAC and the continuous noise level during any one-hourperiod (Leq) are associated with each activity category.In determining and abating traffic noise impacts, primary consideration is given to exterior areas. ITD definesa traffic noise impact in Section 1300 <strong>of</strong> the <strong>Environmental</strong> Process Manual. The definition contains twocriteria; only one has to be met <strong>for</strong> defining a traffic noise impact. Traffic noise impacts are defined asfollows:• A “relative” noise impact occurs when the predicted noise levels <strong>for</strong> the design year exceed theexisting traffic noise levels by 15 dBA (see box <strong>for</strong> definition) or more, even if it does not approach orexceed the “absolute” NAC; or,• Determine the “absolute” impact by comparing the predicted noise levels <strong>for</strong> the design year to thenoise “abatement criteria” levels in Table 3-7 <strong>for</strong> various land use activity categories and determine ifthe criteria are approached or exceeded. Approach means within 1 dBA.The applicable ITD NAC <strong>for</strong> residential and commercial properties is 66 dBA and 71 dBA.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-40Project No. A010(963)June 2011


Table 3-7. FHWA and ITD Noise Abatement CriteriaActivityCategoryLand Use – Primary ActivityFHWA NoiseAbatementCriteria(dBA)ITD NoiseAbatementCriteria(dBA)ABCDESubstantialincreaseLand on which serenity and quiet are <strong>of</strong> extraordinarysignificance and serve an important need and wherethe preservation <strong>of</strong> those qualities is essential if thearea is to continue to serve its intended purpose.Picnic areas, recreation areas, parks, residences,motels, schools, churches, libraries and hospitals.Properties/activities that are not included in CategoriesA or B (e.g., most commercial and industrial activities).Undeveloped lands (no established noise levelguidelines).Interior noise levels <strong>for</strong> picnic areas, recreation areas,parks, residences, motels, schools, churches, librariesand hospitals.A substantial increase <strong>of</strong> 15 dBA over the existingnoise level57 5667 6672 71-- --52 (interior) 51 (interior)15 15Traffic noise levels <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project were calculated using FHWA’s Traffic NoiseModel (TNM ® Version 2.5). The TNM computes highway traffic noise at nearby receivers and aids in thedesign <strong>of</strong> mitigation measures. Inputs to the model include three-dimensional descriptions <strong>of</strong> road alignments,vehicle volumes in defined vehicle classes, vehicle speeds, traffic control devices, and data on thecharacteristics and locations <strong>of</strong> specific ground types, topographical features, and other features likely toinfluence the propagation <strong>of</strong> vehicle noise between the roadway and the receiver.Noise levels were measured using a Larson Davis 820 noise meter and Larson Davis CAL 150 calibrator. Themeter was set at a height <strong>of</strong> approximately 5 feet <strong>for</strong> all measurements. The microphone was covered with awindscreen. The noise meter was calibrated be<strong>for</strong>e, during, and after field measurements. Measurements weretaken in terms <strong>of</strong> Leq. Concurrent traffic counts were taken during the noise level monitoring. The TNMmodel input/output and traffic data used in the analysis, including volumes in each modeled vehicle class andposted speeds, are included in Appendix C.Existing conditions (2011), No-Build conditions, and Proposed Action conditions were modeled. The No-Build condition assumes full build-out <strong>of</strong> planned future development in the area north <strong>of</strong> I-<strong>90</strong> without thenew interchange. The Proposed Action condition includes planned future development, the new interchangeand associated connections as described in Section 2.3.2.3.8.2 Existing ConditionsIf monitored and modeled results are within 3 dBA, the model is considered to be reasonably accurate inpredicting noise levels. The results <strong>of</strong> the model calibration show that modeled and measured noise levelsagree within 3 or less dBA.Existing noise levels were monitored at seven locations within the project area in February 2011 <strong>for</strong> thepurpose <strong>of</strong> validating the noise model (i.e., ensuring that the model accurately estimates existing traffic noiseduring the monitoring period), and providing a general indication <strong>of</strong> existing noise levels. The results <strong>of</strong> theI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-41Project No. A010(963)June 2011


model calibration show that modeled and measured noise levels agree within 3 or less dBA. A comparison <strong>of</strong>the noise levels predicted using the noise model to the noise levels measured in the field is shown inTable 3-8.Table 3-8. Monitored and Predicted Noise Levels in the Project AreaMonitoringPointMeasuredLevel(Leq – dBA)ModeledLevel(Leq – dBA)Difference(Leq – dBA)M1 74 72 2M2 52 53 1M3 48 51 3M4 44 45 1M5 70 71 1M6 57 55 2M7 56 58 2Following validation <strong>of</strong> the noise model, existing sound levels were modeled at 36 receptors (noise predictionsites). Sound levels were predicted at 5 feet above ground level. The monitoring locations, noise receptor orprediction sites, and roadway configurations are shown in Figure 3-16. Receptor locations where selected torepresent both existing noise receptors (Jacklin Seed Co., Greyhound Park and Event Center, Sysco Foods,and the Woodbridge Subdivision) and future noise receptors (future development along N. <strong>Beck</strong> <strong>Road</strong>).Predicted existing peak hour sound levels at receptors are listed in Table 3-9. The traffic data is based on<strong>for</strong>ecast analysis conducted to support the IJR <strong>for</strong> this project (HDR 2010).Under existing conditions, modeled noise levels range from 47 dBA to 78 dBA. Predicted exceedances <strong>of</strong>noise levels that approach the absolute NAC (i.e., the 66 NAC <strong>for</strong> category B land uses, and the 71 dBANAC <strong>for</strong> category C land uses) are shown in shaded cells. The existing conditions modeling shows that trafficnoise levels in the project study area are generally below the NAC, except at locations very close to I-<strong>90</strong>where existing noise levels are in the low 70 dBAs. These receptors include R6, R9, R11, and R12. Two <strong>of</strong>these receptors are on the Centennial Trail, which runs just south <strong>of</strong> I-<strong>90</strong>.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-42Project No. A010(963)June 2011


ReceiverCurrent LandUseTable 3-9. Predicted Peak Hour Sound Levels (Leq) <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange ProjectFuture LandUse 1NACActivityCategoryDistancefrom Nearest<strong>Road</strong>wayCenterline(feet)Nearest<strong>Road</strong>wayNumber <strong>of</strong>ResidentialUnitsNoiseAbatementCriteria(dBA)Existing(2010) No-Build NoiseLevels(dBA) 3Future(2030) No-BuildNoiseLevels(dBA) 3Future(2030) BuildNoiseLevels(dBA) 3R1 Commercial Commercial C 640 I-<strong>90</strong> EB — 71 61 64 64R2 Commercial Commercial C 9<strong>90</strong> I-<strong>90</strong> EB — 71 57 59 62R3 Commercial Commercial C 940 I-<strong>90</strong> EB — 71 56 59 60R4 Commercial Commercial C 780 I-<strong>90</strong> EB — 71 57 60 59R5 Commercial Commercial C 220 I-<strong>90</strong> EB — 71 68 71 66R6 Recreational Recreational B 110 I-<strong>90</strong> EB — 66 78 80 80R7 2 Undeveloped Recreational B 255 I-<strong>90</strong> EB — 66 - - 63R8 2 Undeveloped Recreational B 125 I-<strong>90</strong> EB — 66 - - 68R9 Recreational Recreational B <strong>90</strong> I-<strong>90</strong> EB — 66 72 74 73R10 Undeveloped Commercial C 245 I-<strong>90</strong> WB — 71 66 68 64R11 Undeveloped Commercial C 160 I-<strong>90</strong> WB — 71 73 76 73R12 Undeveloped Commercial C 155 I-<strong>90</strong> WB — 71 75 78 77R13 Undeveloped Commercial C 605 I-<strong>90</strong> WB — 71 59 69 72R14 Undeveloped Commercial C 325 I-<strong>90</strong> WB — 71 65 69 68R15 Undeveloped Commercial C 575 I-<strong>90</strong> WB — 71 62 65 65R16 Undeveloped Commercial C 555 I-<strong>90</strong> WB — 71 61 64 72R17 Undeveloped Commercial C 705 I-<strong>90</strong> WB — 71 58 70 74R18 Undeveloped Commercial C 770 I-<strong>90</strong> WB — 71 56 69 73R19 Commercial Commercial C 1055 I-<strong>90</strong> WB — 71 55 63 65R20 Undeveloped Commercial C 1020 I-<strong>90</strong> WB — 71 55 69 70R21 Undeveloped Commercial C 1375 I-<strong>90</strong> WB — 71 53 69 70R22 4 Undeveloped Commercial C 14<strong>90</strong> Seltice Way — 71 50 70 71R23 4 Undeveloped Commercial C 1175 Seltice Way — 71 48 70 70R24 4 Undeveloped Commercial C 835 Seltice Way — 71 47 62 63I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-44Project No. A010(963)June 2011


ReceiverCurrent LandUseFuture LandUse 1NACActivityCategoryDistancefrom Nearest<strong>Road</strong>wayCenterline(feet)Nearest<strong>Road</strong>wayNumber <strong>of</strong>ResidentialUnitsNoiseAbatementCriteria(dBA)Existing(2010) No-Build NoiseLevels(dBA) 3Future(2030) No-BuildNoiseLevels(dBA) 3Future(2030) BuildNoiseLevels(dBA) 3R25 4 Undeveloped Commercial C 660 Seltice Way — 71 48 58 58R26 4 Undeveloped Commercial C 645 Seltice Way — 71 48 62 64R27 4 Undeveloped Commercial C 965 Seltice Way — 71 48 63 64R28 4 Undeveloped Commercial C 750 Seltice Way — 71 48 62 63R29 4 Undeveloped Commercial C 510 Seltice Way — 71 50 68 67R30 Residential Residential B 715 Seltice Way 2 66 48 60 58R31 Residential Residential B 570 Seltice Way 2 66 48 56 55R32 Residential Residential B 475 Seltice Way 1 66 49 56 55R33 Residential Residential B 395 Seltice Way 2 66 51 57 56R34 Residential Residential B 300 Seltice Way 1 66 53 58 57R35 Residential Residential B 235 Seltice Way 1 66 56 59 59R36 Residential Residential B 135 Seltice Way 1 66 63 65 651Future commercial development is planned <strong>for</strong> the area between I-<strong>90</strong> and W. Seltice Way in the project area. The noise analysis considers this development as plannedby the <strong>City</strong>; however, construction <strong>of</strong> this development has not yet begun, nor are there any building permits issued <strong>for</strong> this area.2Note that Receptors 7 and 8 represent the proposed realignment <strong>of</strong> Centennial Trail. Existing and future No-Build noise levels on the Centennial Trail are provided byReceptors 6 and 9.3 Predicted noise levels that are shaded represent values that approach the absolute NAC; numbers in bold represent values predicted to be 15 dBA or more aboveexisting noise levels.4A special use permit has been approved by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> that would allow mixed land uses with some multi-family development near receptors 22-29 along N.<strong>Beck</strong> <strong>Road</strong>. The current zoning <strong>for</strong> this area remains Community Commercial Services and no building permits have been issued and no development plans have beensubmitted to the <strong>City</strong>.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-45Project No. A010(963)June 2011


3.8.3 <strong>Environmental</strong> ConsequencesNo-BuildThe No-Build Alternative noise modeling results are summarized in Table 3-9. No-Build noise levels arepredicted to range from 56 to 80 dBA. The results <strong>of</strong> the No-Build condition analysis also show that changesin noise levels when compared to the existing condition are predicted to range from a reduction <strong>of</strong> 2 dBA toan increase <strong>of</strong> 22 dBA. Increases in noise levels between the existing and No-Build conditions are partly dueto natural traffic volume increases over time, but predominantly due to the construction <strong>of</strong> planned futuredevelopment north <strong>of</strong> I-<strong>90</strong>. The analysis assumes that by 2030, full build-out <strong>of</strong> this area will have occurred,and traffic volumes on surface streets in this area reflect this level <strong>of</strong> development. Decreases in noise levels,where predicted, are due to changes in traffic patterns as a result <strong>of</strong> new roadways associated with plannedfuture development.Increases in noise levels over the existing condition <strong>of</strong> up to 22 dBA occur at areas that are undeveloped atthis time and, as a result, currently experience relatively low ambient noise levels. It should be noted thatfuture noise levels at these receptors are not in exceedance <strong>of</strong> the absolute ITD NAC activity category C <strong>for</strong>commercial developments (71 dBA), and that the traffic volumes that create these increases are a direct result<strong>of</strong> future development.The No-Build analysis predicts that exceedance <strong>of</strong> the ITD NAC would occur at the Centennial Trail (NACactivity category B), and at three receptors (NAC activity category C) adjacent to I-<strong>90</strong>. In addition, increasednoise would occur at receptors (NAC activity category C) adjacent to N. <strong>Beck</strong> <strong>Road</strong>. However, as previouslynoted, these commercial structures have not yet been constructed and no building permits have been issued.Noise impacts are not anticipated to existing or planned residential development under the No-Buildcondition.Proposed ActionDirect ImpactsThe results <strong>for</strong> the future (2030) Build condition analysis are shown in Table 3-9.The Proposed Action noiselevels range from 55 to 80 dBA. Predicted exceedances <strong>of</strong> the absolute NAC are shown in shaded cells. Noiselevels predicted to be 15 dBA or more above existing noise levels are shown in bold typeface. Predicted levelsunder the Proposed Action reflect noise level changes similar to the No-Build condition that result fromannual traffic growth on I-<strong>90</strong> as well as traffic volume increases from the planned development in the projectarea, combined with noise contributions from the new interchange and associated changes in traffic patternsthat result from the new I-<strong>90</strong> interchange. Impacted receptors include R13, R16, R17, R20, R21, R22, R23,R24, R26, R27, R28, and R29.The results <strong>of</strong> the Build condition analysis show that changes in noise levels when compared to the existingcondition are the same as are predicted under the No-Build condition (i.e., changes range between a reduction<strong>of</strong> 2 dBA to an increase <strong>of</strong> 22 dBA). However, the magnitude <strong>of</strong> noise levels at specific locations under theBuild condition vary somewhat from the No-Build due to changes in traffic patterns (i.e. changes in trafficdistribution on the roadway network; particularly with the construction <strong>of</strong> the new I-<strong>90</strong> interchange), andchanges in shielding (i.e., topography that can block noise, such as fill used to build interchange ramps). TheBuild condition analysis shows that changes in noise levels when compared to the No-Build condition rangebetween a reduction <strong>of</strong> 5 dBA to an increase <strong>of</strong> 8 dBA.The Build analysis predicts that exceedances <strong>of</strong> the NAC would occur at the Centennial Trail (NAC activitycategory B), at two receptors (NAC activity category C) directly north <strong>of</strong> I-<strong>90</strong>, and at four future receptors(NAC activity category C) adjacent to N. <strong>Beck</strong> <strong>Road</strong>. In addition, substantial increases would occur <strong>for</strong> futureI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-46Project No. A010(963)June 2011


eceptors (NAC activity category C) adjacent to N. <strong>Beck</strong> <strong>Road</strong>. No noise impacts to existing residentialdevelopments are predicted under the Build condition and no building permits have been issued.The changes in noise levels that occur at receptors due to the project would occur in the context <strong>of</strong> the broadernoise environment and would be cumulative relative to other changes that may occur. The general noiseenvironment in the project area includes:• Traffic noise from I-<strong>90</strong>, W. Seltice Way, and adjacent roadways• Train noise from the railway line and at-grade railroad crossings north <strong>of</strong> W. Seltice Way• Noise from local industrial and commercial activities• Noise from residential developments in the general vicinityConstruction <strong>of</strong> the project could be expected to cause short-term noise impacts in areas directly adjacent toconstruction activity. Construction equipment noise levels are usually measured at 50 feet from the source.Construction equipment noise levels decrease 6 dBA per doubling <strong>of</strong> distance because <strong>of</strong> geometricdivergence alone, provided there is a clear line <strong>of</strong> sight to the equipment. For example, a bulldozer creating 80dBA <strong>of</strong> noise at 50 feet will have an observed value <strong>of</strong> 74 dBA at 100 feet and 68 dBA at 200 feet.Indirect ImpactsAs described above, the Proposed Action is associated to land use changes from undeveloped land to a moresuburban setting with commercial and industrial developments. This change in land use would result ingreater noise in the area associated with increases in people and vehicles. In addition, temporary noiseimpacts associated with construction activities are expected. Using standard specifications <strong>for</strong> control <strong>of</strong> noisesources during construction can minimize construction impacts.Cumulative ImpactsThe changes in noise levels that occur at individual properties due to the project would occur in the context <strong>of</strong>the broader noise environment and would be cumulative relative to other changes that may occur. The generalnoise environment in the project area includes traffic noise from I-<strong>90</strong> and W. Seltice Way, from the railwayline and an at-grade railroad crossing north <strong>of</strong> W. Seltice Way, from local industrial and commercialactivities, as well as from residential developments in the general vicinity.Noise in the area is likely to gradually increase over time as road capacities are expanded and developmentoccurs. Noise studies would be conducted <strong>for</strong> transportation projects that receive federal funding andmitigation would be considered following state and federal guidelines. When transportation projects aredeveloped with federal monies, cities and counties are provided with noise transects (noise levels at a givendistance) to help them in establishing setback requirements. Noise from construction <strong>of</strong> other projects andincreased human presence in the area due to development can also be expected.In an ef<strong>for</strong>t to provide local <strong>of</strong>ficials with in<strong>for</strong>mation to prevent future traffic noise impacts on currentlyundeveloped lands in con<strong>for</strong>mance with 23 CFR 772.15, ten-point transects were modeled <strong>for</strong> I-<strong>90</strong> andN. <strong>Beck</strong> <strong>Road</strong> to give an indication <strong>of</strong> future (2030) Proposed Action condition noise levels at distances <strong>of</strong> 50,75, 100, 125, 150, 200, 250, 300, 400, and 800 feet from roadway centerlines. This in<strong>for</strong>mation can be foundin the Technical Noise Report (HDR 2011a).MitigationUnder the 23 CFR 772, NAC require that if noise impacts are identified (i.e. a receptor approaches or exceedsFHWA NAC), abatement measures must be considered. Those considerations, when they are determined tobe both reasonable and feasible, are to be incorporated into the project.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-47Project No. A010(963)June 2011


The six considerations <strong>for</strong> mitigation are as follows:• Traffic management measures• Alteration <strong>of</strong> horizontal and vertical alignments• Acquisition <strong>of</strong> property rights <strong>for</strong> construction <strong>of</strong> noise barriers• Construction <strong>of</strong> Noise Barriers• Acquisition <strong>of</strong> real property or interests therein <strong>for</strong> buffer zones includes landscaping <strong>for</strong> aestheticpurposes (in or out <strong>of</strong> R/W)• Noise insulation <strong>of</strong> public use or non-pr<strong>of</strong>it institutional structuresThe ITD Noise Policy (ITD 2007) states that ITD will consider abatement measures to alleviate traffic noiseimpacts adjacent to Type 1 projects (which includes the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project). ITD’s policyalso states that while ITD will consider all six abatement measures described in 23 CFR 772.13(c), ITDconsiders that, typically, noise barriers are primarily the only feasible and reasonable noise abatementmeasure. Further, ITD’s policy states that it will consider existing or approved residences and other sensitiveland uses to be reasonable candidates <strong>for</strong> the construction <strong>of</strong> noise walls. ITD considers parking lots, highwaybusinesses, and other commercial or industrial enterprises as uses typically located adjacent to highways <strong>for</strong>exposure purposes and highly dependent on transportation access; there<strong>for</strong>e, they are considered noisetolerantreceptors and given less emphasis <strong>for</strong> traffic noise abatement. In fact, ITD prefers these types <strong>of</strong> usesare located adjacent to higher volume roads as a noise buffer to the more sensitive uses such as residentialdevelopments.The impacted noise receptors occur along N. <strong>Beck</strong> <strong>Road</strong> between W. Pointe Parkway and W. Seltice Way orat the intersection <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> and W. Pointe Parkway. According to 23 CFR 772.13(b), noise abatementmeasures will only be approved along lands where land development predates the existence <strong>of</strong> the project or ifthe granting <strong>of</strong> a building permit on impacted property occurs prior to FONSI approval. None <strong>of</strong> the parcels inthe project area adjacent to the remaining impacted noise receptors are developed. Bill Melvin, the <strong>City</strong>Engineer at the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> was contacted to identify if there are any active building permits <strong>for</strong> theimpacted receptor locations in the project vicinity (Melvin 2011). Mr. Melvin verified that no active buildingpermits are currently being processed by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> <strong>for</strong> this area. A special use permit was recentlyapproved by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> that would allow mixed land uses with some multi-family developmentalong N. <strong>Beck</strong> <strong>Road</strong> north <strong>of</strong> W. Expo Parkway. The current zoning <strong>for</strong> this area remains CommunityCommercial Services (retail, pr<strong>of</strong>essional, and consumer services), no building permits have been issued andno development plans <strong>for</strong> N. <strong>Beck</strong> <strong>Road</strong> have been received by the <strong>City</strong>.For the Centennial Trail receptors (R6, R7, R8 and R9), an ITD Noise Barrier Abatement Checklist wascompleted to assess the feasibility <strong>of</strong> a barrier <strong>for</strong> sound level reduction (Appendix A). For barrier feasibility,criteria number 3 was answered as a “no” indicating that a barrier is not feasible, where criteria 3 states:Can an effective barrier be constructed considering the existing site characteristics and topography, andwithout reconfiguring the site or neighborhood (not including minor access modifications)?The Centennial Trail would likely have to be shifted to accommodate a noise barrier in this location.Moreover, the effectiveness <strong>of</strong> a noise barrier is uncertain because it would only block noise <strong>for</strong> a small extent<strong>of</strong> the Centennial Trail that follows I-<strong>90</strong> <strong>for</strong> a considerable distance.With the exception <strong>of</strong> noise impacts to the Centennial Trail (a recreational use and NAC activity category B),all noise impacts associated with the Proposed Action are predicted at properties with CommunityCommercial Services zoning (NAC activity category C). All noise impacts are predicted at receptorsrepresentative <strong>of</strong> future development sites. In the majority <strong>of</strong> cases, substantial noise increases at plannedfuture development locations occur as a result <strong>of</strong> the development (i.e. increased traffic generated byI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-48Project No. A010(963)June 2011


commerce as part <strong>of</strong> the No-Build condition), rather than the construction <strong>of</strong> the Proposed Action andassociated roadway connections. Further, although future development is planned in these areas, none <strong>of</strong> theseproperties are built today. Due to the type <strong>of</strong> land use zoning in this area, noise mitigation <strong>for</strong> predicted noiseimpacts is not recommended based on ITD policy. The future land uses and building permits granted <strong>for</strong> theseparcels will be subject to <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> approval. The city will be notified <strong>of</strong> the projected impactsoutlined in this document.FHWA outlines physical techniques to reduce noise impacts such as increasing the distance between the noisesource and the receiver or through other acoustical site planning techniques (FHWA 2011). In the futuredevelopment areas where noise impacts are projected to occur, ensuring appropriate land uses and regulatingbuilding setbacks or building orientation should be considered via local zoning code to provide mitigation <strong>for</strong>noise impacts. In<strong>for</strong>mation from the Noise Technical Report <strong>for</strong> this project will be provided to local <strong>of</strong>ficialsto notify them <strong>of</strong> these impacts (HDR 2011a).Noise impacts at the Centennial Trail are a result <strong>of</strong> traffic on I-<strong>90</strong> and not related to the project. Table 3-9shows that noise impacts would occur on the trail with or without the project (monitoring point M5) due tothe proximity to I-<strong>90</strong> and W. Riverbend Avenue. In some locations, fill associated with the proposedinterchange would result in lower future noise levels on the Centennial Trail in the project area. In addition,there are no areas on the trail in the project area where users would tend to spend any extended length <strong>of</strong> time(such as seating or picnic areas). As a result, noise mitigation <strong>for</strong> the Centennial Trail is not recommended.The project is not located in or directly adjacent to an existing residential area and is there<strong>for</strong>e not subject to<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> construction activity noise requirements (see <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>, 1992). Construction noisecan be reduced by using enclosures or walls to surround noisy equipment, installing mufflers on engines,substituting quieter equipment or construction methods, minimizing time <strong>of</strong> operation, and locatingequipment farther from sensitive receptors. To reduce construction noise at nearby receptors, the followingmitigation measures could be incorporated into construction plans and contractor specifications:• Construction equipment engines will be equipped with adequate mufflers, intake silencers, and engineenclosures when feasible• Construction equipment will be turned <strong>of</strong>f during prolonged periods <strong>of</strong> nonuse• Equipment will be maintained and equipment operators will be trained to reduce noise levels andincrease efficiency <strong>of</strong> operation.• Stationary equipment will be located away from receiving properties to decrease noise to the extentpracticable.3.9 Prime FarmlandThis section describes the affected environment and evaluates the impacts <strong>of</strong> the Proposed Action onfarmlands that are classified as prime, unique, or <strong>of</strong> statewide or local importance.3.9.1 Affected EnvironmentAs set <strong>for</strong>th by the farmland Protection Policy Act <strong>of</strong> 1981, federal programs are required to minimizeunnecessary and irreversible conversion <strong>of</strong> farmland to non-agricultural uses and should be compatible withpolicies to protect farmland. Thus, prime and unique farmlands are reviewed as part <strong>of</strong> the EA process.Farmlands are classified as prime, unique, or <strong>of</strong> statewide or local importance and are defined below.Prime farmland:• Has the best combination <strong>of</strong> physical and chemical characteristics <strong>for</strong> producing food, feed, <strong>for</strong>age,fiber, and oilseed crops.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-49Project No. A010(963)June 2011


• Is available <strong>for</strong> other uses like cropland, pastureland, rangeland, <strong>for</strong>est land, and other agriculturalcrops with minimum inputs <strong>of</strong> fuel, fertilizer, pesticides, and labor, and without intolerable soilerosion.• Has the soil quality, growing season, and moisture supply needed to economically produce sustainedhigh yields <strong>of</strong> crops when treated and managed, including water management, according to acceptablefarming methods.Unique farmlands:• Is land other than prime farmland that is used <strong>for</strong> production <strong>of</strong> specific high-value food and fibercrops.• Has the special combination <strong>of</strong> soil quality, growing season, and moisture supply temperature,humidity, air drainage, elevation, and aspect to economically produce sustained high-quality or highyields <strong>of</strong> specific crops when treated and managed according to acceptable farming methods (NRCS2008).Farmland <strong>of</strong> statewide or local importance:• Is farmland, other than prime or unique farmland, that is important <strong>for</strong> the production <strong>of</strong> food, feed,fiber, <strong>for</strong>age, or oil-seed crops, as determined by the state or local government agency or agencies,using U.S. Department <strong>of</strong> Agriculture guidelines (NRCS 2008).Table 3-10 summarizes soils mapped in the project area and whether they are classified as suitable <strong>for</strong>supporting prime farmland, unique farmland, or farmland <strong>of</strong> statewide importance. Figure 3-17 depicts thesoil designations in the project area.The soils and farmland resource review <strong>for</strong> the project consisted <strong>of</strong> compiling soil in<strong>for</strong>mation from theNatural Resource Conservation Service (NRCS) Web Soil Survey and conducting a Farmland ConversionImpact Rating with the Idaho state <strong>of</strong>fice <strong>of</strong> the NRCS. According to the Web Soil Survey, approximately 77percent <strong>of</strong> the project area is comprised <strong>of</strong> Garrison gravelly silt loam, which is considered to be PrimeFarmland, if irrigated (NRCS 2007). This soil type is located on both sides <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong>, north <strong>of</strong> theinterstate (see Web Soil Survey in Appendix C). As shown in the aerial photograph in Figure 1-2, most <strong>of</strong>this area has been rezoned and developed or has been graded and/or filled and is no longer available <strong>for</strong> use asfarmland.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-50Project No. A010(963)June 2011


Table 3-10. Summary <strong>of</strong> Soils and Prime Farmland in the Project AreaMapUnitSymbolMap Unit NameAcres inArea <strong>of</strong>InterestPercent<strong>of</strong> Area <strong>of</strong>InterestPrime Farmland?Kootenai County Area, Idaho101 Aquic xer<strong>of</strong>luvents, nearly level 11.5


3.9.2 <strong>Environmental</strong> ConsequencesNo-BuildThe farmland in the N. <strong>Beck</strong> <strong>Road</strong> area is no longer zoned agricultural and is not currently being cultivated<strong>for</strong> agricultural purposes. Under the No-Build Alternative this area would continue to be developed.Proposed ActionDirect ImpactsThe Farmland Protection Policy Act is intended to minimize the impact federal programs have on unnecessaryand irreversible conversion <strong>of</strong> farmland to nonagricultural purposes. None <strong>of</strong> the land in the project area iscurrently used <strong>for</strong> agricultural purposes. Most <strong>of</strong> the land that would include the footprint <strong>of</strong> the ProposedAction is adjacent to N. <strong>Beck</strong> <strong>Road</strong> and I-<strong>90</strong>, and is reserved and graded <strong>for</strong> future development.Hal Swenson <strong>of</strong> the Idaho state <strong>of</strong>fice <strong>of</strong> the NRCS was consulted <strong>for</strong> the Farmland Conversion Impact Rating<strong>for</strong> the project, which is required <strong>for</strong> all federal projects. Mr. Swenson stated that if none <strong>of</strong> the area impactedby the project is currently used <strong>for</strong> agriculture and if it is already committed to urban land use, then the projectwould not be considered to be converting farmland. The completed impact rating, received from Mr. Swensonon February 3, 2011, indicated that there was no farmland in the project corridor, and there<strong>for</strong>e, none could beconverted by the project (Appendix C).Indirect ImpactsThe interchange would likely influence the rate <strong>of</strong> development in the area. However, none <strong>of</strong> the land in thearea is currently being cultivated <strong>for</strong> farmland.Land use, including changes from undeveloped land to residential, commercial or industrial uses, areidentified in locally- and regionally-approved planning documents. These documents assume the presence <strong>of</strong>an interchange near N. <strong>Beck</strong> <strong>Road</strong> and encourage commercial and industrial development. Thus, the ProposedAction does not contribute to indirect impacts on farmland.Cumulative ImpactsThe Proposed Action would have no direct impact to farmland, and there<strong>for</strong>e, no cumulative impacts t<strong>of</strong>armland.MitigationNo mitigation is required because the Proposed Action would have no effects on farmlands.3.10 Air QualityThis section describes the affected environment and evaluates potential impacts <strong>of</strong> the Proposed Action on airquality in the project area.3.10.1 Affected EnvironmentThe framework <strong>for</strong> controlling air pollutants in the United States is mandated by the 1970 Clean Air Act(Public Law 91-604), as amended in 1977 and 19<strong>90</strong>. The Rules <strong>for</strong> the Control <strong>of</strong> Air Pollution in Idaho are inIDAPA 58.01.01.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-53Project No. A010(963)June 2011


The air-quality review <strong>for</strong> the Proposed Action evaluated air quality attainment areas listed by IDEQ at:(http://www.deq.idaho.gov/air/data_reports/monitoring/overview.cfm). USEPA uses the following three airqualityclassifications <strong>for</strong> geographic areas based on air-pollutant levels (See box):• Attainment Area• Non-attainment Area• Maintenance AreaThe <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> is in attainment, so animplementation plan is not necessary to meet airqualitystandards.The USEPA Office <strong>of</strong> Air Quality Planning andStandards has set National Ambient Air QualityStandards (NAAQS) <strong>for</strong> six principal pollutantscalled "criteria" pollutants: carbon monoxide, lead,nitrogen dioxide, particulate matter, ozone, andsulfur dioxide. USEPA also regulates mobilesourceair toxics (MSATs), which includecompounds emitted from highway vehicles andnon-road equipment. These are further discussedbelow.3.10.2 <strong>Environmental</strong> ConsequencesNo-BuildNone <strong>of</strong> the emissions expected from future activities along the existing N. <strong>Beck</strong> <strong>Road</strong> and I-<strong>90</strong> corridors areexpected to cause adverse impacts on air quality or public health, or violate the NAAQS. Under the No-BuildAlternative, traffic congestion and emissions would be greater compared to the Proposed Action. Greateremissions, however, would likely be <strong>of</strong>fset by future tighter vehicle-emission standards.Proposed ActionPotential effects on air quality as a result <strong>of</strong> the Proposed Action are described in the following sections.Direct ImpactsITD’s Air Screening Policy (ITD 2007) outlines requirements <strong>for</strong> air analysis <strong>for</strong> transportation projects inIdaho receiving federal actions. The project is not within a federally designated air quality non-attainment ormaintenance area nor is it within an IDEQ air quality area <strong>of</strong>concern. There<strong>for</strong>e, air quality impacts were not required to beevaluated in this EA. However, consideration is given to airquality impacts and mitigation measures are outlined below.Because the proposed interchange would include traffic signalsand create new queuing areas, air-quality changes caused byadditional idling may occur. Additionally, USEPA isincreasingly concerned about MSATs, which are compoundsemitted from vehicles and other equipment that are known orsuspected to cause cancer or other serious health andenvironmental effects (see box).Air Quality ClassificationAttainment Area – A geographic area with pollutantlevels at or below the National Ambient Air QualityStandards.Non-attainment Area – An area with persistent airqualityproblems (the area has violated federalhealth-based standards <strong>for</strong> outdoor air pollution).Non-attainment areas are declared <strong>for</strong> specificpollutants.Maintenance Area – An area that has been redesignatedby the USEPA from non-attainment toattainment as a result <strong>of</strong> both a 10-year record <strong>of</strong>monitored attainment (no exceedances <strong>of</strong> standards)and an USEPA-approved maintenance plan.Mobile-Source Air ToxicsMSATs are toxic compounds emittedfrom highway vehicles and non-roadequipment that are known or suspectedto cause cancer or other serious healthand environmental effects. Some arepresent in fuel and emitted into the air;others are emitted from the incompletecombustion <strong>of</strong> fuels, as secondarycombustion products, or as metaltoxics from engine wear or impurities inoil or gasoline.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-54Project No. A010(963)June 2011


Some toxic compounds are present in fuel and are emitted into the air when fuel evaporates or passes throughthe engine unburned. Others are emitted from the incomplete combustion <strong>of</strong> fuels or as secondary combustionproducts. Metal air toxics also result from engine wear or impurities in oil or gasoline.Currently, no known models are available to adequately predict changes in MSATs as a result <strong>of</strong> the I-<strong>90</strong><strong>Beck</strong> <strong>Road</strong> Interchange project. FHWA guidance suggests a three-tiered approach to analyzing the effects <strong>of</strong> atransportation project in terms <strong>of</strong> public exposure to MSATs (FHWA 2009):1. No analysis <strong>for</strong> projects with no potential <strong>for</strong> meaningful MSATs effects2. Qualitative analysis <strong>for</strong> projects with low potential <strong>for</strong> MSATs effects3. Quantitative analysis to differentiate alternatives <strong>for</strong> projects with higher potential <strong>for</strong> mobile-sourceair toxicsThe Proposed Action would enhance access and cross-freeway mobility, improve the level <strong>of</strong> service <strong>for</strong>traffic in the project area, and provide safe and efficient movement <strong>of</strong> traffic. The Proposed Action is notexpected to cause a meaningful increase in emissions effects compared to the No-Build Alternative.There<strong>for</strong>e, FHWA has determined that the Proposed Action does not cause any special concerns <strong>for</strong> MSATs.In addition, vehicle emissions would likely be lower than current levels <strong>for</strong> design year 2030 as a result <strong>of</strong>USEPA national air pollution control programs that are projected to reduce MSATs by 57 to 87 percentbetween 2000 and 2020. Local conditions may differ from these national projections due to fleet mix andturnover, vehicle miles growth rates, and local control measures. However, the magnitude <strong>of</strong> the USEPAprojectedreductions is so great (even after accounting <strong>for</strong> potential vehicle-use growth) that MSATsemissions in the project area are likely to be lower in the future in nearly all cases. Based on current bestavailable in<strong>for</strong>mation, the project would have no significant adverse impact on air quality because <strong>of</strong> MSATsemissions.Under the Proposed Action, short-term construction-related emissions would result from exhaust pollutantsgenerated by heavy construction vehicles and equipment on and <strong>of</strong>f-site over the construction period.Construction traffic and lane closures could increase congestion in the area, causing a temporary increase inemissions.Construction-related fugitive dust and particulate emissions could occur during construction <strong>of</strong> the proposedinterchange. Fugitive dust consists <strong>of</strong> small airborne particles from non-point sources such as unpaved roads,cropland, and construction sites. Sources include unpaved roads, cropland, and construction sites. Fugitivedust could occur during activities such as:• Cut-and-fill activities• Operating rock crushers and sorters <strong>for</strong> aggregate sizing• Extraction and processing <strong>of</strong> borrow material• Operation <strong>of</strong> vehicles and equipment• Clearing vegetationIndirect ImpactsPlanned development in the project area could cause some localized, short-term air quality impacts if severalprojects were under construction simultaneously. However, none <strong>of</strong> the expected commercial or industrialdevelopment in the area is expected to contribute to poor air quality once under operation. There<strong>for</strong>e, theProposed Action would have no long-term indirect impacts on air quality.Cumulative ImpactsOngoing and planned future projects in the area may produce localized, short-term impacts such asconstruction related fugitive dust emissions. Such impacts would have minimal effect on the area’s overall airquality. There<strong>for</strong>e, the Proposed Action would have no long-term cumulative impacts on air quality.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-55Project No. A010(963)June 2011


MitigationConstruction specifications would require contractors to comply with applicable federal, state, and local airqualitystandards and emission limitations <strong>of</strong> the Clean Air Act. During construction, contractors will berequired to use methods and devices that are available to control, prevent, and otherwise minimizeatmospheric emissions or discharges <strong>of</strong> atmospheric contaminants.Contractors will be required to reduce dust that originates from construction operations and prevent dust fromdamaging dwellings or causing a nuisance. This will include periodically spraying exposed soils with water.Long-term soil stabilization will be achieved by re-vegetating exposed areas once they are no longer needed<strong>for</strong> project construction.General construction requirements and BMPs to prevent fugitive dust and reduce air emissions are outlinedbelow. ITD Standard Specifications and BMPs in the ITD Erosion and Sediment Control manual will befollowed. These measures are in accordance with the IDAPA 58.01.01, Sections 650 through 651 and IDEQguidelines:• Water trucks will be used to control fugitive dust during construction operations.• Open-bodied trucks transporting materials likely to produce fugitive dust will be covered.• Trash and other combustible materials will be disposed <strong>of</strong> in an approved sanitary landfill.• Asphalt plants and rock crushers will be used in compliance with IDEQ regulatory requirements.Rock crushers must be properly permitted by the IDEQ and the contractor would submit PortableEquipment Relocation Forms when movement <strong>of</strong> such equipment is necessary. Settling chambersand filters, or other primary or secondary collection devices, may be necessary <strong>for</strong> particulate control.3.11 Earth ResourcesThis section describes the affected environment and evaluates potential impacts <strong>of</strong> the Proposed Action on thesoils and geology in the project area (groundwater and surface waters are addressed in Section 3.6).3.11.1 Affected EnvironmentThe proposed interchange site is located in the Spokane Valley on the Rathdrum Prairie, which is composed<strong>of</strong> ancient geologic features that have been slowly <strong>for</strong>med by millions <strong>of</strong> years <strong>of</strong> water flow toward thePacific Ocean. During the last glacial age, between 12,000 and 1.6 million years ago, a series <strong>of</strong> catastrophicfloods covered this area as a result <strong>of</strong> the rapid draining <strong>of</strong> ancient Lake Missoula in Montana when ice damsbroke. These floods deposited thick layers <strong>of</strong> coarse sediments (gravels, cobbles, and boulders) in this area.The saturated portion <strong>of</strong> these sediments, where void spaces are filled with water, comprises the SVRPA.Waters from adjacent lakes, mountain streams, the Spokane River, precipitation, and flow through the floodsediments help replenish the aquifer (MacInnis 2009).The geologic history <strong>of</strong> the area includes ancient mountain building, basalt lava flows, and some <strong>of</strong> the largestknown glacial outburst floods (Spokane County 2011). The creation <strong>of</strong> the SVRPA is defined by three majorgeologic events. The first was the emplacement, metamorphism, and erosion <strong>of</strong> the Precambrian basementrock; the second was the eruption <strong>of</strong> Tertiary (Miocene) flood basalts that created the Columbia Plateau; andthe third was the glaciation in the Quaternary Period that first eroded, then filled the Spokane Valley-Rathdrum Prairie area with coarse sediments and gravel that <strong>for</strong>med the aquifer (MacInnis 2009).Bedrock, which includes the Precambrian to Tertiary metamorphic and intrusive igneous rocks and Tertiarybasalt and their interbeds, underlies and laterally bounds the SVRPA. These are generally low-permeabilityrocks (MacInnis 2009). The majority <strong>of</strong> the project area is characterized by garrison gravelly and stony siltloam soils (Section 3.9.1). The parent material <strong>of</strong> these soils is volcanic ash and loess and is <strong>of</strong>ten located onoutwash terraces.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-56Project No. A010(963)June 2011


The project area overlays Missoula Flood deposits. The western part <strong>of</strong> Kootenai County, west <strong>of</strong> Coeurd’Alene Lake and the Rathdrum Prairie belongs to the lower plate <strong>of</strong> the Priest River core complex. Thenormal fault bounding the uplifted metamorphic rocks <strong>of</strong> the core complex dips eastward and follows thenorth-trending basin <strong>of</strong> Lake Coeur d’Alene. The nearest fault line is a normal fault which travels through theCoeur d’Alene Lake and continues northward just east <strong>of</strong> Coeur d’Alene, approximately 12 miles from theProposed Action.The SVRPA flows beneath a wide valley that slopes downward from Lake Pend Oreille to downtownSpokane – a loss <strong>of</strong> almost 700 feet in elevation. In the northern part <strong>of</strong> the aquifer boundary, Five-milePrairie splits the valley and the aquifer flows north from downtown Spokane to the west along the SpokaneRiver. In general, the higher the surface elevation, the greater the depth <strong>of</strong> the aquifer. The valley above theaquifer covers about 202 square miles in Idaho, including the Rathdrum Prairie, and 120 square miles inWashington, including the Spokane Valley (MacInnis 2009).Most <strong>of</strong> the Rathdrum Prairie is nearly level (zero to 2 percent grade) to moderately sloping (2 to 7 percent).Most <strong>of</strong> the water infiltrates rather than runs <strong>of</strong>f, except when the ground is frozen. A few steeper areas alongdrainages and foothills have some run<strong>of</strong>f (the steeper the slope, the greater the run<strong>of</strong>f).3.11.2 <strong>Environmental</strong> ConsequencesNo-BuildThere would be no impacts to earth resources under the No-Build Alternative.Proposed ActionPotential effects on earth resources as a result <strong>of</strong> the Proposed Action are described in the following sections.Direct ImpactsThe geologic features <strong>of</strong> the project site do not present constraints on the selection <strong>of</strong> a preferred location <strong>for</strong>the Proposed Action. There is a terrace that separates the Jacklin Seed Company operation from theGreyhound Park and Event Center. Cut slope and grading <strong>of</strong> this terrace will be required under the ProposedAction. Embankments will be required <strong>for</strong> the approach fill <strong>of</strong> the Proposed Action. Approximately 350,000cubic yards <strong>of</strong> fill will be furnished by the contractor <strong>for</strong> project construction.Indirect ImpactsThere would be no indirect impacts to earth resources as a result <strong>of</strong> the Proposed Action.Cumulative ImpactsThere would be no cumulative impacts to earth resources as a result <strong>of</strong> the Proposed Action.MitigationThe cut slope <strong>of</strong> the terrace just east <strong>of</strong> Jacklin Seed will be designed to ensure the structural integrity <strong>of</strong> theGreyhound Park and Event Center parking lot and the surrounding bench area.3.12 Hazardous MaterialsThis section describes the affected environment and evaluates potential impacts <strong>of</strong> the Proposed Action onhazardous materials. The hazardous materials investigation conducted <strong>for</strong> this project reviewed availablepublic records, including federal and state databases, to help identify the occurrence <strong>of</strong> known solid wastelandfills, hazardous waste sites, and Superfund sites. A review <strong>of</strong> the entire study area and adjacent areas wasI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-57Project No. A010(963)June 2011


completed as part <strong>of</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange <strong>Environmental</strong> Scan (HDR 2011b). Only sites within ornear the project footprint are discussed in this EA. In addition, the online searchable IDEQ undergroundstorage tank and leaking underground storage tank databases were reviewed. A windshield survey was alsoconducted.3.12.1 Affected EnvironmentThe area surrounding the proposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project is commercial and industrial.USEPA and IDEQ databases were searched <strong>for</strong>potential hazardous materials and waste sitesduring the <strong>Environmental</strong> Scan from W. SelticeWay to the Spokane River and from the State Line<strong>Road</strong> Interchange to the Pleasant View <strong>Road</strong>Interchange. This database search found severalbusinesses on or near W. Riverbend Avenue, S.Clearwater Loop, N. Pleasant View <strong>Road</strong>, and onW. Seltice Way. For the EA, the search wasnarrowed to the area within or adjacent to thefootprint <strong>of</strong> the Proposed Action. Only onebusiness, Jacklin Seed Company (also listed asJacklin Plant Food Center) was located within orFigure 3-18. Waste storage at Jacklin Seed adjacent to this footprint.The Jacklin Seed facility was listed in the following databases:• Resource Conservation and Recovery Act – This listing involves a cleanup <strong>for</strong> a dry well containingpesticides. The cleanup began in October 1995 and was listed as completed in April 1998.• Underground Storage Tank – Four tanks (one 10,000-gallon diesel, two 6,000-gallon gasoline, one10,000-gallon gasoline) were listed <strong>for</strong> the property. The status <strong>of</strong> the tanks was “permanently out <strong>of</strong>use.” The tanks were installed in the 1970s. No known leaks have occurred from these tanks.Windshield surveys (visual observation) <strong>of</strong> the project area were conducted on September 19, 2007 andJanuary 25, 2011. At the Jacklin Seed facility, evidence <strong>of</strong> debris and old machinery was observed in thesoutheastern corner <strong>of</strong> the property (Figure 3-18). No soil staining or other evidence <strong>of</strong> spills orcontamination were observed. Outside <strong>of</strong> the Jacklin Seed facility, no signs <strong>of</strong> hazardous materials storage,hazardous waste contamination, or past uses <strong>of</strong> property involving potential hazardous materials or wasteswere observed.3.12.2 <strong>Environmental</strong> ConsequencesNo-BuildThe No-Build Alternative would not cause construction disturbance to potential hazardous materials areas,nor would it pose a potential <strong>for</strong> spills during construction. If hazardous materials were present in the projectarea, continued business operations and future disturbances to currently undeveloped areas could spreadpotential contamination without <strong>for</strong>mal mitigation strategies.Proposed ActionConsequences <strong>for</strong> hazardous materials conditions in the project area as a result <strong>of</strong> the Proposed Action aredescribed in the following sections.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-58Project No. A010(963)June 2011


Direct ImpactsBased on the complete review <strong>of</strong> properties presented in the <strong>Environmental</strong> Scan (HDR 2011b), the ProposedAction would not impact hazardous materials or waste sites. The Proposed Action involves acquisition <strong>of</strong>portions <strong>of</strong> properties <strong>for</strong> proposed right-<strong>of</strong>-way. <strong>Environmental</strong> site assessments are commonly conductedprior to acquisition <strong>of</strong> sites that may have a history <strong>of</strong> hazardous materials use. The purpose <strong>of</strong> suchassessments is to identify existing recognized environmental conditions that would limit the buyer’s liability<strong>for</strong> past actions resulting in contamination. An environmental site assessment would likely be conducted <strong>for</strong>right-<strong>of</strong>-way to be acquired <strong>for</strong> the Proposed Action from the Jacklin Seed facility. If environmental siteassessments identify hazardous materials or areas <strong>of</strong> concern, these areas would be cleaned up prior to right<strong>of</strong>-wayacquisition.The Proposed Action would not displace residences or remove structures and there<strong>for</strong>e would not requirepotential disposal <strong>of</strong> asbestos and lead paint containing materials. If these materials were encountered, theywould be disposed <strong>of</strong> in accordance with federal, state, and local laws at the time <strong>of</strong> demolition.Hazardous materials can affect road construction projects in two ways:• The discovery <strong>of</strong> previously unknown hazardous materials during construction• The impacts <strong>of</strong> hazardous material releases from construction operationsDiscovery <strong>of</strong> contamination can stop a project until the contamination is defined and mitigation is determined.It is important not to make any contamination worse by spreading the material to non-impacted areas.Construction activities can result in hazardous material releases, such asa rupture in a hydraulic fuel line or an accidental overflow duringequipment fueling. The potential <strong>for</strong> releases can be avoided orminimized by implementing BMPs, such as regular equipmentmaintenance and checks, and having secondary containment aroundfuel tanks and other stored chemicals at the job site. Oil storage at theconstruction site may also be subject to 40 CFR 112, Oil PollutionPrevention, which requires a Spill Prevention, Control, andCountermeasure Plan <strong>for</strong> sites meeting certain criteria.Secondary ContainmentSecondary containment is acontainer or structural barrierplaced under or around avessel to contain the contents<strong>of</strong> the vessel in the event <strong>of</strong> anaccidental spill or leak.Indirect ImpactsThe Proposed Action may affect the rate <strong>of</strong> development in the project area. Construction <strong>for</strong> thisdevelopment would be required to follow applicable laws and regulations regarding hazardous materials.There would be no indirect hazardous materials impacts under the Proposed Action.Cumulative ImpactsThe Proposed Action would have no direct impacts to hazardous materials, and there<strong>for</strong>e would have nocumulative impacts to hazardous materials.Mitigation<strong>Environmental</strong> commitments <strong>for</strong> hazardous materials would be as follows:• If required, a Spill Prevention, Control, and Countermeasure Plan will be prepared and followed <strong>for</strong>management <strong>of</strong> fuels and used in response to accidental petroleum releases in accordance withapplicable federal and state regulations. A specific area would be designated <strong>for</strong> equipment repair andfuel storage.• The contractor would immediately notify the project sponsor if an underground storage tank, burieddrum, contaminated soil, or hazardous materials or debris not scheduled <strong>for</strong> removal under theI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-59Project No. A010(963)June 2011


contract is discovered during construction. In turn, the sponsor would follow procedures in place <strong>for</strong>notification or IDEQ, the Panhandle Health District, and other agencies required <strong>for</strong> notice dependingon the severity <strong>of</strong> the discovery.• If a hazardous material spill occurs as part <strong>of</strong> the construction process or in the construction area, thecontractor will immediately notify the project sponsor. If necessary, the sponsor will call the IdahoState Communication Public Health Paging System at 1-800-632-8000 to activate the responsesystem. The contractor would be required, at a minimum, to ensure the spill is contained immediately.If hazardous material enters a stormwater conveyance (ditch, culvert, or basin) with the potential toreach surface waters, that conveyance system would be blocked, dammed, or diked.• Contractors will be required to comply with the Idaho Hazardous Waste Management Regulationsestablished under the authority <strong>of</strong> the Federal Resource Conservation and Recovery Act <strong>of</strong> 1976.3.13 Visual ResourcesThis section describes the affected environment and evaluates potential impacts <strong>of</strong> the Proposed Action onvisual resources in the project area.3.13.1 Affected EnvironmentFHWA’s manual, Visual Impact <strong>Assessment</strong> <strong>for</strong> Highway Projects (FHWA 1981) provides guidance <strong>for</strong>assessing visual impacts and was used in this visual analysis. The FHWA process involves describing thevisual character and quality <strong>of</strong> existing visual resources based on distance zones and viewer exposuresensitivity.What is a Viewshed?The FHWA defines a viewshed asall <strong>of</strong> the surface area visible froma particular location (e.g., anoverlook) or sequence <strong>of</strong>locations (e.g., a roadway or trail).The dimensions and perimeter <strong>of</strong> a viewshed vary depending onterrain and vegetation or structures that may screen views <strong>of</strong> a projectarea. Because there are potentially an infinite number <strong>of</strong> viewinglocations within the viewshed <strong>of</strong> a project, analyses are typicallyconducted from a limited number <strong>of</strong> key observation points atparticularly sensitive locations to represent the most important views<strong>of</strong> the proposed project.The visual affected environment is characterized by a combination <strong>of</strong> the quality <strong>of</strong> the existing landscape andthe sensitivity <strong>of</strong> likely viewers to visual change. An additional factor is the capacity <strong>of</strong> the characteristiclandscape to absorb visual changes. The visual effects <strong>of</strong> a proposed project typically are evaluated based onthe degree to which project disturbance and facilities would contrast with the existing landscape.Visual quality is somewhat subjective and dependent on context. For example, a small, tree-lined lake wouldhave greater visual importance in the dry semi desert areas <strong>of</strong> southern Idaho, than in the northern IdahoPanhandle where these features are more common. In general, visual quality is a function <strong>of</strong> scenicattractiveness, variety, and the uniqueness <strong>of</strong> the characteristic landscape. A landscape with greater variety inland<strong>for</strong>m, linear features, color, or vegetation type generally is considered higher quality than one with littlediversity. A particular landscape that is similar in character to a large portion <strong>of</strong> the surrounding lands isconsidered lesser quality than one with unique, attractive features.Visual impacts are addressed based on distance zones – <strong>for</strong>eground, middleground, and background – whichare used to describe distance relationships between an observer and visual resources. The distinguishingcharacteristic that separates these three zones is the relative amount <strong>of</strong> detail that is normally perceived byviewers. Most <strong>of</strong> the landscape near bridges, freeways and arterial roadways is either <strong>for</strong>eground ormiddleground. Foreground is the view to a distance <strong>of</strong> about 1/4 mile (all visual patterns in the <strong>for</strong>eground areeasily seen), and middleground is the view from 1/4 to 3 miles away (line, <strong>for</strong>m and color are easily seen, butthe texture <strong>of</strong> visual objects is not perceptible). Details <strong>of</strong> roadway features are not perceptible at theI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-60Project No. A010(963)June 2011


ackground distance beyond 3 miles. Views are considered looking at the roadway features and from theroadway.Visual sensitivity is generally a function <strong>of</strong> the number <strong>of</strong> people who will view a landscape, the duration <strong>of</strong>their views and proximity to the subject landscape, and the reason they are in a position to observe the views.For example, a tourist stopping <strong>for</strong> a leisurely lunch at a scenic overlook is considered to be more sensitive tothe visual environment than a commuter driving by the same location on their way to work. A viewpointhosting 1,000 visitors per day throughout the summer and fall is considered more sensitive than one visited byjust a few people on occasional holiday weekends. Viewers within a quarter mile <strong>of</strong> a particular landscape(<strong>for</strong>eground) are considered to be more sensitive to visual effects than viewers 3 miles away (middleground).Visually sensitive areas are typically primary travel routes, residential communities, and designated recreationfacilities.The I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project area would fall into the lowest sensitivity category due to the extent<strong>of</strong> existing disturbance from development, I-<strong>90</strong>, and the man-made environment (described below).The major viewer groups are roadway users and roadway viewers. <strong>Road</strong>way users include drivers, passengers,bicyclists, and pedestrians who have views <strong>of</strong> the roadway and from the roadway <strong>of</strong> the surroundinglandscape. <strong>Road</strong>way viewers include pedestrians, residents, recreational users, businesses, visitors, and otherswho have views <strong>of</strong> the roadway in a landscape setting.Generally speaking, these two viewer groups have different sensitivities to the visual environment. Forexample, roadway users in heavy traffic are <strong>of</strong>ten focused on their immediate surroundings, traffic, and theroadway, and may not perceive the surrounding built environment or landscape. <strong>Road</strong>way viewers tend tohave a more comprehensive field <strong>of</strong> vision, time to observe the visual environment, a desire <strong>for</strong> visual interestor detail, and higher sensitivity to changes in visual quality.General Landscape CharacterGenerally, the existing landscape is disturbed throughout the project area (Figure 3-19 and Figure 3-20).Distinct alterations in the viewshed include previously disturbed ground, the I-<strong>90</strong>, Centennial Trail, dirt andpaved roadways including N. <strong>Beck</strong> <strong>Road</strong>, commercial and industrial development, overhead power lines,water tower, right-<strong>of</strong>-way fencing, and billboards.Figure 3-19 shows the view looking west from W. Pointe Parkway toward commercial development in thenorthwest project area. Previously disturbed ground vegetated by weedy species is visible in the <strong>for</strong>egroundand middleground. Mountains are visible in the background distance zone. These photos were selected todisplay the general landscape characteristics in the area including; the flat topography, vegetation type,disturbance and the mountains in the background.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-61Project No. A010(963)June 2011


Figure 3-19. View looking west from W. Pointe ParkwayFigure 3-20 shows the view looking east from W. Pointe Parkway at commercial development and presentlyundeveloped land along the I-<strong>90</strong> corridor. The landscape consists <strong>of</strong> disturbed ground and weedy herbaceousvegetation.Views from I-<strong>90</strong> and Centennial TrailFigure 3-20. View looking east from W. Pointe ParkwayThe views from I-<strong>90</strong> and the adjacent Centennial Trail looking at the project area are typical <strong>of</strong> views fromthe interstate that passes through a partially developed commercial strip adjacent to the freeway. Box-typestores are interspersed with commercial or industrial warehouses through this area. The terrain is mostly flatand covered with weedy herbaceous vegetation. The characteristic landscape has little capability to absorbnew structures because <strong>of</strong> the lack <strong>of</strong> relief in the existing topography and lack <strong>of</strong> trees and shrubs to screennew features. Two key observation points were selected to represent views from I-<strong>90</strong> and the Centennial Trail(Figure 3-21).I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-62Project No. A010(963)June 2011


Views <strong>of</strong> I-<strong>90</strong> and <strong>Beck</strong> <strong>Road</strong>The <strong>for</strong>eground views <strong>of</strong> I-<strong>90</strong> are typical <strong>of</strong> a four-lane, divided highway in the area (Figure 3-22). Thefreeway <strong>for</strong>ms a relatively straight line in the landscape, with cars and trucks visible as they travel the route.Similarly, the views <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> from the project area are typical <strong>of</strong> an undeveloped dirt road with littleassociated infrastructure (Figure 3-23).Figure 3-22. View from Centennial Trail, looking west toward I-<strong>90</strong>Figure 3-23. View from W. Pointe Parkway, looking north toward N. <strong>Beck</strong> <strong>Road</strong>I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-64Project No. A010(963)June 2011


3.13.2 <strong>Environmental</strong> ConsequencesNo-BuildNo interchange would be constructed under the No-Build Alternative. The existing configuration <strong>of</strong> I-<strong>90</strong>,N. <strong>Beck</strong> <strong>Road</strong> and the Centennial Trail would not change. The visual environment in the project area couldchange due to new development which is expected to continue under the No-Build Alternative.Proposed ActionDirect ImpactsConstruction <strong>of</strong> the proposed interchange and associated features would result in permanent visual changes inthe immediate area surrounding the interstate and N. <strong>Beck</strong> <strong>Road</strong>. Visual effects <strong>of</strong> the Proposed Action wouldresult from construction and use <strong>of</strong> the interchange and associated features. The main visual elements <strong>of</strong> theproposed project would include:• Introduction <strong>of</strong> new land<strong>for</strong>ms, including roadway, interchange embankments, and a stormwatercollection pond that would contrast with existing topography• Introduction <strong>of</strong> new structural elements, including the interchange bridge, traffic signals, right-<strong>of</strong>-wayfences, and traffic signs that would contrast with the existing characteristic landscape on the basis <strong>of</strong><strong>for</strong>m, line, color, and texture• Removal <strong>of</strong> vegetation• The addition <strong>of</strong> lighting at night (that presently does not exist), which would be most noticeable totravelers in the immediate vicinity <strong>of</strong> the project but may also appear as a glow to more distantviewersFigures 3-24 and 3-25 are renderings <strong>of</strong> the Proposed Action design and proposed Centennial Trailunderpass that show the expected visual changes as a result <strong>of</strong> interchange build-out in the project area. Theseviews show the <strong>for</strong>eground to middleground view <strong>for</strong> those traveling on the Centennial Trail. Views fromI-<strong>90</strong> would be very similar.During construction, temporary visual impacts would occur from equipment operating in the area andpotential dust from construction operations. Areas next to the interchange would likely be used <strong>for</strong> staging <strong>of</strong>materials, which would also add to temporary visual contrasts.Indirect ImpactsWith the likelihood <strong>of</strong> increased development, the area could see an increase in commercial construction.Views in the surrounding area would likely change to a denser mix <strong>of</strong> development following completion <strong>of</strong>the interchange.Cumulative ImpactsConstruction <strong>of</strong> the interchange would add to existing visual changes in the area from past activities,including land-clearing, development <strong>of</strong> commercial and industrial complexes, and construction <strong>of</strong> I-<strong>90</strong> androads in the area.MitigationMitigation measures to reduce visual impacts would include:• Areas disturbed by project construction activities would be landscaped or improved over existingvegetation characteristics.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>3-65Project No. A010(963)June 2011


Chapter 4: Comments and CoordinationStakeholders in the project area were invited to attend a public open house <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project on January 14, 2009. The open house provided in<strong>for</strong>mation on the interchange approvalprocess, alternatives evaluation, the surrounding roadways and future interchange features, and environmentalissues. The open house also provided an opportunity <strong>for</strong> public commentary. To further support stakeholderinvolvement in the project, the TAC was <strong>for</strong>med to provide technical assistance to the project team during theIJR process.Copies <strong>of</strong> meeting agendas, advertisements, and meeting summaries are available from ITD District 1 uponrequest.4.1 Public Open House4.1.1 Notification and ContactStakeholders, including the public, were contacted and notified <strong>of</strong> the public open house <strong>for</strong> the project. Forthe open house, emails, postcards, meeting notices, and newspaper advertisements were used to inviteattendees. Approximately 575 postcard notices were mailed. Stakeholders identified as key agencies, activelyparticipating individuals, businesses, and community members received a <strong>for</strong>mal email invitation be<strong>for</strong>e theopen house. Media involvement included a news release and brochure that was delivered to local businessesto set on their counters.4.1.2 Meeting SummaryThe Public open house was conducted to notify stakeholders and the public <strong>of</strong> project purpose and need, thealternatives considered, the surrounding roadways and future interchange features, and environmental issues.The open house was held on January 14, 2009 at the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> <strong>City</strong> Hall. A total <strong>of</strong> 53 peopleattended the open house. Attendees had the opportunity to visit project stations that provided in<strong>for</strong>mation on:• Interchange alternatives• Interchange and roadway features• Project process• The IJR• The NEPA ProcessDuring the meeting, technical experts were available to explain project specifics and to answer questions.Participants had the opportunity to complete comment sheets and provide input on the project. Participantswere encouraged to visit stations representing in<strong>for</strong>mation about the project and provide commentsafterwards. Eleven comment sheets were submitted during the open house and two <strong>for</strong>mal comment letterswere submitted after the open house by the close <strong>of</strong> the comment period. The majority <strong>of</strong> comments expressedgeneral concerns such as traffic function, business and neighborhood impacts, economics, and the projectschedule. Comments were compiled and summarized by the project team.4.2 Technical Advisory Committee MeetingsThe TAC was created to provide support and insight to the project team during the IJR process (see Section1.3). The committee consisted <strong>of</strong> representatives from the following agencies:• FHWA• ITD• WSDOT• SRTC/KMPOI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>4-1Project No. A010(963)June 2011


<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>PFHDSpokane CountyA description <strong>of</strong> TAC input into the development <strong>of</strong> the IJR is outlined in the Alternatives Development andScreening Memorandums provided in Appendices H-K <strong>of</strong> the IJR (HDR 2010). All TAC meetings took placeat ITD <strong>of</strong>fices in Coeur D’ Alene, Idaho except <strong>for</strong> two meetings in January 2008 that were teleconferencemeetings. TAC meetings were held on: September 7, 2007 November 13, 2007 January 11, 2008 January 23, 2008 May 19, 20 & 21, 2008 June 25 & 26, 2008 October 1, 2008Objectives during the meetings included:Compiling existing in<strong>for</strong>mation and knowledge about the projectIdentification <strong>of</strong> the study areaInput into design and evaluation criteriaIdentification <strong>of</strong> alternatives evaluation criteriaIdentification <strong>of</strong> alternativesInitial alternatives screeningProject scheduling4.3 Agency Consultation/CoordinationAn <strong>Environmental</strong> Scan was conducted <strong>for</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project in October 2007, andupdated in April 2010 and January 2011. The purpose <strong>of</strong> an <strong>Environmental</strong> Scan was to provide preliminaryin<strong>for</strong>mation on environmental resources in the project area. The scan provided support <strong>for</strong> evaluatingalternatives as part <strong>of</strong> the IJR. The <strong>Environmental</strong> Scan process included letter correspondence with agencyrepresentatives in October 2007. Letters were sent to the following agencies:FHWAUSACEUSFWSUSEPANRCSWSDOTITDIdaho Department <strong>of</strong> Fish and Game (IDFG)IDEQIdaho Department <strong>of</strong> LandsIDWRSHPOKootenai CountySpokane County<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>PFHDSRTCResponses were received from IDEQ, <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>, USACE, and WSDOT. Copies <strong>of</strong> thiscorrespondence are included in Appendix D.As part <strong>of</strong> the project scoping process <strong>for</strong> the EA, letters were sent out to resource and regulatory agencies inJanuary 2011, as well as stakeholders and Indian tribes to re-introduce the project and to solicit comments onissues and concerns within and adjacent to the project area. Approximately 60 scoping letters were sent out tovarious federal, state, and local agencies as well as stakeholders and property owners in the project area. Tenfederal agencies, 24 state agencies and 26 local agencies, property owners and stakeholders were contacted.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong> 4-2Project No. A010(963)June 2011


The following agencies responded in writing to the January 2011 scoping letter:• <strong>Post</strong> <strong>Falls</strong> Urban Renewal Agency• <strong>Post</strong> <strong>Falls</strong> School District• Kootenai County Fire and Rescue• PFHD• WSDOT• Hanson Industries• Greyhound Park and Event Center• Jacklin Land Company• USEPA• USACEI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>4-3Project No. A010(963)June 2011


Table 4-1 summarizes the comments received from the agencies as <strong>of</strong> March 31, 2011. Responses to scopingcomments are presented in Appendix D. All agencies will be notified <strong>of</strong> the availability <strong>of</strong> the EA once it isfinalized. Each <strong>of</strong> the agencies identified in Chapter 5 will receive copies <strong>of</strong> this EA <strong>for</strong> review and comment.Table 4-1. Comments Received During Scoping PeriodRespondent Date Comment<strong>Post</strong> <strong>Falls</strong> UrbanRenewal AgencyKootenai County Fire &Rescue<strong>Post</strong> <strong>Falls</strong> SchoolDistrict2/01/20112/04/20112/11/2011PFHD 2/16/2011WSDOT 2/17/2011Hanson Industries 2/21/2011Greyhound Park andEvent Center2/21/2011Jacklin Land Company 3/28/2011USACE 3/30/2011USACE 5/17/11USEPA 3/31/2011SHPO 5/13/11Coeur D’Alene Tribe 5/13/11Provided comments on traffic and access, the Centennial Trail,potable water, and surface water management.They are the emergency service provider in the project area.They feel that the <strong>Beck</strong> <strong>Road</strong> project will enhance access into thecommercial/industrial area.The <strong>Post</strong> <strong>Falls</strong> School District supports the interchange plan <strong>for</strong>the area.Expressed concerns with connectivity <strong>of</strong> W. Riverbend Avenueboth during and after construction, improvements to N. <strong>Beck</strong><strong>Road</strong> north <strong>of</strong> Seltice Way, Centennial Trail construction,stormwater treatment, and improvements to the N. <strong>Beck</strong> <strong>Road</strong>and W. Seltice Way intersection.Expressed concerns with the projected traffic operation (LOS) <strong>of</strong>the I-<strong>90</strong> State Line <strong>Road</strong> Interchange. Additional in<strong>for</strong>mation onthe impacts and the proposed mitigation <strong>for</strong> the <strong>Beck</strong> <strong>Road</strong>interchange were requested.Expressed concerns with project stormwater treatment, W.Riverbend Avenue improvements and access west <strong>of</strong> theinterchange, and interchange signalization plans.Expressed interest in identifying a right-<strong>of</strong>-way agreement, andclarifying property access and signage impacts.Expressed interest in reaching agreement on issues such asright-<strong>of</strong>-way compensation, easements, liability, utilities, impactsto business, and local connectivity.Identified the potential <strong>for</strong> wetlands in the project area andrequested a wetland and waters <strong>of</strong> the US determination <strong>for</strong> theproject.Verified that the project site does not contain wetlands or waters<strong>of</strong> the U.S.Recommended in<strong>for</strong>mation to be analyzed in the EA including airquality/air toxics and diesel particulates, construction mitigation,stimulated travel and growth, aquatic resources and ecologicalconnectivity.Provided concurrence with the determination <strong>of</strong> no historicproperties affected by the project.Confirmed review <strong>of</strong> the cultural resources report and requestednotification <strong>of</strong> the construction schedule <strong>of</strong> the project andrequested the opportunity to inspect soils during construction.Offered a free one hour cultural resource awareness training tothe implementation contractor.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>4-4Project No. A010(963)June 2011


Chapter 5: Distribution ListNumber <strong>of</strong> Copies* Receiving Organization Organization’s Address1 Idaho State Historical Society1 Idaho Department <strong>of</strong> Fish & Game2 Idaho Department <strong>of</strong> Water Resources2 Idaho Department <strong>of</strong> <strong>Environmental</strong> Quality22U.S. Fish and Wildlife ServiceSnake River Basin Office<strong>Environmental</strong> Protection AgencyIdaho Operations Office2 U.S. Army Corps <strong>of</strong> Engineers3 <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>1 Kootenai County3 Idaho State Library*Some copies may be provided electronically.Travis PitkinIdaho State Historical Society210 Main St.Boise, Idaho 83702Chip CorsiIdaho Fish & Game DepartmentPanhandle Region2885 W. Kathleen Ave.Coeur D Alene, Idaho 83815Mary McGown & Aaron GolartDepartment <strong>of</strong> Water Resources322 E Front St.Boise, Idaho 83705Toni Hardesty and Dan Redline1410 North HiltonBoise, Idaho 83706-1255Mr. Mark Robertson & Mr. Brian KellyU.S. Fish and Wildlife ServiceSnake River Basin Office1387 Vinnell Way, Room 368Boise, Idaho 83709Mr. John Olson & Mr. Jim Werntz<strong>Environmental</strong> Protection AgencyIdaho Operations Office1435 N. OrchardBoise, Idaho 83706Ms. Nicholle Braspennickx & Leroy PhillipsU.S. Army Corps <strong>of</strong> Engineers10095 W. EmeraldBoise, Idaho 83704Eric Keck, Bill Melvin, Jon Manley<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>408 N Spokane St.<strong>Post</strong> <strong>Falls</strong>, Idaho 83854Scott ClarkKootenai County Planning451 Government WayCoeur d Alene, Idaho 83814325 W. State StreetP.O. Box 83720Boise, Idaho 83702I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>5-1Project No. A010(963)June 2011


Chapter 6: List <strong>of</strong> Contributors and PreparersAnalysis TeamIdaho Transportation DepartmentJason Minzghor – Project Development EngineerMike Porcelli – Traffic EngineerMichael Hartz – <strong>Environmental</strong> PlannerGreg Brands – Staff EngineerVictoria Jewell Guerra – Senior <strong>Environmental</strong> PlannerMarc Munch – ArcheologistFederal Highway AdministrationJohn Perry – Field Operations EngineerBrent Inghram – Field Operations EngineerDean Moberg – Area EngineerKyle Holman – Operations EngineerHDR Engineering, Inc.Karen Doherty – Project ManagerMichael Murray – <strong>Environmental</strong> Project Manager, <strong>Environmental</strong> <strong>Assessment</strong> Contributing AuthorCorrinna Hugaboom – <strong>Environmental</strong> <strong>Assessment</strong> Contributing AuthorJed Glavin – <strong>Environmental</strong> <strong>Assessment</strong> Contributing AuthorDiane Holloran – GISRick Lovel – 3D VisualizationCheryl Zorn – Project EngineerChristine Whittaker – Visual <strong>Assessment</strong>Craig Milliken – NoiseJinxiang Ren – TrafficTAGBarbara Perry Bauer – HistorianI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>6-1Project No. A010(963)June 2011


Chapter 7: References<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>. <strong>City</strong> Code. Ordinance Title 8.04.020: Construction Activity Prohibited During CertainHours. Available at: http://www.sterlingcodifiers.com/codebook/index.php?book_id=350. 1992.<strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>. “<strong>Post</strong> <strong>Falls</strong> Comprehensive Plan.” Text only version.http://postfallsidaho.org/pzdept/Comp%20Plan.pdf. 2003.Federal Highway Administration. “Draft <strong>Environmental</strong> Impact Statement; I-<strong>90</strong> <strong>Post</strong> <strong>Falls</strong> AccessImprovements Project.” FHWA-ID-EIS-08-01-D. ITD No. IM-<strong>90</strong>-1(220)6, 08920. August 2008.Federal Highway Administration. “Interim Guidance Update on Mobile Source Air Toxic Analysis inNEPA.” Memorandum from April Marchese, Director, Office <strong>of</strong> Natural and Human Environment toDivision Administrators, Federal Lands Highway Division, Engineers. September 30, 2009.Federal Highway Administration. “Physical Techniques to Reduce Noise Impacts.”http://www.fhwa.dot.gov/environment/audible/al4.htm. Accessed March 24, 2011.Federal Highway Administration. “Visual Impact <strong>Assessment</strong> <strong>for</strong> Highway Projects.” FHWA Publication No.HI-88-054, 1983.HDR Engineering, Inc. “A Five-Minute Look at Section 4(f).” Published in HDR Intranet. August 31, 2006.HDR Engineering, Inc. “Draft I-<strong>90</strong> Interchange Justification Report.” October, 2010.HDR Engineering, Inc. “I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange Noise Technical <strong>Assessment</strong> Report.” March, 2011a.HDR Engineering, Inc. “I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange Project <strong>Environmental</strong> Scan.” January, 2011b.Hortness, J.E., and J.J. Covert. “Streamflow Trends in the Spokane River and Tributaries, SpokaneValley/Rathdrum Prairie, Idaho and Washington”. U.S. Department <strong>of</strong> the Interior, U.S. GeologicalSurvey, Reston, Virginia, 17 p. 2005.Idaho Department <strong>of</strong> <strong>Environmental</strong> Quality. Database query: http://www.deq.idaho.gov/Applications/WDI/.Accessed September 2007 and December 2010.Idaho Department <strong>of</strong> <strong>Environmental</strong> Quality. “Groundwater in Idaho: Rathdrum Prairie Aquifer.”http://www.deq.idaho.gov/water/prog_issues/ground_water/rathdrum_prairie_aquifer/index.cfm.Accessed January 31, 2011.Idaho Department <strong>of</strong> <strong>Environmental</strong> Quality. “Surface Water Quality: Subbasin <strong>Assessment</strong>s, TotalMaximum Daily Loads (TMDLs), and Implementation Plans.”http://www.deq.idaho.gov/water/data_reports/surface_water/tmdls/sba_tmdl_master_list.cfm. AccessedDecember 2010.Idaho Department <strong>of</strong> <strong>Environmental</strong> Quality. “Working Principles and Policies <strong>for</strong> the2008 Integrated (303[d]/305[b]) Report.” May 22, 2009.Idaho Department <strong>of</strong> Fish and Game: Idaho Conservation Data Center. “Appendix F: Species Accounts andDistribution Maps <strong>for</strong> Idaho Species <strong>of</strong> Greatest Conservation Need.” 2005.http://fishandgame.idaho.gov/apps/cwcs/index.cfm. Accessed December 2010.Idaho Department <strong>of</strong> Fish and Game: Idaho Conservation Data Center. “Idaho's Special Status Plants.”http://fishandgame.idaho.gov/cms/tech/CDC/plants/. Accessed October 2007.Idaho Department <strong>of</strong> Water Resources. 2007. Listing <strong>of</strong> Driller Reports, T50N, R5W, Sections 6 and 7 andT50N, R6W, Sections 1 and 12. October 2007.Idaho Museum <strong>of</strong> Natural History. Digital Atlas <strong>of</strong> Idaho. Geology <strong>of</strong> Kootenai County.http://imnh.isu.edu/digitalatlas/counties/geomaps/geomap.htm. Compiled by Idaho Geological Survey,September 2002.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>7-1Project No. A010(963)June 2011


Idaho Transportation Department. “Air Screening Policy.” December 2007.Idaho Transportation Department. “Cultural Resources Survey Report, I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange.” ProjectNo. A010(963), Key No. 10963. October 2008.Idaho Transportation Department. “<strong>Environmental</strong> Process Manual.”http://www.itd.idaho.gov/manuals/Online_Manuals/<strong>Environmental</strong>/<strong>Environmental</strong>.htm. Accessed July2007 and December 2010. January 2011.Idaho Transportation Department. Letter from Mike Porcelli, District 1. “I-<strong>90</strong> Level <strong>of</strong> Service Justification.”June 3, 2010.Idaho Transportation Department. Traffic Noise Policy. May 2011.Kootenai County Noxious Weed Control. Noxious Weed List. http://www.kcweeds.com. Accessed December2010.Kootenai Metropolitan Planning Organization. “Existing Conditions & Needs <strong>Assessment</strong> Report <strong>for</strong> PublicTransportation in the Kootenai Metropolitan Area.” July 7, 2004.Kootenai Metropolitan Planning Organization. “Kootenai County Coordinated Public Transit, HumanServices Transportation Plan.” June 7, 2007.Kootenai Metropolitan Planning Organization. Letter from Glenn Miles recognizing regional significance <strong>of</strong>North <strong>Beck</strong> <strong>Road</strong>. May 24, 2010.Kootenai Metropolitan Planning Organization. “Metropolitan Transportation Plan 2007-2030.” October 4,2007.Kootenai Metropolitan Planning Organization. “Metropolitan Transportation Plan 2010-2035.” December 2,2010.MacInnis, J.D., Jr., Lackaff, B.B., Boese, R.M., Stevens, G., King, S., Lindsay, R.C. “TheSpokane Valley-Rathdrum Prairie Aquifer Atlas 2009.” Spokane, Washington, <strong>City</strong> <strong>of</strong> Spokane. 30p.2000 and 2009.MacInnis, J.D., B.B. Lackaff, J.P. Buchanan, R.M. Boese, J. McHugh, G. Harvey, R. Higdem, and G.Stevens. 2004. The Spokane Valley-Rathdrum Prairie Aquifer Atlas. Spokane Aquifer Joint Board.Melvin, Bill. Telephone Interview with Miguel Gaddi <strong>of</strong> HDR. <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> <strong>City</strong> Engineer. January2011.Melvin, Bill. Telephone Record with Jed Glavin <strong>of</strong> HDR: I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange Project Noise AnalysisBuilding Permits Conversation. April 5, 2011.Montana Fish Wildlife and Parks. “Montana’s Threatened and Endangered Species.”http://fwp.mt.gov/wildthings/tande/default.html. Accessed August 29, 2006.National Marine Fisheries Service. “Endangered Species Act Status <strong>of</strong> West Coast Salmon & Steelhead.”http://www.nwr.noaa.gov/ESA-Salmon-Listings/upload/snapshot-7-09.pdf. July 1, 2009.National Park Service. “National Register Criteria <strong>for</strong> Evaluation.”http://www.cr.nps.gov/NR/publications/bulletins/nrb15/nrb15_2.htm. Accessed October 11, 2006.National Park Service. “Wild and Scenic Rivers by State: Idaho and Oregon.”http://www.nps.gov/rivers/wildriverslist.html#id. Accessed September 2007.Natural Resources Conservation Service. “Prime and Other Important Farmland Definitions.” Updated June13, 2008. http://www.pr.nrcs.usda.gov/technical/soil_survey/primefarmdefs.htm. Accessed March 24,2011Natural Resources Conservation Service. “Soil Data Mart, Prime Farmland Reports <strong>for</strong> Kootenai and SpokaneCounties.” October 2007.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>7-2Project No. A010(963)June 2011


Natural Resources Conservation Service. Web Soil Survey 2.0. National Cooperative Soil Survey (NCSS).September 2007.National Response Center. Data query. http://www.nrc.uscg.mil/foiatxt.htm. Accessed October 2007.Schmidt. Angie. Email from IDFG, IDCDC to HDR Engineering. “post falls interchange data request.”January 2011.Spokane County. Atlas. “Geology.” http://www.spokanecounty.org/wqmp/atlas/page%2011-screen.pdf.Accessed January 31, 2011.TAG Historical Research & Consulting. “Cultural Resource Survey <strong>for</strong> the <strong>Beck</strong> <strong>Road</strong> Interchange Project.”February 2011.U.S <strong>Environmental</strong> Protection Agency. Envir<strong>of</strong>acts database query.http://oaspub.epa.gov/enviro/ef_home2.waste. Accessed September 2007 and December 2010.U.S <strong>Environmental</strong> Protection Agency. Sole Source Aquifer Program,http://yosemite.epa.gov/r10/water.nsf/Sole+Source+Aquifers/SSA, viewed January 2010.U.S <strong>Environmental</strong> Protection Agency. “Surf Your Watershed.”http://cfpub.epa.gov/surf/state.cfm?statepostal=ID. Accessed September 2007.U.S. Fish and Wildlife Service. “Candidate Species; Section 4 <strong>of</strong> the Endangered Species Act”, a fact sheetfrom the Endangered Species Act Document Library. http://www.fws.gov/endangered/esalibrary/pdf/candidate_species.pdfAccessed May 2011.U.S. Fish and Wildlife Service. Idaho Fish and Wildlife Office “Endangered, Threatened, Proposed, andCandidate Species With Associated Proposed and Critical Habitats.”http://www.fws.gov/idaho/species/IdahoSpeciesList.pdf. Updated May 5, 2011.U.S. Fish and Wildlife Service. In<strong>for</strong>mation page on Water Howellia.http://ecos.fws.gov/species_pr<strong>of</strong>ile/servlet/gov.doi.species_pr<strong>of</strong>ile.servlets.SpeciesPr<strong>of</strong>ile?spcode=Q2RM. Accessed September 2006.U.S. Fish and Wildlife Service. Telephone conversation between Bob Kibler and Corrie Hugaboom (HDR).February 7, 2011.Washington Department <strong>of</strong> Ecology. Fact Sheet. “Spokane River Metals, CommentsSought on Construction Documents <strong>for</strong> Island Complex and Murray <strong>Road</strong> Recreation Areas.” June2007.Washington State Department <strong>of</strong> Transportation. “2011-2013 Capital Improvement and PreservationProgram; Project Detail” by Paula J. Hammond, P.E. September 2010.I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>7-3Project No. A010(963)June 2011


Appendix A. ITD FormsI-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>A-1Project No. A010(963)June 2011


ITD 0654 (Rev. 1-08)<strong>Environmental</strong> EvaluationKey Number Project Number Program Project Name Date10963 A010(963) T071610 <strong>Beck</strong> Rd Interchange, Kootenai County May 2011District <strong>City</strong>/County Route Number Beginning Milepost Ending Milepost Program Year1 <strong>Post</strong> <strong>Falls</strong>/Kootenai I-<strong>90</strong> 0.5 1.5 2012Acres <strong>of</strong> New Public R/W Acres <strong>of</strong> New Private R/W (Discuss the existing use <strong>of</strong> R/W to be acquired, plus adjacent land use, zoning,1 14development plans, etc. on attached <strong>Environmental</strong> Summary Sheet)Tribal ImpactPublic Interest Expected?Cultural Archeological Reservation None Yes NoAir QualityAttainment Area Non-Attainment Area CO PM Exempt Project Yes NoType One Project (i.e., New Location, Substantial Alignment Change, Addition <strong>of</strong> a Through-Traffic Lane) Yes NoConstruction Impacts Requiring Special Provisions (Enter Details on Reverse Side ) Yes NoProgram YearDesign YearADT DHV % Trucks <strong>Post</strong>ed Speed ADT DHV % Trucks <strong>Post</strong>ed SpeedDistance <strong>of</strong> Nearest Noise Receptor to CenterlineExisting 235' (to I-<strong>90</strong>) Proposed 150' (to proposed I-<strong>90</strong> <strong>of</strong>f-ramp)Project Purpose and BenefitsDouble mark (xx) only the item that best describes the Primary Reason <strong>for</strong> Proposing this ProjectSingle mark (x) all Other Relevant Itemsxx Maintain/Improve User Operating Conditions x Enhance Accessibility <strong>for</strong> the Disabled/Safetyx Maintain/Improve Traffic Flow x Enhance Pedestrian Safety and/or Capacityx Time Savings x Enhance Bicycle Safety and/or Capacityx Increase Capacity Traffic Composition Enhancement (e.g., Truck Route, HOV Lane, Climbing Lane)x Reduce Congestion Visual/Cultural Enhancement (e.g., Landscaping, Historic Preservation)x Reduce Hazard(s) <strong>Environmental</strong> Enhancement (e.g., Air Quality, Noise Attenuation, Water Quality)Reduce Highway User Operating CostsOther, List (e.g., Driver Convenience and Com<strong>for</strong>t regarding Rest Area Projects)Economic Prudence (e.g., Repair Less Expensive than Replacement, B/C Ratio)Check Any <strong>of</strong> the Following That Require Avoidance, Minimization, or Discussion (If Yes, describe in the <strong>Environmental</strong>Document or CE)Yes No Yes No1. Noise Criteria Impacts* 17. Threatened/Endangered Species*2. Change in Access or Access Control Listed Proposed3. Change in Travel Patterns 18. Air Quality Impacts4. Neighborhood or Service Impacts 19. Inconsistent With Air Quality Plan5. Economic Disruption SIP TIP6. Inconsistent W/Local or State Planning 20. Stream Alteration/Encroachment**7. Minorities, Low Income Populations IWDR F&G COE (404)8. Displacements* 21. Flood Plain Encroachment*9. Section 4(f) Lands-DOT Act 1966* Longitudinal Traverse(i.e., Public Parks/Rec Areas/Trails,Wildlife/Waterfowl Refuges, Wild orScenic Rivers, Historic Sites/Bridges,Archaeological ResourcesPage 1 <strong>of</strong> 222. Regulatory FloodwayPE Cert. & FEMA Approval23. Navigable Waters**Revision10. LWCF Recreation Areas/6(f) Lands* CG (Sec 9) COE (Sec 10) Dept. Lands11. Section 106-Nat. Hist. Preserv. Act* 24. Wetlands*12. FAA Airspace Intrusion** Jurisdictional** (404) Non-Jurisdictional13. Visual Impacts 25. Sole Source Aquifer14. Prime Farmland*, Parcel Splits Exempt Project Non-Exempt**15. Known/Suspected "Hazmat" Risks 26. Water Quality, Run<strong>of</strong>f Impacts16. Wildlife/Fish Resources/Habitat** 27. NPDES-General Permit(If no, complete sediment-erosion control plan)*If yes to these items, supplemental reports or documentation are required (e.g., Relocation Report; Wetlands Determination/Finding; Fish andWildlife Species List Update; SCS Form AD-1006, Biological <strong>Assessment</strong>, etc.)**If yes to these items, a letter <strong>of</strong> input is required from the appropriate agency.


Appendix B. 4(f) De Minimis EvaluationI-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>B-1Project No. A010(963)June 2011


SECTION 4(F) DE MINIMIS IMPACT FINDINGI-<strong>90</strong> BECK ROAD INTERCHANGE PROJECTProject No. A010(963)SECTION 4(f) AND DE MINIMIS: 23 USC 138 states: “[T]he Secretary shall not approve any programor project (other than any project <strong>for</strong> a park road or parkway under Section 204 <strong>of</strong> this Title) which requiresthe use <strong>of</strong> any publicly owned land from a public park, recreation area, or wildlife and waterfowl refuge <strong>of</strong>national, state, or local significance as determined by the Federal, State <strong>of</strong> local <strong>of</strong>ficials having jurisdictionthere<strong>of</strong>, or any land from an historic site <strong>of</strong> national, state, or local significance as so determined by such<strong>of</strong>ficials unless (1) there is no feasible and prudent alternative to the use <strong>of</strong> such land, and (2) such programincludes all possible planning to minimize harm to such park, recreational area, wildlife and waterfowlrefuge, or historic site resulting from such use.”The de minimis impact criteria and associated determination requirements specified in Section 6009(a) <strong>of</strong>SAFETEA-LU are different <strong>for</strong> historic sites than <strong>for</strong> parks, recreation areas, and wildlife and waterfowlrefuges. De minimis impacts related to historic sites are defined as the determination <strong>of</strong> either “no adverseeffect” or “no historic properties affected” in compliance with Section 106 <strong>of</strong> the National HistoricPreservation Act (NHPA). De minimis impacts on publicly owned parks, recreation areas, and wildlife andwaterfowl refuges are defined as those that do not “adversely affect the activities, features and attributes” <strong>of</strong>the Section 4(f) resource.RESOURCE: A Section 4(f) resource has been identified within the project area. This resource is theNorth Idaho Centennial Trail. The trail is a non-motorized, multi-use recreational trail, which meanders <strong>for</strong>24 miles from the state line at the Idaho/Washington border to Higgens Point. The trail is said to attractmany recreationists, including in the late fall and early winter <strong>for</strong> those hoping to view bald eagles as theymigrate south. The portion <strong>of</strong> the trail in the project area is paved and follows the south side <strong>of</strong> Interstate <strong>90</strong>(I-<strong>90</strong>). The I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project would construct a new interchange on I-<strong>90</strong> approximatelyone mile east <strong>of</strong> the Idaho/Washington border, providing access to businesses on the north and south sides<strong>of</strong> the highway. The interchange project would include pedestrian and bicycle facilities, providing enhancedaccess to and from the Centennial Trail. Alignment <strong>of</strong> the existing trail in the area <strong>of</strong> the interchange wouldchange slightly, however, design <strong>of</strong> the project will ensure that overall continuity <strong>of</strong> the trail would not beimpacted. The trail would be tunneled under the proposed bridge abutments, and no grade crossings wouldbe required. The activities, features, and attributes <strong>of</strong> the current trail system that qualify this resource <strong>for</strong>protection under Section 4(f) would be restored once construction is complete. However, while the trail willremain open during construction, some disruption <strong>of</strong> trail access such as detours and flaggers would occur.Every attempt would be made to minimize this disruption. Kootenai County, which has jurisdiction over theCentennial Trail in the project area, has concurred in writing that the proposed project will not adverselyaffect the activities, features or attributes <strong>of</strong> the trail that qualify it as a 4(f) resource. The County <strong>of</strong>ficialswere notified that based on that concurrence, FHWA intends to make a finding <strong>of</strong> de minimis impact onthese parks.IMPACTS TO THE NORTH IDAHO CENTENNIAL TRAIL: Temporary impacts resulting fromconstruction <strong>of</strong> the interchange project include disrupted trail access, noise from construction equipment,and visual impacts from construction equipment and materials. Following construction, continuity <strong>of</strong> thetrail would not be impacted by operation <strong>of</strong> the project. The trail would be tunneled under the proposedbridge abutments, and no grade crossings would be required. Access to the trail from north <strong>of</strong> the highwaywould be enhanced by pedestrian and bicycle facilities at the new interchange. No park facilities will bedisplaced by the project. The proposed interchange is consistent with community planning documents andis considered an enhancement to the trail.


FINDING FOR NORTH IDAHO CENTENNIAL TRAIL: For the reasons noted above, FHWA hasdetermined that the project will have a de minimus impact to the Section 4(f) resource, the North IdahoCentennial Trail.


Appendix C. Supporting DataI-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>C-1Project No. A010(963)June 2011


United States Department <strong>of</strong> the InteriorIDAHO FISH AND WILDLIFE OFFICE1387 S. Vinnell Way, Room 368Boise, Idaho 83709Telephone (208) 378-5243http://www.fws.gov/idahoU.S. Fish and Wildlife Service - Idaho Fish and Wildlife OfficeEndangered, Threatened, Proposed, and Candidate SpeciesWith Associated Proposed and Critical Habitats(Updated May 5, 2011)Federal Agency Assistance and ConsultationSection 7(c) <strong>of</strong> the Endangered Species Act directs the U.S. Fish and Wildlife Service to consultwith federal agencies on any proposed actions (direct or indirect) on federal lands that maypotentially affect listed, proposed or candidate species or their habitat.It is the responsibility <strong>of</strong> federal "action agencies" (or their designated representatives) to obtainan <strong>of</strong>ficial table ("Species List") <strong>of</strong> listed, proposed and candidate species that may be presentwhere the proposed activity is to occur. If the project potentially affects the species or its habitat,the federal agency is required to consult with the Service.To assist agencies with this task, the Service prepares and regularly updates Species Lists bycounty. The lists are valid <strong>for</strong> up to 180 days. Species List areas may be larger than the footprint<strong>of</strong> the proposed activity. Status changes, such as listings, delistings or critical habitatdesignations, will be updated immediately by the Service so the action agencywill always have access to the most current in<strong>for</strong>mation <strong>for</strong> project planning.Obtaining Species Lists <strong>for</strong> Proposed Federal ActionsThe Fish and Wildlife Service is developing a web-based system that will allow Action Agenciesto generate project-specific Species Lists. We will provide instructions when thenew web-based species list system is launched.Until this system is operational, please use the attached table) <strong>for</strong> project-specific Species Lists.These county lists will assist with proposed activity consultation. Please print and retain a copy <strong>of</strong>this list with your project records. Because Species List in<strong>for</strong>mation may change, frequent checks<strong>of</strong> our website are advised to obtain a most current list (www.fws.gov/idaho/agencies).Be<strong>for</strong>e initiating an action, a federal action agency (or their designated representative) that isplanning an activity must obtain a list <strong>of</strong> species that may be present in the proposed project area.(Please note that the area <strong>for</strong> which this list is being generated may encompass a larger areathan the footprint <strong>of</strong> the construction.) The area includes any effects <strong>of</strong> the action(direct and indirect) that may potentially affect species or habitats.This species/county table meets the Fish and Wildlife Services' regulatory obligation underSection 7(c) <strong>of</strong> the Endangered Species Act (Act) to provide federal agencieswith a species list. Please print and retain a copy <strong>of</strong> this tableand this in<strong>for</strong>mation sheet with your project records.


Use this in<strong>for</strong>mation to verify the habitats and/or species present in the areaaffected by the projects you are developing. Any project-specific species list generated from thistable is valid <strong>for</strong> up to 180 days. Because the in<strong>for</strong>mation in this tablemay change without notice, you are advised to visit our internet page(www.fws.gov/idaho/agencies) frequently to ensure that your project recordscontain the most current species list. Should your project plans expand or change to includeadditional counties, you will need to download an updated list.When you submit a request <strong>for</strong> Section 7 Consultation, please include a copy <strong>of</strong>your downloaded species list marked with the date that it was downloaded.This will document your compliance with 50 CFR 402.12(c).If the area affected by the proposed project extends beyond the boundary <strong>of</strong> the State <strong>of</strong> Idaho,please contact the appropriate U.S. Fish and Wildlife Service <strong>of</strong>fice listed below toobtain a species list <strong>for</strong> their area <strong>of</strong> jurisdiction.U.S. Fish and Wildlife Service ContactsIdaho – Bob Kibler, bob_kibler@fws.gov (208) 378-5255Montana – Montana Ecological Services Field Office (406) 449-5225Nevada – Nevada Fish & Wildlife Office (775) 861-6300Oregon – La Grande Field Office (541) 962-8584Utah – Utah Ecological Service Field Office (801) 975-3330Washington – Spokane Field Office (509) 891-6839Wyoming – Wyoming Ecological Services Field Office (307) 772-2374Candidate Species ConservationThough candidate species have no protection under the Act, they are includedin the table <strong>for</strong> early planning consideration. Candidate species could be proposed or listed duringthe project planning period. The Service advises you to evaluate potential effects to candidatespecies that may occur in the project area. Should the species be listed, this may expedite section7 consultation under the Act.NOAA Fisheries SpeciesListed or proposed species that are under National Marine Fisheries Service’s (NOAA Fisheries)jurisdiction do NOT appear on the Service's Species Lists.In Idaho, please contact NOAA Fisheries at (208) 378-5696 or visit NOAA Fisheries' webpage(http://www.nwr.noaa.gov/Species-Lists.cfm) <strong>for</strong> consultation in<strong>for</strong>mation.2


Listed, Proposed, and Candidate Species Designated and Proposed Critical Habitat in Idaho (Last Updated 05/05/2011)Page 1 <strong>of</strong> 5GroupingCommonNameScientificNameAmphibianColumbia spotted frog-Great Basin populationGreater Sage-GrouseYellow-billed cuckooRana luteiventris Centrocercus urophasiunus Coccyzus americanusBirdStatus [C] [C] [C]Ada x xAdamsxBannock x xBear LakexBenewahBingham x xBlaine x xBoisexBonnerBonneville x xBoundaryButtexCamasxCanyonxCaribouxCassia x xClark x xClearwaterCuster x xElmore x xFranklinxFremont x xGemxGoodingxIdahoxJefferson x xJeromexKootenaixLatahxLemhi x xLewisxLincolnxMadison x xMinidoka x xNez PerceOneidaxOwyhee x x xPayettexPowerxShoshoneTetonTwin <strong>Falls</strong> x x xValleyWashingtonx[C] Candidate[P] Proposed[T] Threatened[E] Endangered[CH] Designated Critical Habitat[XN] Experimental Nonessential


Listed, Proposed, and Candidate Species Designated and Proposed Critical Habitat in Idaho (Last Updated 05/05/2011)Page 2 <strong>of</strong> 5GroupingCommonNameScientificNameCanada lynxLynx canadensisMammalGrizzly bear Northern Idahoground squirrelUrsus arctoshorribilisSpermophilusbrunneus brunneusSelkirk Mountain caribouRangifer tarandus caribouStatusAdaAdamsBannockBear LakeBenewahBinghamBlaineBoiseBonnerBonnevilleBoundaryButteCamasCanyonCaribouCassiaClarkClearwaterCusterElmoreFranklinFremontGemGoodingIdahoJeffersonJeromeKootenaiLatahLemhiLewisLincolnMadisonMinidokaNez PerceOneidaOwyheePayettePowerShoshoneTetonTwin <strong>Falls</strong>ValleyWashington[T] [CH] [T] [T] [E]xxxxxx x xxxx x x xxxxxxxxxxxxxxxxxxxxxxxxxx[C] Candidate[P] Proposed[T] Threatened[E] Endangered[CH] Designated Critical Habitat[XN] Experimental Nonessential


Listed, Proposed, and Candidate Species Designated and Proposed Critical Habitat in Idaho (Last Updated 05/05/2011)Page 3 <strong>of</strong> 5GroupingCommonNameScientificNameStatusAdaAdamsBannockBear LakeBenewahBinghamBlaineBoiseBonnerBonnevilleBoundaryButteCamasCanyonCaribouCassiaClarkClearwaterCusterElmoreFranklinFremontGemGoodingIdahoJeffersonJeromeKootenaiLatahLemhiLewisLincolnMadisonMinidokaNez PerceOneidaOwyheePayettePowerShoshoneTetonTwin <strong>Falls</strong>ValleyWashingtonMammalSouthern Idaho ground squirrelSpermophilus brunneus enemicus[C]xxxxWolverineGulo gulo[C]xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx[C] Candidate[P] Proposed[T] Threatened[E] Endangered[CH] Designated Critical Habitat[XN] Experimental Nonessential


Listed, Proposed, and Candidate Species Designated and Proposed Critical Habitat in Idaho (Last Updated 05/05/2011)Page 4 <strong>of</strong> 5GroupingCommonNameScientificNameBull troutSalvelinusconfluentusFishKootenai River whitesturgeonAcipenser transmontanusBanburySpringsLanx sp .Bliss RapidssnailTalorconchaserpenticolaMolluskBruneau hotspringsnailPyrgolopsisbruneauensisSnake River physasnailHaitia (Physa)natriciniaStatusAdaAdamsBannockBear LakeBenewahBinghamBlaineBoiseBonnerBonnevilleBoundaryButteCamasCanyonCaribouCassiaClarkClearwaterCusterElmoreFranklinFremontGemGoodingIdahoJeffersonJeromeKootenaiLatahLemhiLewisLincolnMadisonMinidokaNez PerceOneidaOwyheePayettePowerShoshoneTetonTwin <strong>Falls</strong>ValleyWashington[T] [CH] [E] [CH] [E] [T] [E] [E]xxx xxxxxxxxxx x x xx xx xx xx xx x x xxxxxxxxxxxxxx x xx x x xxxxxx x xx xx x xxxxxx[C] Candidate[P] Proposed[T] Threatened[E] Endangered[CH] Designated Critical Habitat[XN] Experimental Nonessential


Listed, Proposed, and Candidate Species Designated and Proposed Critical Habitat in Idaho (Last Updated 05/05/2011)Page 5 <strong>of</strong> 5GroupingCommonNameScientificNameStatusAdaAdamsBannockBear LakeBenewahBinghamBlaineBoiseBonnerBonnevilleBoundaryButteCamasCanyonCaribouCassiaClarkClearwaterCusterElmoreFranklinFremontGemGoodingIdahoJeffersonJeromeKootenaiLatahLemhiLewisLincolnMadisonMinidokaNez PerceOneidaOwyheePayettePowerShoshoneTetonTwin <strong>Falls</strong>ValleyWashingtonChrist'spaintbrushCastillejachristiiGoose CreekmilkvetchAstragalusanserrinusMacfarlane'sfour-o'clockMirabilismacfarlaneiPackard'sMilkvetchAstragaluscusickii var.parkardiaeSlickspotpeppergrassLepidiumpapilliferumSpalding'scatchflySilenespaldingiiUte ladies'-tressesSpiranthesediluvialisWaterHowelliaHowelliaaquatilis[C] [C] [T] [C] [T] [T] [T] [T]xxxxxPlantxxxxxxxxxxxxxxxxxxxxx[C] Candidate[P] Proposed[T] Threatened[E] Endangered[CH] Designated Critical Habitat[XN] Experimental Nonessential


Sockeye Salmon(Oncorhynchusnerka)Chinook Salmon(O. tshawytscha)Coho Salmon(O. kisutch)Chum Salmon(O. keta)Steelhead(O. mykiss)Pink Salmon(O. gorbuscha)Endangered Species Act Status <strong>of</strong> West Coast Salmon & Steelhead(Updated July 1, 2009)Species 1CurrentEndangeredSpecies ActListing Status 2ESA Listing ActionsUnder Review1 Snake River Endangered2 Ozette Lake Threatened3 Baker River Not Warranted4 Okanogan River Not Warranted5 Lake Wenatchee Not Warranted6 Quinalt Lake Not Warranted7 Lake Pleasant Not Warranted8 Sacramento River Winter-run Endangered9 Upper Columbia River Spring-run Endangered10 Snake River Spring/Summer-run Threatened11 Snake River Fall-run Threatened12 Puget Sound Threatened13 Lower Columbia River Threatened14 Upper Willamette River Threatened15 Central Valley Spring-run Threatened16 Cali<strong>for</strong>nia Coastal Threatened17 Central Valley Fall and Late Fall-run Species <strong>of</strong> Concern18 Upper Klamath-Trinity Rivers Not Warranted19 Oregon Coast Not Warranted20 Washington Coast Not Warranted21 Middle Columbia River spring-run Not Warranted22 Upper Columbia River summer/fall-run Not Warranted23 Southern Oregon and Northern Cali<strong>for</strong>nia Coast Not Warranted24 Deschutes River summer/fall-run Not Warranted25 Central Cali<strong>for</strong>nia Coast Endangered26 Southern Oregon/Northern Cali<strong>for</strong>nia Threatened27 Lower Columbia River Threatened Critical habitat28 Oregon Coast Threatened29 Southwest Washington Undetermined30 Puget Sound/Strait <strong>of</strong> Georgia Species <strong>of</strong> Concern31 Olympic Peninsula Not Warranted32 Hood Canal Summer-run Threatened33 Columbia River Threatened34 Puget Sound/Strait <strong>of</strong> Georgia Not Warranted35 Pacific Coast Not Warranted36 Southern Cali<strong>for</strong>nia Endangered37 Upper Columbia River Threatened38 Central Cali<strong>for</strong>nia Coast Threatened39 South Central Cali<strong>for</strong>nia Coast Threatened40 Snake River Basin Threatened41 Lower Columbia River Threatened42 Cali<strong>for</strong>nia Central Valley Threatened43 Upper Willamette River Threatened44 Middle Columbia River Threatened45 Northern Cali<strong>for</strong>nia Threatened46 Oregon Coast Species <strong>of</strong> Concern47 Southwest Washington Not Warranted48 Olympic Peninsula Not Warranted49 Puget Sound Threatened Critical habitat50 Klamath Mountains Province Not Warranted51 Even-year Not Warranted52 Odd-year Not Warranted1 The ESA defines a “species” to include any distinct population segment <strong>of</strong> any species <strong>of</strong> vertebrate fish or wildlife. For Pacific salmon, NOAAFisheries Service considers an evolutionarily significant unit, or “ESU,” a “species” under the ESA. For Pacific steelhead, NOAA Fisheries Servicehas delineated distinct population segments (DPSs) <strong>for</strong> consideration as “species” under the ESA.


I<strong>90</strong><strong>Beck</strong><strong>Road</strong>InterchangeTrafficNoiseModelTrafficInputsTable1.2010DHV(ExistingNoBuildCondition)LinkName LinkSegment LinkID Direction<strong>Post</strong>edSpeedLimit[miles/hr]AllVehicles[veh/hr]Automobile(%)Automobile(Volume)MediumTruck(%)MediumTruck(Volume)HeavyTruck(%)HeavyTruck(Volume)Bus(%)Bus(Volume)Motorcycle(%)Motorcycle(Volume)I<strong>90</strong> Mainline EB 70I<strong>90</strong> Mainline WB 703138 95.4% 2994 2.4% 75 2.2% 69 0.0% 0 0.0% 03180 95.4% 3034 2.4% 76 2.2% 70 0.0% 0 0.0% 0SelticeWay East<strong>of</strong>BaughWay EB 45ASelticeWay East<strong>of</strong>BaughWay WB 45568 93.6% 532 0.5% 3 4.1% 23 1.1% 6 0.8% 5568 94.3% 536 0.3% 2 3.8% 22 0.8% 5 0.9% 5BaughWay South<strong>of</strong>SelticeWay NB 40 241 93.8% 226 1.5% 4IBaughWay South<strong>of</strong>SelticeWaySB 40 253 93.6% 237 1.3% 34.2% 10 0.4% 1 0.1% 03.4% 9 0.2% 1 1.5% 4PointeParkway BaughWayto<strong>Beck</strong>Rd EB 40 254 89.5% 227 0.8% 2 6.7% 17 1.2% 3 1.9% 5KPointeParkway BaughWayto<strong>Beck</strong>Rd WB 40 254 89.5% 227 0.8% 2 6.7% 17 1.2% 3 1.9% 5RiverbendAve West<strong>of</strong>ClearwaterLoop EB 35 351 94.4% 331 1.8% 6 1.8% 6 1.0% 4 1.0% 4J1RiverbendAve West<strong>of</strong>ClearwaterLoop WB 35 341 95.8% 327 0.5% 2 2.5% 9 0.0% 0 1.2% 4


Table2.2030NoBuildDHV(FutureNoBuildCondition)LinkName LinkSegment LinkID Direction<strong>Post</strong>edSpeedLimit[miles/hr]AllVehicles[veh/hr]Automobile(%)Automobile(Volume)MediumTruck(%)MediumTruck(Volume)HeavyTruck(%)HeavyTruck(Volume)Bus(%)Bus(Volume)Motorcycle(%)Motorcycle(Volume)I<strong>90</strong> Mainline EB 70 5250 93.5% 4<strong>90</strong>9 3.3%I<strong>90</strong> Mainline WB 70 5250 93.5% 4<strong>90</strong>9 3.3%173 3.2% 168 0.0% 0173 3.2% 168 0.0% 00.0%00.0% 0SelticeWay West<strong>of</strong><strong>Beck</strong>Rd EB 45 1144 93.6% 1071 0.5% 6 4.1% 47 1.1% 13 0.8% 9ASelticeWay West<strong>of</strong><strong>Beck</strong>Rd WB 45 1144 94.3% 1079 0.3% 3 3.8% 43 0.8% 9 0.9% 10SelticeWay East<strong>of</strong><strong>Beck</strong>Rd EB 45 <strong>90</strong>4 93.6% 846 0.5% 5 4.1% 37 1.1% 10 0.8% 7BSelticeWay East<strong>of</strong><strong>Beck</strong>Rd WB 45 <strong>90</strong>4 94.3% 852 0.3% 3 3.8% 34 0.8% 7 0.9% 8BaughWay SelticetoPointePkway NB 40 446 93.8% 418 1.5% 7 4.2% 19 0.4% 2 0.1% 0IBaughWay SelticetoPointePkway SB 40 446 93.6% 417 1.3% 6 3.4% 15 0.2% 1 1.5% 7PointePkway BaughWayto<strong>Beck</strong>Rd EB 40 755 89.5% 676 0.8% 6 6.7% 51 1.2% 9 1.9% 14KPointePkway BaughWayto<strong>Beck</strong>Rd WB 40 755 89.5% 676 0.8% 6 6.7% 51 1.2% 9 1.9% 14<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>PointePkwaytoExpoPkwayPointePkwaytoExpoPkwayHNB 40 769 89.5% 688 0.8% 6 6.7% 52 1.2% 9 1.9% 15SB 40 769 89.5% 688 0.8% 6 6.7% 52 1.2% 9 1.9% 15<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>ExpoPkwaytoJacklinWayExpoPkwaytoJacklinWayFNB 35 180 89.5% 161 0.8% 1 6.7% 12 1.2% 2 1.9% 3SB 35 180 89.5% 161 0.8% 1 6.7% 12 1.2% 2 1.9% 3<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>JacklinWaytoSelticeWayJacklinWaytoSelticeWayDNB 40 568 89.5% 508 0.8% 5SB 40 568 89.5% 508 0.8% 56.7% 38 1.2% 7 1.9% 116.7% 38 1.2% 7 1.9% 11<strong>Beck</strong><strong>Road</strong> North<strong>of</strong>SelticeWay NB 50 325 89.5% 291 0.8% 3 6.7% 22 1.2% 4 1.9% 6C<strong>Beck</strong><strong>Road</strong> North<strong>of</strong>SelticeWay SB 50 325 89.5% 291 0.8% 3 6.7% 22 1.2% 4 1.9% 6ExpoPkway East<strong>of</strong><strong>Beck</strong><strong>Road</strong> EB 35 359 77.4% 278 1.1% 4 18.2% 65 1.2% 4 2.1% 8GExpoPkway East<strong>of</strong><strong>Beck</strong><strong>Road</strong> WB 35 359 72.0% 258 1.9% 7 16.2% 58 4.5% 16 5.4% 19


LinkName LinkSegment LinkID Direction<strong>Post</strong>edSpeedLimit[miles/hr]Table2.2030NoBuildDHV(FutureNoBuildCondition)[Continued]AllVehicles[veh/hr]Automobile(%)Automobile(Volume)MediumTruck(%)MediumTruck(Volume)HeavyTruck(%)HeavyTruck(Volume)Bus(%)Bus(Volume)Motorcycle(%)JacklinWay East<strong>of</strong><strong>Beck</strong><strong>Road</strong> EB 35 464 93.6% 434 0.5% 2 4.1% 19 1.1% 5 0.8% 4EJacklinWay East<strong>of</strong><strong>Beck</strong><strong>Road</strong> WB 35 464 93.6% 434 0.5% 2 4.1% 19 1.1% 5 0.8% 4RiverbendAve West<strong>of</strong>ClearwaterLoop EB 35 483 94.4% 456 1.8% 9 1.8% 9 1.0% 5 1.0% 5J1RiverbendAve West<strong>of</strong>ClearwaterLoop WB 35 483 95.8% 463 0.5% 2 2.5% 12 0.0% 0 1.2% 6Motorcycle(Volume)LinkName LinkSegment LinkID DirectionI<strong>90</strong>I<strong>90</strong>I<strong>90</strong>I<strong>90</strong>MainlineWest<strong>of</strong>EBOffRampMainlineEast<strong>of</strong>WBOffRampMainlineBetweenInterchangeRampsMainlineBetweenInterchangeRamps<strong>Post</strong>edSpeedLimit[miles/hr]AllVehicles[veh/hr]Table3.2030BuildDHV(FutureBuildConditions)Automobile(%)Automobile(Volume)MediumTruck(%)MediumTruck(Volume)EB 70 5113 93.5% 4781 3.3% 169WB 70 529993.5%HeavyTruck(%)HeavyTruck(Volume)Bus(%)Bus(Volume)Motorcycle(%)EB 70 4671 93.5% 4367 3.3% 154 3.2% 149 0.0% 0 0.0% 0WB 70 4423 93.5% 4136 3.3%3.2%164Motorcycle(Volume)0.0% 0 0.0% 04955 3.3% 175 3.2% 170 0.0% 0 0.0% 0146 3.2% 142 0.0% 0 0.0% 0I<strong>90</strong>EBOffRampI<strong>90</strong>EBOffRamp EB 40 442 93.5%413 3.3% 15 3.2% 140.0% 0 0.0% 0I<strong>90</strong>EBOnRamp I<strong>90</strong>EBOnRamp EB 40 115893.5% 1083 3.3% 38 3.2% 37 0.0% 0 0.0%0I<strong>90</strong>WBOffRamp I<strong>90</strong>WBOffRamp WB 40 876 93.5% 819 3.3% 29 3.2% 28 0.0% 0 0.0%0I<strong>90</strong>WBOnRampI<strong>90</strong>WBOnRampWB 40 993 93.5% 928 3.3% 33 3.2% 32 0.0% 0 0.0% 0SelticeWay West<strong>of</strong><strong>Beck</strong>RdEB 45 861 93.6% 806 0.5% 4 4.1% 35 1.1% 9 0.8% 7ASelticeWay West<strong>of</strong><strong>Beck</strong>Rd WB 45 861 94.3% 812 0.3% 3 3.8% 33 0.8% 7 0.9% 8SelticeWay East<strong>of</strong><strong>Beck</strong>Rd EB 45 759 93.6% 710 0.5% 4 4.1% 31 1.1% 8 0.8% 6BSelticeWay East<strong>of</strong><strong>Beck</strong>Rd WB 45 759 94.3% 716 0.3% 2 3.8% 29 0.8% 6 0.9% 7BaughWay SelticetoPointePkway NB 40 446 93.8% 418 1.5% 7 4.2% 19 0.4% 2 0.1% 0IBaughWay SelticetoPointePkway SB 40 446 93.6% 417 1.3% 6 3.4% 15 0.2% 1 1.5% 7


Table3.2030BuildDHV(FutureBuildConditions)[Continued]LinkName LinkSegment LinkID Direction<strong>Post</strong>edSpeedLimit[miles/hr]AllVehicles[veh/hr]Automobile(%)Automobile(Volume)MediumTruck(%)MediumTruck(Volume)HeavyTruck(%)HeavyTruck(Volume)Bus(%)Bus(Volume)Motorcycle(%)Motorcycle(Volume)PointePkway BaughWayto<strong>Beck</strong>Rd EB 40 1811 89.5% 1621 0.8% 14 6.7% 121 1.2% 22 1.9% 34KPointePkway BaughWayto<strong>Beck</strong>Rd WB 40 1811 89.5% 1621 0.8% 14 6.7% 121 1.2% 22 1.9% 34<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>RiverbendAv.toEBRampsRiverbendAv.toEBRampsNNB 40 766 89.5% 686 0.8% 66.7% 51 1.2% 9 1.9% 15SB 40 766 89.5% 686 0.8% 6 6.7% 51 1.2% 9 1.9% 15<strong>Beck</strong><strong>Road</strong> EBRampstoWBRamps NB 40 1423 89.5% 1274 0.8% 11 6.7% 95 1.2% 17 1.9% 27M<strong>Beck</strong><strong>Road</strong> EBRampstoWBRamps SB 40 1423 89.5% 1274 0.8% 11 6.7% 95 1.2% 17 1.9% 27<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>WBRampstoPointePkwayIntersectionWBRampstoPointePkwayIntersectionLEB 40 1961 89.5% 1755 0.8% 16 6.7% 131 1.2% 24 1.9% 37WB 40 1961 89.5% 1755 0.8% 16 6.7% 131 1.2% 24 1.9% 37<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>PointePkwaytoExpoPkwayPointePkwaytoExpoPkwayHNB 40 1006 89.5% <strong>90</strong>0 0.8% 8 6.7% 67 1.2% 12 1.9% 19SB 40 1006 89.5% <strong>90</strong>0 0.8% 8 6.7% 67 1.2% 12 1.9% 19<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>ExpoPkwaytoJacklinWayExpoPkwaytoJacklinWayFNB 35 291 89.5% 260 0.8% 2 6.7% 19 1.2% 3 1.9% 6SB 35 291 89.5% 260 0.8% 2 6.7% 19 1.2% 3 1.9% 6<strong>Beck</strong><strong>Road</strong><strong>Beck</strong><strong>Road</strong>JacklinWaytoSelticeWayJacklinWaytoSelticeWayDNB 40 568 89.5% 508 0.8% 5 6.7% 38 1.2% 7 1.9% 11SB 40 568 89.5% 508 0.8% 5 6.7% 38 1.2% 7 1.9% 11<strong>Beck</strong><strong>Road</strong> North<strong>of</strong>SelticeWayNB 50 331 89.5% 296 0.8% 3 6.7% 22 1.2% 4 1.9% 6C<strong>Beck</strong><strong>Road</strong> North<strong>of</strong>SelticeWay SB 50 331 89.5% 296 0.8% 3 6.7% 22 1.2% 4 1.9% 6ExpoPkway East<strong>of</strong><strong>Beck</strong><strong>Road</strong>EB 35 249 77.4% 193 1.1% 3 18.2% 45 1.2% 3 2.1% 5GExpoPkway East<strong>of</strong><strong>Beck</strong><strong>Road</strong> WB 35 249 72.0% 179 1.9% 5 16.2% 40 4.5% 11 5.4% 13JacklinWay East<strong>of</strong><strong>Beck</strong><strong>Road</strong>EB 35 262 93.6% 245 0.5% 1 4.1% 11 1.1% 3 0.8% 2EJacklinWay East<strong>of</strong><strong>Beck</strong><strong>Road</strong> WB 35 262 93.6% 245 0.5% 1 4.1% 11 1.1% 3 0.8% 2


LinkName LinkSegment LinkID DirectionRiverbendAveRiverbendAveRiverbendAveClearwaterLooptoInterchangeClearwaterLooptoInterchangeWest<strong>of</strong>InterchangeJ1<strong>Post</strong>edSpeedLimit[miles/hr]Table3.2030BuildDHV(FutureBuildConditions)[Continued]AllVehicles[veh/hr]Automobile(%)Automobile(Volume)EB 35 500 94.4% 472MediumTruck(%)EB 35 225 95.4% 215 0.4%MediumTruck(Volume)HeavyTruck(%)HeavyTruck(Volume)Bus(%)Bus(Volume)Motorcycle(%)Motorcycle(Volume)1 2.6% 6 0.7% 2 0.8% 2J2RiverbendAve West<strong>of</strong>Interchange WB 35 225 94.3% 212 0.3% 1 3.8% 9 0.8% 2 0.9% 21.8%9 1.8% 9 1.0% 5 1.0% 5WB 35 500 95.8% 479 0.5% 3 2.5% 13 0.0% 0 1.2% 6


W CLEARWATER LOOPSoil Map–Kootenai County Area, Idaho, and Spokane County, Washington(<strong>Beck</strong> <strong>Road</strong> Interchange Project Area)49600049650049700049750049800049850049<strong>90</strong>004995005000005285000W ELK DR528500052840005284500E FRANCIS AVEN VINCENT RDCHASE RDE ROWAN AVEN IDAHO RDN STATE LINE RDW ANTE RDW SELTICE WAY120N BECK RDW SELTICE BLVD120W JACKLIN RD120N PLEASANT VIEW RD156W 5TH AVEN SPOKANE RDW RAILROAD AVE528400052845005282000528250052830005283500N CHASE RDE WABASH AVEE WELLESLEY AVEN SPOKANE BRIDGE RDE KILDEA AVEN POWELL RDE APPLEWAY AVEE QUEEN AVEGgAE ANTE RDE EASTLAND DRE WABASH AVEE EASTLAND AVEGmBWRhE APPLEWAY AVERhCnBGgA101120156101205121150119S RICHARDS RDS BECK RD120W LAURA LN156205I<strong>90</strong>W RIVERBEND AVEW SELWAY AVELOCHSA ST205 119S GOLD FINCH RDCLEARWATER CTS PLEASANT VIEW RDBATES LNS PLEASANT LNS MAJESTIC VIEW DRS SPOKANE RDW RIVERVIEW DRCanalMADISON RDMEADOW RD5282000528250052830005283500496000496500497000497500498000Meters0 350700 1,400 2,100Feet0 1,000 2,000 4,000 6,00049850049<strong>90</strong>00499500500000Natural ResourcesConservation ServiceWeb Soil Survey 2.0National Cooperative Soil Survey9/26/2007Page 1 <strong>of</strong> 3


Soil Map–Kootenai County Area, Idaho, and Spokane County, Washington(<strong>Beck</strong> <strong>Road</strong> Interchange Project Area)MAP LEGENDMAP INFORMATIONArea <strong>of</strong> Interest (AOI)Area <strong>of</strong> Interest (AOI)SoilsSoil Map UnitsSpecial Point FeaturesBlowoutBorrow PitClay SpotClosed DepressionGravel PitGravelly SpotLandfillLava FlowMarshMine or QuarryMiscellaneous WaterPerennial WaterRock OutcropSaline SpotSandy SpotSeverely Eroded SpotSinkholeSlide or SlipSodic SpotSpoil AreaStony SpotVery Stony SpotWet SpotOtherSpecial Line FeaturesGullyShort Steep SlopeOtherPolitical FeaturesMunicipalitiesCitiesUrban AreasWater FeaturesOceansStreams and CanalsTransportationRails<strong>Road</strong>sInterstate HighwaysUS RoutesState HighwaysLocal <strong>Road</strong>sOther <strong>Road</strong>sOriginal soil survey map sheets were prepared at publication scale.Viewing scale and printing scale, however, may vary from theoriginal. Please rely on the bar scale on each map sheet <strong>for</strong> propermap measurements.Source <strong>of</strong> Map: Natural Resources Conservation ServiceWeb Soil Survey URL: http://websoilsurvey.nrcs.usda.govCoordinate System: UTM Zone 11NThis product is generated from the USDA-NRCS certified data as <strong>of</strong>the version date(s) listed below.Soil Survey Area: Kootenai County Area, IdahoSurvey Area Data: Version 5, Jan 26, 2007Soil Survey Area: Spokane County, WashingtonSurvey Area Data: Version 1, May 3, 2006Your area <strong>of</strong> interest (AOI) includes more than one soil survey area.These survey areas may have been mapped at different scales, witha different land use in mind, at different times, or at different levels<strong>of</strong> detail. This may result in map unit symbols, soil properties, andinterpretations that do not completely agree across soil survey areaboundaries.Date(s) aerial images were photographed: 5/22/1992; 6/9/1998The orthophoto or other base map on which the soil lines werecompiled and digitized probably differs from the backgroundimagery displayed on these maps. As a result, some minor shifting<strong>of</strong> map unit boundaries may be evident.Natural ResourcesConservation ServiceWeb Soil Survey 2.0National Cooperative Soil Survey9/26/2007Page 2 <strong>of</strong> 3


Soil Map–Kootenai County Area, Idaho, and Spokane County, Washington<strong>Beck</strong> <strong>Road</strong> Interchange Project AreaMap Unit LegendKootenai County Area, Idaho (ID606)Map Unit Symbol Map Unit Name Acres in AOI Percent <strong>of</strong> AOI101 Aquic Xer<strong>of</strong>luvents, nearly level 11.5 0.8%119 Garrison gravelly silt loam, 0 to7 percent slopes120 Garrison very stony silt loam, 0to 7 percent slopes1,099.0 77.0%116.6 8.2%121 Pits, gravel 27.8 2.0%150 McGuire-Marble association,20 to 45 percent slopes156 Narcisse silt loam, 0 to 5percent slopes54.6 3.8%8.0 0.6%205 Water 31.0 2.2%Spokane County, Washington (WA063)Map Unit Symbol Map Unit Name Acres in AOI Percent <strong>of</strong> AOICnB Cheney and uhlig silt loams, 0to 8 percent slopesGgA Garrison gravelly loam, 0 to 5percent slopesGmB Garrison very gravelly loam, 0to 8 percent slopes10.0 0.7%20.6 1.4%24.2 1.7%Rh Riverwash 15.3 1.1%W Water 8.0 0.6%Totals <strong>for</strong> Area <strong>of</strong> Interest (AOI) 1,426.6 100.0%Natural ResourcesConservation ServiceWeb Soil Survey 2.0National Cooperative Soil Survey9/26/2007Page 3 <strong>of</strong> 3


Appendix D. Scoping ResponsesI-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange<strong>Environmental</strong> <strong>Assessment</strong>D-1Project No. A010(963)June 2011


Glavin, JedFrom:Sent:To:Cc:Subject:Tom Lien [postfallsura@gmail.com]Tuesday, February 01, 2011 6:03 PMGlavin, JedBobbi RollinsEA CommentMichael Murray<strong>Environmental</strong> Manager,HDR EngineeringThank you very much Mike <strong>for</strong> the in<strong>for</strong>mation and opportunity to comment on the pending EA <strong>for</strong> the <strong>Beck</strong><strong>Road</strong> Interchange. I would comment as follows from the items on your list:#3. Traffic and access - I would expect to see mitigation <strong>of</strong> access <strong>for</strong> traffic ingress and egress to the Expodevelopment site which is on the north side <strong>of</strong> I-<strong>90</strong> and on the east side <strong>of</strong> the interchange. This is an area thatis equally important <strong>for</strong> development in the area. The proponent should be contacted and assurances made thataccess to that development received positive consideration.#4. On the south side <strong>of</strong> I-<strong>90</strong> there is the Centennial Trail. This is used extensively by foot and bike traffic.Will assurances be made to provide <strong>for</strong> dust mitigation and protection from construction equipment duringconstruction.#7. Potable water source. To the north <strong>of</strong> the Interchange, just south <strong>of</strong> Seltice Way, is a water tower. Will youplease look at that water tower in light <strong>of</strong> whether it is potable water or just fire suppression. If potable waterand there is a well on-site, how deep is the well and would the source be affected in any way by construction orblasting.#12. Surface water management. In general, all the surface water from this site will flow to the freeway andthence to the west to the Spokane River. Will containment measures be in place to prevent contamination fromthe construction site in case <strong>of</strong> any storm event.Thank you.Tom LienExecutive Director--<strong>Post</strong> <strong>Falls</strong> Urban Renewal AgencyP.O. Box 236 * <strong>Post</strong> <strong>Falls</strong>, ID 83877Office 208-777-8151 * Fax 208-777-8117 * Cell 509-844-8720www.pfura.com1


Glavin, JedFrom:Sent:To:Subject:jkeane [jkeane@sd273.com]Friday, February 11, 2011 12:25 PMGlavin, Jed<strong>Beck</strong> <strong>Road</strong> Interchange<strong>Post</strong> <strong>Falls</strong> School District supports the plan as it was shown in your letter dated January 20, 2011. Thanks.Jerry KeaneSuperintendent <strong>of</strong> Schools<strong>Post</strong> <strong>Falls</strong> School District # 273www.pfsd.comjkeane@sd273.comph. 208-773-1658fax 208-773-32181


Glavin, JedFrom:Sent:To:Cc:Subject:Douglas Okuniewicz [okuniewicz@gmail.com]Monday, February 21, 2011 5:08 PMGlavin, JedErich GrosseI-<strong>90</strong>/<strong>Beck</strong> <strong>Road</strong> Interchange - Greyhound Park and Event CenterMr. Murray,I am responding to your January 20th letter requesting notification <strong>of</strong> issues or concerns related to the proposedI-<strong>90</strong>/<strong>Beck</strong> <strong>Road</strong> Interchange.1. Enclosed in your January 20th letter was an aerial view photo including a mock up <strong>of</strong> the interchange that isdifferent than the Pointe Parkway Interchange Standard Diamond Alternative (PP1.1) included in thepreliminarily approved Interstate Justification Report (IJR). The January 20th drawing utilizes substantiallymore area on our property <strong>for</strong> both the surface streets and the southern driveway circle than in the previouslysubmitted IJR alternative PP1.1.2. As yet we do not have an agreement <strong>for</strong> right <strong>of</strong> way.3. Ingress, egress and traffic flow on property.4. Reader board replacement or relocation.Erich Grosse met with me on February 1st to discuss the project and has since provided me with an option <strong>for</strong> aparking lot layout and ingress/egress.I appreciate all the work the developer and your team are putting <strong>for</strong>th toward addressing these issues.Sincerely,Doug OkuniewiczGM - Greyhound Park and Event Center1


Glavin, JedFrom:Sent:To:Subject:Somers.Elaine@epamail.epa.govThursday, March 31, 2011 8:04 PMGlavin, JedI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange ProjectAttn: Michael R. Murray, <strong>Environmental</strong> Manager HDR Engineering, Inc.Mr. Murray,Thank you <strong>for</strong> your invitation to submit issues <strong>for</strong> analysis <strong>for</strong> the <strong>Environmental</strong> <strong>Assessment</strong>(EA) you are preparing <strong>for</strong> FHWA and ITD's <strong>Beck</strong> <strong>Road</strong>/I‐<strong>90</strong> Interchange project. If you areable to include them within your study, we would like to recommend adding the followingissues to those listed in your letter <strong>of</strong> January 20, 2011:Air Quality/Air Toxics and Diesel Particulates The NEPA document should characterize theproject area air quality impacts, particularly the near roadway effects <strong>of</strong> criteriapollutants and mobile source air toxics (MSATs) that would potentially result from theproject. Identify sensitive receptor locations and populations to air emissions from bothconstruction and operation <strong>of</strong> the facility.Construction Mitigation Measures. Air toxics emissions, particularly diesel exhaust, areknown or suspected to cause cancer or other serious health effects, such as respiratory,neurological, reproductive, and developmental effects. We recommend augmenting the standardITD air quality construction specifications to emphasize reducing diesel and other emissionsfrom construction vehicles and equipment. Include and commit to implementing a suite <strong>of</strong>construction mitigation measures, such as those from the Clean Construction USA Web site athttp://www.epa.gov/otaq/diesel/construction/. Measures such as diesel engine retr<strong>of</strong>ittechnology in <strong>of</strong>f‐road equipment would greatly help to reduce air toxics and dieselparticulate emissions. Such technology may include diesel oxidation catalyst/dieselparticulate filters, engine upgrades, engine replacements, newer model year equipment, use <strong>of</strong>biodiesel, or combinations <strong>of</strong> these strategies.Indirect and Cumulative effects ‐‐ Stimulated Travel and Growth When examining existing landuse, zoning, and local land use plans <strong>for</strong> the project area, we also recommend analysis anddisclosure <strong>of</strong> the potential <strong>for</strong> stimulating additional travel and development in the projectvicinity and beyond.Aquatic ResourcesInclude riparian areas and the hyporheic zone <strong>of</strong> the Spokane River in addition to theanalysis <strong>of</strong> potential impacts to floodways, floodplains, and wetlands.Ecological ConnectivityAnalyze the potential <strong>for</strong> fragmentation <strong>of</strong> habitats and ecological processes. Ensure thatterrestrial and aquatic habitats, hydrology, and other ecological processes remain connectedto enable safe species movement in the landscape and to protect ecosystem structure,function, and services.If you have questions or would like to discuss these comments, please do not hesitate tocontact me at the number or email address below.Sincerely,Elaine Somers1


<strong>Environmental</strong> Review and Sediment Management Unit U.S. <strong>Environmental</strong> Protection Agency,Region 10 1200‐6th Ave., Suite <strong>90</strong>0, ETPA‐088 Seattle, WA 98101phone: (206) 553‐2966fax: (206) 553‐6984email: somers.elaine@epa.gov2


April 19, 2011Mr. Tom LienExecutive Director<strong>Post</strong> <strong>Falls</strong> Urban Renewal AgencyP.O. Box 236<strong>Post</strong> <strong>Falls</strong>, ID 83877Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 1, 2011 Scoping Comment LetterDear Mr. Lien:We received your email dated February 1, 2011 in response to our scoping letter <strong>for</strong> the proposedI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Our response is categorized by your comments.Traffic and Access: The project will provide new access to I-<strong>90</strong> as well as associatedimprovements to select surface roads in the project area. It will be the responsibility <strong>of</strong> individualdevelopers to seek appropriate access to these improvements based on development plans andlocal approval <strong>of</strong> those plans by the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>. It is not within the scope <strong>of</strong> the project toconstruct additional access and connectivity to future development.Centennial Trail: The North Idaho Centennial Trail will remain open during construction,although some disruption <strong>of</strong> trail access such as temporary detours, gravel/dirt resurfacing andflaggers may occur. Attempts will be made to minimize disruption <strong>of</strong> the trail duringconstruction and construction plans will clearly identify temporary connections. Constructionmitigation measures <strong>for</strong> the Centennial Trail have been outlined in Chapter 3 <strong>of</strong> the EA.Fugitive Dust: During construction, contractors will be required to use methods and devices thatare available to control, prevent, and otherwise minimize atmospheric emissions or discharges <strong>of</strong>atmospheric contaminants. Contractors will be required to reduce dust that originates fromconstruction operations and prevent dust from damaging dwellings or causing a nuisance. Longtermsoil stabilization will be achieved by re-vegetating exposed areas once they are no longerneeded <strong>for</strong> project construction. Mitigation measures <strong>for</strong> fugitive dust have been addressed inChapter 3 <strong>of</strong> the EA.Potable Water Source: Construction <strong>of</strong> the proposed interchange as well as improvements to N.<strong>Beck</strong> <strong>Road</strong> would not impact the water tower in the project area.1 | P age


Mr. Tom LienApril 19, 2011Surface Water: Construction <strong>of</strong> the project will require a Construction Stormwater GeneralPermit under the National Pollutant Discharge Elimination (NPDES) program, as well as aStormwater Pollution Prevention Plan (SWPPP) and implementation <strong>of</strong> best managementpractices (BMPs) to control stormwater run<strong>of</strong>f and sediment erosion. Stormwater run<strong>of</strong>f from theconstruction and operation <strong>of</strong> the Proposed Action would be designed to be retained on-site.Concept-level design details on stormwater water management <strong>for</strong> the project have beenaddressed in Chapter 3 <strong>of</strong> the EA. No impacts will occur to the Spokane River.The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.032 | P age


April 19, 2011Mr. Ron SampertFire ChiefKootenai County Fire & RescueP.O. Box 2200<strong>Post</strong> <strong>Falls</strong>, ID 83877Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 4, 2011 Scoping Comment LetterDear Mr. Sampert:We received your email dated February 4, 2011, in response to our scoping letter <strong>for</strong> theproposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Thank you <strong>for</strong> providing your comments. Yourinput has been considered during the development <strong>of</strong> the <strong>Environmental</strong> <strong>Assessment</strong> (EA).The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.031 | P age


April 19, 2011Mr. Jerry KeaneSuperintendent<strong>Post</strong> <strong>Falls</strong> School District #273206 W. Mullan Ave.<strong>Post</strong> <strong>Falls</strong>, ID 83877Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 11, 2011 Scoping CommentDear Mr. Keane:We received your email dated February 11, 2011 in response to our scoping letter <strong>for</strong> theproposed I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange project. Thank you <strong>for</strong> providing your support. Yourinput has been documented during the development <strong>of</strong> the <strong>Environmental</strong> <strong>Assessment</strong> (EA).The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.031 | P age


April 19, 2011Mr. Lynn HumphreysChairman<strong>Post</strong> <strong>Falls</strong> Highway District5629 E Seltice Way<strong>Post</strong> <strong>Falls</strong>, ID 83854Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 16, 2011 Scoping Comment LetterDear Mr. Humphreys:We received your letter dated February 16, 2011, in response to our scoping letter <strong>for</strong> theproposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Our response is categorized by your fivecomments.Item 1: The existing W. Riverbend Avenue will be re-aligned to connect to Pointe Parkway andthe proposed interchange. A W. Riverbend Avenue extension will also provide connectivity west<strong>of</strong> the interchange, where it will be a two-lane collector road with sidewalk on the south side, atwo-way left turn lane west <strong>of</strong> the interchange, and turn lanes at the appropriate intersections.Access to existing businesses southwest <strong>of</strong> the interchange will be maintained duringconstruction <strong>of</strong> the interchange. The realignment <strong>of</strong> W. Riverbend Avenue falls within theguidance provided by “Practical Solutions <strong>for</strong> Highway Design” in that it is local roadway (non-NHS) and the design recognizes constrained right-<strong>of</strong>-way availability. The proposed designconcept has been discussed with the governing agencies as part <strong>of</strong> the Technical AdvisoryCommittee (TAC) process, which included representatives <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> Highway District.Preliminary design details <strong>of</strong> the Proposed Action are addressed in Chapter 3 <strong>of</strong> the<strong>Environmental</strong> <strong>Assessment</strong> (EA).Item 2: Long-range plans <strong>for</strong> improving N. <strong>Beck</strong> <strong>Road</strong> north <strong>of</strong> W. Seltice Way to SH-53 areanticipated as this area transitions from rural to urban and is developed (as identified in theKootenai Metropolitan Transportation Plan, 2010). These improvements north <strong>of</strong> W. Seltice Wayare not part <strong>of</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. According to discussions with <strong>City</strong> <strong>of</strong><strong>Post</strong> <strong>Falls</strong>’ staff, the current industrial zoning <strong>for</strong> the area north <strong>of</strong> W. Seltice Way along N. <strong>Beck</strong><strong>Road</strong> is not anticipated to change in the near future. Zoning <strong>for</strong> areas further north are currentlyrural and outside the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> limits. <strong>City</strong> staff anticipates that the proposed interchangewould not change the industrial land-use zoning <strong>for</strong> this area. It has also been noted by <strong>Post</strong> <strong>Falls</strong>city staff that commercial land uses on the north side <strong>of</strong> the W. Seltice Way and N. <strong>Beck</strong> <strong>Road</strong>intersection is restricted by the steep grade.Future traffic was modeled <strong>for</strong> project alternatives to evaluate if building an I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange project would trigger the immediate need <strong>for</strong> transportation improvements on N.<strong>Beck</strong> <strong>Road</strong>, north <strong>of</strong> W. Seltice Way. The traffic was modeled <strong>for</strong> the year 2012, the assumedconstruction completion year <strong>for</strong> the project. A traffic signal will be installed at the intersection1 | P age


Mr. Lynn HumphreysApril 19, 2011<strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> and W. Seltice Way as part <strong>of</strong> the project. The traffic model shows noadditional road improvements would be needed in 2012 north <strong>of</strong> W. Seltice Way on N. <strong>Beck</strong><strong>Road</strong> beyond the new traffic signal as a result <strong>of</strong> the project. Based on the 2012 Opening Daytraffic analysis conducted <strong>for</strong> the IJR (page 7-9 <strong>of</strong> the October 2010 IJR), the intersection <strong>of</strong> N.<strong>Beck</strong> <strong>Road</strong> and W. Seltice Way is projected to operate at LOS B. The 2030 traffic analysis <strong>of</strong>this signalized intersection indicates an LOS C (page 2-9 <strong>of</strong> the October 2010 IJR). Chapter 3 <strong>of</strong>the EA addresses the impacts <strong>of</strong> land use and the independent utility <strong>of</strong> the Proposed Action.Item 3: The North Idaho Centennial Trail will remain open during construction, although somedisruption <strong>of</strong> trail access such as temporary detours, gravel/dirt resurfacing and flaggers mayoccur. Attempts will be made to minimize disruption <strong>of</strong> the trail during construction andconstruction plans will clearly identify temporary connections. Construction mitigation measures<strong>for</strong> the Centennial Trail have been addressed in the EA.Item 4: Construction <strong>of</strong> the project will include a Construction Stormwater General Permit underthe National Pollutant Discharge Elimination (NPDES) program, as well as a StormwaterPollution Prevention Plan (SWPPP) and implementation <strong>of</strong> best management practices (BMPs)to control stormwater run<strong>of</strong>f and sediment erosion. Stormwater run<strong>of</strong>f from the construction andoperation <strong>of</strong> the Proposed Action will be designed to be retained on-site. Concept-level designdetails <strong>for</strong> stormwater management <strong>for</strong> the project have been addressed in the EA. The projectproponent and their contractor will coordinate with the <strong>Post</strong> <strong>Falls</strong> Highway District to obtainnecessary agreements regarding maintenance and control <strong>of</strong> stormwater in District right-<strong>of</strong>-wayor easements.Item 5: A traffic signal will be installed at the intersection <strong>of</strong> N. <strong>Beck</strong> <strong>Road</strong> and W. Seltice Wayas part <strong>of</strong> the project. Improvements to this intersection will be based on traffic engineeringrecommendations and will be coordinated with the <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong> and the <strong>Post</strong> <strong>Falls</strong> HighwayDistrict. Refer to item 2 response <strong>for</strong> additional in<strong>for</strong>mation on LOS analysis.The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.032 | P age


March 21, 2011Mr. Greg FiggRegion Development ServicesWashington State Department <strong>of</strong> TransportationEastern Region2714 N. Mayfair StreetSpokane, WA 99207-2050Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 17, 2011 Scoping Comment LetterDear Mr. Figg:We received your comments in response to our scoping letter <strong>for</strong> the proposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong>Interchange Project. Our response is categorized by your four comments.Item 1: The project purpose is to improve regional traffic operations to and from I-<strong>90</strong>, betweenand including the Pleasant View <strong>Road</strong>/I-<strong>90</strong> and State Line <strong>Road</strong>/I-<strong>90</strong> interchanges. Asdemonstrated in the October 2010 Interstate Justification Report (IJR) as provisionally approvedby FHWA, the 2030 peak hour traffic volumes at the State Line Interchange ramp terminiintersections decrease with the addition <strong>of</strong> the I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange. The 2030 PM peakhour volumes <strong>for</strong> the No-Build unsignalized scenario are 2,367 vehicles east bound (totalvehicles at the EB ramp terminus intersection) and 2,445 vehicles west bound (total vehicles atthe WB ramp terminus intersection). Compared to the 2030 PM peak hour volumes <strong>for</strong> the <strong>Beck</strong><strong>Road</strong> Standard Diamond Build scenario <strong>of</strong> 2,032 EB (total vehicles at the EB ramp terminusintersection) and 1,674 WB (total vehicles at the WB ramp terminus intersection), the addition <strong>of</strong>the <strong>Beck</strong> <strong>Road</strong> Interchange reduces the PM peak hour volumes by 14% EB and 32% WB <strong>for</strong>total vehicles at the State Line ramp termini intersections. Both scenarios listed above aremodeled with unsignalized intersections at the State Line ramp termini. The project purpose issatisfied through reduction <strong>of</strong> PM peak hour volume and increase in volume to capacity ratio.(Source - October 2010 IJR, Appendix F, No-Build Traffic Operations Analysis and AppendixU, PP1.1 2030 Operations Analysis, Standard Diamond).During the course <strong>of</strong> the Summer 2010 IJR revisions, the project purpose was examined giventhe decrease in hourly volumes described above. This decrease in volumes, combined with theanalysis <strong>of</strong> the State Line ramp terminus intersections as unfunded deficiencies in 2015 by theSpokane Regional Transportation Council (SRTC) Metropolitan Transportation Plan, caused the<strong>Beck</strong> <strong>Road</strong> Interchange project to remove the signals from the proposed action.1 | P age


Mr. Greg FiggMarch 21, 2011These facts support Federal Policy Point 3 as noted in the IJR to that “An operational and safetyanalysis has concluded that the proposed change in access does not have a significant adverseimpact on the safety and operation <strong>of</strong> the Interstate facility...”Item 2: The ramp terminal intersections <strong>of</strong> the State Line Interchange will exhibit poor LOSregardless <strong>of</strong> the provision <strong>of</strong> the <strong>Beck</strong> <strong>Road</strong> Interchange. The Level <strong>of</strong> Service (LOS) at the I-<strong>90</strong> Stateline interchange ramps will be “F” at design year 2030 without the proposed interchange(Source – October 2010 IJR, Appendix F, No-Build Traffic Operations Analysis). Thisconfiguration includes the revised ramp control from current stop control <strong>of</strong> Stateline <strong>Road</strong> tostop control <strong>of</strong> the ramp movements <strong>for</strong> the WB ramps as part <strong>of</strong> the modifications to the Port <strong>of</strong>Entry. (Refer to page 1-4 <strong>of</strong> the October 2010 IJR – Intersection #52 <strong>for</strong> description <strong>of</strong> thisintersection.)As unsignalized intersections, these locations are expected to per<strong>for</strong>m poorly under the<strong>for</strong>ecasted 2030 PM peak hour conditions and any effect <strong>of</strong> adding the <strong>Beck</strong> <strong>Road</strong> Interchange isan improvement. The SRTC Metropolitan Transportation Plan identified these ramp terminusintersections as unfunded deficiencies in 2015. The effect <strong>of</strong> providing the <strong>Beck</strong> <strong>Road</strong>Interchange would be to delay the emergence <strong>of</strong> this deficiency beyond the projected 2015horizon year. That additional time may allow the SRTC, WSDOT, and its regional partners t<strong>of</strong>ind the appropriate, funded solution to this recognized deficiency.Item 3: The queue length <strong>for</strong> the eastbound and westbound movements indicates an error in theanalysis due to the LOS “F”. Since this LOS “F” also exists in the No-Build scenario, theproposed interchange does not mitigate <strong>for</strong> a condition that is pre-existing and already identifiedas an unfunded deficiency. As stated above, the proposed <strong>Beck</strong> <strong>Road</strong> Interchange will delay theemergence <strong>of</strong> this deficiency beyond the projected 2015 horizon year, providing the responsibleagencies additional time to mitigate <strong>for</strong> thispre-existing deficiency.Item 4: The inconsistency noted regarding the content <strong>of</strong> the memo in Appendix K is because thememo was written on May 20, 2010, which was prior to the removal <strong>of</strong> the signalizedimprovements at the State Line intersections. The analyses showing signalized intersectionswere included in the Aug 2010 IJR and were replaced with analyses showing unsignalizedoperations prior to the FHWA provisionally approved October 2010 IJR submittal.The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.2 | P age


Mr. Greg FiggMarch 21, 2011Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Peter Hartman, FHWA Idaho DivisionGus Shanine, FHWA Idaho DivisionYamilee Volcy, FHWA Washington DivisionLoren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQMike Frucci, WSDOTHarold White, WSDOTCharlene Kay, WSDOTErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.033 | P age


April 19, 2011Mr. Doug OkuniewiczPresidentGreyhound Park and Event Center5100 W. Riverbend Avenue<strong>Post</strong> <strong>Falls</strong>, ID 83854Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 21, 2011 Scoping Comment LetterDear Mr. Okuniewicz:We received your email dated February 21, 2011 in response to our scoping letter <strong>for</strong> theproposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Our responses are outlined below.The updated design supports connectivity and required design queue lengths <strong>for</strong> the proposedPointe Parkway and W. Riverbend Avenue intersection south <strong>of</strong> the interchange. Propertyagreements will be negotiated with property owners subject to final design requirements <strong>of</strong> theproject. Detailed design issues will be discussed with property owners as part <strong>of</strong> right-<strong>of</strong>-waynegotiations. Continued coordination will occur with property owners as the project moves<strong>for</strong>ward.The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.031 | P age


April 19, 2011Mr. Robert BoylePresidentHanson Industries, Inc.15807 E. Indiana Ave.Spokane, WA 99216Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to February 21, 2011 Scoping Comment LetterDear Mr. Boyle:We received your email dated February 21, 2011, in response to our scoping letter <strong>for</strong> theproposed I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Our response is categorized by your fivecomments.Item 1: Construction <strong>of</strong> the project will require a Construction Stormwater General Permit underthe National Pollutant Discharge Elimination (NPDES) program, as well as a StormwaterPollution Prevention Plan (SWPPP) and implementation <strong>of</strong> best management practices (BMPs)to control stormwater run<strong>of</strong>f and sediment erosion. Stormwater run<strong>of</strong>f from the construction andoperation <strong>of</strong> the Proposed Action would be designed to be retained on-site. Concept-level designdetails on stormwater management <strong>for</strong> the project have been addressed in Chapter 3 <strong>of</strong> the<strong>Environmental</strong> <strong>Assessment</strong> (EA). No impacts will occur to the Spokane River.Item 2: The project includes the construction <strong>of</strong> an extension <strong>of</strong> W. Riverbend Avenue west <strong>of</strong>the proposed interchange to connect to properties in that area. It would also provide necessaryimprovements to the North Idaho Centennial Trail. Access to existing businesses southwest <strong>of</strong>the interchange will be maintained during construction <strong>of</strong> the interchange. Utilities will beaddressed during final design in accordance with the Idaho Transportation Department’s Guide<strong>for</strong> Utility Management and <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>’ standards. Details on the Proposed Action designhave been addressed in Chapter 2 <strong>of</strong> the EA and potential business impacts have been addressedin Chapter 3 <strong>of</strong> the EA.Item 3: Several intersections will be signalized as part <strong>of</strong> the Proposed Action as detailed in theInterchange Justification Report. A visual representation <strong>of</strong> the Proposed Action includingsignalized intersections has been included in Chapter 2 <strong>of</strong> the EA.Item 4: The existing W. Riverbend Avenue will be re-aligned to connect to Pointe Parkway andthe interchange. A W. Riverbend Avenue extension will also provide connectivity west <strong>of</strong> the1 | P age


Mr. Robert BoyleApril 19, 2011interchange, where it will be a two-lane collector road with sidewalk on the south side, a twowayleft turn lane west <strong>of</strong> the interchange, and turn lanes at the appropriate intersections. Therealignment <strong>of</strong> Riverbend Avenue falls within the guidance provided by “Practical Solutions <strong>for</strong>Highway Design” in that it is local roadway (non-NHS) and the design recognizes constrainedright-<strong>of</strong>-way availability. The proposed design concept has been discussed with the governingagencies during the project planning process.Item 5: Visual resources have been considered and evaluated in the EA. Visual renderings <strong>of</strong> theinterchange and surrounding area have also been provided in Chapter 3 <strong>of</strong> the EA.The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.032 | P age


April 19, 2011Mr. Bruce CyrProperty ManagerJacklin Land Co.4752 W. Riverbend Ave<strong>Post</strong> <strong>Falls</strong>, ID 83854Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to March 28, 2011 Scoping Comment LetterDear Mr. Cyr:We received your email dated March 28, 2011, in response to our scoping letter <strong>for</strong> the proposedI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Our response is categorized by the general themes in yourcomments.On-going Negotiations: There are several items that are still in negotiations with neighboringproperty owners; the design team is still evaluating the impacts <strong>of</strong> several items related to finaldesign. Property agreements will be negotiated with property owners subject to final designrequirements <strong>of</strong> the project. These agreements will address right-<strong>of</strong>-way and compensation,easements, liability, business impacts, and local connectivity. Indemnification issues will also beaddressed at that time. Continued coordination will occur with property owners as the projectmoves <strong>for</strong>ward.Right-<strong>of</strong>-Way and Easements: As stated above, we recognize these issues are still in negotiations.Continued coordination will occur with property owners as the project moves <strong>for</strong>ward.Construction Impacts: The project includes the construction <strong>of</strong> an extension <strong>of</strong> W. RiverbendAvenue west <strong>of</strong> the proposed interchange to connect to properties in that area. It would alsoprovide necessary improvements to the North Idaho Centennial Trail. Access to existingbusinesses southwest <strong>of</strong> the interchange will be maintained during construction <strong>of</strong> theinterchange.Utilities and “Late-Comer Fees”: Utilities will be addressed during design in accordance withthe Idaho Transportation Department’s Guide <strong>for</strong> Utility Management and <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>’standards.1 | P age


Mr. Bruce CyrApril 19, 2011Encroachment and Detailed Design Features: Detailed design issues, such as retaining walls,entrance road design, signs, flags, gates, fencing, scales, and billboards are not yet finalized andwill be discussed with property owners as part <strong>of</strong> the final design process and right-<strong>of</strong>-waynegotiations. Continued coordination will occur with property owners as the project moves<strong>for</strong>ward.The project schedule indicates that the draft EA will be available <strong>for</strong> review in late Spring 2011.You will receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.032 | P age


April 29, 2011Elaine Somers<strong>Environmental</strong> Review and Sediment Management UnitU.S. <strong>Environmental</strong> Protection Agency, Region 101200-6th Ave., Suite <strong>90</strong>0, ETPA-088Seattle, WA 98101Subject:I-<strong>90</strong>, <strong>Beck</strong> <strong>Road</strong> Interchange, Kootenai CountyITD Project No. A010 (963), Key No. 010963Response to March 31, 2011 Scoping Comment LetterDear Ms. Somers:We received your letter dated March 31, 2011, in response to our scoping letter <strong>for</strong> the proposedI-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project. Your comments are outlined below in italics and responsesare provided below the comment:Air Quality/Air Toxics and Diesel ParticulatesThe NEPA document should characterize the project area air quality impacts, particularly thenear roadway effects <strong>of</strong> criteria pollutants and mobile source air toxics (MSATs) that wouldpotentially result from the project. Identify sensitive receptor locations and populations to airemissions from both construction and operation <strong>of</strong> the facility.Response: The <strong>Environmental</strong> <strong>Assessment</strong> (EA) (Section 3.10) addresses air quality impactsassociated with the Proposed Action. The evaluation is consistent with the Federal HighwayAdministration (FHWA) guidance, which includes addressing carbon monoxide, particulatematter, and MSATs. The project is not within a federally designated air quality non-attainmentor maintenance area nor is it within an Idaho Department <strong>of</strong> <strong>Environmental</strong> Quality (IDEQ) airquality area <strong>of</strong> concern.Construction Mitigation MeasuresAir toxics emissions, particularly diesel exhaust, are known or suspected to cause cancer orother serious health effects, such as respiratory, neurological, reproductive, and developmentaleffects. We recommend augmenting the standard ITD air quality construction specifications toemphasize reducing diesel and other emissions from construction vehicles and equipment.Include and commit to implementing a suite <strong>of</strong> construction mitigation measures, such as thosefrom the Clean Construction USA Web site at http://www.epa.gov/otaq/diesel/construction/.Measures such as diesel engine retr<strong>of</strong>it technology in <strong>of</strong>f-road equipment would greatly help toreduce air toxics and diesel particulate emissions. Such technology may include diesel oxidationcatalyst/diesel particulate filters, engine upgrades, engine replacements, newer model yearequipment, use <strong>of</strong> biodiesel, or combinations <strong>of</strong> these strategies.1 | P age


Ms. Elaine SomersApril 29, 2011Response: Construction specifications <strong>for</strong> the project will require contractors to comply withapplicable federal, state, and local air-quality standards and emission limitations <strong>of</strong> the Clean AirAct. During construction, contractors will be required to use methods and devices that areavailable to control, prevent, and otherwise minimize atmospheric emissions or discharges <strong>of</strong>atmospheric contaminants. ITD Standard Specifications and Best Management Practices(BMPs) in the ITD Erosion and Sediment Control manual will be followed. These measures arein accordance with the Idaho Administrative Procedures Act (IDAPA) 58.01.01, Sections 650through 651 and IDEQ guidelines. Air Quality Mitigation is outlined in Chapter 3.10 <strong>of</strong> the EA.Indirect and Cumulative Effects: Stimulated Travel and GrowthWhen examining existing land use, zoning, and local land use plans <strong>for</strong> the project area, we alsorecommend analysis and disclosure <strong>of</strong> the potential <strong>for</strong> stimulating additional travel anddevelopment in the project vicinity and beyond.Response: <strong>City</strong> <strong>of</strong> <strong>Post</strong> <strong>Falls</strong>’ staff was interviewed as part <strong>of</strong> the EA (Section 3.7Socioeconomics and Land Use) and questions were asked <strong>of</strong> the staff <strong>of</strong> their opinion aboutinduced development associated with the project. The general consensus was that the ProposedAction would likely accelerate the pace <strong>of</strong> commercial development in the project area; however,the area would ultimately be developed with or without the Proposed Action. The ProposedAction provides a benefit <strong>for</strong> travel overall by reducing congestion on the existing interchangesand also on several <strong>of</strong> the local roads.Aquatic ResourcesInclude riparian areas and the hyporheic zone <strong>of</strong> the Spokane River in addition to the analysis <strong>of</strong>potential impacts to floodways, floodplains, and wetlands.Response: The project team conducted field surveys to identify and assess Waters <strong>of</strong> the U.S.and associated special aquatic sites within the project area that would be potentially impacted bythe Proposed Action. No evidence was found <strong>of</strong> wetland hydrology, wetland vegetation and/orhydric soils that could support wetlands at the project site or adjacent to the site.The Spokane River flows from east to west on the south side <strong>of</strong> the interchange and is the onlynatural drainage in the area. The I-<strong>90</strong> <strong>Beck</strong> <strong>Road</strong> Interchange project would not encroach on theSpokane River, and, with the implementation <strong>of</strong> stormwater collection measures, no impactswould occur to the Spokane River. The footprint <strong>of</strong> the Proposed Action is outside <strong>of</strong> the 100-year floodplain. Chapter 3 <strong>of</strong> the EA addresses Wetlands and Water <strong>of</strong> the US and SurfaceWater, Floodplains, and Groundwater.Ecological ConnectivityAnalyze the potential <strong>for</strong> fragmentation <strong>of</strong> habitats and ecological processes. Ensure thatterrestrial and aquatic habitats, hydrology, and other ecological processes remain connected toenable safe species movement in the landscape and to protect ecosystem structure, function, andservices.2 | P age


Ms. Elaine SomersApril 29, 2011Response: The project site has little natural habitat, as the area has been disturbed and mostlydeveloped. Vegetation north <strong>of</strong> I-<strong>90</strong> is mostly weed species with some native grasses and <strong>for</strong>bs.South <strong>of</strong> I-<strong>90</strong>, the project area is developed into roads, parking lots, and buildings with little tono remaining natural vegetation or habitat. Section 3.5 <strong>of</strong> the EA addresses biological resourcesincluding vegetation, Threatened and Endangered Species, and wildlife.The draft EA is expected to be available <strong>for</strong> review in late spring or early summer 2011. Youwill receive notification <strong>of</strong> availability at that time.Sincerely,HDR Engineering, Inc.Karen M. Doherty, P.E.Project Managercc:Loren Thomas, ITD, HQDamon Allen, ITD, District 1Sue Sullivan, ITD, HQErich Grosse, Foursquare PropertiesHDR File 67568, 4.4.033 | P age

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!