Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Ordinance 09-033 Adopting New Street Standards
CITY OF SPOKANE VALLEY SPOKANE COUNTY, WASHINGTON ORDINANCE NO. 09-033 AN ORDINANCE OF THE CITY OF SPOKANE VALLEY, SPOKANE COUNTY, WASHINGTON MODIFYING UNIFORM DEVELOPMENT CODE TITLES 17.80, 18.30, 18.50,22.20, 22.50,22.130 AND 24.50 OF THE SPOKANE VALLEY MUNICIPAL CODE, ADOPTING NEW STREET STANDARDS, REMOVING ENGINEERING REQUIREMENTS INCORPORATED IN THE STREET STANDARDS, AND CLARIFYING LANGUAGE. WHEREAS, Spokane County adopted Standards for Road and Sewer Construction effective April 3, 2001 which included roads and sewers within the City of Spokane Valley; and WHEREAS, the City of Spokane Valley previously adopted Ordinance 33 which became effective on the date of incorporation; and WHEREAS, Ordinance 33 adopted by reference the Spokane County Standards for Road and Sewer Construction as interim standards for road construction within the City; and WHEREAS, after the date of incorporation, the City of Spokane Valley intended to review, revise,and as necessary develop its own standards for road construction; and WHEREAS, the City of Spokane Valley previously adopted Ordinance 07-015 on the 25th day of September,2007,which repealed Ordinance 33; and WHEREAS, Ordinance 07-015 adopted the Uniform Development Code (UDC) which provides regulations for land use including the Spokane County Standards for Road and Sewer Construction; and WHEREAS,the UDC became effective on October 28, 2007; and WHEREAS, in order to maintain the proper function of street infrastructure, maintain and improve street safety, and provide for future street expansion within the City, it is necessary to update the City of Spokane Valley standards for road construction; and WHEREAS, the proposed Street Standards are consistent with the Transportation goals and policies of the Comprehensive Plan; and WHEREAS, study sessions were held with the Planning Commission on March 26, 2009 and April 9,2009; and WHEREAS, a public hearing was held by the Planning Commission on September 24, 2009 and the Planning Commission recommend approval of the Street Standards generally as submitted; and WHEREAS, In accordance with RCW 36.70A.106A, copy of the proposed Street Standards was sent to the Department of Commerce on December 22, 2008, and the code revisions were sent on October 19, 2009. NOW THEREFORE, the City Council of the City of Spokane Valley, Washington do ordain as follows: Ordinance 09-033 Street Standards Page 1 of 18 Section 1. SVMC Title 17.80.030. This ordinance makes changes to SVMC Title 17.80.030 Table 17.80-I —which is modified as follows: Table 17.80-1—Permit Type and Land Use Application Type Land Use and Development Application SVMC Cross Reference Accessory dwelling units 19.40.100 Administrative determinations by community development director, public Multiple works director, or building official Administrative exception 19.140 Administrative interpretation 17.50.010 Boundary line adjustments and eliminations 20.80 Home occupation permit 19.40.140 Right-of-way permits 22.130.100 Typel Shoreline permit exemption(dock permit) 21.50 Site plan review 19.130 --------- Temporary use permit 19.160 Time extensions for preliminary subdivision, short subdivision or binding site 20.30.060 plan Floodplain development 21.30 Building permits not subject to SEPA 21.20.040 Grading permits 24.50 Binding site plan—Preliminary and final 20.50 Binding site plan—Change of conditions 20.50 Wireless communication facilities 22.120 Subdivision—Final 20.40 Type II Plat alterations— Final 20.60 SEPA threshold determination 21.20.060 Preliminary short subdivision, binding site plan—Change of conditions 20.30 Shoreline substantial development permit 21.50 Short subdivision—Preliminary and final 20.30, 20.40 Conditional use permits 19.150 Subdivisions—Preliminary 20.30 Type Variance 19.170 III Preliminary subdivision—Change of conditions 20.50 Zoning map amendments (site-specific rezones) 19.30.030 Type Annual Comprehensive Plan amendments (text and/or map) 17.80.140 Ordinance 09-033 Street Standards Page 2 of 18 IV Area-wide zoning map amendments 17.80.140 Development code text amendments 17.80.150 Section 2. SVMC Title 18.30.010 and 18.50.010. This ordinance makes changes to SVMC 18.30.010 and 18.50.010—these sections of the code are modified to read as follows: 18.30 Community Development Department 18.30.010 Responsibilities The community development department shall have the following responsibilities: A. To review all development permits including street and drainage construction plans to ensure conformance with the appropriate provisions of the Spokane Valley Municipal Code(SVMC) and those additional standards adopted by the code. B. To inspect the construction of all development improvements to ensure conformance with the appropriate provisions of the SVMC and those additional standards adopted by the code. C. To regularly update the comprehensive plan. D. To regularly update the street standards with the concurrence of the public works department. E. To regularly recommend updates to the Spokane Regional Stormwater Manual with the concurrence of the public works department. ' F. To make recommendations concerning proposed changes and amendments to zoning regulations. G. To issue all right of way permits pursuant to SVMC 22.130.100. H. To ensure compliance with SVMC 21.30 Floodplain Regulations I. To coordinate the review of development projects for transportation currency as defined by SVMC 22.20. J. To administer the provisions of the building codes adopted by the city council. K. To make recommendations concerning amendments to the adopted building codes. L. To enforce the provisions of SVMC Title 24. M. To enforce the provisions of the nuisance ordinances in conformance with the requirements of SVMC Chapter 7.05. N. To advise the planning commission and city council where appropriate concerning matters relating to any of the above. 18.50 Public Works Department 18.50.010 Responsibilities. The public works department shall have the following responsibilities: A. To review all street and drainage construction plans for city capital improvement projects to ensure conformance with the applicable provisions of the Spokane Valley Municipal Code (SVMC)and those additional standards adopted by the code. B. To inspect the construction of improvement projects to ensure conformance with the applicable provisions of the SVMC and those additional standards adopted by the code. C. To oversee the planning, design and construction of the city capital improvement projects and public infrastructure for conformance with the civil engineering provisions of the SVMC. Ordinance 09-033 Street Standards Page 3 of 18 D. To review and approve projects for transportation concurrency as defined by SMC 22.20. and all other tasks set forth in the Model Traffic Code. E. To oversee the storm and surface water utility as defined in SVMC 3.80 and to regularly update to the Spokane Regional Stormwater Manual. F. To review, recommend and concur on changes to the Street Standards. G. To review and make recommendation as needed for all project permits as set forth in SVMC 17.80. H. To advise the planning commission and city council where appropriate concerning matters relating to any of the above. Section 3. SVMC Title 22.130. This ordinance makes changes to SVMC Title 22.130, this title adopts the street standards and is hereby established to read as follows: Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS 22.130.010 Purpose. The purpose of this chapter is to: A. Maintain the proper function of street infrastructure; B. Maintain and improve the street safety; C. Provide for future street expansion; D. Identify requirements that may be imposed upon development projects and permits defined in 22.130.020. 22.130.020 Regulated Activities. All new development approvals and permits as set in SVMC 17.80, unless exempt pursuant to SVMC 17.80.040 shall comply with this chapter. 22.130.030 Authority to Develop and Administer Standards The development services senior engineer, under the authority of the community development director, shall develop and administer the Spokane Valley Street Standards (SVMC 22.130.040) and require development projects to provide transportation improvements, dedicate right-of-way and border easements, and future acquisition areas. These improvements will be required to achieve the purpose of this Chapter and goals of the currently adopted comprehensive plan. 22.130.040 Street Standards. Pursuant to RCW 35A.11.020 and 35A.12.140, the City adopts, by reference, the City of Spokane Valley Street Standards (Street Standards), and as it may be amended from time to time. The city clerk shall maintain a copy on file. 22.130.050 Manual on Uniform Traffic Control Devices. The Washington Manual on Uniform Traffic Control Devices (MUTCD), and as it may be amended from time to time, is hereby adopted by reference. (Ord. 07-015 § 4, 2007). 22.130.060 Development Project and Permit Review Process. Following submittal of a completed application pursuant to SVMC 17.80, the project shall be reviewed to determine compliance with all applicable regulations and standards. Additional material and/or analysis may be required to demonstrate compliance. • Ordinance 09-033 Street Standards Page 4 of 18 22.130.070 Required Improvements. A. Prior to the issuance of any approvals for development projects or permits subject to the provisions of this chapter, the development services senior engineer shall determine the extent and type of street improvements, right-of-way/border easements dedication or designation of future acquisition areas required, to the extent allowed by the law, and pursuant to the following: 1. The comprehensive plan; 2. The arterial street map; 3. The street standards(SVMC 22.130.040); 4. The manual on uniform traffic control devices identified in SVMC 22.130.050; 5. The local street plan; 6. Information submitted by the applicant including any preliminary site plans, engineering reports, or other relevant data; and, 7. A determination of the function, safety, efficiency and coordinated future expansion needs of the roadway system to serve the traveling public and emergency vehicles; and, 8. Portions of the uniform development code, SVMC Title 17-25 that specifically identify required future roadways, streets, or other right-of-ways, including but not limited to the Spokane Valley-Sprague Corridors Subarea plan pursuant to SVMC 19.1 10.020. B. Requirements may include but are not limited to: 1. The extent and type of required street improvements pursuant to SVMC 22.130.040; 2. The extent of additional and/or new right-of-way and /or border easement needed to support the required improvements pursuant to SVMC 22.130.040; 3. Designation of future acquisition areas pursuant to SVMC 22.130.080; 4. Participation in capital improvement projects as included on the adopted six year street improvement plan. 22.130.080 Future acquisition areas. A. When a future acquisition area is designated, a title notice shall be completed and recorded with the county auditor. The notice shall run with the land and shall not be removed or amended prior to approval. The notice shall be recorded as soon as possible and, in all cases, prior to the issuance of a building permit. The notice shall: 1. Include the tax parcel number and the full legal description; 2. Make reference to any related approval file number or permit numbers; 3. Include an exhibit showing street names, future acquisition areas, right-of-ways, and their dimensions; 4. Identify any limitations for improvements or features within the acquisition boundary(ies); 5. Indicate that the future acquisition area is private property; 6. Identify the responsibility for relocation or loss of interim features or improvements within the future acquisition areas; and 9. Be mailed to the property owner's and taxpayer's address as shown in the current Spokane County assessor's/treasurer's records, if a complete mailing address is indicated. The establishing agency may approve the amendment and removal of the title notice if the arterial street plan, the local street map or other conditions change and the recorded title notice is no longer necessary. If the City initiates the amendment or removal of the title notice, the property owners will be notified of the change. B. Building Setback. The required setback of buildings as specified in the underlying zone classification shall be measured from the future acquisition area boundary. Exceptions to the full setback may be administratively granted if: I. An existing parcel or lot equals or is up to five percent larger than the minimum lot area required in the underlying zone; or, 2. An existing parcel or lot has an existing building proposed for expansion. Ordinance 09-033 Street Standards Page 5 of 18 3. The applicant adequately demonstrates a site design or use limitation for the existing property. Such exceptions may be granted; provided,that: i. The property is not part of a zone reclassification and/or subdivision application; and, ii. The property has no reasonable alternative site design solution feasible; and, iii. A title notice is recorded pursuant to this section that further identifies likely impacts (such as noise, crowding, loss or relocation of improvements) to the site when the street is widened in the future; and iv. The building is located at the greatest setback possible, but in any case shall be no closer than one-quarter of the required setback from the future acquisition area boundary and shall not be located within the future acquisition area. C. Landscaping. Significant landscape features, such as trees, shall be located in such a manner that when the street is widened in the future a significant portion of such landscaping features, such as matured trees, will not need to be destroyed or relocated. A majority of the trees required in the current landscaping areas shall be planted eight feet from the future acquisition area boundary within the future planting strip and shall be spaced no less than 60 feet from one another. D. Parking. All on-site parking required by the underlying zone classification shall be located outside the future acquisition area. If no reasonable site design solution complying with parking location requirements is feasible, exceptions to these requirements may be administratively granted if: I. An existing parcel or lot equals or is up to five percent larger than the minimum lot area of the underlying zone; 2. An existing parcel or lot has an existing building proposed for expansion; or 3. The applicant adequately demonstrates a site design or use limitation for the existing property. Such exceptions may be granted; provided, that: i. The property is not part of a zone reclassification and/or subdivision application; and, ii. The property has no reasonable alternative site design solution feasible; and, iii. A title notice is recorded pursuant to this section that further identifies likely impacts to the site when the street is widened in the future; and iv. The fewest number of parking stalls is located in the future acquisition area as possible and, in any case, shall contain no more than one-quarter of the required parking stalls for the site. E. Drainage Improvements. All required drainage facilities and structures for the site shall be located outside the future acquisition area. A portion of the drainage facility improvement may be temporarily allowed within the future acquisition area if a conditional use permit is issued pursuant to the provisions of SVMC 22.130.090. The permit shall provide for the relocation of the drainage facility to an alternative site by the property owner when the street is widened. The permit shall identify the alternate location and the means of relocating the facility. F. Physical Structures, Improvements and Utilities. Physical structures (such as signs, fencing, and architectural features) and improvements (such as site drainage, 208 drainage swales, landscaping, and parking) shall not be located within the future acquisition area unless a conditional use permit has been issued pursuant to SVMC 22.130.090. If permitted, they shall be considered "interim" and shall be relocated or removed if the right-of-way is widened in the future, subject to the conditions of the conditional use permit. All developers, agencies and purveyors installing utilities in, adjacent to or across rights-of-way shall show the future acquisition area and boundary (ies) on construction plans or drawings. Impacts from the future street widening and other relocation cost shall be considered when designing and siting utilities and improvements. (Ord. 08-006 § 1, 2008). 22.130.090 Conditional use permit. A. The City may temporarily allow, as an interim conditional use, site features or improvements located within or adjacent to the future acquisition area that are in conflict with the provisions of this chapter; provided, that a hardship can be demonstrated and the use can be reasonably conditioned and Ordinance 09-033 Street Standards Page 6 of 18 restricted to ultimately accomplish the intent of this chapter. Examples of site features or improvements include driveways, drainage facilities and structures, parking stalls, utilities and signs. B. Permit Required. Conditional use permits shall be issued administratively at or before the time development approvals and permits are granted. Conditional use permits shall, at a minimum, specify the temporary or interim use allowed, the conditions of the permit, the provisions for and timing of removal, relocation or installation and the responsibility for the cost of relocation, removal or installation. C. Appeals. Any appeal of the administrative decision shall be heard pursuant to Chapter 17.90 SVMC, Appeals. All conditional use permits shall be referenced by a title notice pursuant to SVMC 22.130.080. (Ord. 08-006 § 1, 2008). 22.130.100 Right-of-way permit and use requirements. A. Right-of-Way Permit Applicability. Unless exempt from permit requirements, a right-of-way permit is required of any person or company who performs construction work or otherwise engages in activity within existing City rights-of-way, or on City-owned infrastructure. Right-of-way permit authorizes a permittee to perform work or conduct activity in a right-of-way or easement. Permits shall not be required for the following: 1. Work done by or for the City within its right-of-way. 2. Work that is two hours or less in duration, as long as that work does not require the closure of more than 50 percent of a non-arterial street, does not close any lanes on an arterial street, does not involve excavation within the right-of-way, or does not involve cutting or placement of pavement, sidewalks, curbs or gutters. Exemption from the permit requirements of the SVMC shall not be deemed to grant authorization for any work to be done in any manner in violation of the provisions of the SVMC or any other laws, ordinances or standards of this jurisdiction. B. Expiration. Right-of-way permits issued between April 1 and September 30 are valid for 30 days after the date of issuance, with a one-time 30 day extension available. Right-of-way Permits issued between October 1 and March 31 shall be valid until the following April 30. C. Emergency Repairs. In the case of an emergency repair, a private or public utility may commence work prior to obtaining a permit, provided the person responsible for the work obtains a construction permit within 48-hours after work is commenced or on the first City business day following said elapsed 48-hour period. D. Right-of-Way Permit — Application. No right-of-way permit shall be issued unless a written application is submitted and approved by the City. The application shall, at a minimum, contain the following: 1. Construction plans or drawings approved by the City, if required; 2. A traffic control plan, if the work closes more than 50 percent of the non-arterial street, or closes any lanes on an arterial street; 3. The period of time during which the right-of-way will be obstructed; and 4. Proof of the contractor's and all subcontractors' state licensing, insurance and requirements. Depending upon the nature and extent of the construction activity or work, the City may require engineering, restoration and drainage plans prepared by a Washington-licensed engineer at the applicant's sole cost and expense. At the discretion of the City, a multiple-use permit may be available for licensed and bonded businesses and public utilities. The multiple-use permit fee will be established by resolution in the master fee schedule. The multiple-use permit shall expire at the end of the City fiscal year. The administrative regulations governing the multiple-use permit shall be written and approved by the City. Failure to comply with the administrative regulations shall be a violation of this code. E. Right-of-Way Permit Fees. Permit fees shall be assessed in accordance with the currently adopted Spokane Valley Master Fee Schedule.F.Notice Required. The applicant shall give to the City notice not less than 48 hours before any work or activity is commenced and shall notify the City upon completion of the same. If a traffic control plan is required to be submitted with the application, the applicant shall give Ordinance 09-033 Street Standards Page 7 of 18 the City not less than 72 hours' notice. In the event of an unexpected repair or emergency, work may be commenced as required under the circumstances. Unexpected repairs and emergency work shall comply with all other requirements of this section. G. Construction Standards. All work within the City right-of-way shall be in accordance with adopted City standards in effect at the time of the application for the permit. These include but are not limited to current versions of the Spokane Valley Street Standards, the Spokane Regional Stormwater Manual, the Manual on Uniform Traffic Control Devices (MUTCD); Washington State Department of Transportation (WSDOT) Standard Specifications for Road, Bridge and Municipal Construction; and applicable standards of the American Public Works Association (APWA). H. Maintaining Access. In the event it is necessary for the permittee to excavate the entire width of the street, no more than half of the street shall be opened for construction and closed to traffic at one time. Such portion of the work shall be backfilled and completed before the remaining portion of the street may be excavated. If it is impossible, infeasible or unsafe to permit the work while maintaining an open lane for traffic, the City may, with the concurrence of the chief of police and fire chief, permit the street to be blocked for a short period of time where suitable detours can be provided and the public will not be unnecessarily inconvenienced. The permittee shall furnish facilities, such as bridges or other suitable means, or clearly identify appropriate detours, to allow the flow of traffic without unnecessary congestion. I. Traffic Control. Any person or company that performs construction work or otherwise engages in activity within the existing City rights-of-way, or on City-owned infrastructure, is responsible for all traffic control and assumes the responsibility to maintain appropriate signage, signals and barricades that protect the public safety, in accordance with the MUTCD. The person or company shall provide for the safe operation of all equipment,vehicles and persons within the right-of-way. J. Damage to Existing Infrastructure. All damage to existing public or private infrastructure and/or property during the progress of the construction work or activity shall be repaired by the permittee. Methods and materials for such repair shall conform to adopted City standards. If the permittee fails to furnish the necessary labor and materials for such repairs, the City shall have the authority to cause said necessary labor and materials to be furnished by the City and the cost shall be charged against the permittee. Such charge shall be immediately paid by the permittee and shall, if not paid on demand, be deemed a valid claim on the bond filed with the City. K. City's Right to Restore Right-of-Way and Easements. If the permittee fails to restore any City right- of-way or easement to its original and proper condition upon the expiration of the time fixed by such permit or shall otherwise fail to complete the right-of-way construction work covered by such permit or if the work of the permittee is defective and the defect is discovered within one year from the completion of the right-of-way construction work, the City or designee shall have the right to do all work and things necessary to restore the right-of-way and/or easement and to complete the right-of-way construction work. The permittee shall be liable for all costs and expenses of restoration or completion. The City shall have a cause of action for all fees, expenses and amounts paid for such work. Following demand, the City may enforce its rights pursuant to this section. No additional permits shall be granted until the invoice for City-performed work has been paid. L. Insurance — Evidence. Permittee, prior to the commencement of construction hereunder, shall furnish the City satisfactory evidence in writing that the permittee has in force during the performance of the construction work or activity, commercial general liability insurance of not less than $1,000,000 per occurrence and $2,000,000 general aggregate duly issued by an insurance company authorized to do business in this state. In addition, the policy shall name the City as an additional named insured. The City may reduce the insurance limits if good cause exists. M. Indemnification and Hold Harmless. The permittee shall defend, indemnify and hold harmless the City, its officers, officials, employees and volunteers from any and all claims, injuries, damages, losses or suits, including attorney fees, arising out of the permit issued under this section except as may be caused by the negligence or willful conduct on the part of the City. Ordinance 09-033 Street Standards Page 8 of 18 N. Rules and Policy. To implement the right-of-way permit and provide for the public health and safety, the City, under the supervision of the city manager, may develop and adopt rules, policies and forms consistent with this section. All adopted rules, policies and forms shall be filed with the city clerk. O. Violations — Penalties. Any person violating the provisions of this section shall be subject to all enforcement actions and penalties as found in SVMC 17.100 22.130.110 Liability. The express intent of the City of Spokane Valley is that the responsibility for compliance with the provisions of this chapter shall rest with the permit applicant and their agents. This chapter and its provisions are adopted with the express intent to protect the health, safety, and welfare of the general public and are not intended to protect any particular class of individuals or organizations. (Ord. 07-015 § 4, 2007). Section 4. SVMC Title 22.20. This ordinance makes changes to SVMC 22.20.020, 22.20.040, and 22.20.080—these sections of the code are modified to read as follows: 22.20.020 Concurrency review. A. All project permits/project applications except for those exempt as set forth in subsection C of this section shall be subject to concurrency review at the time an application is submitted. Concurrency shall be determined by evaluating the anticipated impact of the application against the level of service (LOS) set forth in the Comprehensive Plan. A certificate of concurrency issued by the reviewing authority shall be required prior to approval of any nonexempt application. B. A finding of concurrency requires that adequate facilities are available when the service demands of development occur, or in the case of transportation "concurrent with development" shall mean that improvements or strategies are in place at the time of development, or that a financial commitment is in place to complete the improvements or strategies within six years. The cumulative impact of development should be considered when making this determination. C. The following shall be exempt from concurrency review: 1. Project permits that were issued, or project applications that were determined to be complete (see Chapter 36.70B RCW) prior to the effective date of these concurrency regulations. 2. The first renewal of a previously issued, unexpired project permit; provided, that substantial progress has been made as determined by the appropriate review authority. 3. Any project permit that will have transportation impacts of less than 10 peak hour vehicular trips, and that will not change the traffic volumes and flow patterns in the afternoon peak travel period, as determined by the senior traffic engineer. 4. The following project permit actions: a. Boundary line adjustments; b. Final subdivisions/final PRDs/final short plats/final binding site plans; c. Temporary use permit; d. Variances. 5. Proposed project permits/project applications that do not create additional impacts on transportation facilities. Such projects may include but are not limited to: a. Any addition or accessory structure to a residence with no change or increase in the number of dwelling units over four units; b. Interior renovations with no change in use or increase in number of dwelling units over four units; c. Any addition, remodel, or interior completion of a structure for use(s) with the same or less intensity as the existing use or previously approved use. (Ord. 07-015 § 4, 2007). Ordinance 09-033 Street Standards Page 9 of 18 22.20.040 Application procedures. A. Applications for concurrency review shall be submitted to the City. 1. Concurrency review shall be performed for the specific property, uses, densities and intensities, and traffic distribution information provided by the applicant/property owner and shall include any project phasing proposed by the applicant. 2. The City may request additional information in order to make a determination. 3. All applications shall be circulated for comment to the appropriate departments or agencies. 4. The project permit may be conditioned to assure adequate facilities are available to meet the demand generated by the project. If the project is approved, a concurrency certificate shall be issued to the property owner, his heirs and assigns. 5. If adequate facilities cannot be made available to maintain adopted level of service (LOS), the project application shall be denied. 6. The concurrency certificate shall automatically be voided if the project permit has been withdrawn, expires, or is otherwise cancelled. B. Concurrency Certificate. 1. Shall apply only to the specific land uses, densities, intensities and project described in the application and project permit; 2. Is not transferable to other property, but may be transferred to new owners of the same property; 3. Shall remain valid so long as the accompanying project permit has not expired or been revoked; 4. Is valid for any modification of the permits for which the certificate was issued so long as such modification does not require the applicant to obtain a new project permit; and 5. Shall only be issued upon payment of any traffic review fee due. C. Any capacity that is not used because the full extent of the development is not built shall be considered available capacity for a period not to exceed 6 years . D. Concurrency Certificate Fees. Fees for issuing concurrency certificates shall be based on the currently adopted Spokane Valley Master fee schedule. (Ord. 07-015 § 4, 2007). 22.20.080 Transportation concurrency—Additional considerations. A. Transportation concurrency shall be in accordance with City of Spokane Valley Street Standards adopted pursuant to SVMC 22.130.040 Street Standards. Section 5. SVMC Title 22.50. This ordinance makes changes to SVMC 22.50.030, 22.50.040, 22.50.050, and 22.50.060. These titles are modified to read as follows: Figure 22.50-3 22.50..030 Off-street loading. A. Every building or part thereof erected or occupied for retail business, service, manufacturing, storage, warehousing, hotel/motel, industrial or any other use similarly involving the receipt or distribution by vehicles of materials or merchandise shall provide and maintain on the same premises loading space in accordance with the following requirements: 1. Off-street loading spaces shall measure as follows: a. When one space is required, it shall measure 12 feet wide, 30 feet long and 15 feet high (if a dock). b. When two or more spaces are required, they shall measure 12 feet wide, 60 feet long and 15 feet high (if a dock). Ordinance 09-033 Street Standards Page 10 of 18 2. Loading facilities located on the side of a building but not facing a street shall be set back from the front property line a minimum distance of 60 feet. 3. All parking, loading and maneuvering of trucks shall be conducted on private property. 4. Required passenger vehicle parking shall not be allowed within the truck dock apron space. 5. The minimum number of off-street loading spaces shown on the following table are required: Table 22.50-7—Loading Spaces Required Use/Gross Square Feet Required Loading Spaces Industrial, manufacturtng hole 'e;;iNiffg1 ise, similar u -" ' 10,000—40,000 square feet 1 space 40,001 —60,000 square feet 2 spaces 60,001 — 100,000 square feet 3 spaces Over 100,000 square feet 1 space for each 50,000 square feet or part thereof 3otelXmotel, restaurants 20,000—60,000 square feet 1 space 60,001 — 100,000 square feet 2 spaces Over 100,000 square feet 1 space for each 50,000 square feet or part thereof Hospitas, convalescen UZuM,rsi ng homes and similar institutons „ s"4 � • 10,000—40,000 square feet 1 space 40,000— 100,000 square feet 2 spaces Over 100,000 square feet 1 space for each 50,000 square feet or part thereof = p' tope§,,re ail and�oth�er�gotrunercialluses . � ��A� �'� +� 10,000—20,000 square feet 1 space 20,001 —50,000 square feet 2 spaces 50,001 — 100,000 square feet 3 spaces Over 100,000 square feet 1 space for each 50,000 square feet or part thereof B. Screening of Off-Street Loading Areas. 1. Off-street loading spaces and apron space shall not be located on the street side of any building in commercial or residential zones. In those instances where three or more sides of the building face dedicated streets, loading spaces and apron space shall be located at the rear or side of the building and screened from view of the abutting streets for a minimum of 35 feet in accordance with the provisions of SVMC 22.70.030(I). In the industrial zones, off-street loading spaces and apron space may be located on the street side of buildings providing that they are screened from view of the abutting streets for a minimum of 35 feet in accordance with the provisions of SVMC 22.70.030(1); 2.No loading dock or service bay doors shall be constructed on any portion of a front wall or on a side or rear wall within 60 feet of any front property line or adjacent to the street. (Ord. 08-007 § 1, 2008; Ord. 07-015 § 4, 2007). 22.50.040 Bicycle parking. Bicycle spaces are individual units within ribbon racks, inverted "U” racks, locking wheel racks, lockers,or other similar permanent structures accommodating five or more bicycles. Ordinance 09-033 Street Standards Page 11 of 18 A. Bicycle racks and/or storage shall be provided when 25 or more parking spaces are required, at a ratio of one rack for every 25 parking spaces. B. Required bicycle parking must be located within 50 feet of an entrance to the building or use. C. If bicycle parking is not visible from the street, a sign must be posted indicating the location of the bicycle parking spaces. D. All bicycle parking must be separated from motor vehicle traffic by a barrier, curb, post, bollard or other similar device. E. The property owner of a site shall have a continuing obligation to properly maintain any bicycle parking facilities on their property. (Ord. 07-015 § 4, 2007). 22.50.050 Landscaping in parking areas. See SVMC 22.70.030, Screening and buffering. (Ord. 07-015 § 4, 2007). Section 6. SVMC Title 24.50. This ordinance replaces SVMC Title 24.50 entirely. SVMC Title 24.50 is modified to read as follows: Chapter 24.50 Land Disturbing Activities 24.50.010 GENERAL A. General Applicability. This subtitle applies to all land disturbing activities, whether or not a permit is required. All land disturbing activities shall comply with this subtitle and the requirements set forth by SVMC Title 21 Environmental Controls and 22.130.040 Street Standards. B. Purpose. The purpose of this ordinance is to regulate all land disturbing activities to protect and safeguard the general health, safety, and welfare of the public residing within the City of Spokane Valley by: 1. Establishing procedures for issuance of permits, plan approval, and inspection of grading construction; and, 2. Controlling erosion and preventing sediment and other pollutants from leaving the project site during construction by implementing best management practices; and, 3. Reducing stormwater runoff rates and volumes, soil erosion and nonpoint source pollution, wherever possible, through stormwater management controls and to ensure that these management controls are properly maintained and pose no threat to public safety; and, 4. Protecting downstream properties and public infrastructure. C. Definitions. 1. Applicant is the private party or parties desiring to construct a public or private improvement within City right-of-way, easements, or private property, securing all required approvals and permits from the City, and assuming full and complete responsibility for the project. The Applicant may be the owner or the individual designated by the Owner to act on his behalf. 2. Clearing and grubbing includes, but it is not limited to, removing trees, stumps, roots, brush, structures, abandoned utilities, trash, debris, and all other material found on or near the surface of the ground in the construction area. Ordinance 09-033 Street Standards Page 12 of 18 3. Grading is the physical manipulation of the earth's surface and/or surface drainage pattern which includes surcharging, preloading, contouring, cutting, and/or filling. Grading activities fall into two general categories: engineered grading and regular grading. 4. Land disturbing activity result in a change in existing soil cover (vegetative or non- vegetative) or site topography. Land disturbing activities include, but are not limited to, demolition, construction, clearing and grubbing, grading and logging. 5. Site includes all the parcels included in the project. D. Permit Required. A separate permit shall be obtained for each site. No land disturbing activity, unless specifically exempted, shall be performed without first having obtained a permit. The following are the types of permit: 1. Engineered grading. Refer to SVMC 24.50.020 for general exemptions. Refer to SVMC 24.50.030 for applicability, additional exemptions, and permit requirements. All engineered grading shall comply with the Washington State Environmental Policy Act. 2. Regular grading. Regular grading is grading work that is not required to be engineered. Refer to SVMC 24.50.020 for general exemptions. Refer to SVMC 24.50.040 for applicability, additional exemptions, and permit requirements. 3. Clearing and grubbing permit. Refer to SVMC 24.50.050 for applicability, exemptions, and permit requirements. E. Fees. Permit fees, including plan review, shall be assessed in accordance with the currently adopted Spokane Valley Master Fee Schedule. F. Surety. The Applicant shall post a surety in an amount determined by the Development Services Senior Engineer. Acceptable surety instruments are cash savings assignments and letters of credit issued by a duly chartered financial institution. G. Inspection. All land disturbing activities shall be subject to inspection by the Development Services Senior Engineer. For all engineered grading permits, special inspection of grading operations and special testing shall be performed in accordance with the provisions of Chapter 9 of SVMC 22.130.40 Street Standards. If during an inspection, site conditions and/or construction of permanent items are found not be as shown in the permit application or approved plans, the permit may be deemed invalid. No land disturbing activity shall be undertaken, or continued, until revised plans have been submitted and approved. The Development Services Senior Engineer shall be notified when work.authorized by a permit issued subject to this chapter is ready for final inspection. Final approval shall not be granted until all work has been completed in accordance with the approved grading plans and any required reports have been submitted. H. Hazards. If the Development Services Senior Engineer determines that any land disturbing activity has or may become a hazard to life and limb, endanger property, cause erosion, or adversely affect drainage, the safety, use, stability of a public way or drainage channel, the owner shall be notified in writing. The owner is responsible to mitigate the hazard within the time specified by the Development Services Senior Engineer. If not corrected, the land disturbing activity shall be deemed to be a violation pursuant to SVMC 24.050.10 1. I. Violations. Unless exempt, any land disturbing activity performed without a permit shall be considered hazardous and a public nuisance, subject to all enforcement actions and penalties as found Ordinance 09-033 Street Standards Page 13 of 18 in SVMC Title 17. An investigation fee may be assessed pursuant to International Building Code Section 108.4. The fee is payable prior to the issuance of a permit. Payment of the investigation fee does not vest the illegal work with any legitimacy, nor does it establish any right to any permit for continued development of the project. Any person, firm, or corporation violating any of the provisions of this chapter shall be subject to fines as provided in Title 17 of this code. J. Construction Stormwater Permit. The Applicant shall contact Washington Department of Ecology (Ecology)to determine if a Construction Stormwater Permit is required. K. Changes in the Field. Revised plans may be required when changes are made to the approved grading plans. Land disturbing activities affected by such changes shall not continue until the revised plans are reviewed and approved by the Development Services Senior Engineer. 24.50.020 GRADING PERMIT—GENERAL EXEMPTIONS A grading permit, either engineered grading or regular grading, is not required for the following land disturbing activities: 1. Excavations which, meets all of the following: o Are less than 3 feet in height; and, o Have slopes flatter than 2:1 (H:V), and, o Do not exceed 50 cubic yards on any one lot. 2. Fills which, meets all of the following: o Are less than 2 feet in height; and, o Have slopes flatter than 2:1 (H:V),and, o Are not intended to support structures; and, o Do not obstruct a drainage course; and, o Do not exceed 50 cubic yards on any one lot. 3. An excavation below finished grade for basements and footings of a building, retaining wall, or other structure authorized by a valid building permit. This shall not exempt any fill made with the material from such excavation nor exempt any excavation having an unsupported height greater than 4 feet after the completion of such structure; 4. Cemetery graves; 5. Refuse disposal sites controlled by other regulations; 6. Excavations to facilitate the septic tank elimination program; 7. Mining, quarrying, excavating, processing, stockpiling of rock, sand, gravel, aggregate, or clay where established and provided for by law such operations do not affect the lateral support or increase the stresses in or pressure upon any adjacent or contiguous property; 8. Exploratory excavations under the direction of a geotechnical engineer or engineering geologists; Ordinance 09-033 Street Standards Page 14 of 18 • 24.50.030 ENGINEERED GRADING PERMITS A. Applicability. An engineered grading permit is required for the following land disturbing activities: 1. Grading in excess of 500 cubic yards; and, 2. Excavations with cut slopes equal to or steeper than 2:1 (WV) and heights greater than 2- 1/2 feet; and, 3. Excavations with cut slopes equal to or steeper than 10:1 (H:V) and heights greater than 4 feet; and, 4. Fill slopes equal to or steeper than 2:1 (H:V) heights greater than 2- 1/2 feet; and, 5. Fill slopes equal to or steeper than 10:1 (H:V) heights greater than 4 feet; and, 6. Grading in the floodplain; and, 7. Grading in Critical Areas identified in the SVMC Title 21; 8. Grading in a drainage channel; and, 9. Grading to support a building or structure of a permanent nature; and, 10. Grading associated with subdivisions pursuant to SVMC Title 20; and, I I. Grading for engineered driveways, regardless of the amount of excavation or fill required for construction; and, 12. Grading for all ponds, water features, and man-made lakes greater than 500 sq. ft. in surface area; and, 13. Major use permits and/or any other project likely to cause major land disturbances as determined by the City; and, 14. Grading to support other engineering works such as, but not limited to, tanks, towers, machinery, retaining wall, and paving; and, 15. Projects deemed to be a potential hazard. B. Exemptions. An engineered grading permit is not required for the following land disturbing activities: 1. Grading work already included in a building permit or land action application; 2. Grading work exempted per SVMC 24.50.020; and grading work not meeting the requirements of SVMC 24.50.030 A. In this latter case, the grading would be considered regular grading. C. Engineered Grading Permit Submittal Requirements. The minimum documents required for permit application are as follows: 1. Completed permit application; and, 2. Two sets of all required plans stamped by a civil engineer licensed in the State of Washington, • Ordinance 09-033 Street Standards Page 15 of 18 3. Two sets of all required reports, specifications, and supporting information prepared and stamped by a civil engineer or geologist licensed in the State of Washington, 4. Plans shall demonstrate compliance with the provisions of this Title, SVMC 22.130.40 Street Standards and all relevant laws, ordinances, rules, and regulations;' 5. Temporary Erosion and Sediment Control (TESC) plan. The TESC plan shall include all • of the minimum elements specified in SVMC 24.150 Spokane Regional Stormwater Manual Chapter 9 and Plan elements required in Chapter 4 of SVMC Title 22.130.040 Street Standards, as applicable. The TESC plan may also be prepared by a Certified Erosion and Sediment Control Technician. All erosion prevention and sediment control measures shall be maintained, including replacement and repair as needed. These minimum guidelines are not intended to resolve all project soil erosion conditions. The applicant is responsible for confining all soil on the project site and implementing additional measures as necessary to accommodate changing or unexpected site and weather conditions; 6. When required by the SVMC 22.130.040 Street Standards Chapter 5 and/or the Development Services Senior Engineer, a geotechnical evaluation demonstrating compliance with SVMC 22.130.040 Street Standards Chapter 5; 7. Drainage report demonstrating compliance with SVMC 24.150 Spokane Regional Stormwater Manual Chapter 3; 8. When required by the Development Services Senior Engineer, an engineering geology report including an adequate description of the geology of the site; 9. SEPA checklist D. Engineered Grading Permit Final Acceptance. The following items are required prior to final acceptance: 1. Inspection by a qualified professional hired by the Applicant; and, 2. As-graded grading plans; and, 3. A letter from the inspector that certifies that grading was conducted in accordance with the grading plan. Certification requirements shall be in compliance with SVMC 22.130.040 Street Standards. 24.50.040 REGULAR GRADING PERMIT A. Applicability. A grading permit is required for all grading operations unless exempted below. All grading shall comply with the Washington State Environmental Policy Act and SVMC 22.130.40 Street Standards. An engineered grading permit shall be required if the project meets the criteria specified in SVMC 24.50.030. B. Exemptions. A regular grading permit is not required for the following land disturbing activities: 1. Grading work already included in a building permit; 2. Work exempt under SVMC section 24.50.020 or already included in an engineered grading permit; C. Regular Grading Permit Submittal Requirements. The minimum documents required for permit application are as follows: 1. Completed permit application; and, Ordinance 09-033 Street Standards Page 16 of 18 2. Plans demonstrating compliance with Chapter 4 and 5 SVMC 22.130.40 Street Standards and all other applicable laws, ordinances, rules and regulations. The name of the owner and the name of the person who prepared the plan shall be included in all submitted plans and documents; and, 3. Temporary Erosion and Sediment Control (TESC) plan. The TESC plan shall include all of the minimum elements specified in SVMC 24.150 Spokane Regional Stormwater Manual Chapter 9 and Plan elements required in Chapter 4 of SVMC Title 22.130.040 Street Standards, as applicable. The TESC plan may also be prepared by a Certified Erosion and Sediment Control Technician. All erosion prevention and sediment control measures shall be maintained, including replacement and repair as needed. These minimum guidelines are not intended to resolve all project soil erosion conditions. The applicant is responsible for confining all soil on the project site and implementing additional measures as necessary to accommodate changing or unexpected site and weather conditions. 24.50.050 GRUBBING AND CLEARING PERMIT A. Applicability. A grubbing and clearing permit is required for the following land disturbing activities: 1. All grubbing and clearing activities disturbing 5,000 square feet or more of area; and, 2. Any clearing on slopes, wetlands, erodible soils, critical areas, etc; and, 3. Any removal of trees and vegetation that does not trigger the grading permit requirements. B. Exemptions. The following land disturbing activities are not required to obtain a clearing and grubbing permit: 1. Commercial agriculture as regulated under RCW Chapter 84.34.020. Clearing associated with agricultural uses, excluding timber cutting not otherwise exempted; 2. Forest practices regulated under WAC Title 222, except for Class IV General Forest Practices that are conversions from timberland to other uses; 3. Clearing and grubbing already included in a grading or building permit; 4. The removal of six(6)trees or less per acre per parcel; 5. The removal of trees and ground cover by utility companies in emergency situations; or, 6. Routine landscape maintenance and minor repair. C. Permit Submittal Requirements. The minimum documents required for permit application are as follows: 1. Completed permit application; and, 2. Plans demonstrating compliance with Chapter 4 and 5 SVMC 22.130.40 Street Standards and all other applicable laws, ordinances, rules and regulations; and, 3. Temporary Erosion and Sediment Control (TESC) plan. The TESC plan shall include all of the minimum elements specified in SVMC 24.150 Spokane Regional Stormwater Manual Chapter 9 and Plan elements required in Chapter 4 of SVMC Title 22.130.040 Street Standards, as applicable. The TESC plan may also be prepared by a Certified Erosion and Sediment Control Technician. All erosion prevention and sediment control measures shall be maintained, including replacement and repair as needed. These Ordinance 09-033 Street Standards Page 17 of 18 minimum guidelines are not intended to resolve all project soil erosion conditions. The applicant is responsible for confining all soil on the project site and implementing additional measures as necessary to accommodate changing or unexpected site and weather conditions. 24.50.060 SEVERABILITY • If any section, subsection, sentence, clause or phrase of this ordinance is determined invalid for any reason in whole or in part by court, such decision shall not affect the validity of the remaining portions of the ordinances. Section 7. Severability. If any section, sentence, clause or phrase of this ordinance shall be held -to be invalid or unconstitutional by a court of competent jurisdiction, such invalidity or unconstitutionality shall not affect the validity or constitutionality of any other section, sentence, clause or phrase of this Ordinance. Section 8. Effective Date. This Ordinance shall be in full force and effect thirty (30) days after date of publication of this Ordinance or a summary thereof in the official newspaper of the City. PASSED by the City Council this 8th day of December, 2009. A E i*/ - � ' ichard M. M son, Mayor / Christine Bainbridge, City Clerk Approved as to Form: /1. Qp Office o(4 the City torney Date of Publication: 12/18/2009 Effective Date: 01/18/2010 Ordinance 09-033 Street Standards Page 18 of 18 Street Standards Spokane . Valley December 2009 CITY OF SPOKANE VALLEY STREET STANDARDS City of Spokane Valley Street Standards Table of Contents Title Page No. Chapter 1. Introduction 1.1 Title 1-1 1.2 Intent and Provisions 1-1 1.3 Objectives of Street Standards 1-1 1.3.1 Minimum Standards 1-1 1.3.2 Objectives 1-2 1.4 Authority 1-2 1.4.1 Development Services Senior Engineer 1-2 1.4.2 Senior Traffic Engineer 1-3 1.4.3 Senior Capital Project Engineer 1-3 1.5 Document Organization 1-4 1.6 Amendments and Revisions to Standards 1-4 1.6.1 Policy Revisions 1-4 1.6.2 Technical Revisions 1-4 1.7 Interpretation of Standards 1-5 1.7.1 Governing Standards 1-5 1.7.2 Prior Acceptance of Construction Plans 1-5 1.7.3 Severability 1-5 1.8 Contact Information 1-6 1.9 Reference Material 1-6 1.10 Variance 1-7 1.11 Design Deviations 1-7 1.12 Abbreviations 1-8 1.13 Definitions 1-10 Chapter 2. Development Engineering Requirements 2.1 Introduction 2-1 2.2 Applicability 2-1 2.3 Required Dedications and Improvements 2-1 2.3.1 Typical Requirements 2-2 2.3.2 Specific Requirements for Short Subdivisions, Long Subdivisions and Binding Site Plans 2-3 2.3.3 Specific Requirements for Commercial Building Permits 2-3 2.3.4 Specific Requirements for Miscellaneous Projects 2-5 December 2009 -i- CITY OF SPOKANE VALLEY STREET STANDARDS 2.3.5 Other Requirements 2-5 2.4 Modifications to Requirements 2-6 2.4.1 Variance 2-6 2.4.2 Capital Projects 2-6 2.4.3 Limiting Site Conditions 2-6 2.5 Applicant's Responsibilities 2-7 Chapter 3. Traffic Analysis 3.1 Introduction 3-1 3.2 Trip Generation& Distribution Letter Guidelines 3-1 3.2.1 Applicability 3-1 3.2.2 Minimum Elements 3-2 3.3 Traffic Impact Analysis 3-3 3.3.1 Applicability 3-3 3.3.2 Scope 3-3 3.3.3 Methodology 3-3 3.3.4 TIA Report Minimum Elements 3-4 3.3.4.1 Title Page 3-4 3.3.4.2 Introduction and Summary 3-4 3.3.4.3 Proposed Development 3-5 3.3.4.4 Summary of Existing Conditions 3-5 3.3.4.5 Background Projects 3-6 3.3.4.6 Analysis Scenarios 3-6 3.3.4.7 Other Analyses 3-6 3.3.4.8 Findings 3-7 3.3.4.9 Appendices 3-7 3.4 Meetings 3-7 Chapter 4. Requirements for Plan Submittal 4.1 Introduction 4-1 4.2 General Requirements 4-1 4.2.1 Plan Completeness 4-1 4.2.2 Fonts 4-1 4.2.3 Lines and Symbols 4-1 4.2.4 Sheet Size/Plan Medium 4-1 4.2.5 Engineer Signature and Stamp 4-2 4.2.6 Scale 4-2 4.2.7 North Arrow 4-2 4.2.8 Vertical and Horizontal Datum 4-2 4.2.9 Utility Locate Note 4-2 4.2.10 Title Block 4-2 4.2.11 Required Civil Plan Sheets 4-3 4.2.12 Required Traffic Plan Sheets 4-3 4.2.13 Other Required Plan Sheets 4-3 4.3 Specific Requirements for Plan Sheets 4-3 4.4 Cover Sheet 4-4 December 2009 - ii- CITY OF SPOKANE VALLEY STREET STANDARDS 4.4.1 Applicability 4-4 4.4.2 Minimum Elements 4-4 4.5 Clearing and Grading Plan 4-5 4.5.1 Applicability 4-5 4.5.2 Minimum Plan Elements 4-5 4.6 Street Improvements Plan 4-6 4.6.1 Applicability 4-6 4.6.2 Minimum Plan View Elements 4-6 4.6.3 Minimum Profile View Elements 4-8 4.6.4 Minimum Typical Cross Section Elements 4-8 4.7 Onsite Improvement Plan 4-9 4.7.1 Applicability 4-9 4.7.2 Minimum Elements for Onsite Improvement Plan 4-10 4.8 Drainage Plan 4-11 4.9 Temporary Erosion and Sediment Control Plan 4-11 4.10 Temporary Traffic Control Plan 4-11 4.11 Permanent Traffic Control Plan 4-11 4.11.1 Area Map 4-11 4.11.2 Road Segment Pages 4-11 4.11.3 Signing Plan 4-11 4.11.4 Striping Plan 4-12 4.11.5 Traffic Signal Plan 4-12 4.12 Site Plan of Record 4-12 Appendix 4A—General Construction Notes 4-13 Chapter 5. Land Disturbing Activities 5.1 Introduction 5-1 5.2 Geotechnical Evaluation 5-1 5.2.1 Applicability 5-1 5.2.2 Qualified Professional 5-2 5.2.3 Geotechnical Report 5-2 5.3 Clearing, Grubbing & Grading 5-2 5.4 Erosion and Sediment Control Requirements 5-3 5.5 Cuts and Fills 5-4 5.5.1 General Requirements 5-4 5.5.2 Ground Preparation and Fill Material 5-5 5.5.3 Cut and Fill Setbacks 5-7 5.6 Terracing 5-9 5.7 Slope Easements 5-9 5.8 Retaining Walls 5-10 Chapter 6. Utilities 6.1 Introduction 6-1 6.2 Design Criteria 6-1 6.2.1 Utilities Located within Right-of-Way 6-1. 6.2.2 Underground Utilities 6-1 December 2009 - iii- CITY OF SPOKANE VALLEY STREET STANDARDS 6.2.3 Aboveground Utilities 6-2 6.2.4 Regional Pavement Cut Policy 6-2 Appendix 6A—Regional Pavement Cut Policy 6-4 Chapter 7. Street Elements 7.1 Introduction 7-1 7.2 Terrain Types 7-1 7.3 Street Types 7-1 7.3.1 - Public Streets 7-1 7.3.2 Private Streets 7-2 7.3.3 Alleys 7-2 7.3.4 Private Driveways 7-3 7.4 Half-Street Improvements 7-3 7.5 Street Geometry 7-4 7.5.1 Design Criteria 7-4 7.5.2 Right-of-Way 7-8 7.5.3 Border Easement 7-8 7.5.4 Grade 7-8 7.5.5 Cross Slope 7-8 7.5.6 Horizontal Curves 7-9 7.5.7 Vertical Curves 7-9 7.5.8 Street Surfacing Requirements 7-10 7.5.9 Curb and Gutter 7-10 7.5.10 Landscape Strip and Swales 7-10 7.5.11 Turnarounds 7-10 7.5.12 Bikeways 7-11 7.5.13 Intersections 7-12 7.5.14 Street Layout 7-13 7.5.15 Survey Monuments 7-14 7.5.16 Traffic Control Devices 7-15 7.6 Roadside Elements 7-16 7.6.1 Sidewalks 7-16 7.6.2 Pedestrian Ramps 7-16 7.6.3 Side Slopes 7-17 7.6.4 Clear Zone 7-17 7.6.5 Sight Distance 7-18 7.7 Miscellaneous Features 7-21 7.7.1 Street Names 7-21 7.7.2 Mailboxes 7-21 7.7.3 Guardrail 7-21 7.7.4 Bollards 7-21 7.7.5 Roadway Barricades 7-22 7.7.6 Entrance Gates 7-22 7.8 Approach Design Criteria 7-22 7.8.1 Applicability 7-23 7.8.2 Access Limitations 7-23 December 2009 -iv- CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.3 General Design 7-24 7.8.4 Driveway Approach Horizontal and Vertical Grade 7-24 7.8.5 Approach Widths 7-25 7.8.6 Driveway Approach On-Site Layout 7-25 7.8.7 Corner Clearance from Intersections 7-26 7.8.8 Driveway Approach Spacing—Same Side of Street 7-27 7.8.9 Driveway Approach Methods of Measurements 7-27 7.8.10 Restricted Access Driveways 7-28 7.8.11 Alignment of Cross-Street Driveway Approaches 7-28 7.8.12 Signalized Driveway Approaches 7-28 7.8.13 Approaches on State Highways 7-28 7.9 Traffic Calming 7-29 7.9.1 New Development 7-29 7.9.2 Existing Development 7-29 7.9.3 Traffic Calming Devices 7-29 Chapter 8. Pavement Design 8.1 Introduction 8-1 8.2 Street Classification 8-1 8.3 Street Pavement and Subgrade 8-1 8.3.1 Travelways in Residential Zones 8-1 8.3.2 Travelways in Non-Residential Zones 8-2 8.3.3 Subgrade Preparation 8-2 8.4 Engineered Pavement Parameters 8-3 8.4.1 Traffic Parameters 8-3 8.4.2 Reliability Level 8-4 8.4.3 Overall Standard Deviation 8-4 8.4.4 Initial and Terminal Serviceability Indexes 8-4 8.4.5 Structural Layer Coefficients 8-4 8.4.6 Drainage Layer Coefficients 8-4 8.4.7 Subgrade Evaluation 8-5 8.5 Report Submittal 8-5 8.6 Materials Specifications 8-6 8.6.1 Gravel Base 8-6 8.6.2 Crushed Rock 8-6 8.6.3 Asphalt or Concrete Treated Base 8-6 8.6.4 Hot Mix Asphalt 8-6 8.6.5 In-place Mainline Asphalt Compaction Test Requirements 8-7 8.6.6 Cold Joint Requirements 8-7 8.6.7 Longitudinal and Transverse Joint Requirements 8-7 8.6.8 Tack Coats—Preparation of Existing Surfaces 8-8 8.6.9 Cover Asphalt Loads During Transport 8-8 8.6.10 Breakdown Rolling Maximum Temperature Loss 8-8 8.6.11 Asphalt Temperature Placement Requirements 8-8 8.6.12 Paving Dates & Weather Limitations 8-9 December 2009 -v- CITY OF SPOKANE VALLEY STREET STANDARDS Chapter 9. Inspection and Certification 9.1 Introduction 9-1 9.2 Applicability 9-1 9.3 Authority to Stop Work 9-1 9.4 Responsibilities 9-1 9.4.1 Development Inspector 9-1 9.4.2 Onsite Inspector 9-2 9.4.3 Applicant's Engineer 9-3 9.4.4 Contractor 9-3 9.5 Right-of-Way Permits 9-3 9.6 Pre-Construction Meeting 9-4 9.7 Construction Notification 9-4 9.7.1 Notices of Upcoming Construction 9-4 9.7.2 Notices of Utility Shutdown and Access Limitations 9-5 9.7.3 Notices for Inspection 9-6 9.8 Field and Lab Testing 9-6 9.8.1 Reporting 9-6 9.8.2 Minimum Material Testing Frequencies 9-6 9.8.3 Field Testing and Lab Requirements 9-6 9.9 Required Inspections 9-7 9.9.1 Erosion and Sediment Inspections 9-7 9.9.2 Utility Inspections 9-7 9.9.3 I-IMA Inspections 9-7 9.9.4 Drainage Structure Inspections 9-8 9.9.5 Drainage Swale and Drainage Facilities Inspections 9-8 9.9.6 Swale Inspections During Warranty Period 9-9 9.10 Miscellaneous 9-9 9.10.1 Changes During Construction 9-9 9.10.2 Construction Complaints 9-9 9.10.3 Conflict Resolution 9-9 9.11 Final Walk-Through 9-9 9.12 Record Drawings 9-10 9.13 Project Certification 9-10 9.13.1 Certification of Drainage Facilities 9-11 9.14 Performance Surety 9-11 9.14.1 Building Permit 9-11 9.14.2 Short Plats, Long Plats, and Binding Site Plans 9-12 9.14.3 Performance Surety Amount 9-12 9.14.4 Acceptable Sureties 9-12 9.14.5 Performance Surety Release 9-12 9.15 Warranty Surety 9-13 9.15.1 Warranty Surety Amount 9-13 9.15.2 Acceptable Sureties 9-13 9.15.3 Warranty Duration 9-13 9.15.4 Time Frames to Complete Repair 9-13 9.15.5 Failure to Complete Repair 9-14 December 2009 -vi- CITY OF SPOKANE VALLEY STREET STANDARDS 9.15.6 Responsibility for Maintenance 9-14 9.16 Street Establishment 9-14 Appendix 9A—Minimum Material Testing Frequencies 9-16 Appendix 9B—Final Certification Checklist(Sample) 9-17 Appendix 9C—Examples of Sureties 9-18 Appendix 9D—Erosion and Sediment Control Log 9-25 Chapter 10. Maintenance 10.1 Introduction 10-1 10.2 Maintenance Responsibility 10-1 10.2.1 Public Streets 10-1 10.2.2 Private Streets and Driveways 10-1 10.3 Required Documents 10-2 10.3.1 Homeowners' and Property Owners' Associations 10-2 10.3.2 Operation and Maintenance Manual 10-2 10.3.3 Financial Plan 10-3 10.3.4 Conversion from Private to Public Street 10-4 Chapter 11. Standard Plans Last Updated Drafting D-100 Drafting Standards—General Survey, Sewer& Line Weights 9/1/09 D-101 Drafting Standards—General Water, Gas, Power, Tele & TV 9/1/09 D-102 Drafting Standards—General Power, Tele, TV & Special Features 9/1/09 D-103 Drafting Standards—Pavement Markings 9/1/09 D-104 Drafting Standards—Line Types and Text 9/1/09 D-105 Drafting Standards—Line Types and Text 9/1/09 Roads/Streets R-102 Curbing 9/1/09 R-103 Sidewalk 9/1/09 R-105 Pedestrian Ramps - Typical 9/1/09 R-106 Pedestrian Ramps - Midblock and Adjacent Sidewalk 9/1/09 R-I10 Driveway Approach Separated Sidewalk 9/1/09 R-111 Driveway Approach Swale Inlet 9/1/09 R-112 Driveway Approach Adjacent Sidewalk 9/1/09 R-113 Driveway Approach High Volume 9/1/09 R-114 Driveway Approach Asphalt 9/1/09 R-115 Driveway Approach for Private Streets and Driveways 9/1/09 R-117 Driveways - General Requirements 9/1/09 R-119 Typical Street Section—Half Street 9/1/09 R-120 Typical Street Section Local Residential 9/1/09 R-121 Typical Street Section Local Commercial 9/1/09 R-122 Typical Street Section Collector 9/1/09 R-125 Alley Section 9/1/09 R-127 Longitudinal Step Wedge Cold Joint 9/24/09 R-130 Cul-de-Sac - Public Street 9/1/09 December 2009 -vii- CITY OF SPOKANE VALLEY STREET STANDARDS R-131 Public Street Turnaround - Future Intersection 9/1/09 R-132 Public Street Turnaround—Future Connection 9/1/09 R-133 Private Street and Driveway Turnarounds 9/1/09 R-140 Street Signs 9/1/09 R-142 Type III Barricade 9/1/09 R-145 Survey Monuments 9/1/09 R-150 Gated Access Requirements 9/1/09 Stormwater S-101 Precast Drywells Placed in Swale 9/1/09 S-102 Precast Drywells Placed in Asphalt 9/1/09 S-103 Drywell Details 9/1/09 S-104 Drywell Frame and Grates 9/1/09 S-105 Precast Drywell & Inlet Details 9/1/09 S-110 Curb Inlet Type 1 9/1/09 S-111 Curb Inlet Type 2 9/1/09 S-112 Catch Basin Type 1 9/1/09 S-113 Concrete Inlet Type 1 9/1/09 S-114 Concrete Inlet Type 2 9/1/09 S-115 Combination Inlet 9/1/09 S-117 Catch Basin& Inlet Installation 9/1/09 S-121 Metal Grate Type 1 (Bypass) 9/1/09 S-122 Metal Grate Type 3 (Low Point) 9/1/09 S-130 Roadside Swales 9/1/09 S-140 Oil Water Separator 9/1/09 Traffic T-101 Traffic Circle 9/1/09 Utilities U-100 Utility Location Detail 9/1/09 U-101 Aboveground Utility Placement 9/1/09 U-102 Fire Department Hydrant Requirements 9/1/09 List of Figures ix List of Tables x December 2009 -viii- CITY OF SPOKANE VALLEY STREET STANDARDS City of Spokane Valley Street Standards List of Tables No. Title Page No. Table 2.1 Required Street Improvements for Commercial Building Permits 2-4 Table 7.1 Arterial Street Design Criteria 7-5 Table 7.2 Arterial Street Design Criteria Minimum Widths 7-6 Table 7.3 Access Street Design Criteria 7-7 Table 7.4 Minimum Street Approach Length 7-12 Table 7.5 Minimum Intersection Spacing for Local Access Streets 7-13 Table 7.6 Minimum Stopping Sight Distance 7-18 Table 7.7 Minimum Intersection and Approach Sight Distances 7-19 Table 7.8 Driveway Approach Spacing 7-27 Table 7.9 State Routes Classifications 7-29 Table 8.1 Equivalent Single Axle Loads 8-3 Table 8.2 Initial and Terminal Serviceability Indexes 8-4 Table 8.3 Structural Layer Coefficients 8-4 Table 8.4 Recommended Drainage Coefficients 8-5 Table 8.5 Moduli Ratio 8-5 Table 8.6 Performance Grade 8-7 Table 8.7 Recommended Minimum Laydown Temperature 8-9 Table 9.1 Required Sign Information 9-5 December 2009 -x- CITY OF SPOKANE VALLEY STRE, STANDARDS City of Spokane Valley Street Standards List of Figures No. Title Page No. Figure 5-1 Fill Minimum Requirements 5-6 Figure 5-2 Setbacks 5-8 Figure 7-1 Sight Distance Triangle for Case A 7-20 Figure 7-2 Sight Distance Triangle for Case B 7-20 Figure 9-1 Typical Sign 9-5 December 2009 -ix- CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 1 - INTRODUCTION 1 T 5 1 , ' (T1�aid ^ " �1 )` _� 1°-. - f J 5' w.. -. Jy .� - a 1y4 f _ +.i4 ;•-: CN e 1` h k � . •iT as F- 1-00/2004 a -.. <P.:?i .-'A -Vb., of�+ ..ap• ., .:'v.?. ' :.P- Chapter Organization 1.1 Title 1 1.2 Intent and Provisions 1 1.3 Objectives of Street Standards 1 1.3.1 Minimum Standards 1 1.3.2 Objectives 2 1.4 Authority 2 1.4.1 Development Services Senior Engineer 2 1.4.2 Senior Traffic Engineer 3 1.4.3 Senior Capital Projects Engineer • 3 1.5 Document Organization 4 1.6 Amendments and Revisions to Standards - 4 1.6.1 Policy Revisions 4 1.6.2 Technical Revisions 4 1.7 Interpretation of Standards 5 1.7.1 Governing Standards 5 - 1.7.2 Prior Acceptance of Construction Plans 5 1.7.3 Severability 5 1.8 Contact Information 6 1.9 Reference Material 6 1.10 Variance 7 1.11 Design Deviations 7 1.12 Abbreviations 8 1.13 Definitions 10 • December 2009 Chapter 1—Introduction 1-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 1—Introduction 1-ii CITY OF SPOKANE VALLEY STREET STANDARDS 1.1 TITLE These regulations, along with all future amendments, shall be known as the City of Spokane Valley Street Standards (hereinafter called "Standards" or"Street Standards"). 1.2 INTENT AND PROVISIONS These Standards apply to all capital and development projects within the City's limits and, to the extent allowed by law, to those projects outside of City limits that impact City infrastructure or transportation systems. When full compliance with these Standards makes a capital project impracticable or unfeasible, exceptions may be granted for reconstruction, resurfacing, restoration and rehabilitation of existing public streets. The City's review and approval of any plans, reports, or drawings or the City's inspection and approval of any improvements constructed by the Applicant in accordance with these Standards, does not constitute a representation, warranty, or guarantee by the City that such improvements are free from defects or will operate adequately for the purpose intended. The chapters and appendices that make up these Standards pertain to planning, design, approval, construction, inspection, testing, and documentation of street improvements. The intent of this manual is to establish the minimum acceptable standards. 1.3 OBJECTIVES OF STREET STANDARDS 1.3.1 MINIMUM STANDARDS These Standards shall be the minimum standards necessary for design and construction of all street related improvements in the City. Special situations as determined by the City may require different facilities and/or standards. For items not covered by these Standards, the City may require the use of other standards as referenced in Section 1.9. It is incumbent upon the Applicant's engineer to use good engineering practice and to be aware of and implement, new design practices and procedures that reflect current techniques in civil engineering. Good engineering practice is defined in these Standards as professional and ethical conduct that meets the current codes and regulations adopted for engineers. The proposed design shall consider functionality, constructability, operation, and maintenance, including the health, safety and welfare of the public. December 2009 Chapter 1 -Introduction 1-1 CITY OF SPOKANE VALLEY STREET STANDARDS 1.3.2 OBJECTIVES It is the objective of these Standards to address the following: • To provide for an efficient transportation system and improve local circulation and emergency access by providing connectivity between residential streets and arterials; • To extend the functional life of the existing transportation systems and increase its safe and efficient operation; • To ensure public facilities and services meet level of services established in the adopted Comprehensive Plan; • To encourage the use of public streets in new development; • To protect the public health, safety, environment, and welfare to the greatest extent possible resulting from construction and maintenance activities within the public right-of-way; • To ensure the primary uses of the public right-of-way are for bicycle, pedestrian and vehicular travel; • To ensure the public right-of-way is properly maintained during construction and repair work in these areas; • To protect the City's infrastructure investment by establishing standardized design, materials, construction, and repair criteria for all public improvements; • To optimize the use of the limited physical capacity of public right-of-way held by the City; • To provide an efficient permit system that regulates and coordinates activities in an effective and safe manner; • To protect private and public property from damages that could occur because of faulty design and construction; and, • To provide criteria for inspection of public and private improvements, in order to assure conformance with the approved plans, proper construction techniques, and to ensure that acceptable materials are used for the construction process of such public and/or private improvements. 1.4 AUTHORITY The following sections describe City engineering positions having authority over these Standards. 1.4.1 DEVELOPMENT SERVICES SENIOR ENGINEER The Development Services Senior Engineer is part of the Development Services Division of the Community Development Department and has the authority to: December 2009 Chapter 1 -Introduction 1-2 CITY OF SPOKANE VALLEY STREET STANDARDS • Require development projects to provide and improve future acquisition areas, dedicate right-of-way and border easements, construct new streets, and/or improve existing infrastructure to the applicable standard pursuant to City of Spokane Valley Uniform Municipal Code (SVMC) Title 22.130, RCW 35.63.080, RCW 35.63.090, RCW 35A.63.100, RCW 43.21C, RCW 58.17, and RCW 82.02.020; • Make slight modifications to the standard sections for public streets when site conditions warrant; • Ensure that all design and construction for development projects is completed to a level that is equal to or exceeds the requirements set forth in these Street Standards; • Make revisions to the Street Standards in accordance with Section 1.6; and, • Review and approve design deviations for development projects in accordance with Section 1.11. 1A2 SENIOR TRAFFIC ENGINEER The Senior Traffic Engineer is part of the Traffic Division of the Public Works Department and has the authority to: • Determine traffic concurrency for development projects pursuant to SVMC 22.20; • Review and approve driveway locations within intersections; • Review and approve signal, signing and striping plans to ensure that they meet or exceed the applicable MUTCD standards; • Ensure that capital projects and development projects meet or exceed the traffic requirements set forth in Chapter 3; and, • Impose other traffic requirements to the extent allowed by the law. 1.4.3 SENIOR CAPITAL PROJECTS ENGINEER The Senior Capital Projects Engineer is part of the Capital Improvement Program Division of the Public Works Department and has the authority to: • Ensure that all design and construction for capital projects is completed to a level that is equal to or exceeds the requirements set forth in these Street Standards; • Review and approve design deviations for capital projects in accordance with Section 1.11; and, • Make deviations or modifications to the standard sections for capital projects when site conditions warrant in accordance with Section 1.11. December 2009 Chapter 1 -Introduction 1-3 CITY OF SPOKANE VALLEY STREET STANDARDS 1.5 DOCUMENT ORGANIZATION These Standards are generally organized as described below: • Chapter 2 describes typical project requirements; • Chapter 3 describes traffic analysis requirements; • Chapter 4 describes requirements for plan submittal; • Chapter 5 describes requirements for clearing and grading; • Chapter 6 describes requirements for utility work; • Chapter 7 describes requirements for street design; • Chapter 8 describes requirements for pavement design; • Chapter 9 describes requirements for inspection and certification; • Chapter 10 describes maintenance requirements; and, • Chapter 11 provides the City's Standard Plans. 1.6 AMENDMENTS AND REVISIONS TO STANDARDS The Street Standards may be periodically amended as necessary to provide additional clarity or to reflect changes in policy or in construction or engineering practice. Such revisions to these Standards may consist of either "policy" revisions or "technical" revisions. The City will maintain an electronic file of these Standards. All updates and revisions will be available on the City web page or at the City Clerk's office. 1.6.1 POLICY REVISIONS Policy revisions shall be considered major changes, changes in law and changes that will cause significant increased cost or controversy. Policy revisions also include those changes that relate to the public use and convenience, such as changes in standard street width. Policy revisions require a public hearing process for their adoption and City Council approval. 1.6.2 TECHNICAL REVISIONS Technical revisions shall consist of minor additions, clarifications, revisions, and corrections to the Street Standards and City standard plans as may be necessary to better conform to good engineering and/or construction standards and practice. Technical revisions shall be: • Consistent with all existing policies relevant to the revision; December 2009 Chapter 1 -Introduction 1-4 CITY OF SPOKANE VALLEY STREET STANDARDS • Necessary for the public's health, safety and welfare; • Needed to clarify these Standards; or, • Consistent with existing law. Technical revisions shall become effective when approved in writing. If technical revisions are deemed necessary, the revisions may occur through either: • Planned periodic revisions; or • An accelerated process. If a technical revision is determined to be immediately necessary, then the change shall be made and notification given on the web page. Document holders on record with the City, will be notified of the changes. 1.7 INTERPRETATION OF STANDARDS In the interpretation and application of the provisions of the Street Standards, the following principles apply: 1.7.1 GOVERNING STANDARDS Whenever a provision of the Street Standards or any provision in any law, ordinance, resolution, rule, or regulation of any kind contains restrictions covering any of the same subject matter, the standards that are more restrictive or impose higher standards or requirements shall govern. 1.7.2 PRIOR ACCEPTANCE OF CONSTRUCTION PLANS The Street Standards shall not modify or alter any street construction plans that have been filed with and accepted by the City prior to the effective date of the ordinance or resolution adopting the Street Standards. This exception shall be subject to the conditions and limitations under which said plans were accepted by the City. 1.7.3 SEVERABILITY If any section, sentence, clause or phrase of these Standards should be held invalid or unconstitutional, the validity or constitutionality thereof shall not affect the validity or constitutionality of any other section, sentence, clause or phrase of these Standards. December 2009 Chapter 1 -Introduction 1-5 CITY OF SPOKANE VALLEY STREET STANDARDS 1.8 CONTACT INFORMATION Community Development Department Development Engineering Division City of Spokane Valley City of Spokane Valley 11707 E. Sprague, Suite 106 11707 E. Sprague, Suite 106 Spokane Valley, WA 99206 Spokane Valley, WA 99206 Phone (509)921-1000 Phone(509)921-1000 Fax(509)688-0037 Fax(509)921-1008 Public Works Department Building Division City of Spokane Valley City of Spokane Valley 11707 E. Sprague, Suite 106 11707 E. Sprague, Suite B-3 Spokane Valley, WA 99206 Spokane Valley, WA 99206 Phone (509)921-1000 Phone(509) 720-5240 Fax(509)688-0261 Fax(509) 688-0037 Spokane Valley Fire Department Fire Protection District 8 Prevention Office 13319 E Sprague 12100 E Palouse Highway Spokane Valley, WA 99206 Valleyford, WA 99036 Phone (509)928-1700 Phone(509)926-6699 Fax(509) 892-4125 Fax(509) 924-8358 1.9 REFERENCE MATERIAL The Street Standards are supplemented by the "Washington State Department of Transportation/American Public Works Association (WSDOT/APWA) Standard Specifications for Road, Bridge and Municipal Construction," latest edition. The Street Standard Details are comprised of the City's construction and design detail drawings for grading, storm drainage, and street work within the City that are supplemented by the Washington State Department of Transportation (WSDOT) "Standard Plans for Road, Bridge and Municipal Construction." The current edition of the following publications should be used as additional reference material for design applications: A. American Association of State Highway and Transportation Officials' (AASHTO) "A Policy on Geometric Design of Highways and Streets" B. AASHTO Guide for the Development of Bicycle Facilities C. AASHTO Standard Specifications for Highway Bridges D. Americans with Disabilities Act(ADA)Accessibility Guidelines E. American Society for Testing and Materials (ASTM) F. Associated Rockery Contractors, Standard Rock Wall Construction Guidelines G. City of Spokane Valley Municipal Code December 2009 Chapter I -Introduction 1-6 CITY OF SPOKANE VALLEY STREET STANDARDS H. Federal Highway Administration (FHWA) Engineering Circulars I. Highway Capacity Manual J. Institute of Transportation Engineers (ITE) Trip Generation Manual K. International Fire Code adopted by the City of Spokane Valley L. Washington Model Traffic Ordinance (Chapter 308-330 WAC) M. Spokane County Standards for Road and Sewer Construction N. Spokane Regional Stormwater Manual 0. U. S. Department of Transportation Manual on Uniform Traffic Control Devices, (MUTCD) P. Washington Department of Ecology Stormwater Management Manual for Eastern Washington Q. Washington State Department of Transportation (WSDOT) Design Standards R. WSDOT Guidelines for Urban Arterial Program S. WSDOT Local Agency Guidelines T. WSDOT Standard Specifications for Road, Bridge and Municipal Construction U. WSDOT"Design Standards" V. Design criteria of federal agencies including the Federal Housing Administration, Department of Housing and Urban Development; and the Federal Highway Administration, Department of Transportation 1.10 VARIANCE The requirements established in Chapter 2 can only be waived or reduced through a variance. Refer to SVMC Title 19.170 for variance process and requirements. 1.11 DESIGN DEVIATIONS In special cases, strict application of Street Standards may not best address a particular engineering situation. In these cases, a design deviation may be requested. Design deviation requests shall be on the City's form and include applicable engineering justification for the deviation. The Development Services Senior Engineer is the final authority to deny or approve a design deviation request for development projects. For capital projects, the authority lies with the Senior Capital Projects Engineer. The Applicant shall request a design deviation when either of the following situations applies: • The project proposes non-standard methods, analysis, design elements or materials; or, December 2009 Chapter 1 -Introduction 1-7 CITY OF SPOKANE VALLEY STREET STANDARDS • The project proposes design elements above maximum criteria or below the minimum criteria found in these Standards. A design deviation will only be considered for review if: • The design elements proposed do not conflict with or modify a condition of approval; and, • The design elements proposed are based on sound engineering principles, and are not inconsistent with the public interest, and the City's goals and policies. For consideration of a design deviation, the Applicant shall submit a design deviation request and supporting documentation. The supporting documentation shall include sufficient information for the City to make a decision as to the adequacy of the proposal. The design deviation package shall demonstrate that: • There are special physical circumstances or conditions affecting the property that may prohibit the application of some of the requirements of these standards; • Every effort has been made to find alternative ways to meet the objectives of the Street Standards; • Approving the design deviation will not cause adverse impact on down gradient or adjacent properties, public health or welfare; and, • Approving the design deviation will not adversely affect the goals and policies of the City's Comprehensive Plan, Municipal Code, Sprague Appleway Sub-Area Plan,Street Master Plan, and Transportation Improvement Plan. 1.12 ABBREVIATIONS When the following abbreviations appear in these Standards, they shall mean the following: AASHTO American Association of State Highway and Transportation Officials ADA Americans with Disabilities Act ADT Average Daily Trips APWA American Public Works Association ASA American Standards Association ASTM American Society for Testing Materials BMPs Best Management Practices CBR California Bearing Ration CC&Rs Covenants, Codes and Restrictions CESCL Certified Erosion and Sediment Control Lead CSBC Crush surfacing base course CSTC Crush surfacing top course December 2009 Chapter 1 -Introduction 1-8 CITY OF SPOKANE VALLEY STREET STANDARDS Dbh Diameter Breast Height ESALs Equivalent Single-Axle Loads ESC Erosion and Sediment Control FAA Federal Aviation Administration FEMA Federal Emergency Management Agency FHWA Federal Highway Administration FOP Field Operating Procedure GMA Growth Management Area HCM Highway Capacity Manual HMA Hot Mix Asphalt HOA Homeowner's Association IBC International Building Code IRC International Residential Code ITE Institute of Transportation Engineers LOS Level of Service Mr Resilient Modulus MUTCD Manual on Uniform Traffic Control Devices O&M Operations and Maintenance PI Point of Intersection PC Point of Curvature PCR Point of Curve Return PE Professional Engineer PGIS Pollution Generating Impervious Surfaces PLS Professional Land Surveyor POA Property Owner's Association PT Point of Tangency RCW Revised Code of Washington SEPA State Environmental Policy Act SI Street intersection SR State Route SRSM Spokane Regional Stormwater Manual SRTC Spokane Regional Transportation Council December 2009 Chapter 1 -Introduction 1-9 CITY OF SPOKANE VALLEY STREET STANDARDS SVMC Spokane Valley Municipal Code TESC Temporary Erosion and Sedimentation Control TIA Traffic Impact Analysis TIP Transportation Improvement Program USGS United States Geological Survey WAC Washington Administrative Code WAQTC Western Alliance for Quality Transportation Construction WSDOT Washington State Department of Transportation 1.13 DEFINITIONS For the purpose of these Street Standards, certain words and terms are herein defined. The word "shall" is always mandatory. The word "may" is permissive, subject to the judgment of the person administering the code. The word "should" indicates an advisory condition, recommended but not required. These definitions take precedence over those found elsewhere. In the event a technical term is not listed below, definitions shall be taken from the WSDOT Design Manual. Access Management: The concept of a public agency controlling the location of access points in order to achieve the dual purposes of providing access to individual land uses and limiting access on higher order streets in order to facilitate the smooth flow of traffic with a limited amount of impedance. Applicant: The party or parties desiring to construct a public or private improvement within City rights-of-way, easements or private property, securing all required approvals and permits from the City, and assuming full and complete responsibility for the project. The Applicant may be the Owner or the individual designated by the Owner to act on his behalf. Binding Site Plan: A division of land approved administratively by the Department of Community Development, which legally obligates a person making a proposal to conditions, standards or requirements specified by these Standards and the SVMC. Border Easement: A dedicated easement on private property adjacent to public street right-of-way established for the purpose of utility, drainage facilities, pedestrian access or other public purpose. Building Division: The Division at the City of Spokane Valley responsible for reviewing, issuing and certifying construction permits. Certificate of Occupancy: An official certificate issued by the City building official that indicates conformance with building requirements and zoning regulations and authorizes legal use of the premises for which it is issued. Certification Package: A packet prepared by the Onsite Inspector including, but not limited to, Mylar record drawings, weekly reports, certification checklist and related construction documents, for review by the City to determine project acceptability. December 2009 Chapter 1 -Introduction 1-10 CITY OF SPOKANE VALLEY STREET STANDARDS City: City of Spokane Valley, Washington. Clear Zone: A relatively flat area void of fixed objects or obstructions beyond the edge of the traveled way that allows drivers to stop safely or regain control of a vehicle that leaves the traveled way. Clearing and grubbing: Includes, but is not limited to, removing trees, stumps, roots, brush, structures, abandoned utilities, trash, debris and all other materials found on or near the surface of the ground in the construction area. Concurrency: A requirement that those public facilities and services necessary to support development shall be adequate to serve the development at the time the development is available for occupancy and use, without decreasing the current level of service below locally established minimum standards. Contractor: The individual, partnership, firm or organization to whom a construction contract has been awarded by the Applicant, or who has been issued a right-of-way work permit by the City, for work covered by the contract. Agents, employees, workers, subcontractors, or designers employed by the Contractor are also bound by the terms of the contract or permit. Corner Clearance: At an intersecting street, the distance measured along the curb line from the projection of the intersecting street flowline to the nearest edge of the curb opening. County: Spokane County. Design Deviation: An administrative approval of design elements that do not conform to or are not explicitly addressed by these Standards. Designer: The person or persons responsible for the creation and submission of contract documents or construction plans for the purpose of one-time construction of a facility. This person shall be a Washington licensed professional engineer. Development: Any man-made change to improved or unimproved real estate. Development Agreement: The contract between the City and the Applicant that defines public improvement requirements, costs, and other related public improvement issues. Development Inspector: A City employee, responsible for coordinating with the Onsite Inspector(s), reviewing and accepting certification packages and warranty sureties, and recommending public streets for establishment. Driveway: Any area, improvement or facility between a public or private street and private property, which provides ingress/egress for vehicles from a public or private street to a lot or parcel. Driveway Approach: The transition at the end of a private street or driveway where it connects to a public or private street. For details, see standard plans. Easement: A right to use the land of others. The right may be from the common law or may be acquired, usually by purchase or condemnation and occasionally by prescription or inverse condemnation. The right is not exclusive, but subject to rights December 2009 Chapter I -Introduction 1-11 CITY OF SPOKANE VALLEY STREET STANDARDS of others in the same land, the lesser right being subservient to a prior right which is dominant. Easements for drainage may give rights to impound, divert, discharge or concentrate surface flow, extend pipelines, deposit silt, erode, scour, or any other necessary consequence of a development. Engineer: Shall mean a professional engineer. See Professional Engineer definition. Engineered Driveways: Driveways, which due to their length, surface area or other situational factors, are required to be designed by a professional engineer licensed in the State of Washington. Fill: A deposit of earth material placed by artificial means. Fire Department: Fire district having jurisdiction. Fire Lane: An access designated to accommodate emergency access to a parcel of land or its improvements. Final Acceptance: The written notification from Development Engineering, after the Development Services Senior Engineer finds the Warranty Period to be satisfactorily completed, that all public improvements are free of defects and the City releases the Applicant from future maintenance obligations. Frontage Improvements: Required improvements on public streets fronting the property which typically include pavement widening, curb, gutter, grassy swale, and sidewalk. Future Acquisition Area: Area identified on property as potential right-of-way for public purposes, typically reserved through an easement restricting construction within the easement area. Grading: The physical manipulation of the earth's surface and/or surface drainage pattern which includes surcharging, preloading, contouring, cutting, and filling to establish final site grades. Half-Street Improvements: Shall mean, the construction of frontage improvement on the street fronting the property or development, including paving from the street centerline, curb, gutter, swale or grassy strip, and sidewalk, plus a minimum of a 12- foot lane on the opposite side of centerline with a 1-foot gravel shoulder and grassy ditch for stormwater treatment. The final pavement width shall be at least 28 feet. Improvements: All public or private improvements within City right-of-way or easements. Development of a public or private street, typically including some or all of the following: pavements, curb, gutter, landscaped swale, sidewalk, drainage improvements. Intersection Sight Distance: The distance necessary for the driver of a motor vehicle stopped at an intersection or driveway to see approaching vehicles, pedestrians, and bicyclists along the intersecting major street and have sufficient space to make any allowed move to cross the intersection or merge with traffic without causing vehicles, pedestrians, or bicyclists traveling at or near the design speed on the major street to slow down. The controlling distance for design is the longest distance, generally the distance necessary to merge with traffic. December 2009 Chapter 1 -Introduction 1-12 CITY OF SPOKANE VALLEY STREET STANDARDS Land Disturbing Activity: The result in a change in existing soil cover (vegetative or non-vegetative) or site topography. Land disturbing activities include, but are not limited to, demolition, construction, clearing and grubbing, grading and logging. Level of Service (LOS): A measure of a public facility or service's operational characteristics used to gauge its performance. Offsite Improvements: Construction of facilities located away from and up to a project site, necessary to serve the proposed development or to mitigate effects of the development. Onsite Inspector: A qualified person or firm, hired by the Applicant or Owner, responsible for project inspection and certification. Pollution Generating Impervious Surface (PGIS): Impervious surfaces that are significant sources of pollutants in stormwater runoff. Such surfaces include those that are subject to vehicular use, industrial activities, or storage of erodible or leachable materials that receive direct rainfall, or run-on or blow-in of rainfall. Metal roofs are considered to be PGIS unless coated with an inert, non-leachable material. Roofs that are subject to venting of manufacturing, commercial, or other indoor pollutants are also considered PGIS. A surface, whether paved or not, shall be considered PGIS if it is regularly used by motor vehicles. The following are considered regularly-used surfaces: streets, non-vegetated street shoulders, bike lanes within the traveled lane of a street, driveways, parking lots, unfenced fire lanes, vehicular equipment storage yards, and airport runways. Pre-Construction Meeting: A meeting between the Designer and assigned agents, the Onsite Inspector, and the Development Inspector to review proposed work necessary to construct the project, prior to proceeding with the work. A meeting may be required for each project, at the Development Inspector's discretion. Private Street: A local access street that is privately owned and maintained by capable and legally responsible owner(s). Professional Engineer (P.E.): A civil engineer licensed in Washington under Chapter 18.43 RCW who is qualified by examination and/or experience to practice in the fields of civil, geotechnical and/or soils engineering. Professional Land Surveyor (P.L.S.): A Washington licensed land surveyor. Project: The public or private improvement(s) designated in the approved plans, which are to be constructed in conformance with these Standards. The term "Project" includes any and all public or private improvement projects for or within the City, whether development projects, private utility projects, or capital improvement projects. Public Improvements: Public facilities to be located within the right-of-way or border easement which include pavement, curb and gutter, sidewalk, pedestrian/bike/equestrian paths, storm drain facilities, bridges, water distribution or transmission facilities with related appurtenances, pavement markings, signage and striping, traffic signals and related appurtenances, erosion control and right-of-way • December 2009 Chapter 1 -Introduction 1-13 CITY OF SPOKANE VALLEY STREET STANDARDS grading, or earth excavation processes integral to construction of other public improvements listed herein. Punch list, Initial or Final: A written list of work items, compiled by the Onsite Inspector, which do not conform to these Standards, the plans or other associated City Codes that govern the project and require correction prior to project approval. Record Drawings: Original approved design drawings, updated by a professional engineer which depicts all modifications from the design that occurred during construction. Redevelopment: Removal or modification of existing improvements and construction of new improvements or substantial remodeling. Regional Pavement Cut Policy: A regional policy adopted by the City of Spokane Valley, City of Spokane, and Spokane County. This policy, amongst other things, restricts cutting or replacing street improvements for a period of three years following the construction of a newly paved street. Right-of-way (Also "public right-of-way"): The land area (owned by the City) provided by dedication for public use of streets, utilities, walks, and other uses, also providing access to adjoining properties. Right-of-way Permit: A permit, with or without conditions specified by the City, which allows an Applicant to construct any public or private improvements within the public right-of-way or border easement. Short Subdivision: A division of land resulting in the creation of 9 or fewer lots. Slope, Recoverable: A slope on which a motorist may retain or regain control of a vehicle by slowing or stopping. Slopes flatter than 4:1 are generally considered recoverable. Slope, Non-recoverable: A slope considered being traversable but on which an - errant vehicle continues to bottom. Embankment slopes between 3:1 and 4:1 may be considered traversable but non-recoverable if they are smooth and free of fixed objects. Specifications: Construction and standards adopted by the City. Speed — 85th Percentile: The speed at or below which 85 percent of the motorists drive on a given street unaffected by slower traffic or poor weather. This speed indicates the speed that most motorists on the street consider safe and reasonable under ideal conditions. Street: A public or private way for vehicular travel, exclusive of the sidewalk or shoulder even though such sidewalk or shoulder is used by persons riding bicycles. Street Classifications: The identification of a street according to different levels of emphasis on traffic movement versus direct access to property. Surety: A financial instrument securing the Applicant's responsibility to complete construction of public or private improvements within an approved project. Surety shall also mean a financial instrument securing the Applicant's obligations throughout December 2009 Chapter 1 -Introduction 1-14 CITY OF SPOKANE VALLEY STREET STANDARDS the Warranty Period. Sureties approved by the City include cash, letters of credit and savings assignment. Surety, Performance: A surety securing the Applicant's responsibility to complete construction of public or private improvements within an approved project. Surety, Warranty: A surety securing the Applicant's obligations throughout the warranty period; required of projects in the public right-of-way and border easements, guaranteeing against defects in street construction, utility work and/or drainage facilities. Surveyor: Shall mean a professional land surveyor, see definition. Swale: A grassland percolation area designed to accept and treat storm runoff from impervious areas such as streets, driveways, sidewalks, parking lots, roofs, etc. Traffic Calming Devices: Physical measures included in the design of travel ways that improve neighborhood livability by reducing the speed and impact of vehicular traffic on residential streets. Travel Lane: The portion of the street intended for the movement of vehicles, exclusive of shoulders and lanes for parking. Trip Generation and Distribution Letter: A document, prepared by a professional civil engineer with experience in traffic, design and analysis; that identifies the amount of traffic anticipated to and from a development. The letter is reviewed to determine if a traffic impact analysis is required. Traffic Impact Analysis (TIA): A study of the potential traffic impacts of a development on the transportation system. Variance: The process used to change or reduce improvements required of a project. Warranty Period: The period of time that the Applicant is responsible for material and workmanship defects in the public improvements, which remains in effect until written notification is issued by the City. Warranty period is a minimum of two years. Wheel Path: The 3-foot wide portion of a travel lane, located on both sides of the travel lane and the 2-foot wide portion from the center of the travel lane. December 2009 Chapter 1 -Introduction 1-15 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 1 -Introduction 1-16 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 2 - DEVELOPMENT ENGINEERING REQUIREMENTS toi „tea . ' "' akas * wR . +R^„,-�- 'rte , "i 3 gar- u.,. `� .•n04.1.. 1`t _c l! -p •lira s . _ t 1J �a ♦ "1,_IL P , I ! - r \----c-,:„-.4_::' ry 1�f �� t i e .` ?A°' �t ., r , %_ p� i v r ',,it s Dr 4r Q `?w , 'f..;."-."rt �,'..:1 t t r ti"*�^�',14.A; Chapter Organization 2.1 Introduction 1 2.2 Applicability 1 2.3 Required Dedications and Improvements 1 2.3.1 Typical Requirements 2 2.3.2 Specific Requirements for Short Subdivisions, Long Subdivisions and Binding Site Plans 3 2.3.3 Specific Requirements for Commercial Building Permits 3 2.3.4 Specific Requirements for Miscellaneous Projects 5 2.3.5 Other Requirements 5 2.4 Modifications to Requirements 6 2.4.1 Variance 6 2.4.2 Capital Projects 6 2.4.3 Limiting Site Conditions 6 2.5 Applicant's Responsibilities 7 List of Tables Table 2.1 Required Street Improvements for Commercial Building Permits 4 December 2009 Chapter 2—Development Engineering Requirements 2-i CITY OF SPOKANE VALLEY STREET STANDARDS • THIS PAGE IS INTENTIALLY LEFT BLANK December 2009 Chapter 2—Development Engineering Requirements 2-ii CITY OF SPOKANE VALLEY STREET STANDARDS 2.1 INTRODUCTION This chapter sets forth the specific requirements of the Development Engineering Division (Division) of the Community Development Department for development projects. These requirements are intended to supplement the general requirements of Spokane Valley Municipal Code (SVMC) Chapter 22.130, and are adopted pursuant to SVMC 22.130.040. Required improvements and dedications shall be in compliance with all Chapters in these Street Standards. An overview of the review process for this Division can be found in the "Development Engineering Guidelines" which are adopted herein by reference. 2.2 APPLICABILITY Projects reviewed and conditioned by Development Engineering fall within three general categories: • Land divisions (short plats, subdivisions and binding site plans); • Commercial building permits; and, • Miscellaneous projects which include access permits, boundary line adjustments, rezones, changes of use, changes of occupancy, temporary use permits and conditional use permits. In some instances, this last category of projects may not need a building permit. They may, however, result in an increase in traffic and other impacts that can require street improvements and other mitigation. 2.3 REQUIRED DEDICATIONS AND IMPROVEMENTS This section describes the dedications and types of improvements that may be required pursuant to SVMC Chapter 22.130, RCW 35.63.080, RCW 35.63.090, RCW 35A.63.100, RCW 43.21C; RCW 58.17, and RCW 82.02.020. Land divisions and development permits trigger requirements for dedications of public right-of-way, border easements, future acquisition areas, and other improvements. Other project types may also trigger these requirements. Specific requirements shall be determined during project review. To determine the requirements for a project, the City considers the following: • Existing improvements both onsite and offsite, such as curb, gutter, swale and sidewalk; • Any anticipated increase in traffic that would lead or contribute to an unacceptable level of service; • Connectivity of existing or future streets to better serve public and emergency vehicle mobility; December 2009 Chapter 2—Development Engineering Requirements 2-1 CITY OF SPOKANE VALLEY STREET STANDARDS • Street classification, as shown in the Comprehensive Plan; • City of Spokane Valley 6-year Transportation Improvement Program and any anticipated improvements in the project vicinity; • Public safety as affected by the project (i.e. pedestrian and vehicle safety, traffic flow, etc); • Bike routes, as shown in the Comprehensive Plan; and, • Environmental impacts as identified through applicable SEPA reviews as related to street, sidewalk, drainage improvements, or traffic impacts. 2.3.1 TYPICAL REQUIREMENTS Typical requirements for all projects, except for single-family dwellings, set forth more specifically herein include the following: • Design and construction of all new streets to provide adequate transportation service within a development; • Design and construction of fronting improvements on existing streets necessary to provide adequate transportation service to, or within, a development, as applicable (see Sections 2.3.2 and 2.3.3); • Adequate access for all parcels. Offsite streets used to access the project shall be improved to the applicable standard. Improvement shall extend from the nearest public street meeting the pavement width requirements. Curb and gutter and sidewalk may not be required for the offsite improvements unless made necessary by the proposed development. However, provisions for sormwater management per the Spokane Regional Stormwater Manual shall be required; • Dedications of right-of-way and border easements for full build-out of the project's side of all adjacent and interior public streets (Chapter 7); • Creation of future acquisition areas as required by SVMC Chapter 22.130; • Emergency access to all parcels of land, in conformance with City standards and the latest International Fire Code; • Driveway approaches in accordance with Chapter 7; • Relocation of rigid objects out of the clear zone more specifically set forth in Chapter 7; • Repair and replacement of damaged curb, gutter, swales/planters, sidewalk, survey monuments, etc (Chapter 8); • Removal of abandoned or substandard approaches and replacement with frontage improvements (Chapter 7); and • Mitigations as determined in a traffic impact analysis, more specifically described in Chapter 3. Mitigations may include construction of or December 2009 - Chapter 2—Development Engineering Requirements 2-2 CITY OF SPOKANE VALLEY STREET STANDARDS contributions to traffic calming devices, traffic signals, street lights, signing and/or pavement markings, etc. 2.3.2 SPECIFIC REQUIREMENTS FOR SHORT SUBDIVISIONS, LONG SUBDIVISIONS AND BINDING SITE PLANS Short subdivisions, long subdivisions, and binding site plans shall provide fronting improvements along all public streets adjacent to the project. The extent of required improvements shall be based on existing conditions, the identified impact of the project or transportation improvement, and the applicable standard. Required improvements typically include pavement widening, curb, gutter, grassy swale and sidewalk. All land division projects shall fully improve new internal streets. If the existing fronting street is unimproved or will have less than 28 feet of pavement with fronting improvements, the Applicant shall provide half-street improvements as defined in Section 1.13. "No Parking On Pavement" signs shall be installed on one side of the street. Curb, gutter, and sidewalk are only required on the side of the street adjacent to the parcel. Provisions for stormwater management are required for the sides of the street being improved (Chapter 7). 2.3.3 SPECIFIC REQUIREMENTS FOR COMMERCIAL BUILDING PERMITS Fronting improvements for building permits are determined based on type of project, square footage of the project, and peak hour vehicle trips. These projects shall provide improvements for the street fronting their projects in accordance with Table 2.1. In the event that the street used to access the project is unimproved or has less than 28 feet of pavement, the Applicant shall provide fronting improvements and/or half- street improvements to meet the applicable standards regardless of the proposal type or size. In these instances, curb, gutter, and sidewalk requirements, for the side of the street adjacent to the project, shall be determined based on Table 2.1. Provisions for stormwater management are required for the sides of the street being improved. December 2009 Chapter 2—Development Engineering Requirements 2-3 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 2.1 REQUIRED STREET IMPROVEMENTS FOR COMMERCIAL BUILDING PERMITS PROJECT PROPOSAL - COMMERCIAL BUILDING PERMITS FOR PARCELS WITH EXISTING OR NEW BUILDING Gross Area of Building(for Up to 999 1,000 to 5,999 6,000 to 12,000+ proposed additions or new 11,999 structures)in sq. ft;or, Number of New Peak Hour Up to 4 5 to 9 10 to 15 16+ Trips Generated by Project COMMERCIAL BUILDING PERMIT FOR PARKING LOT ONLY(NO NEW OR EXISTING BUILDING) Up to 9 spaces 10 to 19 spaces 20 to 40 spaces 41+spaces REQUIRED IMPROVEMENTS Widen Pavement ./(i) ./ •/ Curb&Gutter (2) Grass Strip or Swale Sidewalk t2) I2) ./ Right-of-way,Future Y(3) Acquisition Areas and Border Easements 1. The final pavement width on the project's side of the street is the half-street width,plus 6 inches to allow for future curb installation. If the amount of pavement width needing to be added is less than 2 feet, then widening can be omitted unless the full width is less than 28 feet. Grassed ditches or swales are required along pavement edges required to be improved for stormwater treatment,regardless of amount of widening. 2. If a project is located in an area already improved to the requirements above,the project may be required to provide curb and gutter and/or sidewalk. 3. Not required if project is determined to have insignificant impact. When using Table 2.1 for commercial building permits with existing or new buildings, the Applicant shall identify the size of building and number of peak hour vehicular trips. The one triggering the most improvement requirements shall be used. For example, an Applicant is proposing an addition to an existing building; the proposed addition is 3,000 square feet. The proposal also generates 10 peak hour vehicular trips. This project will be required to provide fronting improvements which include pavement widening, curb and gutter installation, grass strip/swale construction, and right-of-way and border easement dedication. If the required improvements currently exist, then the project will be required to provide sidewalk. December 2009 Chapter 2—Development Engineering Requirements 2-4 CITY OF SPOKANE VALLEY STREET STANDARDS 2.3.4 SPECIFIC REQUIREMENTS FOR MISCELLANEOUS PROJECTS Miscellaneous projects include access permits, boundary line adjustments, rezones, changes of use, changes of occupancy, temporary use permits and conditional use permits. In some instances, this last category of projects may not need a building permit. They may, however, result in an increase in traffic and other impacts that can require street improvements and/or other mitigation. Required improvements for change of use and conditional use permits are determined based on traffic impacts pursuant to SVMC Chapter 22.20. Required improvements for boundary line adjustments, rezones, changes of occupancy, and temporary use permits are determined on a case-by-case basis during project review using the criteria specified in Section 2.3. 2.3.5 OTHER REQUIREMENTS Additional improvements may be required on a case-by-case basis, depending on site- specific conditions. These requirements may include, but are not limited to, the following: • Improvements previously required by City Council by ordinance, past land use action, or resolution,to be provided in the vicinity of the project; • New streets (and accompanying dedications) as required by the Street Master Plan, Local Street Plan, Sprague Appleway Subarea Plan and according to the City's Comprehensive Plan; • Participation in the City's Transportation Improvement Program; • Other public improvements when physical characteristics of the property (including but not limited to topography, slope, soil type, drainage pattern or vegetation) create potential hazards; and, • Other public improvements necessitated by the public's health safety or welfare. December 2009 Chapter 2—Development Engineering Requirements 2-5 CITY OF SPOKANE VALLEY STREET STANDARDS 2.4 MODIFICATIONS TO REQUIREMENTS 2.4.1 VARIANCE The requirements established in this chapter can only be waived or reduced through a variance. Refer to SVMC Title 19.170 for variance process and requirements. 2.4.2 CAPITAL PROJECTS Generally, all improvements shall be constructed prior to issuing a certificate of occupancy or final platting. In certain circumstances, installation of some or all of the frontage improvements may not be appropriate at the time development occurs. These may include instances where: • Required improvements are part of a larger project scheduled for construction in the City's Transportation Improvement Program; or, • Sanitary sewer is not available but is scheduled to come through in less than three years. In these situations, the installation of such improvement may be deferred to a later date or waived. A developer's agreement may be required and a surety, as deemed sufficient by the City consistent with Section 9.14. 2.4.3 LIMITING SITE CONDITIONS Generally, all projects shall build public streets to the applicable standard. However, the City can approve a slightly smaller section when full construction of the public improvements renders the project unfeasible. Reduction of the requirements for public improvement may be considered if the parent short plat or subdivision parcel meets the following criteria: • Is in an R1, R2, or R3 zone, and, • Is smaller than 2.5 acres, and, • Will have block lengths that do not exceed 300 feet for a through street; and, • Has less than 216 feet of street frontage. The Applicant shall demonstrate that full improvement construction is not possible and propose an alternative section. The Applicant is not guaranteed to have double frontage on the public street and/or the maximum number of lots at the minimum square footage allowed by SVMC. All proposals shall be approved before the submittal of the preliminary plat application. Request after the preliminary plat application will be required to go through the variance process. December 2009 Chapter 2—Development Engineering Requirements 2-6 CITY OF SPOKANE VALLEY STREET STANDARDS 2.5 APPLICANT'S RESPONSIBILITIES The Applicant is the party or parties desiring to construct a public or private improvement within City right-of-way, easements or private property, securing all required approvals and permits from the City, and assuming full and complete responsibility for the project. The Applicant may be the Owner or the individual designated by the Owner to act on his behalf. The Applicant is responsible for the following: • General project management; • Communicating requirements and project status with the Owner, if Applicant and Owner are not the same; • Coordinating project consultants; • Providing complete submittals; • Ensuring all required applications have been submitted to the City; • Ensuring adherence to: o The standards and criteria presented in these Standards, as amended; o Hearing Examiner's decision and staff report with administrative decisions, if applicable; and, o Any conditions established by City staff December 2009 Chapter 2—Development Engineering Requirements 2-7 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 2—Development Engineering Requirements 2-8 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 3 -TRAFFIC ANALYSIS 4 �_ .I I lF ' ;, .x Tom i „ r ` ? ., *II i a • n :..,..:ag 1'tli Chapter Organization 3.1 Introduction 1 3.2 Trip Generation & Distribution Letter Guidelines 1 3.2.1 Applicability 1 3.2.2 Minimum Elements 2 3.3 Traffic Impact Analysis 3 3.3.1 Applicability 3 3.3.2 Scope 3 3.3.3 Methodology 3 3.3.4 TIA Report Minimum Elements 4 3.3.4.1 Title Page 4 3.3.4.2 Introduction and Summary 4 3.3.4.3 Proposed Development 5 3.3.4.4 Summary of Existing Conditions 5 3.3.4.5 Background Projects 6 3.3.4.6 Analysis Scenarios 6 3.3.4.7 Other Analyses 6 3.3.4.8 Findings 7 3.3.4.9 Appendices 7 3.4 Meetings 7 December 2009 Chapter 3—Traffic Analysis 3-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK December 2009 Chapter 3—Traffic Analysis 3-ii CITY OF SPOKANE VALLEY STREET STANDARDS 3.1 INTRODUCTION This chapter describes the contents of the trip generation and distribution letter and traffic impact analysis (TIA) submittals. The TIA is a comprehensive report containing all of the technical information and analysis necessary to evaluate a proposed new development or redevelopment project for compliance with level of service (LOS) standards. The City will not sign off on a project until transportation concurrency has been determined. All projects except those exempt as set forth in the City of Spokane Valley Municipal Code (SVMC), Title 22.20.020 are subject to concurrency review. 3.2 TRIP GENERATION & DISTRIBUTION LETTER GUIDELINES All projects which generate 10 or more new peak hour vehicular trips shall submit a trip generation and distribution letter. The letter shall be based on the latest edition of the Institute of Transportation Engineers (ITE) Trip Generation Manual and developed by an Engineer. If a project is subject to State Environmental Policy Act (SEPA) review, the trip generation and distribution letter shall be submitted for review at the time of the SEPA application. The letter is required to be approved by the City prior to submittal of a traffic impact analysis report. 3.2.1 APPLICABILITY A trip generation and distribution letter is required for most projects. However, the following projects are typically under the peak hour threshold and may not be required to prepare a trip generation and distribution letter: • Residential short plats; • Multi-family projects with 9 units or less; • Drive-through coffee stands with no indoor seating; • Changes of use from residential to commercial with no new buildings or building additions; • Office projects of less than 2,500 square feet (ITE land uses 700-799); and, • Industrial projects of less than 9,000 square feet (ITE land uses 100-199). December 2009 Chapter 3—Traffic Analysis 3- 1 CITY OF SPOKANE VALLEY STREET STANDARDS For projects expected to generate less than 10 peak hour vehicular trips the project applicant is required to submit a letter with the following information for all proposed development phases for the property: • Brief project description; • Number of expected employees; • Hours of business; and, • The expected number of vehicular trips (customers and employees) to the business during the AM and PM peak hours. 3.2.2 MINIMUM ELEMENTS The trip generation and distribution letter for projects generating 10 or more peak hour trips shall include the following elements: • Project description, including proposed use; • Site plan with vicinity map; • Building size noted in square feet; • Zoning of the property; • Proposed and existing access points, site circulation, queuing lengths and parking locations; • Project phasing and expected opening year; • An estimate of trip generation for the typical weekday, AM peak hour, and PM peak hour conditions. Supporting calculations and data sources shall be shown. Any adjustments for transit use, pass-by trips, and/or diverted trips shall be clearly stated; • A comparison of the trip generation between the previous and the proposed site use for projects involving a change of use. If the comparison shows a net increase in trip generation, the project will be subject to the TIA requirements of a new development; • A preliminary distribution pattern for traffic on the adjacent street network, shown in a graphical format; and, • The engineering seal signed and dated by the Engineer who prepared the letter. December 2009 Chapter 3—Traffic Analysis 3-2 CITY OF SPOKANE VALLEY STREET STANDARDS 3.3 TRAFFIC IMPACT ANALYSIS 3.3.1 APPLICABILITY A TIA is required for the following situations: • Projects adding 20 or more peak hour trips to an intersection of arterial streets as defined in Chapter 4 of the City Comprehensive Plan within a one mile radius of the project site as shown by the trip generation and distribution letter; or, • Projects impacting local access intersections, alleys, or driveways located within an area with a current traffic problem as identified by the City or previous traffic study, such as a high-accident location, poor roadway alignment or capacity deficiency. 3.3.2 SCOPE The scope of the TIA shall be developed by a professional engineer licensed in the state of Washington. Prior to submittal of the TIA, the City and other impacted jurisdictions/agencies shall approve the scope of the TIA. The scope of the TIA shall conform to the following: • The study area shall include any intersections of arterial streets within a one mile radius of the site that would experience an increase of at least 20 vehicle trips during a peak hour. Some intersections may be excluded if analyzed within the past year and are shown to operate at LOS C or better. All site access points shall be analyzed. Additional arterial intersections outside of the one mile radius and intersections of local streets may also be required at the discretion of the City; • A PM peak hour LOS analysis shall be conducted for all study area intersections. An LOS analysis of the AM peak hour, Saturday afternoon, or other time period may be required at the discretion of the City; and, • Additional analysis may be required by other reviewing agencies. The LOS shall meet or exceed the thresholds set forth in the City of Spokane Valley Comprehensive Plan — Chapter 4: Capital Facilities Table 4.3 Spokane Valley Level of Service Standards. 3.3.3 METHODOLOGY The analysis shall be done using the following methodology: • Background growth rate — The background growth rate may be based on historical growth data and/or the SRTC Regional Travel Demand Model, as approved by the City. This rate is to be applied to existing turning movement volumes prior to the addition of background project traffic or site generated traffic volumes. The minimal growth rate of 1.1 percent is December 2009 Chapter 3—Traffic Analysis 3-3 CITY OF SPOKANE VALLEY STREET STANDARDS required. Under no circumstances shall the growth rate be less than 1.1 percent; • The LOS shall be determined in accordance with the methods reported in the latest edition of the Highway Capacity Manual (HCM); • Use of the two-stage gap acceptance methodology for unsignalized intersections is subject to City approval; • Other analysis tools may be utilized with City approval if HCM methodology cannot accurately model an intersection; • Trip generation data shall be based on the latest edition of the ITE Trip Generation Manual. Trip generation data from studies of similar facilities may be substituted as approved by the City; and, • Turning movement counts shall be recorded less than one year prior to submitting a traffic study. Counts less than 2 years old may be used if no significant development projects or changes to the transportation network have occurred. Counts should be taken on a Tuesday, Wednesday, or Thursday representing a typical travel day. Counts should not be taken during a week which contains a holiday. Projects near schools may be required to collect turning movement counts during the school year. 3.3.4 TIA REPORT MINIMUM ELEMENTS The TIA report shall include the following, at a minimum: 3.3.4.1 Title Page The TIA shall include a title page with the following elements: • Name of project; • City project number/permit number; • Applicant's name and address; • Engineer's name, address and phone number; • Date of study preparation; and, • The engineering seal, signed and dated by the professional engineer licensed in the State of Washington who prepared the report. 3.3.4.2 Introduction and Summary • Purpose of report and study objectives; • Executive summary; • Proposed development description; • Location and study area; • Findings; and, December 2009 Chapter 3—Traffic Analysis 3-4 CITY OF SPOKANE VALLEY STREET STANDARDS • Recommendations and mitigation. 3.3.4.3 Proposed Development The TIA shall include the following information for the proposed development: • Project description; • Location and vicinity map; • Site plan with building size (square feet); • Proposed zoning; • Land use; • Access points, site circulation, queuing lengths, and parking locations; • An estimate of trip generation for the typical weekday, AM peak hour, and PM peak hour conditions. Any adjustments for transit use, pass-by trips, and/or diverted trips shall be clearly stated; • A distribution pattern for traffic on the adjacent street network, shown in a graphical format; and, • Project phasing and timing. 3.3.4.4 Summary of Existing Conditions The TIA shall provide a summary of existing conditions for the study area that includes the following: • Transportation network description, including functional classification, bike/pedestrian facilities and transit routes; • Existing zoning; • Existing traffic volumes including percent heavy vehicles; • Accident history—past 3 years; • Posted speed limits (and if known the 85 percentile speed determined from a speed study); • Length of existing turn pockets at signalized intersections; and, • Location of the following: o On-street parking, o Bus stops, o Private and public schools in the area, and, o Hospitals, police and fire stations in the area. December 2009 Chapter 3—Traffic Analysis 3-5 CITY OF SPOKANE VALLEY STREET STANDARDS 3.3.4.5 Background Projects Background project traffic includes the following : • Traffic from newly constructed projects; • Projects for which traffic impacts have been tentatively reserved; • Projects for which a Concurrency Certificate has been awarded; • Non-project, general background traffic increases; and, • Vested traffic for vacant buildings that are undergoing redevelopment. The TIA shall provide the following information for background projects, as identified by the City: • Project descriptions; • Vicinity map; • Trip generation; • Trip distribution; and, • Planned transportation improvements (private development and City). 3.3.4.6 Analysis Scenarios The TIA shall include the following analysis scenarios: • Existing conditions; • Build-out year without project; • Build-out year with project; • Build-out + 5 analysis if project is expected to proceed in phases, take more than 6 years to complete, or if the study intersection is included on the City's 6-Year TIP; and, • Build-out Year + 20 analysis if the project mitigation involves installation or modification to an intersection controlled with a traffic signal or roundabout. Forecast volumes shall be estimated using the SRTC Regional Travel Demand Model. 3.3.4.7 Other Analyses Other analyses may be required as requested by the City, including but not limited to: • Sight distance; • Queue lengths at signalized intersections; • Queue lengths at driveways and drive-up windows; • Noise; • Air quality (typically required when physical improvements are proposed and requires electronic submittal of Synchro files); December 2009 Chapter 3—Traffic Analysis - 3-6 CITY OF SPOKANE VALLEY STREET STANDARDS • Intersection control warrant analysis (signal, 4-way stop, yield); • Auxiliary lane warrant analysis; • Site access; and, • Pedestrian study. 3.3.4.8 Findings The following shall be addressed in the findings section: • Traffic impacts; • Compliance with level of service standards; • Proposed project improvements; and, • Recommendations and mitigation. 3.3.4.9 Appendices The following information shall be included in appendices: • Definitions; • Trip generation sources; • Passer-by and origin-destination studies; • Volume and turning movement count sheets; • Level of service calculations; • Synchro report printouts (electronic submittal may be required); • Warrant analysis calculations; and, • References. 3.4 MEETINGS A public meeting(s) may be required for any residential project generating over 100 PM peak hour trips, commercial projects generating over 100 PM peak hour trips impacting a residential area, or for other projects at the discretion of the City. The intent of the public meeting is to let the public know about the proposed project and to allow for public input to determine the scope of the TIA. Notice of date, time, place and purpose of the public meeting(s) shall be provided by the following means: • One publication in Spokane Valley's official newspaper at least 15 days prior to the meeting; • A mailing to adjacent residents, property owners, neighborhood groups, jurisdictions, and /or organizations within a 400-foot radius of the project boundaries, not less than 15 days prior to the public meeting; and, December 2009 Chapter 3—Traffic Analysis 3-7 CITY OF SPOKANE VALLEY STREET STANDARDS • A sign shall be erected, on the subject property fronting and adjacent to the most heavily traveled public street, at least 15 days prior to the meetings. The sign shall be at least 4 feet in width and 4 feet in height and shall have letters 3 inches in size. The sign shall be easily read by the traveling public from the right-of-way. This sign shall announce the date, time and place of the traffic meetings and provide a brief description of the project. Proper notification and all associated costs shall be the responsibility of the Applicant. Notification shall be considered satisfied upon receipt of an affidavit provided by the Applicant to the City stating the above requirements have been completed. December 2009 Chapter 3—Traffic Analysis 3-8 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 4 - REQUIREMENTS FOR PLAN SUBMITTAL __„ c y . • I. ij.-i .t 2.7 .' - r..` a mi,- Nz a. •7: 40 . .. Y_ Chapter Organization 4.1 Introduction 1 4.2 General Requirements 1 4.2.1 Plan Completeness 1 4.2.2 Fonts 1 4.2.3 Lines and Symbols 1 4.2.4 Sheet Size/Plan Medium 1 4.2.5 Engineer Signature and Stamp 2 4.2.6 Scale 2 4.2.7 North Arrow 2 4.2.8 Vertical and Horizontal Datum 2 4.2.9 Utility Locate Note 2 4.2.10 Title Block 2 4.2.11 Required Civil Plan Sheets 3 4.2.12 Required Traffic Plan Sheets 3 4.2.13 Other Required Plan Sheets 3 4.3 Specific Requirements for Plan Sheets 3 4.4 Cover Sheet 4 4.4.1 Applicability 4 4.4.2 Minimum Elements 4 4.5 Clearing and Grading Plan 5 December 2009 Chapter 4—Requirements for Plan Submittal 4-i CITY OF SPOKANE VALLEY STREET STANDARDS 4.5.1 Applicability 5 4.5.2 Minimum Plan Elements 5 4.6 Street Improvements Plan 6 4.6.1 Applicability 6 4.6.2 Minimum Plan View Elements 6 4.6.3 Minimum Profile View Elements 8 4.6.4 Minimum Typical Cross Section Elements 8 4.7 Onsite Improvement Plan 9 4.7.1 Applicability 9 4.7.2 Minimum Elements for Onsite Improvement Plan 10 4.8 Drainage Plan 11 4.9 Temporary Erosion and Sediment Control Plan 11 4.10 Temporary Traffic Control Plan 11 4.11 Permanent Traffic Control Plan 11 4.11.1 Area Map 11 4.11.2 Road Segment Pages 11 4.11.3 Signing Plan 11 4.11.4 Striping Plan 12 4.11.5 Traffic Signal Plan 12 4.12 Site Plan of Record 12 List of Appendices Appendix 4A- General Construction Notes 13 December 2009 Chapter 4—Requirements for Plan Submittal 4-H CITY OF SPOKANE VALLEY STREET STANDARDS 4.1 INTRODUCTION The Applicant is required to submit a complete plan set for all proposed public and private improvements. This chapter provides the minimum plan elements for a complete submittal. To be accepted for review, plans shall be clear, concise and easy to read with all lettering and lines legible. Hand drawn plans are not acceptable. Incomplete plan sets will not be reviewed and will be returned to the Applicant. State law requires that engineering work be performed by or under the direction of a professional engineer currently licensed in the State of Washington. 4.2 GENERAL REQUIREMENTS 4.2.1 PLAN COMPLETENESS All plan submittals are assumed to be the final plan set and so all plan sheets for every submittal shall be signed by the developer and the Applicant's Engineer as per Section 4.2.5. It is the responsibility of the Applicant's Engineer to verify that all minimum requirements specified in the Street Standards and the Spokane Regional Stormwater Manual are met and are incorporated in the plan set. Each submittal of revised plans and supporting documents shall be accompanied by a letter that indicates how each review comment was addressed and provides a brief description of any changes made that were not in direct response to a review comment. 4.2.2 FONTS Lettering shall be legible to be easily read and understood by the reviewer. Lettering shall be of sufficient size and scale to produce clear, readable images when scanned digitally by an optical scanner. 4.2.3 LINES AND SYMBOLS Standard drafting lines and symbols are shown on the Standard Plan R-100. All drawings submitted for review shall use these line types and symbols. When used in the plans, the symbols and line types shall be shown in a legend in the plan set. 4.2.4 SHEET SIZE / PLAN MEDIUM All plan sets shall be plotted or copied on standard drafting paper with dark ink. When the plans or plats are accepted, the City will specify the media type required in the acceptance letter. All plan sheets shall be 24 inches by 36 inches (D size). December 2009 Chapter 4—Requirements for Plan Submittal 4- 1 CITY OF SPOKANE VALLEY STREET STANDARDS 4.2.5 ENGINEER SIGNATURE AND STAMP All sheets shall include the engineer's signature, stamp, and date of signature in accordance with the regulations established by the State of Washington Board of Registration of Professional Engineers. 4.2.6 SCALE The scale for all plan and profile sheets shall be: • Horizontal: 1 inch = 20, 30, 40, or 50 feet (scales greater than 1 inch = 50 feet shall not be accepted) • Vertical: 1 inch= 5 or 10 feet • Overall plan: 1 inch = 100 feet, maximum • Cross sections: vertical exaggeration ratio shall be 5:1 4.2.7 NORTH ARROW All design sheets shall have a north arrow oriented toward the top or right side of applicable sheets. 4.2.8 VERTICAL AND HORIZONTAL DATUM The City of Spokane Valley vertical datum shall be based on the National American Vertical datum (NAVD 1988). The horizontal datum is a coordinate system based on 1983(91) State Plane Coordinates. 4.2.9 UTILITY LOCATE NOTE All utilities shall be located prior to construction. All sheets except the cover sheet, detail sheets and traffic control plan shall have the following message: CALL 2 BUSINESS DAYS BEFORE YOU DIG 811 OR 1-800-424-5555 4.2.10 TITLE BLOCK A title block is required on every sheet. The title block shall be located in the extreme lower right hand comer, the right side margin, or along the bottom edge of the sheet. The following information shall appear in the title block: • Project name and number (including permit number, Short plat, Subdivision or Binding Site Plan numbers) provided by the City; • The type and location of improvement. (For profile sheets, the title block shall have the name of the street and beginning/end stations); December 2009 Chapter 4—Requirements for Plan Submittal 4-2 CITY OF SPOKANE VALLEY STREET STANDARDS • Engineer's name, address, including zip code, telephone number, and fax number; • Date and brief description of all revisions; • Sheet number and total number of sheets; and, • Name of property Owner and Applicant. 4.2.11 REQUIRED CIVIL PLAN SHEETS Civil plan sets are reviewed by Development Engineering. The civil plan set shall include the following, as applicable: • Cover sheet(see Section 4.4); • Clearing and grading plan(see Section 4.5 ); • Street improvement plan (see Section 4.6); • Onsite improvement plan (see Section 4.7); • Drainage plan (see Section 4.8); • Temporary erosion and sediment control plan (see Section 4.9); and, • Detail sheets, as needed. 4.2.12 REQUIRED TRAFFIC PLAN SHEETS Traffic plan sets are reviewed by the Traffic Division of the Public Works Department. The traffic plan set shall include the following, as applicable: • Permanent traffic control plan (see Section 4.11); • Detail sheets, as needed. 4.2.13 OTHER REQUIRED PLAN SHEETS The site plan of record is reviewed by Development Engineering and the Planning Division. See Section 4.12 for the requirements from Development Engineering. 4.3 SPECIFIC REQUIREMENTS FOR PLAN SHEETS This section outlines the minimum required information to be included on specific sheets of the plan set. The sheets are listed in the order they should appear in the plan set. Some sections of the plan set may have more than one sheet, but should be labeled alike. December 2009 Chapter 4—Requirements for Plan Submittal 4-3 l CITY OF SPOKANE VALLEY STREET STANDARDS 4.4 COVER SHEET 4.4.1 APPLICABILITY All plan sets shall include a cover sheet. 4.4.2 MINIMUM ELEMENTS The following shall be included on the cover sheet: • The project name and the number (including permit number, Short plat, Subdivision or Binding Site Plan numbers) shown in the top center of the page; • A legible vicinity map, approximately 8-V2 inches by 11 inches, showing the location and name of all arterial roadways within one mile of the proposed construction, and all other roadways within 1/2 mile of the proposed construction. The project area shall be indicated by shading; • An index of all sheets within the plan set; • Impervious area calculations for all commercial projects. Calculations shall include the existing, proposed and total rooftop area, pavement area and gravel area, and the overall, total impervious area; • Type of roofing material for all commercial projects; • Section, Township, and Range; • Legend of line types and symbols for all appurtenances related to each type of facility; • General construction notes as provided in Appendix 4A; • Applicant's signature; • The datum used and all benchmarks, which must refer to the established control when available; • Private Improvements Statement. The note below shall appear on the cover sheet of the construction plans that include private improvements: The City of Spokane Valley will not be responsible for the maintenance of street and appurtenant improvements, including storm drainage structures and pipes,for the following private streets: (list street names). December 2009 Chapter 4—Requirements for Plan Submittal 4-4 CITY OF SPOKANE VALLEY STREET STANDARDS 4.5 CLEARING AND GRADING PLAN 4.5.1 APPLICABILITY Clearing and grading sheets are required for projects applying for: • A clearing and grubbing permit; • A grading only permit; • A building permit for all new non-residential development and for residential construction of four or more units per lot; • Short plats; • Long plats; or • Binding Site Plans. 4.5.2 MINIMUM PLAN ELEMENTS Clearing and grading sheets shall clearly convey design and construction intent and shall depict only the work to be done with the requested permit. Clearing and grading sheets shall include, as applicable: • Property limits and accurate contours of existing ground elevations. For existing topography, one-foot contour intervals are preferred unless the City determines that available 5-foot contour mapping is adequate and detailed enough to describe current landforms; • The extent of clearing and/or grading areas, delineated and labeled "excavation" or "fill"; • Finish contours to be achieved by the grading and related construction. The contour interval for proposed topography must be no more than 1- foot, unless the slope is greater than 10 percent, in which case, the City may accept 5-foot contour intervals. Periodically call out the proposed slope. One-foot contours may still be necessary to show certain features such as swales; • Existing and proposed surface and subsurface drainage facilities; • Footprint of onsite buildings or structures and the location of adjacent buildings or structures located within 15 feet of the property or which may be affected by the proposed grading operations; • Cross-section along the proposed and/or existing street, spaced every 50 feet, when required by the City. The cross-sections shall show proposed and existing topography along the street, at tie in points and property boundaries; December 2009 Chapter 4—Requirements for Plan Submittal 4-5 CITY OF SPOKANE VALLEY STREET STANDARDS • Information covering construction and material requirements including, but not limited to, specification of the soil compaction to be achieved in any areas of fill placement; • Estimated amount and vertical dimensions of cut and fill; • Delineation of sensitive areas, floodplains, and critical areas per SVMC Title 21; • The approximate location of all trees 8-inches diameter breast height (dbh) and larger, and a description of the tree protection standards to be implemented during construction; • Delineation of any areas to be preserved. 4.6 STREET IMPROVEMENTS PLAN 4.6.1 APPLICABILITY Street improvements sheets are required for projects: • Proposing new public or private street or street extensions; • Proposing private engineered driveways; or, • Required to provide frontage improvements. 4.6.2 MINIMUM PLAN VIEW ELEMENTS The plan view shall include, at a minimum, the following: • Survey lines and stationing lines. Lines shall normally be based on centerline of street. Other profiles may be included but shall be referenced to centerline stationing. Stationing in cul-de-sacs shall be on the centerline to the center of the bulb, with dimensioned slopes along the flowlines within the bulb; • Property limits and accurate contours of existing ground elevations. For existing topography, one-foot contour intervals are preferred unless the City determines that available 5-foot contour mapping is adequate and detailed enough to describe current landforms; • Finish contours to be achieved by the grading and related construction. The contour interval for proposed topography must be no more than one- foot, unless the slope is greater than 10 percent, in which case, the City may accept 5-foot contour intervals. Periodically call out the proposed slope. One-foot contours may still be necessary to show certain features such as swales; • Lot lines, lot numbers and block numbers; • Proposed and adjoining subdivision names; December 2009 - Chapter 4—Requirements for Plan Submittal 4-6 CITY OF SPOKANE VALLEY STREET STANDARDS • Existing and proposed street names; • Section, Township, and Range; • Existing and proposed property and/or right-of-way lines, easements, and/or tracts. All of them shall be labeled and dimensioned; • Road alignments with 100-foot stationing, reading from left to right, and stationing at points of curve, tangent, and intersections, with appropriate ties to existing road surveys and stationing, section corners, quarter corners, and the County GPS control net. Stations shall increase from west to east and from south to north; • Match lines and stations; • Bearings on the road centerline, keyed to an associated plat map; • Station and elevation of all horizontal curves including PI, PC's, PT's, etc.; existing and proposed, centerline bearings, distances, and complete curve data; • Curve data including radius, delta, arc length and semi-tangent length on all street centerlines and curb returns; • Stations and elevations of all curb returns; including beginning, mid-point, and ending elevations of curb returns; • Location of all proposed and existing approaches; • All existing utilities; • All proposed utilities that will be designed and constructed. The plan sheet shall show the extent of the pavement cut for connections; • Proposed drainage features including station and type of all structures, direction of flow, size and kind of each drainage channel, ditch or pipe and any other requirements as specified in the Spokane Regional Stormwater Manual, as amended; • A thorough search for all survey monuments shall be conducted. Any survey monuments shall be shown; • Fire hydrant locations; • No Parking signs and locations; • Turnaround locations; • Fire emergency access easements; • Traffic elements such as conduit,junction boxes, signal cabinets, electrical service, signal poles, push-button poles, and loops; • Storm drainage flow direction arrows, particularly at intersections and all high and low points; and, December 2009 Chapter 4—Requirements for Plan Submittal 4-7 CITY OF SPOKANE VALLEY STREET STANDARDS • Station and critical elevation (flowline, invert of pipe, etc.) of all existing and proposed utility or drainage structures. Location of utilities shall be identified with horizontal and vertical dimensions as measured from roadway centerline profile grade. 4.6.3 MINIMUM PROFILE VIEW ELEMENTS The profile view shall include, at a minimum, the following: • Stationing, shown the same as in the horizontal plan, reading from left to right. It shall include stationing of points of curve, tangent, length, and point of intersection of vertical curves, with elevations to 0.01 feet; • Original ground line at 100-foot stations and at significant ground breaks and topographic features, based on field measurement and accurate within 0.1 feet on unpaved surface and 0.01 feet on paved surface; • Profiles for curbed streets shall show and label the tops of both curbs and the centerline. Profiles for shouldered streets may show the centerline only. The centerline, top of curb, and existing ground lines of all streets (except cul-de-sacs) shall be continued for 100 feet beyond the proposed construction; • High and low point and PI of all vertical curves; • Ditch and swale flowlines and drainage structures; • A continuous profile for both existing and proposed improvements, shown on a grid of numbered lines; • Elevation of vertical grade breaks, K values, grade and length of vertical curves; • Storm drainage flow direction arrows, particularly at intersections and all high and low points; and, • Station and critical elevation (flowline, invert of pipe, etc.) of all existing and proposed utility or drainage structures. Location of utilities shall be identified with horizontal and vertical dimensions as measured from roadway centerline profile grade. 4.6.4 MINIMUM TYPICAL CROSS SECTION ELEMENTS A typical street section shall include, at a minimum, the following: • A separate full-width, typical section required for each street or portion of the street that differs significantly. The typical section shall be drawn looking in the direction of increasing stations; • Station limits; December 2009 Chapter 4—Requirements for Plan Submittal 4-8 CITY OF SPOKANE VALLEY STREET STANDARDS • The dimensions of traffic lanes, shoulders, gutters, sidewalks, swales, depths, planting strips, easements, right-of-way, etc.; • The cross slope of elements such as pavement, ditches, sidewalks, etc.; • Type of curb; • Dimensions and type of structural section material layers; and, • Retaining walls, as applicable. 4.7 ONSITE IMPROVEMENT PLAN 4.7.1 APPLICABILITY Onsite improvement plans are required for projects proposing: • New commercial developments; • Residential construction of three or more units per lot; • Drywells; • A project site that will have both of the following: 1) any addition or replacement of impervious surface and 2) 5000 or more total square feet of impervious surface. If both of these criteria are met then the runoff from the new and/or replaced PGIS surfaces and areas hydraulically connected to them will need to be treated prior to disposal. The site includes all of the parcels involved in the project whether or not they are contiguous. Impervious surface includes roofs, paved areas, gravel travelways, etc. Full build-out includes all the project's phases even if- o The different phases will be constructed under separate contract and/or by separate owners, and/or, o The project is phased over multiple years, but the phases are still under a consistent plan for long term development; and, • Additions or alterations to, or change in use of existing buildings, sites, or parking areas where the work: o Increases impervious areas to 5,000 square feet or more; o Alters site access requirements, including adding or removing driveways; or, o Connects to and impacts City streets and utilities. December 2009 Chapter 4—Requirements for Plan Submittal 4-9 CITY OF SPOKANE VALLEY STREET STANDARDS 4.7.2 MINIMUM ELEMENTS FOR ONSITE IMPROVEMENT PLAN The onsite improvement plan shall include, at a minimum, the following: • Property limits and accurate contours of existing ground elevations. For existing topography, one-foot contour intervals are preferred unless the City determines that available 5-foot contour mapping is adequate and detailed enough to describe current landforms; • Finish contours or spot elevations to be achieved by the grading and related construction. The contour interval for proposed topography must be no more than 1-foot, unless the slope is greater than 10 percent, in which case, the City may accept 5-foot contour intervals. Periodically call out the proposed slope. One-foot contours may still be necessary to show certain features such as swales; • Lot lines, lot numbers and block numbers; • Existing street names; • Section, Township, and Range; • Existing and proposed property and/or right-of-way lines, easements, and/or tracts. Type and dimension of easement or tract shall be clearly labeled. Dimensions of property and right-of-way lines shall be marked. • Location of all proposed and existing driveways; • All existing utilities; • All proposed utilities that will be designed and constructed. The plan shall show the extent of pavement cut(s) for connections; • Proposed drainage features including, structure type, locating information, direction of flow, size and kind of each drainage channel, ditch or pipe and any other requirements as specified in the Spokane Regional Stormwater Manual, as amended; • Fire hydrant locations; • No Parking signs and locations; • Turnaround locations; • Storm drainage flow direction arrows, particularly at intersections and all high and low points; and, • Station and critical elevation (flowline, invert of pipe, etc.) of all existing and proposed utility or drainage structures. Location of utilities shall be identified with horizontal and vertical dimensions as measured from roadway centerline profile grade. December 2009 Chapter 4—Requirements for Plan Submittal 4- 10 • CITY OF SPOKANE VALLEY STREET STANDARDS 4.8 DRAINAGE PLAN A drainage plan, showing the location of drainage facilities intended to provide flow control, treatment, and conveyance shall be submitted with the construction plans and shall conform to Section 3.5.2 of the Spokane Regional Stormwater Manual (SRSM), as amended. For small projects, the drainage plan may be included in the Onsite Improvement Plan. 4.9 TEMPORARY EROSION AND SEDIMENT CONTROL PLAN A Temporary erosion and sediment control (TESC) plan shall be submitted for all projects as specified in Section 5.3.1 and shall conform to Section 5.3 and the SRSM, as amended. For small projects, the temporary erosion and sediment control plan may be included in the clearing and grading plan. 4.10 TEMPORARY TRAFFIC CONTROL PLAN A temporary traffic control plan shall be included with the right-of-way permit. The plan shall be in detail appropriate to the complexity of the project per MUTCD Chapter 6 B. 4.11 PERMANENT TRAFFIC CONTROL PLAN When required, permanent traffic control plan sheets shall include the components outlined below. Permanent signage and striping shall be complete and in place prior to the acceptance of the certification package. 4.11.1 AREA MAP Separate signage and striping plans shall consist of an overall area map noting all specific use areas, such as schools, parks, recreation centers, library, commercial, industrial, etc. 4.11.2 ROAD SEGMENT PAGES The pages following the area map shall be broken down into street segments, for notation of signage and striping details. 4.11.3 SIGNING PLAN The permanent signing plan shall: • Show the longitudinal location of each sign (horizontal offset and station); • Specify the sign legend and sign type (from MUTCD and International Fire Code); • Specify the sign size and applicable standard plan; December 2009 Chapter 4—Requirements for Plan Submittal 4- 11 CITY OF SPOKANE VALLEY STREET STANDARDS • Refer to Standard Plan R-140 for post and base dimensions and installation plan; • Specify the blank gauge of the sign; and, • Note the reflectorization provided. 4.11.4 STRIPING PLAN The striping plan shall show: • Color and type; • Lane widths,taper lengths, storage lengths, etc.; • Striping/skip interval; • Any construction or application notes, (e.g., application temperatures, surface cleaning methods to be used prior to application, etc.); • Typical treatments for acceleration/deceleration lanes, turning lanes, and crosswalks; • Type of material (epoxy, latex, thermoplastic, etc.); and, • Station and offset or dimensions to all angle points, symbol locations, and line terminations. 4.11.5 TRAFFIC SIGNAL PLAN Traffic signal installation and equipment shall be coordinated with and approved by the Public Works Department. The applicable MUTCD signal warrants shall be met. 4.12 SITE PLAN OF RECORD Development Engineering requires that the following items be included: • The footprint of drainage facilities including swales, ponds, channels, detention/retention basins, inlets, drywells, etc. • A table providing the following areas in square feet: total rooftop areas, total pavement area, total gravel area and total impervious area. December 2009 Chapter 4—Requirements for Plan Submittal 4- 12 CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 4A-GENERAL CONSTRUCTION NOTES 1. All work and materials shall be in conformance with the latest edition of the City of Spokane Valley Street Standards, Spokane Regional Stormwater Manual and all other governing agency's standards. 2. Prior to site construction, the Contractor is responsible for locating underground utilities. Call the underground utility location service at 1-800-424-5555 before you dig. 3. Locations of existing utilities shown in the plans are approximate. The Contractor shall be responsible for locating all underground utilities. Any conflicting utilities shall be relocated prior to construction of road and drainage facilities. 4. The Contractor is required to have a complete set of the accepted street and drainage plans on the job site whenever construction is in progress. 5. If the Contractor discovers any discrepancies between the plans and existing conditions encountered, the contractor shall immediately notify the Applicant's engineer and Onsite Inspector. 6. The Contractor shall take precautions to protect the infiltration capacity of stormwater facilities (e.g., line the facility with filter fabric, over-excavate upon completion of the infrastructure, etc.) 7. Where directed by the City of Spokane Valley, the Contractor shall place traffic control devices, the placement and type of which shall conform to the Manual of Uniform Traffic Control Devices (MUTCD). - 8. It shall be the Contractor's responsibility to coordinate with and contact all appropriate utilities involved prior to construction. 9. All pavement cuts to connect utilities shall be repaired in conformance with the Regional Pavement Cut Policy. 10. All survey monuments shall be protected during construction by or under the direction of a Licensed Surveyor as required by State Law. Any disturbed or damaged monuments shall be replaced by or under the direction of a licensed Surveyor prior to certification /final plat and/or release of surety. The Contractor is responsible for the filing of permits for monument removal and replacement with the Washington State Department of Natural Resources, as required by WAC-120-070. 11. Contractor shall be responsible for scheduling and acquiring electrical inspections required by the State. 12. Contractor is responsible to verify that all required permits have been obtained prior to initiating construction. 13. The Contractor and all subcontractors shall have a current City of Spokane Valley Business License. 14. The Contractor and all subcontractors shall be licensed by the State of Washington and bonded to do work in the public right-of-way. December 2009 Chapter 4—Requirements for Plan Submittal 4- 13 CITY OF SPOKANE VALLEY STREET STANDARDS 15. No work on this project shall commence until a City of Spokane Valley right-of-way permit has been issued. 16. The Contractor shall protect adjacent properties, public or private, at all times during construction. 17. Contractors shall control dust in accordance with regulations of local air pollution control authority. 18. Contractor shall remove all construction related debris to an approved waste disposal site. 19. Fire hydrants shall be installed and functioning prior to the construction of any structures. 20. Contractor shall maintain fire apparatus access streets during construction. 21. The Contractor is required to notify the On-site Inspector 1 business day before any construction or product placement takes place that requires testing or observation (Refer to Appendix 9A- Minimum Material Testing Frequencies). The On-site Inspector will determine the time required to satisfactorily achieve the necessary testing, observation and documentation. The On-site Inspector will be required to be on site 100% of the time during HMA placement, drywell placement, and trench work. Supplemental notes used when applicable: 22. For any curb grades less than 1.0% (0.01 ft/ft), a Professional Land Surveyor currently licensed in the State of Washington shall verify that the curb forms are at the grades noted on the accepted plans, prior to placement of concrete. The Contractor is responsible for arranging and coordinating work with the Surveyor. 23. The Contractor shall employ a Professional Land Surveyor currently licensed in the State of Washington to verify that the cross-gutter forms are at the correct plane grade prior to concrete placement.. 24. Concrete aprons are required at the inlet into any swale or pond. The finish grade of the swale/pond side slope, where the concrete inlet apron ends, shall be a minimum of 2 inches below the finished elevation of the concrete curb apron extension. The intention is to allow stormwater runoff to enter the swale/pond unobstructed, without backing up into the street and gutter due to sod overgrowth at the inlet. 25. Unlined pond and bio-infiltration swale bottoms are expected to infiltrate via the pond floor, and therefore, shall not be heavily compacted; equipment traffic shall be minimized on the pond bottoms. The facility sub-grade shall be a medium- to well- draining material, with a minimum thickness of 48 inches and a minimum infiltration rate of 0.15 in/hr. The facility shall drain within 72 hours of a storm event. If the pond also serves as a water quality treatment facility, the treatment zone (sod and 6 inches of treatment soil) shall be a medium- to well-draining material, with a minimum infiltration rate of 0.25- 0.50 in/hr. Scarify the finish grade of the pond bottom prior to hydroseeding/sodding. Testing that verifies subgrade minimum infiltration rate may be required by the local jurisdiction prior to construction certification to ensure adequate drainage. Infiltrative testing of the treatment zone is only required if soils other than silty loam or loamy soils are proposed. December 2009 Chapter 4—Requirements for Plan Submittal 4- 14 CITY OF SPOKANE VALLEY STREET STANDARDS 26. If during final inspection, it is found that the constructed pond or swale does not conform to the accepted design, the system shall be reconstructed so that it does comply. Refer to Appendix 9A of the Spokane Regional Stormwater Manual for Erosion and Sediment Control Standard Notes. December 2009 - Chapter 4—Requirements for Plan Submittal 4- 15 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 4—Requirements for Plan Submittal 4- 16 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 6 - UTILITIES � �4 S -"•"4, . lam � k 4 '�L t m .t II t �> CT' �t iV ryya ea 8 l 4c. X� � {ti tt,a„�`t rat .,� xt„r rY4g'` r _ lit Zy 1+[' - ' YK{ ,- a yn�G o h4 4 i 1-.., 1_ `�Syy' � �� - P" t:Dff -n"'�.+111 T Tvf�S- r ^ti- 3; :,'tQ1 _ wi +7 4 r Zvi; 1 is \+ . f�KK'ark 1.,' i K �.t`,M 6iC`:2 .L : i i. 1S V `t tt j.n y�y S•x .qr�t, J "'.� '6 ' \ TyY �4•t+a c i Ln ;;I*4-,---s:,a,`- ' ' 1 z lay -Pte.� � u"n�"' •x ■ .IN � bL t 't ,��..1' 'tl.'.R'•a'r` 5 Chapter Organization 6.1 Introduction 1 6.2 Design Criteria 1 6.2.1 Utilities Located within Right-Of-Way 1 6.2.2 Underground Utilities 1 6.2.3 Aboveground Utilities 2 6.2.4 Regional Pavement Cut Policy 2 Appendix 6A - Regional Pavement Cut Policy 4 • December 2009 Chapter 6—Utilities 6-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 6—Utilities 6-ii CITY OF SPOKANE VALLEY STREET STANDARDS 6.1 INTRODUCTION The design and construction of public and private utilities located within City right-of- way shall be in conformance with these standards. 6.2 DESIGN CRITERIA The City has established the following minimum requirements to ensure the efficient construction of utilities with the least impact to City transportation and utility infrastructure. 6.2.1 UTILITIES LOCATED WITHIN RIGHT-OF-WAY In accordance with SVMC Title 20.20.090 M, the short subdivision, subdivision, or binding site plan shall provide underground utilities within all new public right-of- way, alleys, or utility easements including, but not limited to, those for electricity, communication, and street lighting. 6.2.2 UNDERGROUND UTILITIES New underground utilities shall meet the following requirements: • Private utility lines shall be located within the right-of-way only when approved by the City. Utility companies shall have a current franchise or public way agreement consistent with Spokane Valley's Uniform Development Code; • Private utilities shall be located a minimum horizontal distance of 5 feet from buildings and public utilities; • When crossing public utilities, private utilities shall be located a minimum vertical distance of 12 inches from the public utility; • Manhole covers, utility box lids, and all other underground utility and irrigation access covers shall not be located within the sidewalk or driveway approaches; • Sewer utility installation shall satisfy Spokane County's Standards for Road and Sewer Construction and the Department of Health's Orange Book, • Water line installations or modifications shall satisfy AWWA (American Water Works Association) Standard Specifications; • End markers shall be installed at the end of all utility stubs or crossings, and locator tape shall be installed at a maximum of 6 inches above all conduits, pipe and cables; and, • The Applicant shall notify the applicable utility companies of upcoming street construction, so they have the opportunity to upgrade their utilities in conjunction with the development project, if desired. December 2009 Chapter 6—Utilities 6• I CITY OF SPOKANE VALLEY STREET STANDARDS 6.2.3 ABOVEGROUND UTILITIES On projects where underground requirements do not apply, the following parameters shall be addressed in locating aboveground utilities: • Utilities shall be located per Standard Plan U-100; • Utility poles and other aboveground utility structures located on curbed streets with separated sidewalks shall be installed a minimum of 2 feet behind the back of curb. When the sidewalk is adjacent to the curb, they shall be located a minimum of 2 feet behind the sidewalk. For shouldered streets, utility poles and other aboveground utility structures shall be located outside the clear zone in accordance with the AASHTO manual "A Policy on Geometric Design of Highways and Streets" and Chapter 7; • Utility poles and other aboveground utility structures shall not be located within the sidewalk. Sidewalks shall have a continuous unobstructed path of at least five feet wide; • Utility poles and other aboveground utility structures shall not interfere with driveways, intersections, clear zone, and all other road features. They shall not obstruct with sight distance, road signing, traffic signals, culverts, etc. This may require that existing poles be relocated at the Applicant's expense; • No utility pole or other aboveground utility structures shall be located in such a way as to pose a hazard to the general public. Utility companies shall locate and replace poles and other structures with primary consideration given to public safety and roadway functionality; and, • When an Applicant-driven project requires the relocation of private utilities due to public utility extensions or other City required improvements, the cost of relocation of the private utility shall be borne by the Applicant. 6.2.4 REGIONAL PAVEMENT CUT POLICY Modification or removal of pavement within the City's right of way is governed by the most current Regional Pavement Cut Policy. General requirements are as follows: • A right-of-way permit is required of any person or company cutting pavement within existing City rights-of-way or on City-owned infrastructure UDC Title 22.130.060; • Permit fees are established in the Spokane Valley Master Fee Schedule; • A pavement cut moratorium is in effect for three years from the date of pavement or reconstruction of pavement for public streets. For streets beyond the moratorium period, cuts are allowed if the requirements of this policy are met; and, December 2009 Chapter 6—Utilities 6-2 CITY OF SPOKANE VALLEY STREET STANDARDS • For pavement cuts and other infrastructure affected by the work, the Applicant shall provide a warranty in accordance with this policy; December 2009 Chapter 6—Utilities 6-3 CITY OF SPOKANE VALLEY STREET STANDARDS Appendix 6A— Regional Pavement Cut Policy December 2009 Chapter 6—Utilities 6-4 t gnarl .a•-,;t1 ' € f SPOKANE E s z F4 1i . Sril ` 61 y -- ¢ pOanl r� rail T. . ri: y galley ) • • DRAFT MODIFIED REGIONAL PAVEMENT CUT POLICY • March 11,2008 PURPOSE: The purpose of this policy is to establish a uniform approach to pavement cuts and repair applicable to utilities and other contractors working in the public rights-of-way. POLICIES: The local agency shall establish a tiered system based on the date of construction or reconstruction of pavement and may apply also criteria for roadway condition. The policies applicable are as follows: • 1. A pavement cut moratorium will be in effect for a period of three years for all new and reconstructed Tier 1 roadways. 2. The policies for Tiers 2-4 roadways is as follows: • a. Full Policy: Patches/paving shall extend the full width of an established travel lane. Pavement cuts shall be full depth and extend 2 feet(2'-0")beyond the nominal trench edge. longitudinally and transversely. There shall be no gaps<four feet(4'-0")from curb or gutter. b. Modified Policy: Patches paving shall extend beyond the wheel path to the middle of the travel lane.Pavement cuts shall be full depth and extend one foot(1'-0")beyond the nominal trench edge longitudinally and transversely..There shall be no gaps<four feet(4'-0")from • curb or gutter. c. Trench Only: Pavement cuts shall be full depth and extend one foot(1'-0")beyond the nominal trench edge longitudinally and transversely at all locations within the roadway.No longitudinal joints shall be located in the wheel path. 3. Tiers Based on Age of Pavement Revised: 3/11/2008 by S. Trabun,Avista 1 Tier 1 Tier 2 Tier 3 Tier 4 Arterial Streets: <3 years Years 4-5 Years 6-12 >12 years Modified Principal Moratorium Policy Full Policy Full Policy Policy Modified Minor Moratorium Policy Full Policy Modified Policy Policy Neighborhood Collector Moratorium Policy Full Policy Modified Policy Trench Only Local Access Streets: Industrial/Commercial Moratorium Policy Modified Policy Modified Policy Trench Only Residential Moratorium Policy Modified policy Modified Policy Trench Only Note: It is the discretion of each jurisdiction to review the individual road seg cent ages to determine patch requirements on longitudinal installation over multiple roadway segments with variable ratings. In principle, each road section will be patched according to the tier in which it is ranked. Note: Any deviation from the Tier Policy will require approval in advance by the local agency. Note: Each agency will provide date of last major reconstruct either electronically or on each permit. Maintenance does not constitute a reconstruct for age determination. Note: Moratorium policy will be reviewed as seam-sealing technology improves. DEFINITIONS Permittees: The utility company or contractor who submits an application for a permit to obstruct and/or conduct construction operations in the public right-of-way. Local agencies and their contractors shall be considered permittees for application of this policy even though the respective agencies and/or their contractors may not take out permits. Local Agency: The governing entity having jurisdiction of the area that the permittee has submitted an application to obstruct or conduct construction operations. Agency Engineer: City or County Engineer,his/her designee(Engineers,Inspectors,Project Managers,Field Personnel)representing a Local Agency. Standard Specifications: Current version of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction, Supplemental Specifications and/or Drawings as attached by local agencies. Project Completion: Date when the following has occurred: final permanent restoration of roadway is complete and approved by the inspector, and all as-built documentation has been submitted to the local agency.A fax transmittal confirmation ticket of`as built' shall be considered confirmation. New Roadway: Any roadway that has had a designed rehabilitation in the permitted excavation location that is less than or equal to three years. Revised: 3/11/2008 by S. Trabun,Avista 2 • Travel Lane: travel lanes shall be established based on striping,or where there is no striping, shall be twelve feet(12'-0")in width. Length of Patch:For this document the length of all patches is the patch dimension parallel to the roadway. Width of Patch: For this document the width of all patches is the patch dimension perpendicular to the roadway. Assignee: The contractor who is taking out the permit. Patch: Cut in the pavement as part of the current permitted job. Potholing: Potholing is the practice of digging a test hole to expose underground utilities to ascertain the horizontal and vertical location of the facility.The horizontal and vertical position of the exposed facility must be tied to a survey benchmark or permanent above grade feature. The position may be identified by GPS or traditional survey coordinates or by measuring the distance, with a tape measure,to permanent features in three horizontal directions.In addition,the vertical distance below grade should be obtained. Bell Hole: A hole dug to allow room for workmen to make a repair or connection in buried pipe, such as caulking bell-and-spigot pipe or welding steel pipe.A bell hole can also be used for the starting location of an underground bore,when using the directional boring equipment.In the broad sense,any hole other than a continuous trench opened for working on a buried facility Compaction: Restoration and backfill of the Trench,Pothole, and Bell hole. Each shall be compacted in lifts using the industry standard equipment to tamp the backfill material to 95% density. Tier: Age of asphalt Full depth:Asphalt depth top td base of asphalt or thickness of asphalt Gap: Distance between two asphalt patches Keyhole:New technology for core drilling;used to drill a plug in the asphalt when checking the depth of existing utilities. MUTCD: Manual on Uniform Traffic Control Devices: Traffic Control should be set up to warn and protect the workers and general public by avoiding the working area during construction. Traffic Control must meet or exceed the Washington State modifications to the MUTCD code for all work done with the City Right of Way(see http://mutcd.fhwa.dot.eov section. Chapter 6G and 611). Revised: 3/11/2008 by S. Trabun,Avista 3 GENERAL REQUIREMENTS 1. Patching: a. No patching material will be allowed within an existing patch if the new patch exceeds seventy percent or more(70%+)of the existing patch. The entire existing patch shall be replaced. b. The minimum length of the patch parallel to the road shall be six feet(6'- 0"). If any part of the excavation,patch or damaged area intrudes into an adjacent lane,that lane shall also be replaced in accordance with the tiered chart. c. New patches adjacent to any existing patch shall be installed at the existing patch line. When this is not feasible,no gap of 4 feet or less shall exist. d. When 2 or more patches are created within a given job that measure 15 feet or less longitudinally or transversely they will be incorporated into a single patch. Anytime five or more patches are required within a 350-foot longitudinal area,the utility will notify the agency to determine if cost sharing is an option to expand the pavement repair/replacement area. e. Only saw cutting or approved grinding device will be allowed. Only parallel and perpendicular pavement cuts will be allowed.No jagged,broken or undermined edges. f. All pavement overcuts shall be sealed using a product approved by the agency. g. The completed surface of all courses shall be of uniform texture; smooth, uniform as to crown and grade and free from defects.The completed surface of the wearing course shall not vary more than 1/4 inch from the lower edge of a ten foot straightedge placed parallel to the centerline. Recognition and consideration will be made for existing roadway conditions. The Agency Engineer must approve corrective measures. 2. Materials. All patching materials and construction requirements not addressed in this document shall conform to each Local Agency's Standards. Longitudinal cuts that extend through multiple tier classifications will require discussion with the local agency to determine appropriate patching approach.In principle,each road section will be patched according to the tier in which it is ranked. 3. Traffic Control: a. All existing traffic control markings will be replaced as soon as possible after permanent paving is completed. b. Temporary markings for lane lines and stop lines shall be in place prior to the roadway opening for traffic. c. All remaining temporary striping will be completed within seven days of new pavement completion and shall be maintained by permittee until permanently restored. d. All traffic markings will be replaced per normal work practices. All temporary traffic control for the work zone shall conform to the MUTCD and Washington State modifications to the MUTCD.All traffic control is subject to the approval of the Agency Engineer or his/her designee Revised:3/11/2008 by S. Trabun,Avista 4 4. Emergency Repairs. The permittee shall be allowed to make emergency repairs provided a more reasonable alternative does not exist. Every reasonable effort will be made to restore the roadway quickly. Local agency will be notified of emergency repairs not later than the next business day. SPECIFIC REQUIREMENTS 1. Chip sealed roads shall be rehabilitated according to construction requirements for asphalt roads as outlined in this document. 2. All existing pavement types shall be constructed at the existing depth of asphalt and crushed surfacing, in accordance with applicable Local Agency Standards(including any fabric or membranes);Replacement section of asphalt and crushed rock shall not be less than the minimum section specified in Local Agency's Design Standards. 3. All concrete road cuts shall be pre-approved before beginning work(except in the case of an emergency situation). Concrete roads shall require full panel replacement unless approved otherwise by local agency. All concrete joints shall require an approved tie bar and dowel retrofit.Depth of concrete replacement shall match the existing thickness,or shall be in accordance with Local Agency's Standards. Care shall be made not to undermine the existing panels.If the adjacent panels are disturbed or damaged,they also shall be replaced at the discretion of the Local Agency.All joints shall be sealed with an approved material. 4. Asphalt over concrete road cuts—if known- shall be pre-approved before beginning work(except in the case of an emergency situation). Saw cutting or other approved practice for removal of the concrete shall be allowed at the discretion of Local Agency. The asphalt portion of the cut shall be constructed according to the pavement cut policy. 5. All areas outside of the travel lanes that are affected by the work shall be restored to their original condition. All shoulders shall be restored to their original condition. EXCEPTIONS: 1. Valve and manhole repairs shall be exempt from the patching requirements of this policy.Valve and manhole patching requirements shall be per each Local Agency's Standards. All warranty and construction requirements shall be met.No longitudinal. construction joints shall be allowed in the wheel path. 2. Potholing to find utilities shall be allowed. To be exempt from the gap and patching policy, cuts shall be a maximum of two-feet square(2'-0") with no longitudinal joints in the wheel path and shall be backfilled with controlled density or other approved fill from six inches above the utility to six inches below bottom of asphalt. Round vs. square cuts are preferred. Revised: 3/11/2008 by S. Trabun,Avista 5 NEW DEVELOPMENT The moratorium policy will be explained both as to costs and to construction practices by the Local Agencies as part of the permitting/zoning process for new construction or major remodeling projects.Individual permittees/utilities will not be responsible for this function. Individual permittees/utilities will be responsible for doing the work and the costs associated with the moratorium policy as they open roadways for work. Cost recovery from developers will be calculated and coordinated by permittee/utility. WARRANTY REQUIREMENTS 1. Pavement cuts on roadways ten years old or less will have a warranty period of five years.The patch in the roadway shall be repaired as necessary until the warranty has passed. 2. All other roadways shall require a minimum three-year warranty period.All warranties shall become void if rehabilitation work is performed to the road within the patching limits. 3. For road cuts performed by a Utility using its internal capability,that Utility or assignee will be responsible for repairs required during the warranty period. 4. All curb,sidewalks and structures that are affected by the excavation shall be included in this policy and have a warranty for five years. 5. All warranty work requires that an agency inspector be on site. The permittee shall be required to coordinate inspection with the appropriate department within the Agency. 6. The following defects identified by the local agency engineer shall be covered by warranty: a. Sunken pavement patches greater than or equal to one-quarter inch (Measured by a ten-foot straight edge). b. Failure to meet agency visual rating standard for patching and joints to medium or high). c. Poor workmanship. d. Inadequate compaction per Agency standard. e. Sunken or damaged curb and sidewalks in excavation work area. f. Sunken or damaged drywells and catch basins in excavation work area. Revised: 3/11/2008 by S. Trabun,Avista 6 7. Notice of Repairs. a. If emergency repairs are needed due to safety concerns,the permittee shall have twenty- four hours in which to make such repairs from time of verbal notice by the Local Agency. b. For non-emergency repairs on arterial roads the permittee shall have forty-eight hours to make such temporary repairs. c. Residential streets,the permittee shall have up to seven days to make such temporary repairs. The local agency may provide for repairs not completed within the specified timeframe and permittee will be assessed all costs associated with the repairs. The costs shall be based on actual costs or the average bid items for comparable projects for the year preceding,plus ten percent overhead fees. If repairs are made other than seam sealing to the warranted patch,a new warranty will be implemented for the new patch. The permittee shall have two days to notify their asphalt company of the needed permanent repairs.If the work is not done in a timely manner and following notification the work shall be privately contracted or Local Agency maintenance crews will perform the needed repairs. The permittee shall be assessed the associated fees for the repairs.All utility cut construction shall follow the construction and warranty requirements per local agencies standards. TEMPORARY PATCHING 1. During winter asphalt concrete paving plant closures or outside of temperature specifications (see section 5-04 of the WSDOT/APWA Standard specification). The permittee shall install and maintain a temporary patch until it can construct a permanent patch. A temporary patch will be required if the road must be opened to traffic before a permanent patch can be made. 2. The temporary patch shall consist of two inches of crushed surfacing and two inches of cold- mix asphalt pavement and/or steel plates, or upon approval of the Agency Engineer, crushed surfacing top coarse may be used. On arterials, when a temporary patch is required for more than two months,Portland Cement Concrete shall be used to construct the temporary patch if weather permits (Contact Local Agency for mix design requirements). The permittee shall maintain the temporary patch until the patch has been permanently restored. PERMITS 1. All work in the `Public Right-of Way' requires a permit issued by the local agency. Permittee shall take out all permits and perform all work. 2. The permittee shall fax or send a letter to the appropriate Local Agency permit center designating their assignees. The permittee will be required to submit a construction and traffic control plans required by local agencies when applying for a permit. If the Agency Engineer determines that abuse of obligations are prevalent,future construction permits shall not be issued until the permittee has fulfilled all obligations to existing permits. Written notification by Local Agency will be sent prior to this action. 3. The permittee shall provide a detailed "As-built" record of the pavement cut after construction is completed. The permittee shall provide details indicating existing pavement section, new pavement section and any unusual conditions at the location of the constructed utility. The location shall include the name of the road the work is being performed on and Revised: 3/11/2008 by S. Trabun,Avista 7 the name of the closest intersections in each direction. Distance measurements shall be from intersecting streets. This information will be provided to the Local Agency's Permit department for a permanent record. This information shall be returned no later than seven days after the completion of the permitted project by mail, fax, or other electronic means by either permittee or patching contractor. The intent of this process is to record small patching details. Larger projects shall be reviewed and approved prior to construction. 4. Each Local Agency may provide permittee to contribute normal patching costs to local agencies to accomplish paving or full depth replacement of the roadway. (This does not apply to work done within sewer projects). 5. The Local Agency should be notified of existing problems with the adjacent roadway to a proposed patch. Every effort will be made to leverage both utility and agency dollars for street improvements. RESPONSIBLE PARTY The permittee shall be responsible for all construction and warranty requirements of this policy. Utilities will provide identity of excavator/permittee as known to local agencies.Local agencies will attempt to get permittee to correct warranty defects. If permittee is a subcontractor for utilities,the utilities will assume responsibility if permittee can not/will not make repairs. COMPLIANCE Failure to comply with any part of this policy may result in denial of future permits. After 3 notices of noncompliance,the Agency shall send a notice to comply within 10 working days or all future permits may be denied until the problems have been corrected. A meeting shall be arranged with the appropriate Agency and a plan of action to prevent future noncompliance shall be presented before issuance of any new permits. An appeal can be applied for in writing to the appropriate Agency. Noncompliance Activities include: 1. Failure to take out a permit. 2. Failure to maintain temporary patches. 3. Failure to make permanent repairs. 4. Failure to make emergency repairs. 5. Failure to make warranty repairs. 6. Failure to send back As-Built information. 7. Failure to inform agency of asphalt completion date. 8. Failure to follow traffic control measures, as required. EXEMPTIONS FOR MORATORIUM ROADWAYS It is understood that field conditions may warrant a waiver or an exemption from these regulations. Developers,Contractors or Owners may appeal for a waiver of the moratorium to allow for excavation into a street that meets the criteria for the moratorium tier. The appeal process completion in NO WAY obligates the affected Agency Engineer to allow such an excavation, and any such decisions are at the Agency Engineer's discretion. Revised: 3/11/2008 by S. Trabun, Avista 8 • Submit a letter of intent to the affected Agency Engineer outlining their proposed project and the impact of the project. • Establish that all alternative avenues have been investigated and fail to meet the needs of the project. • Acknowledge the requirements of restoration of the area affected, and that there will be required special inspection,the cost of which shall be borne by the applicant of the waiver. • Propose a meeting with the Agency Engineer to discuss the project. • Establish a timeline of the project through completion. POLICY REVIEW The local agencies will host a meeting with each other and other interested stakeholders at the end of each construction season for the purpose of reviewing the effectiveness of the policy for the completed construction season and suggested improvements for future construction seasons. Revised: 3/11/2008 by S. Trabun,Avista 9 REFERENCES "Trench Restoration Requirements". City of Bellevue "Utility Trench Cut Restoration Specifications". Metropolitan Transportation Commission(January 1997) "Asphalted Pavement Warranties". Wisconsin Department of Transportation(June 2001) "Impact of Utility Cuts on Pavement Performance". City of Seattle "Managing Utility Cuts"APWA(August 1997) "Gas Industry's Use of Public Right-of-Way"A.G.A. White Paper(September 1998) "Pavement Cut and Repair Standards Manual"DPW&T City of Dallas(October 2003) Revised:3/11/2008 by S Trabun,Avista 10 . TYPICAL TRENCH EXCAVATION EXHIBIT A • • IAsphalt Concrete Wearing Surface r// r, ri• uivirir rte/irra 70/t) • ./ / i •d . . � ": "! ;7..e•O.' J � ..g. :..°;{:•' a. .•' 4. :4'x'•4•• t 4 ° ,z, I ° ° ° Undercutting of ' .Concrete ete ° o I Pavement ' Pavement Base ° e ° e 0• • v e C ° _ Sag from Release • of Lateral Support Mai 3' 3' r Pavement Weakened By Excavation J . Revised:3/11/2008 by S. Trabun,Avista 11 ASPHALTAND CONCRETE PAVEMENT REPAIR Permittee Name: . Job Address: _ _ Coordinates: ❑Street (if no base number.pleasefsihundad4iod<) (&le: 15N 24v) fl Alley Project/Task#: _ RC/Area: Date Cut: Crew: PO/Job#: City/County Permit#: Unusual Conditions/Special Instructions: • Tier#: 1 2 3 4 (Please circle) • Policy: Maitcdum Full Modified Trench (Please circle) .Condition of Cut Tyne of Work Tyne of Repair Existing Road Condition • Overcut Sealant [Circle arythat apply) (PypmyedList) 6"Gravel(required) Gas Asphalt Depth of Asphalt Dow Caning - Cold Mix Electric Concrete Depth of Gravel 660-SL Self Leveling Silicone Joint Sealant Winter Mix Wafer Sub Base Type Schneborn - Sonolastic SL1:One- Sawcut CAN Compound Elastomeric, Grind Communications Self Leveling Polyurethane Sealant Sewer Other ; Asphalt J _ .. 'r I I. . . Width Length x x . I x Concrete Width Length ❑ x x . striping(linear toot) Date Sent for.Repair I • Date Completed: . • I I I C/L Patching Co.Signori: (patching company to fax to local agency at completion) Fax Completed Form to: Spokane County,Sylvia Lightfoot: 509/477.7198 N-2600 (11-07) City of Spokane,Dan Eaton: 509/625-6124 City of Spokane Valley, Scott Wallace: 509/688-0037 Revised:3/11/2008 by S. Trabun,Avista 12 EXHIBIT B1-MORATORIUM/FULL POLICY-ARTERIAL _.AERGENCY ONLY FOR MORATORIUM OR PRIOR APPROVAL CURB UNE r I A. I LANE 4 LANE LINE TRTaa1 11` (NN (ny) (Tyr) LANE 3 ts>ns.^.4,6-23 s.1w.:'Y STREET C/L • NIAHIHM ILMbw34I• � —INX le Int) LANE 2 LANE UNE p 0, _TT_ F (M) 0 6 I A I IV (TYP) LANE 1 PARKING 7 MN ►, F `\ I I LINE r` T! e'(TTPY PARKING CURB LINE . - '', YRN SEWER/WATER WATER(TYP) SERER(TYPO •Nom Pus DCPIN (TM) SERVICE(11P) REPLACEMENT IS IEO'D TO CURB UNE RIEN FEMNNNG I FCEND; TRANSVERSE CUT I DN(dTUOINAI CHIT GSTANCC S6IMEEN WE UNE t MB IS LESS 1HMI 4-FE MM EN PAWNFNT I J TM as OR LESS WE -- (l1OMi0RUN)L A PAVELE]JT PATCH IS RED'D WE UNE TO THESE LAM NO JLNTS GI PEDUCDON N PAVDAOIT LM FULL-DEPTH PAVEMENT REMOVAL AREA ARE ALLOWED. orrI I Ovum VARIES) NMEN PAVEMENT S CREAM THAN}MS DLO r MN DI M ® PAWNENT PATCHIS REDD TO THESE EMUS.NO 7 , Bs.) Eir, 'DINTS OR REWCTICN IN AREA APE ALLOWED• 1.9-15%5742R-5:47:75;7747.4 I_I I i III RNOZ.e I I TRENCH LIMITS AT TOP OF PAVEMENT . AV/ / \(CiY. 1"FULL-DEPTH PAVEMENT PATCH JOINTS 4ULL BE SEALER EXCAVATION ChM • • L ALL CUR W To BE PERPENDICUR TO ORELTON DF TRAWL SECTION A–A =MADE 3.PAVF]ENT REPL*SEWNT IS RECAP TO THE NEST AD MNT ama PAWRNG, REGIONAL PAVEMENT CUT POLICY OR WE LJE WHENEVER A TRENCH OR S PT ASPHALT , ARTERYI � PORr MA n EXTENDS eEra I/( SUCH M EXHIBIT S� MORATORIUM L B1 EXHIBIT B2-MORATORIUM/FULL POLICY—RESIDENTIAL/LOCAL ACCESS "EMERGENCY ONLY FOR MORATORIUM OR PRIOR APPROVAL" CURB LINE TA -I PARKING LANE LINE \ Y MN TRENCH `\�' (iYP) LANE 2 uA s STREET C/L (TM) . P4'Law'. TAI s'MN \`' 12 re) LANE 1 (TYP) I� :TFFY.�[O;■ \\\ PARKING r'f IS'FPN E.X!'-,1 — h —F LINE JI�P�-F(TMP) I:f➢E.l. I L`� E A E a'(MN PARKING CURB LINE SEVER/WATER r MN SFRNCf(TYPO WATER twin SEWER MP) •NOTE: J FULL DEPTH REPLACEMENT IS RED'D TO LONGITUDINAL CUT UM UNE WHEN REMAINING TRANSVERSE GUT DISTANCE BLTIEEN LANE UNE R.AIRS IS LESS THAN 4-FT. I FGFND• LANE DANE UIE F1A1 DD'1H PAVEMENT REMOVAL WHEN ToR,J PAVEMENT IS 3 IRS 01D OR LESS PAVEMENT (M1DIH VAPoES) C--I (NDRATORNN}A PA19.ENT PATGT IS �UCRro(MI IN AREA ATENAOIIPAFR (TM ['\-�I WHEN PAVEMENT IS GREATER MAN h.2.' MIN A. NI \\1 3-YRS GD,A PAVEMENT PATCH 6 REVD e���/._---`-__! ( )_ r ./ TO THESE UNITS NO JOINTS CR REDUCTION IN AREA APE ALLOWED.' I:Si_i i�1_W-2i_i4 IZfir ie A`(Ii9.22g31.i1i i 1__t.i 9FE MI TRENCH UMIns AT TOP CF PAVEMENT '. / ) • / i4,�`I% `-/ • //.. i CSTC MP) PENN // 1 SOIL EXCAVATIION ` {\ I.FULL-OEPM PAVEMENT PATCH JOINTS SHALL DE SEALED. / • \4> SLBfPAOE 2 MA ALL DITS TO BE PERPECULAR TO ORECMN OF TRAVEL /'" v\ SECTION A-A 1 REPLACEMENT IS REM TO ME NEXT ADJACENT CURB,PARKING,OR LANE REGIONAL PAVEMENT CUT POLICY LNE WHENEVER SAJIDE R A TRENCH OR •.q�7i Y,__ RESIDENTIAL/LOCAL ACCESS NATI_Dav Of AtND OR SUPPORT N. uAri onolDS IsroxD sua LINE. EXHIBIT MORATORIUM/FULL POLL BZ Revised: 3/11/2008 by S. Trabun,Avista 13 • • EAHIBIT B3-MORATORIUM/FULL POLICY–INTERSECTIONS "EMERGENCY ONLY FOR MORATORIUM OR PRIOR APPROVAL" III 1 � 44 010 414 • 1 . tif....;;At ..ct_ R":",‘"\\:1:::::\,--:...,:::::::::::::::::: I \ I" , , , . \ , \\ ,. .. \ _I I. � � yV `A� \�aA A1— 1 1 FLLL REPLACEMENT IS REDD CURB LINE WIEN (rn) NSTA SCE BETWEEN E UNE&CURB IS LESS THAN+-n. NDTF' g l i.FULL-DEPTH PAVEMENT PATCH SMITS SHALL BE SEATED. X55 EGENl1• 2 All CUTS TO BE PERPENDICULAR TO DIRECTION OF TRAVEL p WOI PAVEMENT 5 LEES TIRAN >RfPUCEMENT IS REO1D TO THE NEXT ADJACENT CURB, -, ]-MS 0.D DR LESS(MOUiORAIM]. PA NAwATDR LEE WE WHENEVER A TRENCH OR A PAVEMENT PATCH IS REDO TO OSRFDANCE CF ASPHALT DR SUPPORT NAT'L rams THESE WITS NO JOINTS OR BEYDNO SUCH LEE REDUCTION N AREA ARE ALLOWED. K\7VWI PAVEMENT B GREATER 1 THAN]-MN 0.D,A PA IT PATCH REND TO mcg UNTS N D JOINTS Etigii REGIONAL PAVEMENT CUT T POLICY RED IN AR EA ARE INTERSECTIONS AllOVENT Trrtz4 II 4 FITS AT TOP DP 4C5INIECENT MORATORIUM/FULL POLICY EXHIBIT B3 EXHIBIT B4-MODIFIED POLICY-ARTERIAL "EMERGENCY ONLY FOR MORATORIUM OR PRIOR APPROVAL" CURB LINE FULL-OEPT1 PAVEMENT RENFENENT R REDO TO 1-FT MN BEYEND TRENCH UNITS ESTENO PAVEMENT RESTORATION TO LAVE UNE OR LEE CAL TO AVOID WHEEL PATH(M) LANE 4 LANE UNE _ LAME C/L TgpyDI A-E- 1'MN • uulis - (TIP) LANE 3 STREET C/L (rn) c° •�- 1 _ LINE CLL _- S\.\\ \ I7(TIP) LANE 2 A t LANE UNE C Me _. - — (1 fl 1p _ UNE 1L \ 17( "°°�� __\,._-- LANE 1 PARKING rl {r MN • ', 1 LINE )--,(rn) ; a(TYP)• PARKING CURB LINE -a 1 1 I'MN SEWOT/WATER WAS MR) SEWER(TIP) •NoTE J nu_0 'TH (rn) SERVICE ) REPLACEMENT IS REDO TO . I FCFND" TRANSVERSE CUT IONE:IT I(11NAL CUT OAS UNE IX BETWEEN LATE UTE It CLIPS IS LESS MAN 4-FT. 1 WHEN PAVEMENT IS GREATER THAN UNE UNE OR LIE UNE OR R L\\T 5-IPS 0.O,A PAVEMENT PATCH 5 LANE CA. FLU-DEPTH PAV9d01T'kEN REMOVAL FALl LINE C/L PAVEENT TO TIEDE MATS'MEN 1'MN REMOVAL PALLS AEOb TO THESE UNITS NO JOINTS OR (M) I WA WHEEL PAM(MOTH VALES) RmUCTON IN AREA ARE ALLOWED.. 1'IAN(TIP) � �A wm Rim � ME TRENCH()NITS AT TOP a PAVEMENT ����/ �`�'1�/��iv��i 1 IS_I I�I�I 'ILIj�:�l�"�:PJ ILA"•�`���"i:A HOE: �� �%,�� `�'� i7r/ ,>N es� E J I.FULL-DEPTH PAVEMENT PATCH JOINTS AIi SHALL BE SEALED. CsiC Dip) RIFIKV .� �4 / /* .7 2 ALL CATS 5141E BE Pf11PEFOICULM EYCAVWRS \`�� TO DETECTION CO TRAVEL V �I VVV FCTION A-A tO 4 SLUMP DE S PAVEMENT REPLACEXENi1S REDO TO WE LIIE ER LINE CAL WHENEVER A TRENCH M OSNRBM(E OF ASPHALT ON ..• REGIONAL PAVEMENT CUT POLICY SUPPORT MAIL VMS INTO MTEIiIAL WHEEL PATH. - &mnanaT N MODIFIED POLICY EXHIBIT B4 Revised: 3/11/2008 by S. Trabun,Avista 14 1 BIT 85-MODIFIED POLICY—RESIDENTIAL/LOCAL ACCEE "EMERGENCY ONLY FOR MORATORIUM OR PRIOR APPROVAL" FUJ.-DEPTH PAVEMENT REPLACEMENT IS REVD TO 1-FT MIN BEYOND TRENCH LIMBS • EXTEND PAVEMENT RESTORATION TO LACE UNE oft LACE C/L TO AVID WHEEL PATH(Ti?) • CURB UNE PARKING LANE UNE — — — — - 'MN LANE 1L „`"O )"(TYP) LANE 2 STREET C/L _. 02..(1..W).1 i I r%:ssv.-non MO 111', i �__�\ - wan 1a'(TIP) LANE 1 PARKING T'MIN 3 'F.tL � LINE .II 1m A�t-� a'(nPN PARKING CURB LINE - I- V .. _ __-. _ 'L. MIN SEVER/WATER WA1 rip) SEM£R(TIP) •NOTE: FULL DEPTH (Tn.) YFVTCE(TYP) REPLACEMENT IS REVD TO TR ANNFRSF CUT LONGITUDINAL CUT DITMEEEISC 'EEEH LANE REMAINING &CURB IS LESS THAN 4-FT. LANE LEE OR LANE LIE OR I FGFND• LANE C/L FULL-DEPTH PAVEMENT REPLACEMENT REVD LANE C/L 1\\\I *HEN PA+,£NENT IS GREATER THAN PAVEMENT TO THESE UNITS MHEN I'MN REMOVAL FALLS 1 S-YAS OLD,A PAVEMENT PATCH IS REVD OW) WII WTEEL PATH(N101H VARIES) 1 TO THESE LIMITS.NO PEAL OR REDUCTION IN AREA ARE ALLOWED.• 1'MN(TTP) 1..3,.. .1 NOT%,rdf////A O OM PATH_ 7 4, MTRENCH LIMITS AT TOP OF PAVEMENT - ° py,'~ :j.i 1.FULL-DEPTH PAVEMENT PATCH JOINTS Dm(TYP) EXCAVATION \ I. SHALL EE SEALED. LUIS [[ SUBoRADE 2.ALL CUTS SHALL BE PERPENDICULAR i�\�' Ay s' DIRECTOR CF TRAVEL POTION A-A, 1 LANE UNE R 1M4EM]IT N REVD TO ATTRENCCHH OR INSTURBBANCCE OFL"VER . ASPHALT DR SUPPORT McT1 SPOIGINE REGIONAL PAVEMENT CUT POLICY EXTENDS INTO Wr1EEL PATH. RESIDENTIAL /LOCAL ACCESS meo �` \ I MODIFIED POLICY EB51T t HCmD* • • • Revised:3/11/2008 by S. Trabun,Avista 15 EXHIBIT B6-MODIFIED POLICY—CUL-DE-SAC "EMERGENCY ONLY FOR MORATORIUM OR PRIOR APPROVAL" :2Fi fi1i€ r/ WHEN PA'E11ENT IS 3 YEAR— • OR DES A NCAATSJUN MEN PAVEMENT 9 OPE R'THAN 3 YEARS ID PAVEI.IEIIT PATN IS PEOE TO 1HESS UNITS. IF ANY PART 12 YEARS CID,A IAEOIFIED PAVD.&IT PATCH IS OF THE PATCH ECRUEES INTO ANOTHER HALF CF THE COL ROOD TO THESE WITS. IF ANY PART CF THE. DE SIA THAT ADDIMONAL HALF SHALL FiC REPLACER. PATEN EA-TRUCES INTO ANOTHER ME OUATAER CF THE OIL DE SAG THAT ACDMENAL ONE WARIER DOLL EE TENACED. C 2Fn ;3_ _ PAVEHINT UNITS CTO , THEIICN UNITS AT • FC TOP OF PA1£NENT NOIm 1. ALL OrERDJT5 N1M± BE E 11. MIEN PNhNENT 15 GREATER THAN 12 WARS, A TP.DIW PAYENENT PATCH IS BEND TO THE 2. ALL COTS SHALL BE PERPENDICULAR UNITS. PATCH MAY EE LOCATED MNYPIIEFE IN THE TO DIRECTION CF 1RAYEL CUL CE SAC. P REGIONAL PAVEMENT CUT POLICY I. li RESIDENTIAL CUL—DE—SAC EXHIBIT Li 1.9 e. IAGDIFIm POLICY B6 Revised: 3/11/2008 by S. Trabun,Avista 16 • CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 7 - STREET ELEMENTS ? F c-= �i �t i.". y ii � "n, 5i,`�,e 6"AM� -' '► "'LC7 is ' r. — 1 �1�g� -y-�• .ewe t s^'+'1 1 i� _ ,2 2,4 � L� • • K Chapter Organization 7.1 Introduction 1 7.2 Terrain Types 1 7.3 Street Types 1 7.3.1 Public Streets 1 7.3.2 .Private Streets 2 7.3.3 Alleys 2 7.3.4 Private Driveways 3 7.4 Half-Street Improvements 3 7.5 Street Geometry 4 7.5.1 Design Criteria 4 7.5.2 Right-of-Way 8 7.5.3 Border Easement 8 7.5.4 Grade 8 7.5.5 Cross Slope 8 7.5.6 Horizontal Curves 9 7.5.7 Vertical Curves 9 7.5.8 Street Surfacing Requirements 10 7.5.9 Curb and Gutter 10 7.5.10 Landscape Strip and Swales 10 • 7.5.11 Turnarounds 10 December 2009 Chapter 7—Street Elements 7-i CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.12 Bikeways 11 7.5.13 Intersections 12 7.5.14 Street Layout 13 7.5.15 Survey Monuments 14 7.5.16 Traffic Control Devices 15 7.6 Roadside Elements 16 7.6.1 Sidewalks 16 7.6.2 Pedestrian Ramps 16 7.6.3 Side Slopes 17 7.6.4 Clear Zone 17 7.6.5 Sight Distance _ 18 7.7 Miscellaneous Features 21 7.7.1 Street Names 21 7.7.2 Mailboxes 21 7.7.3 Guardrail 21 7.7.4 Bollards 21 7.7.5 Roadway Barricades 22 7.7.6 Entrance Gates 22 7.8 Approach Design Criteria 22 7.8.1 Applicability 23 7.8.2 Access Limitations 23 7.8.3 General Design 24 7.8.4 Driveway Approach Horizontal and Vertical Grade 24 7.8.5 Approach Widths 25 7.8.6 Driveway Approach On-Site Layout 25 7.8.7 Corner Clearance from Intersections 26 7.8.8 Driveway Approach Spacing - Same Side of Street 27 7.8.9 Driveway Approach Methods of Measurements 27 7.8.10 Restricted Access Driveways 28 7.8.11 Alignment of Cross-Street Driveway Approaches 28 7.8.12 Signalized Driveway Approaches 28 7.8.13 Approaches on State Highways 28 7.9 Traffic Calming 29 7.9.1 New Development 29 7.9.2 Existing Development 29 7.9.3 Traffic Calming Devices 29 List of Figures Figure 7-1 Sight Distance Triangle for Case A 20 Figure 7-2 Sight Distance Triangle for Case B 20 List of Tables Table 7.1 Arterial Street Design Criteria 5 Table 7.2 Arterial Street Design Criteria Minimum Widths 6 Table 7.3 Access Street Design Criteria 7 Table 7.4 Minimum Street Approach Length 12 Table 7.5 Minimum Intersection Spacing for Local Access Streets 13 December 2009 Chapter 7—Street Elements 7-ii i CITY OF SPOKANE VALLEY STREET STANDARDS Table 7.6 Minimum Stopping Sight Distance 18 Table 7.7 Minimum Intersection and Approach Sight Distances 19 Table 7.8 Driveway Approach Spacing 27 Table 7.9 State Routes Classifications 29 December 2009 Chapter 7—Street Elements 7-iii CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK December 2009 Chapter 7—Street Elements 7-iv CITY OF SPOKANE VALLEY STREET STANDARDS 7.1 INTRODUCTION The design of streets within the City of Spokane Valley shall generally conform to American Association of State Highway and Transportation Officials (AASHTO) and the State of Washington Department of Transportation (WSDOT) standards unless modified herein. Some street designs require technical criteria that are above the scope of this manual and therefore not covered. In these cases, design manuals from the above referenced agencies and references listed in Section 1.11 should be used for a basis of design. The standard plans referenced in this chapter can be found in Chapter 11. 7.2 TERRAIN TYPES Terrain type can be classified as flat, rolling or mountainous. Flat terrain is the condition where roadway sight distances, as governed by both horizontal and vertical restrictions, are generally long or could be made to be so without construction difficulty or major expense. The slope of the existing terrain is from 0 percent to and including 5 percent. Rolling terrain is that condition where the natural slope rises above and falls below street grade line consistently. Normal street alignment is restricted some by occasional steep slopes. The slope of the existing terrain is from 5 percent to and including 15 percent. Mountainous terrain is that condition where longitudinal and transverse changes in the elevation of the ground with respect to a street are abrupt and where the roadbed is obtained by frequent benching or side hill excavation. The slope of the existing terrain exceeds 15 percent. 7.3 STREET TYPES Streets within the City include public and private streets. Since community needs are usually best served by streets owned and maintained by the City, most projects are required to be accessed via public streets. Private streets may be appropriate for some local accesses in very limited usage. For the purposes of these Street Standards, the following sections provide additional descriptions of streets. 7.3.1 PUBLIC STREETS Public streets are owned and maintained by the City. All public streets in the City have been classified using the Federal Functional Classification system, which provides a hierarchy, from principal arterials to local access streets, to accommodate existing and anticipated traffic. Street classifications can be found in the City of Spokane Valley Comprehensive Plan. December 2009 Chapter 7—Street Elements 7- 1 CITY OF SPOKANE VALLEY STREET STANDARDS Public streets can be triggered by land actions or development permits as described in Chapter 2. Public streets shall be used to connect two public streets and shall be per Standard Plans R-120 through R-122. Sections 7.3 through 7.7, including Tables 7.1 through 7.3, provide design criteria and requirements for public streets. 7.3.2 PRIVATE STREETS Private streets are local access streets, privately owned and maintained. All new private streets shall be approved by the City. Private streets are permitted when all of the following apply: • Where connectivity to the public street system is not compromised; and, • Where future through connection to public streets is not possible; and, • The private street does not land lock present or planned parcels; and, • The private street serves from 2 to 9 single family dwelling lots; and, • The private street provides direct access to a public street. Access to and from private streets shall be limited to properties immediately adjacent to the private street; and, • The private street is not used to connect two public streets. Private streets shall be designed per Table 7.3. The design of a private street shall discourage any through traffic of non-residents. Traffic calming measures may be utilized in the design of private streets. Private streets shall connect to City streets using a standard driveway approach per Standard Plan R-115. A capable, legally responsible owner or homeowners association shall be established to maintain private streets and associated drainage facilities in perpetuity. A plat or short plat with private streets shall be required to provide an executed recorded Private Street Maintenance Agreement and a Stormwater Easement and Maintenance Agreement that obligate future property owners to maintain the infrastructure in perpetuity (see Chapter 10 for requirements). 7.3.3 ALLEYS Alleys are not typically required. However, certain projects may have the option or may be required to provide alley access by the City Comprehensive Plan or by an adopted Revitalization Plan. Design of alleys typically follows the criteria for local streets (Standard Plan R-125). The following is a list of design standards that differ from local street elements: • Alleys shall have a minimum width of 20 feet of asphalt pavement. If the alley is the only access point to the site, the alley width shall meet the width requirements for local access streets (See Table 7.3); December 2009 Chapter 7—Street Elements 7-2 CITY OF SPOKANE VALLEY STREET STANDARDS • Curb, gutter and sidewalk are not required, unless conditioned otherwise; and, • The pavement area may have an inverted crown at centerline to convey stormwater into catch basins located at low points in the invert. Alleys shall connect to a private or public street at each end. In cases where this is not feasible, adequate turnarounds shall be provided. Alleys can be located in the public right-of-way or a private easement. 7.3.4 PRIVATE DRIVEWAYS Private driveways provide vehicular access to one lot. Private driveways shall comply with the following: • Private driveways longer than 75 but less than 150 feet in length shall meet the requirements for width, grade and signing as private streets (See Table 7.3); • Private driveways longer than 150 feet shall be engineered and meet the requirements for width, grade, and signing as private streets (See Table 7.3); • Private driveways longer than 750 feet shall only be allowed when approved by the Fire Department. Structures accessed by a private driveway and which are not visible from the public street shall post an address at the street. Addresses shall be permanent by nature and the numbers shall be a minimum of 4 inches tall, %2 inch stroke, and contrasting color to the background. Driveways shall not extend off the end of an arm of the hammerhead turn-around. 7.4 HALF-STREET IMPROVEMENTS A half-street is required as an interim facility. Half-street improvements are required for a property fronting a public street that is not currently built to City standards. Half-street construction may also be required for property that abuts future streets proposed in the City's Arterial or Local Street Plan. When half-street improvements are required, the design of the half-street shall be consistent with the existing street classification or as dictated by the City's 6-year Transportation Improvement Plan (TIP) or City Street Plans. This requires construction of more than half the street for safety and drainage reasons. Construction in these circumstances requires a minimum of one travel lane on the opposite side of the roadway and frontage improvements on the project side of the street. Dedication of additional right-of-way and border easements are required, unless the existing right-of-way and easement widths are sufficient to fit the improvements. When half-street improvements are required, a minimum of 28 feet of pavement is required. Street improvements shall be designed to provide drainage for the constructed December 2009 Chapter 7—Street Elements 7-3 CITY OF SPOKANE VALLEY STREET STANDARDS portion of the street. Provisions shall be made to allow for extension of the storm drainage system to the undeveloped portion of the street for future construction. Transition tapers are required when the new edges of pavement do not match the existing edge of pavement. Tapers are required to conform to Chapter 6 of MUTCD, latest edition. All proposed utilities located within the half-street shall be installed during construction. The unfinished side of the half-street shall be finished with a gravel shoulder, grassed ditch and/or side slope to assure proper drainage, bank stability, and pedestrian and traffic safety (see Standard Plan R-119). When half-streets connect to an intersection, the intersection shall be designed and constructed for the full build-out of the street. The intersection design and construction shall extend for at least 75 feet from the street intersection (SI). 7.5 STREET GEOMETRY Factors contributing to the geometric conditions of a street are discussed in the following sections. All public streets in a subdivision, including half-streets, shall be fully constructed to the plat boundaries. Pavement, gutter, curb and sidewalk shall be extended to allow future connections to occur. 7.5.1 DESIGN CRITERIA Minimum and maximum geometric design elements are provided in Tables 7.1 through 7.3. Any revision to a geometric element or traffic control on a State Highway requires WSDOT approval. For in-depth design information on the following criteria, refer to AASHTO Green Book, latest adopted edition. December 2009 Chapter 7—Street Elements 7-4 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.1 ARTERIAL STREET DESIGN CRITERIA MINIMUM DESIGN TERRAIN URBAN ARTERIAL SYSTEM URBAN ELEMENTS TYPE COLLECTOR SYSTEM Classification Principal I Minor Collector Design Flat 40 40 35 Speed(mph) Rolling 40 35 35 Mountainous 35 30 35 Minimum Section Type Crown Crown Crown Horizontal 2% 3% 2% 3% 2% 3% Curve Radius' Flat 765 820 765 820 510 545 (ft) Rolling 765 820 510 545 510 545 Mountainous 510 545 330 350 510 545 Minimum All 150 150 100 Tangent Length2 (ft) Maximum All 4 4 Not allowed Superelevation (%)3 Maximum All 6 8 8 Grade(%)° Acceptable All 2-3 2-3 2-3 Range Cross-slope (%) Minimum Flat 45 45 30 Crest Vertical Rolling 45 30 30 Curvess (K) Mountainous 30 20 30 Minimum Flat 65 65 50 Sag Vertical Rolling 65 50 50 Curves3 (K) Mountainous 50 40 50 1. Minimum horizontal curves reflect a crown section. For superelevated sections,the horizontal curve radius shall be re-calculated using AASHTO—Geometric Design of Highway and Speeds. 2. Minimum tangent required at intersections and between curves. 3. Horizontal curves may be adjusted if a super-elevated section is proposed - use AASHTO — Geometric Design of Highway and Speeds. 4. Maximum grades may be exceeded for short distances subject to approval by the City"(+2%)". 5. Length in feet per percent of algebraic grade difference(K value). L=K x Algebraic difference in grade. K Shall not exceed 167. December 2009 Chapter 7—Street Elements 7-5 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.2 ARTERIAL STREET DESIGN CRITERIA MINIMUM WIDTHS URBAN TYPE URBAN ARTERIAL SYSTEM COLLECTOR SYSTEM Classification Principal Minor Collector Curb & Gutter Required Yes Yes Yes Edge Type Curb Shoulder' Curb Curb Painted Center/Left-turn 12 12 12 12 lanes2 Inside lanes (feet) 12 12 12 12 Intermediate lanes (feet) 12 12 12 12 Outside lanes3(feet) 12 12 12 12 Minimum 6 6 6 (5 to 6)4 Sidewalk(feet) Minimum Intersection return radii (ft)5 50 50 40 30 Minimum Asphalt Width 2 lanes 447 403 (feet)6 3 lanes 44 or 46 -- 44 or 46 -- 4 lanes 56 64 56 -- 5 lanes 68 or 70 78 68 or 70 -- 6 lanes 80 102 -- -- 7 lanes 92 or 94 -- -- -- 1. Shoulder section only when approved by the City. 2. Where raised median islands are required,the center lane or left-turn lane shall be fourteen feet in width. 3 Traveled lanes of a two-lane road are shown as outside lanes. If the street is a shared roadway as designated in the Comprehensive Plan, the outside lane is 14 feet minimum. For streets with a bike lane as designated in the Comprehensive Plan, increase the lane width by 5 feet 8 inches to allow for a 5-feet bike lane and 8-inch stripe. 4. Minimum sidewalk width is 6 feet if it is adjacent to the curb and/or if located in a commercial zone. 5. Return radii at face of curb. 6. When asphalt width varies,the larger width is for a raised median. 7. Parking lanes included. December 2009 Chapter 7—Street Elements 7-6 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.3 ACCESS STREET DESIGN CRITERIA DESIGN TERRAIN INDUSTRIAL/ LOCAL ACCESS PRIVATE ALLEY ELEMENTS TYPE COMMERCIAL STREET ADT All 200+ <200 All All Curb&Gutter Required All Yes Yes Yes No No Design Flat 35 30 25 20 20 Speed(mph) Rolling 30 30 25 20 20 Mountainous 25 25 20 20 . _ 20 Minimum Horizontal Curve Flat 545 350 210 110 110 Radius(ft)1 Rolling 350 350 210 110 110 Mountainous 210 210 110 110 110 Minimum Tangent Length All 100 25 25 25 25 (ft)at intersections Maximum All Not allowed Not Not 2 2 Superelevation Rate(%) allowed allowed Maximum Grade (%)- All 8 8 8 10 8 Acceptable Range All 2 to 3 2 to 3 2 to 3 2 to 3 2 to 3 Cross slope(%) Minimum Flat 40 20 15 10 10 Crest Vertical Rolling 30 20 15 10 10 Curves (K)3 Mountainous 20 15 10 10 10 Minimum Flat 50 40 30 20 20 Sag Vertical Rolling 40 40 30 20 20 Curves (K)3 Mountainous 30 30 20 20 20 Minimum Not Not Sidewalk Width(ft)4 All 6 5 5 required required Min. Asphalt Width(ft)5 All 40 30 286 (20-26)7." (20-30)1° Minimum Intersection return radii at All 30 30 30 30 30 face of curb(ft) 1. Minimum horizontal curves reflect a crown section with a cross-slope of 3 percent. Other section types should be calculated using AASHTO—Geometric Design of Highway and Speeds. 2. Maximum grades may be exceeded for short distances subject to approval by the City(+2%). 3 Length in feet per percent of algebraic grade difference (K value). L=K x Algebraic difference in grade. K shall not exceed 167. 4. Minimum sidewalk width is 6 feet if it is adjacent to the curb and/or if located in a commercial zone. 5. Asphalt width does not include curb and/or gutter section. 6. "No Parking"signs shall be posted on side of the street. 7. A minimum 10-foot maintenance and utility easement shall be provided on each side of the private street. 8. Asphalt width based on the length of the street: up to 500 feet = 20 feet; up to 600 feet = 26 feet. The minimum width is 26 feet if there is a fire hydrant on the private street,regardless of street length. 9. Streets 20 to 26 feet wide shall be posted on both sides as a fire lane and with No Parking signs. Pavement widths greater than 26 shall be posted on side of the street as a fire lane and with No Parking signs. If curb is provided,the curb to curb width can be used to determine if a"No Parking" sign is required. 10. If the alley is the only access point to the site, the alley width is 30 feet unless the ADT is less than 200, then the width is 28 ft. December 2009 Chapter 7—Street Elements 7-7 . CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.2 RIGHT-OF-WAY The public street right-of-way shall extend at a minimum to 2 feet behind the curb for projects with separated sidewalk. When the sidewalk is adjacent to the curb, the right-of-way shall extend 2 feet behind the sidewalk. Right-of-way requirements may vary within a street corridor. The required right-of-way width depends on the required street elements, including number of lanes, on-street parking, bike lanes, medians, turn lanes, roadside swales, pedestrian buffer strips and above and below ground utilities. Right-of-way shall be conveyed to the City on a recorded plat or by a right-of-way dedication. 7.5.3 BORDER EASEMENT Border easements shall be granted to the City on a recorded plat or by a recorded easement. Border easements shall extend from the right-of-way line to the back of sidewalk or the back of public facilities when located behind the sidewalk, whichever is the greatest. The border easement shall run the total length of the street on both sides. Fences shall not be constructed inside the border easement. The border easement area shall be kept clear of other objects that would obstruct a driver's view. The sidewalk shall be open for use of pedestrian traffic at all times. The border easements may be used by the utility companies. Utility and other easements can cross the border easement but cannot be entirely located within the border easement. 7.5.4 GRADE Minimum longitudinal grade shall be 0.5 percent for streets with concrete gutters. The minimum longitudinal grade shall be 0.8 percent for streets with asphalt gutters. Maximum allowable grade shall be per Tables 7.1 and 7.3. 7.5.5 CROSS SLOPE All new streets shall be constructed with a center crown, with the cross slope per Tables 7.1 and 7.3. When widening an existing street, the cross slope may range between 2 and 4.5 percent. The cross slope of the higher priority street shall be extended through the intersection. The grade of the cross street shall be adjusted to meet the cross slope of the higher priority street. When two streets with the same classification meet, the street with the higher average daily trip (ADT) shall be selected to act as the higher priority street. The slope of the other street shall be adjusted as required above. December 2009 Chapter 7—Street Elements 7-8 CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.6 HORIZONTAL CURVES. Curve radii shall be as large as possible; the minimum radii shall be used only where necessary. The minimum allowable centerline radii for horizontal curves shall be per Tables 7.1 and 7.3. Angle points are not allowed. All changes in direction shall be made using horizontal curves. Reverse and compound curves should only be used when a single radius curve will not work. For driver safety, compound curves shall have a ratio no greater than 1.5 where the value of the larger radius is divided by the smaller radius. Whenever two streets intersect, a tangent length (measured from the nearest gutter flowline of the intersected street to the point of curvature in the intersecting street) shall be provided for a safe sight distance and traffic operation. The angle of departure from perpendicular shall not exceed 15 degrees for the length of the tangent. The minimum required tangent length shall be per Tables 7.1 and 7.3. For driver safety, horizontal curves shall not begin near the top of a crest vertical curve or the bottom of a sag vertical curve. Connection with existing streets shall be made to match the existing alignment grade of the existing improvements. The centerline, flowline, and existing ground lines of all streets (except cul-de-sacs) shall be continued for 100 feet beyond the proposed construction. 7.5.7 VERTICAL CURVES The minimum vertical curve length for public and private local access streets is 50 feet and 100 feet for arterials. A vertical curve is required when the grade break is 1 percent or greater. The following guidelines shall be followed when designing a profile: • The grade line shall be smooth flowing; • The roller coaster type profile should be avoided; • A broken-back grade line (successive vertical curves in the same direction) generally shall be avoided; • The grade through intersections on streets shall not exceed 6 percent; • A sag vertical or flat grade is desirable in advance of such features as channelization and ramp takeoffs in order to provide good visibility; • The approach at street intersections shall be per Table 7.4; • When superelevation is allowed,transitions shall be designed per the latest version of the WSDOT Design Manual or AASHTO Policy on Geometric Design of Highways and Streets. The pivot point should be located at the centerline. The gutter profile along the grade break shall be evaluated for stormwater conveyance. Vertical curves and grades created by and along the transition shall conform to these standards; and, December 2009 Chapter 7—Street Elements 7-9 CITY OF SPOKANE VALLEY STREET STANDARDS • Vertical curves should be avoided at the intersection with streets or approaches. 7.5.8 STREET SURFACING REQUIREMENTS All travelways shall be paved, including public and private streets, alleys, and private driveways. Paving requirements are specified in Chapter 8. 7.5.9 CURB AND GUTTER Type B curb and gutter shall be used for all public streets per Standard Plan R-102. When the existing curb is not continuous along the street frontage, the Applicant shall construct curb and/or gutter to provide continuity. 7.5.10 LANDSCAPE STRIP AND SWALES A grass strip shall be provided between the curb and the sidewalk for all public streets, providing a buffer for pedestrians. The width of the grass strip shall be as follows: • Seven feet wide if the grass strip is not used for drainage. In this case, drainage facilities shall be located in a separate tract. Commercial and industrial projects may place drainage facilities within a drainage easement granted to the City; or, • Ten feet wide if a continuous roadside swale is provided within the strip. Planting shall conform to Section 7.8.9 of the Spokane Regional Stormwater Manual and SVMC. Drainage facilities receiving stormwater from public streets shall be located within the right-of-way, within a border easement parallel to the street or within a drainage tract. Drainage facilities receiving stormwater from private streets or engineered driveways shall be located within a drainage easement parallel to the street or a drainage tract. 7.5.11 TURNAROUNDS Streets shall be planned, designed and constructed to connect to future developments. Dead-end public and private streets shall not be more than 600 feet in length. All dead-end streets shall have a turnaround that meets the City and Fire Department requirements. A turnaround is required when: • The length is 150 feet or more for all types of travelways. The length is measured from the street intersection (SI) to the terminus of the travelway; or, • A public street is longer than the depth of one lot. December 2009 Chapter 7—Street Elements 7- 10 CITY OF SPOKANE VALLEY STREET STANDARDS Existing stub-end streets greater than 600 feet in length shall be linked to other streets, unless it can be demonstrated that such connections would lead to a substantial rerouting of through traffic onto the street. Non-motorized paths to adjacent arterials or public facilities, such as schools and parks, shall be provided at the dead-end of the street to shorten walking distances. This requires right-of-way dedication and/or easements. 7.5.11.1 Temporary Turnarounds Temporary turnarounds shall be approved by the City and are allowed only when there is the possibility for extending the street to connect adjacent parcels or other streets. Standard Plans R-131 and R-132 provide acceptable temporary turnarounds for public streets. For public streets, the turnaround shall be placed within an easement. Curb, gutter, and sidewalk shall be provided to the locations specified in standard plans. The plan shall include language indicating that the easement is to be vacated when the street is extended across the adjacent parcel. For private streets, the turnaround shall be part of the access easement and not part of the driveway approach. It is the responsibility of the Applicant to verify that setback requirements are satisfied for the lots with the turnaround. A sign shall be posted at the back of the temporary turnaround stating that the street is planned to be extended in the future (Standard Plan R-142). 7.5.11.2 Permanent Turnarounds Permanent cul-de-sacs shall be provided for approved dead-end public streets (see Standard Plan R-130). For private streets and driveways, cul-de-sacs are the preferred turnaround; hammerheads or other turnaround types (Standard Plan R-133) are only allowed for private streets when approved by the City and the Fire Department. A permanent dead-end street is only allowed when connection to adjacent properties and/or other streets is not needed or possible. Permanent cul-de-sacs shall be constructed with curb, gutter, sidewalk and swales. The grade of the cul-de-sac bulb`shall be a minimum 1 percent at all places along the gutter lines. As topography permits, drainage shall be directed away from the bulb. 7.5.12 BIKEWAYS The minimum design standards for bikeways shall be per AAHSTO Guide for the Development of Bicycle Facilities, latest edition. Typically, bikeways are shared with other transportation modes, although they may be provided exclusively for bicycle use. Types of bicycle facilities and planned bicycle facilities within the City can be found in Chapter 3 of the City of Spokane Valley Comprehensive Plan. December 2009 Chapter 7—Street Elements 7- lI CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.13 INTERSECTIONS 7.5.13.1 General Design Street intersections shall be laid out so the streets intersect as nearly as possible at right angles. If a right angle is not possible, the skew shall not vary more than 15 degrees from a right angle. Opposite street legs shall lie on a straight line, whenever possible. For safe design, the following shall be avoided: • Intersections with more than four intersecting streets; • "Y"type intersections where streets meet at acute angles; and, • Intersections adjacent to bridges, horizontal curves, and vertical curves and other sight obstructions. When a private street intersects a public street, the private street is required to be stop-controlled. A private street is not allowed as the fourth leg of the intersection at existing tee intersections. The minimum return radii shall be per Tables 7.2 and 7.3. 7.5.13.2 Approach Length The street approach area is where vehicles store while waiting to enter an intersection, and shall be designed with a nearly flat grade. For public or private streets, the street approach area at an intersection shall have a downgrade approaching the intersection of no greater than 2 percent. An upgrade approaching the intersection shall be no steeper than 4 percent. The minimum length of the street approach area, measured from the intersected street's edge of curb face, or traveled way where curbs are not present, is to be in accordance with Table 7.4. TABLE 7.4 MINIMUM STREET APPROACH LENGTH Average Daily Traffic Minimum Road Approach Length (feet) (ADT) of Higher (2% Maximum Downgrade and 4% Maximum Priority Road Upgrade) Local Access Streets & Collector Arterials Private Roads ADT< 1000 25 50 1000 <ADT < 5,000 50 75 5,000 <ADT< 7,000 75 100 7,000 <ADT < 9,000 75 analysis required December 2009 Chapter 7—Street Elements 7- 12 CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.13.3 Intersection spacing Arterial spacing shall be per the adopted Arterial Plan. Local access streets and private streets shall be located at the minimum spacing specified in Table 7.5. TABLE 7.5 - MINIMUM INTERSECTION SPACING FOR LOCAL ACCESS STREETS MINOR MAJOR STREET STREET PRINCIPAL MINOR COLLECTOR LOCAL ARTERIAL ARTERIAL SEPARATION ACCESS SEPARATION SEPARATION SEPARATION LOCAL ACCESS & 660 ft 330 ft 330 ft 150 ft PRIVATE STREETS 1. Minimum intersection spacing is measured from centerline to centerline. 7.5.14 STREET LAYOUT The internal local residential street network for a subdivision should be designed to discourage regional through traffic. Subdivisions shall be planned in a manner that minimizes the number of local street accesses to arterials and collectors. Street configuration shall conform to the following: • Blocks lengths shall not exceed 600 feet except as provided in the zoning regulations for estate lots, unless unique characteristics associated with the land such as creeks, woods, or parks justify a longer length; • Public streets, private streets, and driveways shall not be located closer than 2 feet from any point from an interior property line. The only exceptions to this rule are for public streets which shall extend to the plat boundaries to allow for future connection and for half-streets; • Horizontal alignment within intersection area. The horizontal approach to an intersection shall be tangent for a minimum length as specified in Tables 7.1 and 7.3. Longer tangents are highly desirable. The tangent distance is measured from the curb line of one street to the first point of curvature on the intersecting street; • Residential developments with greater than 30 single family dwelling units shall have a minimum of 2 street accesses that meet the Fire December 2009 Chapter 7—Street Elements 7- 13 CITY OF SPOKANE VALLEY STREET STANDARDS Department separation requirement to ensure adequate emergency access; and, • Multi-family developments with greater than 100 dwelling units shall have a minimum of 2 street accesses. 7.5.15 SURVEY MONUMENTS 7.5.15.1 General Requirements Surveys shall conform to all applicable state and local regulations (SVMC Title 20). Prior to any construction or maintenance activities within City right-of-way, a professional land surveyor licensed in the State of Washington (Surveyor) shall conduct a thorough search for all survey monuments. Any found monuments shall be referenced in accordance with current applicable state and local regulations. A copy of the references shall be filed in the office of the County Engineer. The Surveyor shall comply with Chapter 332-120 WAC. If monuments are found to be at risk by construction or maintenance activities, an approved copy of the Application Permit filed with the Washington State Department of Natural Resources (DNR) shall be provided to the City. 7.5.15.2 Monumentation The responsible Surveyor shall set permanent monuments as shown per Standard Plan R-145 with his/her registration number as follows: • For placing new or replacement of section corners, quarter corners, closing corners, witness corners, and meander corners that have been disturbed or destroyed, the minimum acceptable monument is a %-inch inside diameter iron pipe or a #5 (5/8-inch) steel reinforcing rod, 24 inches in length. The monument and cap shall be marked in conformance with state laws and regulations. Any of these corners in paved roads shall be covered by a cast iron monument case and lid per Standard Plan R-145. • For placing new or replacement of disturbed road intersection points on arterials, the minimum acceptable monument is a 1/2-inch inside diameter iron pipe or a #5 (5/8 inch) steel reinforcing rod, 24 inches in length. These monuments shall be covered by a standard cast iron monument case and lid per Standard Plan R-145. • For placing new or replacement of disturbed road centerline angle points, curve points and road intersection points (not identified above), the minimum acceptable monument is a 1/2-inch inside diameter iron pipe or a #5 (5/8-inch) steel reinforcing rod, 24 inches in length. Monuments set in the residential street shall be as shown on Standard Plan R-145. • For placing new or replacement of all permanent monuments not covered above, the minimum acceptable monument is a '/I-inch inside diameter iron pipe or a#4 ('/cinch) steel reinforcing rod, 18 inches in length. December 2009 Chapter 7—Street Elements 7. 14 CITY OF SPOKANE VALLEY STREET STANDARDS • If it is impossible to set the above monuments, the City may approve an alternative monumentation method. For each monument being set or established, the responsible Surveyor shall: • Identify at least three reference points. The reference points may consist of, in order of preference, cross on curbs, bearing trees or accessories, nearby property corners or an alternate as approved by the City. A completed DNR permit shall be filed with the DNR with a copy supplied to the City. • Show on a Record of Survey, Plat, Short Plat or Binding Site Plan sufficient information to comply with RCW 58.09.120. A filed copy of said Record of Survey, Plat, Short Plat or Binding Site Plan shall be supplied to the City as needed. 7.5.15.3 Horizontal Control Network A horizontal control network previously established by the Spokane County Engineer shall be the mapping base for all surveys performed under these Street Standards. Intersections shall also be located and referenced to the current control network as established by the Spokane County GPS control project and that coordinate system. Refer to SVMC Title 20.40 for additional information. All survey work done within the City boundaries shall conform to the degree of accuracy required under applicable state laws. Adequate supplemental information may be required by the City to ensure accuracy. 7.5.15.4 Temporary Bench Mark The Surveyor shall provide a temporary bench mark along the roadway every one thousand feet. These temporary bench marks shall be based on the datum plane approved by the City. Refer to SVMC Title 20.20 for additional information. If requested by the City, the Surveyor shall submit field notes or a sealed statement, insuring work according to third order accuracy. Refer to Washington State Department of Transportation Standards (Highway Surveying Manual M22-97) for additional information. 7.5.16 TRAFFIC CONTROL DEVICES The City uses the Washington State MUTCD as a guideline for traffic control devices including pavement marking and signing. The Applicant is responsible for providing and installing all required traffic control devices, including but not limited to street name signs, regulatory signs (including stop and no parking), warning signs, barricades, crosswalk markings, and bicycle/pedestrian signs. "No Parking" signs shall be posted on both sides of the street for curb to curb widths up to 26 feet and on one side of the street for curb to curb widths greater than 26 feet and up to 32 feet. If the street has no curb, the pavement width shall be used to determine if "No Parking" signs are required. For private streets and private December 2009 Chapter 7—Street Elements 7- 15 CITY OF SPOKANE VALLEY STREET STANDARDS driveways, a minimum of one "No Parking — Fire Lane" sign shall be installed every 100 feet of frontage or as required by the Fire Department. "No Parking" signs on public streets shall be installed when required by these Street Standards at a separation as required by the City and the Fire Department. 7.6 ROADSIDE ELEMENTS 7.6.1 SIDEWALKS Sidewalk is required on public streets along both sides for all street classifications. When approved by the City, the sidewalk may be eliminated on one side of the street if topography or safety prohibits construction. The Applicant shall demonstrate that pedestrian needs are still satisfied. Additionally, sidewalk may not be required on a local access street fronting the project if all of the following are true: • The project is in a low-pedestrian zone(zones R-1, R-2, R-3, I-2); • There are no other sidewalks within its block; and, • Any part of the project is more than one mile radially away from an activity center (which includes but is not limited to parks, schools, large employment centers, religious institutions). The width of sidewalks shall be as required in Tables 7.2 and 7.3. Wider sidewalk may be required to provide corridor continuity. At no location shall a sidewalk provide an unobstructed path of less than the required width. Wider sidewalk may be required at bus stops to allow bus riders a place to stand without hindering pedestrian movements or handicap access. When the existing sidewalk is not continuous along the street frontage, the Applicant shall construct sidewalk along the frontage of the project to provide continuity. The thickness of the sidewalk shall be per Standard Plan R-103. Meandering sidewalks may be approved by the City. The design of meandering sidewalks shall address obstructions, including mailbox mountings, street trees, fire hydrants, power poles, driveways, swales and street signs, without deviation from the required design width. Additional right-of-way (or easement) may be required to accommodate the obstructions or the meander of the sidewalk. 7.6.2 PEDESTRIAN RAMPS Pedestrian ramps shall be provided at all pedestrian crossings having vertical curb sections and shall be per Standard Plans R-105 and R-106. Every pedestrian ramp shall have at least one receiving ramp. This may require construction of "island" landing ramps. In special conditions, pedestrian ramps shall also be provided to enable passage across curbed radius return access points. Pedestrian ramps shall have December 2009 Chapter 7—Street Elements 7- 16 CITY OF SPOKANE VALLEY STREET STANDARDS detectable warning patterns formed with manufactured truncated domes in yellow. Pedestrian ramps are required to meet all ADA guidelines. 7.6.3 SIDE SLOPES Typical slopes for embankments should be 3:1 or flatter. The steepest slope for embankment or excavation shall be 2:1. Refer to Chapter 5 for additional requirements. On shouldered streets, a minimum space of 5 feet shall be provided between the catch point of the side slope and the right-of-way line for the installation of utility poles, fences, sloped rounding, etc. Depending on site conditions, this may require additional right-of-way, retaining walls, or other requirements. The maximum slope of this space shall be 3:1. Slope easements shall be granted to the City when required by terrain or design features. 7.6.4 CLEAR ZONE Clear zone is defined as a relatively flat area void of fixed objects or obstructions beyond the edge of the traveled way that allows drivers to stop safely or regain control of a vehicle that leaves the traveled way. This area may consist of a shoulder, a recoverable slope, a non-recoverable slope, and/or a clean run-out area. The desired minimum width is dependent upon traffic volumes, traffic speeds, side slopes, and the street geometry. A recoverable slope is a slope on which a motorist may retain or regain control of a vehicle by slowing or stopping. Slopes flatter than 4:1 are generally considered recoverable. A non-recoverable slope is considered to be traversable but on which an errant vehicle continues to bottom. Embankment slopes between 3:1 and 4:1 may be considered traversable but non-recoverable if they are smooth and free of fixed objects. A clear run-out area is the area at the top of a non-recoverable slope available for safe use by an errant vehicle. Slopes steeper than 3:1 are not considered traversable and are not considered part of the clear zone. For streets with Type B or Type A curb, the following is required: • Sidewalk adjacent to the curb - Rigid objects shall be placed 2 feet behind the sidewalk; • Separated sidewalk - Rigid objects shall be no closer than 2 feet from the back of the curb; • No sidewalk - Rigid objects shall be no closer than 2 feet from the back of the curb; December 2009 Chapter 7—Street Elements 7- 17 CITY OF SPOKANE VALLEY STREET STANDARDS • Speed limit 40 mph or less - The clear zone distance is 2 feet behind the back of the curb. For all other pavement edges and design speeds, clear zone requirements per AASHTO's "A Policy on Geometric Design of Highways and Streets" shall be used. 7.6.5 SIGHT DISTANCE Sight distance is defined as the length of roadway that is entirely visible to the driver. All roads, intersections, and access points shall be designed to provide adequate sight distance for all normal driving situations and are required to conform to AASHTO's "A Policy on Geometric Design of Highways and Streets, " latest edition. Stopping sight distance shall be calculated for vehicle crest curves and horizontal curves. The stopping sight distance shall not be less than the distances specified in Table 7.6. These values should be adjusted for grades 3 percent or greater, more than 2 lanes, skewed intersections, intersections near vertical or horizontal curves, or for design vehicles other than passenger cars. TABLE 7.6 MINIMUM STOPPING SIGHT DISTANCE Design Speed Stopping Sight (mph) Distance (feet) 20 115 25 155 30 200 35 250 40 305 50 425 55 495 Table 7.7 specifies the required sight distance for different types of intersections and approaches. These values shall be adjusted for grades with slopes of 3 percent or greater, number of lanes greater than two, for design vehicles other than passenger cars, using the procedures in the AASHTO design guidelines. For intersections or approaches located near horizontal or vertical curves, the City may require the 85th- percentile speed be used in the sight distance analysis. The 85th percentile speed is the speed at or below which 85 percent of the motorists drive on a given street unaffected by slower traffic or poor weather. This speed indicates the speed that most motorists on the street consider safe and reasonable under ideal conditions. Sight distance triangles shall be shown in the civil plans for all new intersections and all projects with new driveway approaches. Sight distance shall be continuous. Non- engineered driveways on local access streets are exempt from this requirement. Sight distance triangles shall be developed by an Engineer with traffic engineering experience developing intersection sight distance triangles. December 2009 Chapter 7—Street Elements 7- 18 CITY OF SPOKANE VALLEY STREET STANDARDS Fire hydrants shall be visible for 50 feet in either direction. A sight distance triangle shall be shown at the location of each fire hydrant in the civil plans and lot plans. The area within the sight distance triangle shall be free from any sight-obscuring objects in accordance with AASHTO design guidelines. Sight-obscuring objects include but are not limited to buildings, parked vehicles, signs, fences, and landscaping. For sight triangles in the right-of-way, only grass may be planted. The City may remove, at the expense of the property owner, any vegetation or objects which obstruct sight distance. The sight distance triangle shall be located completely within an easement or right-of- way. The property owner is responsible for removing any objects that become a sight hazard. If an easement is not practical, the City may require additional right-of-way as a condition of development approval to ensure proper maintenance. TABLE 7.7 MINIMUM INTERSECTION & APPROACH SIGHT DISTANCES CASE THROUGH THROUGH DISTANCE FROM SIGHT TYPE STREET TYPE STREET SPEED TRAVELWAY(FT) DISTANCE' LIMIT(MPH) (FT) Case A— Local access or 20 902 90 Uncontrolled lower classification 25 1152 115 Case B— Any 25 153 280 Signal,Stop Control, 30 335 Commercial 35 390 Approach& engineered driveways 1. These values should be adjusted for grades 3 percent or greater, more than 2 lanes, skewed intersections,or for design vehicles other than passenger cars. 2. Distance back from center of intersection. 3. Use Figure 7-2. The following types of intersection and accesses are covered in Table 7.7. Other intersection types shall be analyzed using Chapter 9 of AASHTO Green Book. • Case A can be used to analyze uncontrolled intersections which are intersections not controlled by a stop sign, traffic signal or yield sign. They are usually located on streets that carry low volumes and have a 25 mph speed limit. Figure 7-1 shows the sight distance triangle for this type of intersection. • Case B can be used to analyze street approaches controlled by stop signs or a signal, commercial approaches and alleys. Figure 7-2 shows the sight distance triangle for Case B. December 2009 Chapter 7—Street Elements 7- 19 CITY OF SPOKANE VALLEY STREET STANDARDS Intersection Center _ \ 115 ft s- -----\\ 76 1 • 115 ft r FIGURE 7-1 SIGHT DISTANCE TRIANGLE FOR CASE A Required Sight Distance T/ Major Street (C) (B) (C) (B) Ttop Sign Point A is located at the center of the minor street approach j Points B & C are located at the lane 10 ft from the edge of traveled way for driveway center of major street approach approaches and 15 ft for stop (A) through lane or in the center of controlled and signalized the major street approach if intersections. more than one lane exists. FIGURE 7-2 SIGHT DISTANCE TRIANGLE FOR CASE B December 2009 Chapter 7—Street Elements 7-20 CITY OF SPOKANE VALLEY STREET STANDARDS 7.7 MISCELLANEOUS FEATURES 7.7.1 STREET NAMES The City and the Fire Department review proposed street names to conform to established names within the County grid to expedite property identification by emergency services. Street names shall also comply with the US Postal Services addressing standards. Street name designations shall be as follows: • All north-south streets shall be called Streets; • All east-west streets shall be called Avenues; • Streets in large subdivisions that do not have a definite directional course shall be called Drives; • A permanent dead-end or cul-de-sac street shall be called a Court; • A street that lies diagonally to the east-west, north-south grid system and is an arterial or collector street shall be called a Boulevard; • A street that has its ingress and egress on the same street shall be called a Circle; and, • A private street shall be called a Lane. 7.7.2 MAILBOXES Mailbox installation and placement shall follow AASHTO and US Postal Services guidelines. Mailboxes should not be placed in sight triangles or in clear zones. 7.7.3 GUARDRAIL Evaluation of embankments for guardrail installations shall be in accordance with Chapter 710 of the WSDOT Design Manual. Guardrail installations shall conform to WSDOT/APWA Plan C-1, Beam Guardrail Type 1. End anchors shall conform to WSDOT/APWA Plan C-6, Beam Guardrail Anchor Type I. 7.7.4 BOLLARDS Points of access shall be closed by a line of bollards when necessary to deny vehicle access to an easement, tract, or trail (except for maintenance or emergency vehicles). Bollards shall be wrapped with reflective tape. Closure shall include one or more fixed bollards on each side of the traveled way and removable, locking bollards across the traveled way. Spacing shall provide one bollard on centerline of the trail • and other bollards at a maximum spacing of 3 feet to preclude vehicular access. December 2009 Chapter 7—Street Elements 7-21 CITY OF SPOKANE VALLEY STREET STANDARDS Fire access roads shall not be blocked in this manner without the approval of the Fire Department. Reflective tape and safety striping shall be placed on bollards. Bollards shall be placed 10 feet from the paved edge of roadway. 7.7.5 ROADWAY BARRICADES Temporary and permanent barricades shall conform to Manual on Uniform Traffic Control Devices (MUTCD). Type III barricades (see Standard Plan R-142) shall be used at the end of a local access street terminating abruptly without cul-de-sac bulb or on temporarily stubbed off streets. Each such barricade shall be used together with an end-of-road marker and signed future street extension. 7.7.6 ENTRANCE GATES Entrance gates are not allowed on public streets. Use of entrance gates on private streets shall be approved by the City and the Fire Department. Minimum gate opening width is 20 feet. Proposed gates shall be clearly shown on the street plans. If a center island is used as part of an entrance gate feature, a minimum 14-foot wide lane between face of curb and center island shall be provided. The center island shall not extend past the end of the gate when it is fully opened. Gated streets require a queuing area to allow vehicles to exit the connecting street prior to the gate. The queuing length shall be a minimum of 35 feet plus the gate width. Parking is not allowed within the queuing area, on either side of the street, for a distance equal to the queuing length. Signage for the "No Parking Zone" shall be placed on both sides of the gate. Gates shall be required to have a Fire Department emergency access device installed and maintained: • A Knox key switch shall be installed on gates that provide access to 20 lots or less; or, • An Opticom gate activation device shall be provided for subdivisions with more than 20 lots. 7.8 APPROACH DESIGN CRITERIA The following section contains design criteria for intersections and driveway approaches. These are minimum requirements and may be modified if traffic volumes (existing and/or projected), topography, design speed, design vehicle requirements, drainage, and other conditions, both existing and projected indicate a more stringent criterion is necessary. The City may require additional provisions to ensure public safety. All access points to and from City streets, including intersections and driveways shall be approved by the City prior to construction and require an approach permit. December 2009 Chapter 7—Street Elements 7-22 CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.1 APPLICABILITY These requirements apply to all new or altered intersection and driveway approaches to City streets. 7.8.2 ACCESS LIMITATIONS While no property is denied access to City streets, direct street access is not guaranteed. When direct access is denied, properties may be required to: • Access the street via an alley; • Share a single driveway approach with two or more contiguous properties; or, • Restrict access with a right-in/right-out approach for properties located on arterials and with no available alternate access. Additionally, these properties may be required to construct street improvements to preclude left turning traffic. Properties are restricted to one access point on arterials and two access points on local access streets. The Development Services Senior Engineer after consultation with the Senior Traffic Engineer may grant one additional arterial access point provided that: • Minimum spacing requirements between access points are met with any driveway approaches; • The applicant demonstrates that additional access points will result in an improvement to safety or traffic flow both on-site and off-site; and, • One of the following situations exists: o The PM peak hour volume exceeds 100 PM peak hour vehicles on both directions; or, o Traffic volumes using one driveway would exceed the capacity of a stop sign controlled intersection during the PM peak hour; or, o The ADT using one driveway would exceed 1,000 vehicles both directions. When a property has frontage on two or more streets, and spacing requirements on the major street cannot be met, the driveway approach shall be located on the street with the lowest classification unless safety considerations dictate otherwise. For a development that combines more than one underlying lot, these requirements, including the number and spacing of access points, shall apply to the development as a whole, not to each underlying lot. For all Binding Site Plans, excluding industrial zones, shared access is required between the lots. The shared access shall include parking lot travel lane connections or shared driveway approach. If the Applicant adequately demonstrates a site design or building use limitation for installation of the travel lanes or shared approach on the December 2009 Chapter 7—Street Elements 7-23 CITY OF SPOKANE VALLEY STREET STANDARDS existing property, exceptions to this requirement may be administratively granted. Exceptions may be approved if: • The City finds that the lack of shared access does not negatively impact the present or future function and safety of the parking lot circulation, ingress/egress, or roadway network; and, • The City finds that the lots required to share access have allowable incompatible uses; and, • The property does not have a feasible alternative site design solution. Driveways will not be allowed where horizontal or vertical curves prevent the roadway from having continuous stopping sight distance or adequate intersection sight distance to safely accommodate the movements in and out of the driveway. 7.8.3 GENERAL DESIGN Approaches shall be constructed to avoid interference with existing drainage inlets, culverts, lighting, utility poles, traffic regulating devices, fire hydrants, or other facilities. The Applicant shall be responsible for the cost of relocating any of the above. The agency holding authority for the particular structure shall decide how the facility will be relocated. If at the time of construction the fronting street does not have full width pavement or curb and gutter, a rural driveway approach may be used with the approach starting at the edge of the existing pavement (see Standard Plan R-114). Approaches shall not restrict or impound drainage flow in the street. For shouldered streets with ditches, stormwater shall be conveyed under the driveway with a culvert. The minimum culvert size shall be 12 inches. For curbed roads, stormwater shall be conveyed using a culvert and Standard Plan R-110 or an inverted approach per Standard Plan R-111. If an existing approach is to be altered or abandoned the unused portion of the original approach is to be removed and replaced with curb, gutter and sidewalk matching that which is adjacent. Redevelopment projects shall be required to modify or eliminate any existing driveway approach that does not conform to these standards. 7.8.4 DRIVEWAY APPROACH HORIZONTAL AND VERTICAL GRADE Approaches shall align perpendicular to the street. The angle of intersection to the street shall not be less than 75 degrees. The angle may be reduced to 45 degrees for right-in/right-out driveways where the entering and exiting lanes are separated by a raised "pork chop" island (see Standard Plan R-115). December 2009 Chapter 7—Street Elements 7.24 CITY OF SPOKANE VALLEY STREET STANDARDS The vertical grade of approaches shall not exceed 8 percent within the right-of-way and shall be designed to preclude vehicles dragging when entering or exiting the site. Vertical grades shall not exceed 10 percent within ten feet of the right-of-way. 7.8.5 APPROACH WIDTHS The total approach width shall not be greater than 50 percent of total lot frontage width. When approaches are constructed different than that shown on the construction plans, the design engineer shall verify that any affected street and stormwater facilities will still meet the design goals. If the facilities are inadequate, measures shall be taken to bring the facilities into compliance prior to their acceptance. 7.8.5.1 Single Family Residential Single family driveway approach shall be per Standard Plans R-110 through R-112. 7.8.5.2 Residential Private Streets Approach for private streets shall match the required pavement width and shall be per Standard Plans R-110 and R-112. 7.8.5.3 Commercial/Industrial Commercial/industrial driveway approaches shall be per Standard Plans R-110 through R-112. High volume driveway approaches (Standard Plan R-113) may be required or permitted when all of the following conditions are present: • The access is located along an arterial; • Access volumes indicate a need for a radii curb return where the ADT exceeds 500 or where speed change lanes would be required; • The access is designed to restrict turning movements, requiring the installation of an access island or center median; • The roadway has no curb and gutter; • The access serves an industrial property, or provides for commercial deliveries, where large truck movements are required; and, • A traffic engineering analysis submitted by the applicant determines that a radii access is necessary to ensure adequate traffic safety and operation. 7.8.6 DRIVEWAY APPROACH ON-SITE LAYOUT Approaches shall provide access to an off-street parking area located on private property. The driveway shall be of sufficient length so a vehicle in the driveway does not project into the right-of-way, sidewalk, or pathway. Approaches and on-site parking shall be designed such that vehicle-backing maneuvers will not occur into the street/public right-of-way, impede pedestrian access to sidewalk or vehicles in the December 2009 Chapter 7—Street Elements 7-25 CITY OF SPOKANE VALLEY STREET STANDARDS public street. Driveway approaches shall be designed to allow the largest typical vehicle using the approach (i.e. tractor trailers at large warehouses, delivery trucks at mini marts, etc.)to enter and exit the site without encroaching into opposing traffic. Whenever possible, the site should be designed for counterclockwise circulation of large trucks as left turns and left-hand backing maneuvers are easier and safer since the driver's position is on the left hand of the vehicle. All parking, loading and maneuvering of trucks shall be conducted on private property. 7.8.6.1 Driveway Stacking Length for Multi-use Properties Driveway stacking length for multi-use properties is the distance between the right- of-way and the near side of the first intersecting interior aisle or parking space. The driveway stacking length for multi-use properties shall be as follows: • 20 feet for parking lots with less than 50 spaces; • 50 feet for parking lots with up to 200 spaces; and, • 80 feet for parking lots with over 200 spaces. 7.8.6.2 Driveway Stacking Length for Single-use Properties Driveway stacking length for single-use properties is the distance between the right- of-way and the proposed uses. The minimum length for driveway stacking for drive- thru windows shall be as follows: • 150 feet for drive-in banks and drive-thru restaurants; • 50 feet for automated tellers (ATM) and drive-in cleaners and repair services; • 75 feet for automated car wash and espresso stands; and, • 100 feet for controlled access parking. The City may require a traffic study to determine the stacking and queuing requirements for such uses that include, but are not limited to, service stations, drive- thru restaurants, drive-in banking, etc. The City may require sites with internal traffic congestion to design approaches with long throat lengths to provide extra storage to avoid impacting City streets. 7.8.7 CORNER CLEARANCE FROM INTERSECTIONS The following sections provide minimum corner clearances. Greater corner clearances may be required at the discretion of the City based on existing or proposed conditions at the intersection. In general, full access driveways are not allowed within the functional intersection boundary, which can be minimally defined by the length of the turn pockets, but may extend further from the intersection. Where the driveway location does not meet minimum City criteria, or where a safe driveway location cannot be found, the City requires appropriate mitigation measures to provide for as safe a driveway as feasible. December 2009 Chapter 7—Street Elements 7-26 CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.7.1 Single Family Residential Residential driveway approaches may not be located closer than 15 feet from the point of curvature of a curb return. 7.8.7.2 Commercial/Industrial Commercial driveway approaches may not be located closer than 75 feet from the point of curvature of a curb return. 7.8.8 DRIVEWAY APPROACH SPACING - SAME SIDE OF STREET Table 7.8 provides the minimum distance allowed between the centerlines of adjacent driveway approaches. The distance is measured from centerline to centerline of each approach. TABLE 7.8 - DRIVEWAY APPROACH SPACING STREET DESIRABLE LIMITING CLASSIFICATION CONDITIONS CONDITIONS SEPARATION (FT) SEPARATION (FT) Collector 70 50 Minor Arterial 90 60 Principal Arterial 120 80 Desirable conditions shall be applied when sufficient space or street frontage is available. If sufficient space or street frontage for desirable conditions is not available, then lesser distances, down to, but not less than the requirement for limiting conditions, may be applied. 7.8.9 DRIVEWAY APPROACH METHODS OF MEASUREMENTS Driveway throat width is measured perpendicular to the centerline of the driveway between lines defined by the radii, whether or not that occurs inside the property lines and is physically marked with curbing. Driveway throat length is measured along the centerline of the driveway from the back edge of the driveway apron and the nearest vehicle aisle or circulation road. Dimensions in this section refer to distances from (or along) face of curb. In the absence of a curb, the measurement is considered to be from (or along) the edge of pavement. Driveway angles are measured between the driveway centerline and centerline of the roadway. December 2009 Chapter 7—Street Elements 7-27 CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.10 RESTRICTED ACCESS DRIVEWAYS Restricted access approaches do not allow left-hand turns out of or into the driveway approach. Development or redevelopment of properties, where the required setback from an intersection cannot be achieved in any direction and without other ways to access the site, may be required to use a restricted access driveway. In some cases a raised median may be required down the street centerline. Restricted access approaches shall only be allowed when approved by the City. The existence of other approaches in the vicinity that do not meet standards is not grounds for allowing further substandard approaches. 7.8.11 ALIGNMENT OF CROSS-STREET DRIVEWAY APPROACHES Driveways should be placed directly opposite from each other whenever possible. If this is not possible and adequate left-turn storage capacity is not available in advance of each driveway, combining of driveways on the same side of the street may be required. The requirement above shall not apply if the street to be accessed has a permanent median and/or traffic control device that prevents any cross-street movement of traffic or if the City determines that adhering to said requirement would be unsafe. 7.8.12 SIGNALIZED DRIVEWAY APPROACHES If the Traffic Impact Analysis determines that there is or will be a need to signalize proposed access points, then proposed access points shall be aligned directly opposite any existing or proposed access points or T-intersection across the street. Where driveways are to be signalized, a minimum spacing of 1,320 feet to any other signalized intersection should be maintained or shall be spaced as approved by the City. Roundabouts may be considered as an alternative option by the City. 7.8.13 APPROACHES ON STATE HIGHWAYS This section contains specific access standards for state highways within the City limits, which are classified as managed access facilities. Managed access is based on the premise that access rights of a property owner are subordinate to the public's right and interest in a safe and efficient highway system. In accordance with Chapter 47.50 RCW, the City adopts by reference, the provisions of Chapter 468-52 WAC, together with all future amendments, in order to regulate and control vehicular access and connection points of ingress to and egress from, the State Highway System within the incorporated areas of the City of Spokane Valley. State Routes (SR) within the City include SR-27 (Pines Road) and SR-290 (Trent Avenue). The current access classifications for SR-27 and SR-290 are shown in Table 7.9. December 2009 Chapter 7—Street Elements 7-28 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.9 STATE ROUTES CLASSIFICATIONS STATE BEGINNING ENDING APPROXIMATE CURRENT ROUTE MILEPOST MILEPOST LOCATION ACCESS CLASSIFICATION 27 83.14 84.61 14TH TO CITY M2 LIMITS 27 84.61 86.49 14 " TO—NORA MS 27 86.72 87.70 MONTGOMERY M5 TO 290 290 4.31 6.35 FANCHER TO MS ARGONNE 290 6.35 10.29 ARGONNE TO M4 PROGRESS 290 10.29 12.84 PROGRESS TO M2 CITY LIMITS 7.9 TRAFFIC CALMING Traffic calming devices improve neighborhood livability by reducing the speed and impact of vehicular traffic on residential streets. 7.9.1 NEW DEVELOPMENT The internal local access street layout shall be designed as to discourage through, high-speed traffic or shall incorporate traffic calming devices in the design. The Applicant may utilize one or more of the traffic calming devices. Proposed devices shall be reviewed and approved by the City at the time of preliminary design review. Traffic calming devices shall be installed at the expense of the Applicant. 7.9.2 EXISTING DEVELOPMENT Traffic calming devices are not allowed on arterials. On collectors and local access streets, traffic calming devices are only allowed when warranted by an engineering study and approved by the City. The installation of devices shall be neighborhood funded. 7.9.3 TRAFFIC CALMING DEVICES Currently, the only traffic calming device allowed by the City is the Traffic Circle (see Standard Plan T-101). Alternative devices recommended by the Applicant's Engineer may be permitted with City approval. December 2009 Chapter 7—Street Elements 7-29 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 7—Street Elements 7-30 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 8 - PAVEMENT DESIGN rt r: a __ ✓ e ,{ i 1 r Chapter Organization 8.1 Introduction 1 8.2 Street Classification 1 8.3 Street Pavement and Subgrade 1 8.3.1 Travelways In Residential Zones 1 8.3.2 Travelways In Non-Residential Zones 2 8.3.3 Subgrade Preparation 2 8.4 Engineered Pavement Parameters 3 8.4.1 Traffic Parameters 3 8.4.2 Reliability Level 4 8.4.3 Overall Standard Deviation 4 8.4.4 Initial and Terminal Serviceability Indexes 4 8.4.5 Structural Layer Coefficients 4 8.4.6 Drainage Layer Coefficients 4 8.4.7 Subgrade Evaluation 5 8.5 Report Submittal 5 8.6 Materials Specifications 6 8.6.1 Gravel Base 6 8.6.2 Crushed Rock 6 8.6.3 Asphalt or Concrete Treated Base 6 8.6.4 Hot Mix Asphalt 6 December 2009 Chapter 8 Pavement Design 8-i CITY OF SPOKANE VALLEY STREET STANDARDS 8.6.5 In-place Mainline Asphalt Compaction Test Requirements 7 8.6.6 Cold Joint Requirements 7 8.6.7 Longitudinal and Transverse Joint Requirements 7 8.6.8 Tack Coats—Preparation of Existing Surfaces 8 8.6.9 Cover Asphalt Loads During Transport 8 8.6.10 Breakdown Rolling Maximum Temperature Loss 8 8.6.11 Asphalt Temperature Placement Requirements 8 8.6.12 Paving Dates & Weather Limitations 9 List of Tables Table 8.1 —Equivalent Single Axle Loads 3 Table 8.2 —Initial and Terminal Serviceability Indexes 4 Table 8.3 —Structural Layer Coefficients 4 Table 8.4—Recommended Drainage Coefficients 5 Table 8.5 —Moduli Ratio 5 Table 8.6—Performance Grade 7 Table 8.7—Recommended Minimum Laydown Temperature 9 December 2009 Chapter 8 Pavement Design 8-ii CITY OF SPOKANE VALLEY STREET STANDARDS 8.1 INTRODUCTION This chapter provides the minimum requirement for the design of pavement sections for travelways within the City. The use of these design criteria will ensure that paved transportation corridors are improved in a uniform and consistent manner. The requirements presented in this chapter have been established to minimize structural failures in streets, due to traffic loadings and/or existing soils conditions. 8.2 STREET CLASSIFICATION All public streets in the City have been classified using the Federal Functional Classification system, which provides a hierarchy from principal arterials to local access streets, to accommodate existing and anticipated traffic. Street classifications can be found in the City of Spokane Valley Comprehensive Plan. A street's classification is used to determine the volume and mix of vehicles for which it is designed. In cases where a street has yet to be designated a specific classification, the anticipated traffic volume should be used. If available, the City may provide the anticipated daily traffic for a street. However, the Applicant may be required to obtain additional traffic information. 8.3 STREET PAVEMENT AND SUBGRADE 8.3.1 TRAVELWAYS IN RESIDENTIAL ZONES The requirements of this section apply to local access streets, private streets, alleys, and private driveways located in residential zones. For the purpose of pavement design, the engineering characteristics of the subgrade soil shall be determined through laboratory testing. Laboratory testing consisting of California Bearing Ratio (CBR) testing, Resilient Modulus (Me) testing or Resistance Value (R-value) testing may be used to characterize the subgrade soil supporting capability. A minimum street section of 3 inches of hot mix asphalt (HMA) over 6 inches of properly placed and compacted crushed rock is required for local access streets, private streets, and alleys regardless of native soils. A minimum pavement section of 2 inches of HMA over 6 inches of crushed rock is required for private driveways. A soils investigation is required for all projects. The minimum pavement section cannot be used for sites with poor subgrade soils, which are soils that meet any of the criteria below: • Have CBR less than 3; • Have R-values less than 20; December 2009 Chapter 8 Pavement Design 8-1 CITY OF SPOKANE VALLEY STREET STANDARDS • Have Mr values less than 3,000 psi; or, • Are classified as MH, CL, CH, OL or peat in accordance with the Unified Soil Classification System. When results of laboratory testing indicate that poor subgrade soils are present, an engineered pavement design is required. Subsurface explorations (borings/test pits) are required for each travelway to demonstrate the subgrade soils meet the criteria above. Exploration should extend to a depth of at least 5 feet below proposed pavement subgrade. 8.3.2 TRAVELWAYS IN NON-RESIDENTIAL ZONES Engineered pavement design is required for commercial local access streets, commercial alleys, collector arterials, and arterials. The resilient modulus value can be acquired using the following methods: • Mr testing: Soil samples shall be obtained and sent to a private lab for testing. The proposed street shall have a minimum of one laboratory test for every 1,000 feet of street and/or for every obvious change in subgrade material (minimum of 3 tests per street). • CBR testing or R-value testing: Soil samples shall be obtained and sent to a private lab for testing. The proposed street shall have a minimum of 1 laboratory test for every 1,000 feet of street and/or for every obvious change in subgrade material (minimum of 3 tests per street). A geotechnical engineer shall be retained to provide recommendations for correlations between CBR or R-value results and Mr values. • In-situ testing using a non-destructive deflection test method: The Applicant shall obtain approval from the City for the type of non- destructive deflection test method proposed, before conducting the testing. For non-destructive deflection testing, a statistical analysis is needed. The results shall be reported by street stationing. Test results shall include a graph of the resilient modulus values vs. street stationing. The graph shall be included in the pavement design report. A minimum street section of 4 inches of HMA over 6 inches of properly placed and compacted crushed rock is required regardless of the pavement design results in accordance with Section 8.4. 8.3.3 SUBGRADE PREPARATION Prior to placing any street base material, the subgrade shall be rolled and compacted to a minimum of 95 percent of the maximum dry density as determined by ASTM D- 1557 (Modified Proctor). This degree of compaction shall extend to a depth of at least 1 foot below pavement subgrade elevation in cut areas. The fill areas shall be compacted to at least 95 percent of the maximum dry density based on ASTM D1557 and WSDOT Standard Specification 2-03.3(14)C Compacting Earth Embankments, Method C. Fill placed more than 2 feet below pavement subgrade elevation shall be compacted to at least 95 percent of the maximum dry density based on ASTM D1557. December 2009 Chapter 8 Pavement Design 8-2 CITY OF SPOKANE VALLEY STREET STANDARDS Any street section which cannot be compacted to the degree specified above shall be removed to a depth of 2 feet or to a depth where the pumping ceases, or as directed by the Onsite Inspector, and replaced with granular imported material that can be compacted to at least 95 percent of the maximum density as determined by ASTM D- 1557, or as directed by the Onsite Inspector. Prior to placing any sub-base or base materials, geo-textile fabric on the subgrade may be required if the existing subgrade is a fine-grained soil (ML, CL, MH, or CH). The geotextile fabric shall meet the criteria in Section 9.33 for "Separation" of the most current version of the WSDOT Standard Specifications. If the material is unsuitable, the soil shall be excavated below grade and compacted per WSDOT Standard Specification 2-03.3(3) and 2-03.3(14) Method C. 8.4 ENGINEERED PAVEMENT PARAMETERS Engineered pavement designs shall be in accordance with the 1993 AASHTO Guide for Design of Pavement Structures for flexible pavements and the following criteria: 8.4.1 TRAFFIC PARAMETERS The existing traffic levels shall be increased to match the projected traffic at the end of the street design life. The minimum design life shall be 20-years. The growth rate is 1.5 percent for residential streets and 3.5 percent for commercial/industrial streets and arterial streets. The 1.5 percent growth rate may be waived in closed subdivisions with City approval. This growth rate shall only be used for pavement design purposes and shall not be used for traffic analyses. The engineer shall submit Equivalent Single-Axle Loads (ESALs) calculations. The truck factors found in Table 8.1 may be used in the absence of other information. TABLE 8.1 —EQUIVALENT SINGLE AXLE LOADS VEHICLE TYPE TRUCK FACTOR (ESALs/VEHICLE) School Bus 2.87 STA Bus 2.57 Refuse Truck 1.03 All other trucks (averaged) 0.42 December 2009 Chapter 8 Pavement Design 8-3 CITY OF SPOKANE VALLEY STREET STANDARDS 8.4.2 RELIABILITY LEVEL The reliability level (R) for residential streets and local non-residential streets is 75 percent. For all other street classifications, the reliability level is 90 percent. 8.4.3 OVERALL STANDARD DEVIATION The overall standard deviation (S) is 0.45 for new construction and 0.49 for overlay projects. 8.4.4 INITIAL AND TERMINAL SERVICEABILITY INDEXES The initial and terminal serviceability indexes shall be per Table 8.2. TABLE 8.2—INITIAL AND TERMINAL SERVICEABILITY INDEXES STREET CLASSIFICATION PSI(INITIAL) PSI(TERMINAL) Private streets, alleys, access street, 4.2 2.00 residential streets & local non-residential _ Collector and minor arterials 4.2 2.25 Principal arterials 4.2 2.50 8.4.5 STRUCTURAL LAYER COEFFICIENTS Structural Layer Coefficients (aj) for new material shall be in accordance with Table 8.3. TABLE 8.3—STRUCTURAL LAYER COEFFICIENTS MATERIAL STRUCTURAL COEFFICIENT HMA 0.42 Crushed rock 0.14 Gravel base 0.10 8.4.6 DRAINAGE LAYER COEFFICIENTS Drainage coefficients (mi) for crushed rock and gravel base shall be in accordance with Table 8.4. This coefficient is used to modify the structural layer coefficients of untreated base and subbasin materials in flexible pavements. If limited information is available regarding drainage conditions, a value of 0.95 may be used. December 2009 Chapter 8 Pavement Design 8-4 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 8.4-RECOMMENDED DRAINAGE COEFFICIENTS PERCENT OF TIME PAVEMENT STRUCTURE IS EXPOSED TO MOISTURE LEVELS APPROACHING SATURATION Quality of Less Than Greater Than Drainage 1% 1-5% 5-25% 25% Excellent 1.40-1.35 1.35-1.30 1.30-1.20 1.20 Good 1.35-1.25 1.25-1.15 1.15-1.00 1.00 Fair 1.25-1.15 1.15-1.05 1.00-0.80 0.80 Poor 1.15-1.05 1.05-0.80 0.80-0.60 0.60 Ver Poor 1.05-0.95 0.95-0.75 0.75-0.40 0.40 8.4.7 SUBGRADE EVALUATION Prior to designing the pavement thickness, the subgrade soil shall be evaluated in accordance with Section 8.3.2 to establish a design Mr value. The following moduli ratios (ratio of seasonal moduli to "summer" module) found in Table 8.5 can be used to determine the effective roadbed (subgrade) resilient modulus value (MReff): TABLE 8.5-MODULI RATIO SAMPLE COLLECTION PERIOD MODULI RATIO Winter(January) 1.00 Winter& Spring (February through May) 0.85 Summer(June through September) 1.00 Fall (October through December) 0.90 83 REPORT SUBMITTAL The Applicant shall submit a geotechnical report for all sites. The report shall be prepared and stamped by an Engineer with experience in geotechnical engineering. The report shall include, as applicable: • Narrative of the site conditions and soils; • Recommended pavement section; • Site plan showing soil sample locations; • Field data; including boring or test pit logs; • Laboratory testing results, including discussion of CBRJmodulus subgrade correlation or R value/modulus subgrade correction; and, • Pavement design calculations. December 2009 Chapter 8 Pavement Design 8-5 CITY OF SPOKANE VALLEY STREET STANDARDS 8.6 MATERIALS SPECIFICATIONS The following material requirements refer to or amend the most current version of the WSDOT Standard Specifications. 8.6.1 GRAVEL BASE Gravel base shall be bank run gravel, defined as naturally occurring material having characteristics such that when compacted in place on the street, it provides a course having greater supporting value than the subgrade on which it is placed. It shall be in accordance with Section 9-03.10 of the WSDOT Standard Specifications. 8.6.2 CRUSHED ROCK Crushed rock used shall fall under the following two classifications: • Crushed Surfacing Top Course (CSTC) • Crushed Surfacing Base Course (CSBC) CSTC and CSBC shall be in accordance with Section 9-03.9(3) of the WSDOT Standard Specifications including the following modification: The crushed aggregate portion which is retained on the No. 4 sieve shall contain not more than 15 percent, by weight, of flat or elongated pieces as defined in ASTM D 693. The crushed aggregate shall have at least 90 percent by weight of particles with at least one fractured face. The area of each face shall be equal to at least 75 percent of the smallest mid-section area of the piece. 8.6.3 ASPHALT OR CONCRETE TREATED BASE When compaction soils type or moisture content precludes proper compaction, asphalt treated base (ATB) or concrete treated base (CTB) should be utilized. 8.6.4 HOT MIX ASPHALT Hot mix asphalt shall be in accordance with the current edition of the WSDOT Standard Specifications. Pavement design calculations shall be performed by an Engineer experienced with performance grade oils and pavement design calculations. Asphalt used in City street construction shall use performance grade asphalt binders, in accordance with AASHTO Designation MP-1. The minimum base binder used shall be PG-64-28. Required base binders based on street type and condition are provided in Table 8.6. December 2009 Chapter 8 Pavement Design 8-6 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 8.6—PERFORMANCE GRADE STREET CLASSIFICATION PERFORMANCE GRADE Local access, private streets, and alleys 64-28 Collectors and arterials 70-28 Aggregate for use in hot mix asphalt shall be Class 1/2—inch in accordance with Section 9-03.80) of the WSDOT Standard Specifications. 8.6.5 IN-PLACE MAINLINE ASPHALT COMPACTION TEST REQUIREMENTS A lot consists of 5 random individual tests. Minimum density testing requirements are 1 lot per 400 tons of HMA or 1 lot per day, whichever results in the greater number of lots. A lot shall be rejected if any of the following occurs: • The average compaction of the lot is less than 92 percent of maximum density, as determined by WSDOT FOP for AASHTO T166 and T209; or; • Any individual compaction test in the lot is less than 91 percent or higher than 96 percent of the maximum density, as determined by WSDOT FOP for AASHTO T166 and T209. Additional testing requirements shall be per Appendix 9-A. 8.6.6 COLD JOINT REQUIREMENTS Section 5-04.3(10)B of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction, 2008 edition is supplemented with the following: Extreme care shall be exercised in the construction of cold joints to insure that the joint is properly tacked with a uniform and heavy coating of an approved tacking agent, that the placement of HMA adjacent to the cold joint is properly raked and that the adjacent hot mix is rolled and compacted in such a manner so as to completely seal the joint. The formation of all joints shall be made in such a manner as to ensure a continuous bond between the courses and obtain the required density. All joints shall be the same texture as other sections of the course and meet the requirements for smoothness and grade. If in the opinion of the City, the cold joint has not been properly constructed the joint shall be sealed with a joint compound sealant as per AASHTO M 324, at the Contractor's own expense. 8.6.7 LONGITUDINAL AND TRANSVERSE JOINT REQUIREMENTS Section 5-04.3(12) Joints of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction, 2008 edition is supplemented with the following: The formation of all joints shall be made in such a manner as to ensure a continuous bond between the courses and obtain the required density. All joints shall be the December 2009 Chapter 8 Pavement Design 8.7 CITY OF SPOKANE VALLEY STREET STANDARDS same texture as other sections of the course and meet the requirements for smoothness and grade. When paving occurs on an arterial street within the City of Spokane Valley, cold joints will be limited to the centerline of the roadway and shall be constructed per Standard Plan R-127-Step Wedge Longitudinal Cold Joint. A paving plan shall be submitted, to Public Works, detailing how the work is to be accomplished. Where possible the Contractor is required to use multiple pavers in order to reduce or eliminate longitudinal joints. 8.6.8 TACK COATS - PREPARATION OF EXISTING SURFACES Section 5-04.3(5)A, paragraph 2 of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction is hereby amended as follows: A tack coat of asphalt shall be applied to all paved surfaces on which any course of HMA is to be placed or abutted. Tack coat shall be uniformly applied to cover the existing pavement with a thin film of residual asphalt, free of streaks and bare spots. The application rate shall be 0.02 to 0.08 gallons of retained asphalt per square yard. If the tack coat has been diluted with water, as allowed in this section, then the application rate must be adjusted in order to achieve the retained amount of asphalt required. A heavy application of tack coat will be applied to all joints. Thin lifts of pavement require heavier applications of tack coat to prevent raveling, spalling and delamination. As a guide, existing surfaces that are coarse, dry or milled require a higher application rate of tack coat than surfaces that appear rich or bleeding. For streets open to traffic, the application of tack coat shall be limited to surfaces that will be paved during the same working shift. The spreading equipment shall be equipped with a thermometer to indicate the temperature of the tack coat material. 8.6.9 COVER ASPHALT LOADS DURING TRANSPORT Tarpaulin material shall be used to cover asphalt loads during transport from plant to project for all projects when the ambient air temperature is 50 degrees Fahrenheit or less. 8.6.10 BREAKDOWN ROLLING MAXIMUM TEMPERATURE LOSS Breakdown rolling shall occur before 20° F or greater temperature loss of the mix from the point of laydown. Temperature for basis shall be that observed and recorded in the transport vehicle at time of discharge to the paver. 8.6.11 ASPHALT TEMPERATURE PLACEMENT REQUIREMENTS Table 8.7 shows the minimum laydown temperatures and rolling times. Vibratory compaction shall not be used after the asphalt mat cools below 175°F. The rolling pattern shall be established in conjunction with asphalt density testing. December 2009 Chapter 8 Pavement Design 8-8 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 8.7 RECOMMENDED MINIMUM LAYDOWN TEMPERATURE MAT THICKNESS (INCHES) Base Temp, %2 3A 1 1 % 2 >3 F 40-50 310 300 285 275 50-60 310 300 295 280 270 60-70 310 300 290 285 275 265 70-80 300 ' 290 285 280 270 265 80-90 290 285 275 270 265 260 < 90 280 275 270 265 260 255 Rolling 4 6 8 12 15 15 Time (min) 1. Reference is Table 6-4 from the National Center for Asphalt Technologies, Hot Mix Asphalt, Mixture Design and Construction. 2. Time available between recommended laydown temperature and cessation temperature (175 °F) when attempts to compact the mat should cease. 3. These compaction temperatures are estimates and will vary with different asphalt cements and aggregates. For thin mats, the time available for rolling is short. For example, a '/.-inch mat placed at the recommended minimum laydown temperature has only 6 minutes to be compacted to achieve the target density. The roller speeds cannot be increased significantly without adversely affecting density;hence,additional rollers may be required when paving at low temperatures. 8.6.12 PAVING DATES & WEATHER LIMITATIONS WSDOT Section 5-04.3(16) Weather Limitations is amended as follows: • HMA shall not be placed on any traveled way between October 1st and April 1st without written approval from the City. December 2009 Chapter 8 Pavement Design 8-9 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK December 2009 Chapter 8 Pavement Design 8-10 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 9 - INSPECTION & CERTIFICATION '{0o- ♦.!".�� 1 Z �Vicp.t ' _ • Chapter Organization • 9.1 Introduction 1 9.2 Applicability 1 9.3 Authority to Stop Work 1 9.4 Responsibilities 1 9.4.1 Development Inspector 1 9.4.2 Onsite Inspector 2 9.4.3 Applicant's Engineer 3 9.4.4 Contractor 3 9.5 Right-Of-Way Permits 3 9.6 Pre-Construction Meeting 4 9.7 Construction Notification 4 9.7.1 Notices of Upcoming Construction 4 9.7.2 Notices of Utility Shutdown and Access Limitations 5 9.7.3 Notices for Inspection 6 9.8 Field and Lab Testing 6 9.8.1 Reporting 6 9.8.2 Minimum Material Testing Frequencies 6 9.8.3 Field Testing And Lab Requirements 6 9.9 Required Inspections 7 9.9.1 Erosion and Sediment Inspections 7 December 2009 9-i Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.9.2 Utility Inspections 7 9.9.3 HMA Inspections 7 9.9.4 Drainage Structure Inspections 8 9.9.5 Drainage Swale and Drainage Facilities Inspections 8 9.9.6 Swale Inspection During Warranty Period 9 9.10 Miscellaneous 9 9.10.1 Changes During Construction 9 9.10.2 Construction Complaints 9 9.10.3 Conflict Resolution 9 9.11 Final Walk-Through 9 9.12 Record Drawings 10 9.13 Project Certification 10 9.13.1 Certification of Drainage Facilities 11 9.14 Performance Surety 11 9.14.1 Building Permit 11 9.14.2 Short Plats, Long Plats and Binding Site Plans 12 9.14.3 Performance Surety Amount 12 9.14.4 Acceptable Sureties 12 9.14.5 Performance Surety Release 12 9.15 Warranty Surety 13 9.15.1 Warranty Surety Amount 13 9.15.2 Acceptable Sureties 13 9.15.3 Warranty Duration 13 9.15.4 Time Frames to Complete Repair 13 9.15.5 Failure to Complete Repair 14 9.15.6 Responsibility for Maintenance 14 9.16 Street Establishment 14 List of Figures Figure 9-1 Typical Sign 5 List of Tables Table 9.1 Required Sign Information 5 List of Appendices Appendix 9A - Minimum Material Testing Frequencies 16 Appendix 9B - Final Certification Checklist- Sample 17 Appendix 9C - Examples of Sureties 18 Appendix 9D - Erosion and Sediment Control Log 25 December 2009 9-ii Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.1 INTRODUCTION Inspection oversight is required for the construction of all public and private streets, alleys, driveways, and utility improvements. Water and sewer construction shall also be monitored by the system purveyor and/or agency of system ownership. The City of Spokane Valley's construction certification process is based on the project construction certification procedures found in the Project Construction Certification Procedures for Spokane County Road, Drainage, and Sewer Projects, dated April 2002. Spokane County Department of Public Works and the American Council of Engineering Companies of Washington (a subcommittee named the Spokane County Construction Certification Committee) developed that document. 9.2 APPLICABILITY The following projects require construction certification: • New construction of public streets; • New construction of private streets; • New construction of engineered driveways; • Frontage improvements on public streets, including pavement widening, curb and gutter, sidewalk, and drainage improvements; and, • The swales and drywells for commercial projects. 9.3 AUTHORITY TO STOP WORK The Development Inspector has the authority to stop work when any of the following situations exists: • The Contractor is working without a valid permit; • The Contractor is executing work not included in the approved plans; • Required inspections and tests are not being performed; • Test results do not meet required specifications; and, • Construction activities have the potential to adversely impact public or private property or human life. 9.4 RESPONSIBILITIES 9.4.1 DEVELOPMENT INSPECTOR The Development Inspector is a full time City employee and is responsible for: December 2009 9-1 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS • Coordinating with and reviewing submittals from the Onsite Inspector(s); • Performing development walk-through on private and public streets for acceptance and surety reductions; • Reviewing and accepting certification packages. A project certification will not be accepted if required frequencies for testing are not met or test results do not meet specifications; • Reviewing quantity estimates for performance and warranty sureties; • Performing final inspections of public streets for surety release and street establishment; and, • Inspecting swales located in border easements and/or right-of-way for single family dwellings and duplexes prior to issuing a certificate of occupancy. 9.4.2 ONSITE INSPECTOR The Applicant is required to secure the services of an Onsite Inspector for all projects requiring certification. The Onsite Inspector is responsible for: • Preparing weekly reports; • Ensuring that plans and specifications are followed; • Inspecting paved areas, curb and gutter, sidewalks, approaches, drainage improvements, and utilities within the right-of-way and border easements. The Onsite Inspector shall be present at all times for HMA placement, any trench work within the street prism, and for drywell installation; • Coordinating required testing and frequencies (see Appendix 9A); • Monitoring traffic control; • Verifying fire hydrants, gates, and No Parking signs were installed at the location shown in the plans; • Preparing as-built drawings, and, • Preparing the certification package. December 2009 9-2 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.4.3 APPLICANT'S ENGINEER The Applicant's Engineer is an Engineer, as defined in the Definitions, hired by the Applicant. The Applicant's Engineer provides required project modifications that occur during the construction process, coordinating with the Contractor and obtaining City approval when significant modifications are required. Conflicts arising due to concerns regarding project design or constructability, whether surfaced by the Contractor, Onsite Inspector, or Development Inspector, shall be addressed by the Applicant's Engineer. The method of addressing the concern shall be confirmed by the Development Inspector with specific follow-up oversight by the Onsite Inspector. 9.4.4 CONTRACTOR The Contractor is responsible for: • Attending the pre-construction meeting; • Providing all licenses, bonds and insurance information at the pre- construction meeting; • Construction notification in accordance with Section 9.7; • Having knowledge of the testing frequencies and construction items requiring inspection (see Appendix 9A); • Notifying the Onsite Inspector and Development Inspector, as applicable, prior to the placement of construction items requiring inspection; • Completing all improvements in accordance with the approved plans; and, • Correcting deficiencies as identified by the Onsite Inspector, the Development Inspector, or the applicant. 9.5 RIGHT-OF-WAY PERMITS Right-of-way permits are required for all work in the public right-of-way. No person, firm or corporation shall commence work or permit any other person, firm or corporation to commence work on the construction, alteration, repair or removal, cutting and/or paving of any street, alley or other public place in the City without first obtaining a written right-of-way construction permit and approved plans from the City. The Applicant shall secure the services of an Onsite Inspector before securing a right-of- way construction permit for any given project requiring certification. December 2009 9-3 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.6 PRE-CONSTRUCTION MEETING A pre-construction meeting is required for the following projects: • Long plats; • Short plats; • Binding site plans; • • Commercial projects with frontage and/or full street improvements; and, • Other projects which the City deems a pre-construction meeting is required. The pre-construction meeting shall be held prior to commencing work. The purpose of the pre-construction meeting is to discuss project concerns or issues, construction notification requirements and certification procedures. The Applicant, Applicant's Engineer, Contractor, HMA and concrete subcontractors, Development Inspector and Onsite Inspector are required to attend this meeting. A pre-construction meeting will not be held if the Contractor, paving and concrete subcontractors, and/or the Onsite Inspector are not present. The Contractor shall bring a properly planned and coordinated project schedule to the pre-construction meeting. 9.7 CONSTRUCTION NOTIFICATION 9.7.1 NOTICES OF UPCOMING CONSTRUCTION Construction warning signs shall be securely posted 14 days prior to construction of short plats, long plats, or any other project with street construction. Signs shall be placed at all ingresses to the project area and shall be clearly visible from the right-of- way. A typical sign is included in Figure 9-1. The Contractor shall notify the Development Inspector within 72 hours of installing the sign(s). The signs shall be posted for the duration of the project and shall conform to the following: • The signs shall be made of materials that are able to withstand weather for the duration. The signs shall be maintained to remain readable from the public right-of-way; • The sign supports shall meet current safety standards; • The bottom of the sign shall be 7 feet above ground; • Lettering shall be easily readable and shall be per Table 9.1; and, • The signs shall include the information required in Table 9.1. On large or high profile projects, the Applicant shall provide the proposed project schedule and weekly updates to the City's Public Information Officer to notify the public of the project progress. December 2009 9-4 Chapter 9-Inspection&Certification • CITY OF SPOKANE VALLEY STREET STANDARDS FIGURE 9-1 TYPICAL SIGN Road Work Next 600 Feet Begin: May 25, 2008 — End: Oct. 12, 2008 Work Includes: Sewer and Water Installation, Roadway Widening and Repaving Contractor: Dee Caterpillar, (999) 636-3333, Pave la Tierra, Inc. Engineer: Mike Mylar, (999) 111-2233, Pan Global Engineering Developer: Ima Platter, (999) 555-1212, Progression Homes, LLC Thank you for your patience. TABLE 9.1 REQUIRED SIGN INFORMATION INFORMATION ON SIGN MINIMUM TEXT HEIGHT Road Work Next#Miles/Feet 2 1/2 inch Begin: Month, Day Year—End: Month, Day Year 2 inch Work includes: New Street, Utility Installation, Paving ... 1 inch Contractor: Contact Name, Phone Number, Company Name 1 inch Engineer: Contact Name, Phone Number, Company Name 1 inch Developer: Contact Name, Phone Number, Company Name 1 inch Thank you for your patience. 2 inch 9.7.2 NOTICES OF UTILITY SHUTDOWN AND ACCESS LIMITATIONS Affected residents and businesses are to be notified at least 24 hours in advance of when their utilities (water, electricity, etc.) will be interrupted and/or when access will be limited. The notification shall include the duration of the interruption. The Contractor shall provide written notification and hand deliver the notification to the affected residents and businesses. The Contractor shall provide a copy of the notification and a list of the citizens/businesses notified to the Development Inspector. This information shall be included in the weekly reports. December 2009 9-5 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.7.3 NOTICES FOR INSPECTION The Contractor shall inform the Development Inspector at least 24 hours in advance of paving operations or installation of drywells. Seventy two hours notice is required for work performed during the weekend or on Monday. It is the responsibility of the Contractor to coordinate with the Onsite Inspector for all required inspections and required testing. Development Engineering will not accept any improvements failing to meet the minimum number of required tests or failing to meet the required test results. 9.8 FIELD AND LAB TESTING 9.8.1 REPORTING The Onsite Inspector shall prepare weekly project summary reports. All lab and field-testing reports shall be included in these weekly reports and in final certification packages. Test reports that show failing tests shall have follow-up test reports that show passing tests for the area of failure. Onsite samples shall be used for testing. Any nonconforming issues shall be fully recorded with subsequent documents detailing how the issue was corrected. 9.8.2 MINIMUM MATERIAL TESTING FREQUENCIES Material testing is required as specified in Appendix 9A. The frequency of testing may be increased at the discretion of the Onsite Inspector or the Development Inspector. Any known site soil special areas of concern shall be addressed with increased testing frequencies based on sound engineering judgment. Wet weather conditions may also require additional testing frequencies. The Onsite Inspector shall coordinate the number of tests, locations, etc. with an approved materials lab. The Applicant shall be responsible for the testing and laboratory costs. Development Engineering will not accept any improvements failing to meet the minimum number of required tests or failing to meet the required test results. 9.8.3 FIELD TESTING AND LAB REQUIREMENTS A material supplier, the Applicant, or the Contractor may not perform testing for certification purposes. Field testing shall be conducted by personnel that is adequately trained, qualified, and certified in accordance with the applicable test specifications. Field testing and laboratories shall have a national recognized accreditation, for the field and lab tests performed by the firm, such as AASHTO, Washington Association of Building Officials (WABO), American Association of Laboratory Accreditation (A2LA), etc. December 2009 9-6 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS The entity in charge of field testing and the laboratory shall submit copies of their accreditation to the Onsite Inspector so this information can be included in the certification package. 9.9 REQUIRED INSPECTIONS The Onsite Inspector is required to certify the inspection of the following (See Appendix 9B for required testing frequency): • Placement and maintenance of erosion control. A site log shall be completed for the project; • Embankment placement and density control; • Trenching backfill and density control; • Inspection and testing during pipe installation and pipe zone material placement (see Section 9.8.1 for additional information); • Subgrade line and grade/density control; • HMA surfacing line and grade/density control (see Section 9.8.3 for additional information); • Installation of drainage improvements and any required testing; • Installation of curb and gutter and material quality; and, • Installation of sidewalks and material quality. 9.9.1 EROSION AND SEDIMENT INSPECTIONS A site log shall be completed for the project. The site log shall include the results of all site inspections, sampling as applicable and other records. For sites one acre or larger, inspections must be conducted by a Certified Erosion and Sediment Control Lead(CESCL) (See appendix 9D). 9.9.2 UTILITY INSPECTIONS Utility work shall be in accordance with Spokane County Interim Policy Regarding Sewer Construction Inspections, Record Drawings & Engineer's Statement and Spokane County Division of Utilities Protocol for Television Inspection of Sewers. Whenever pipe installation or pipe zone material placement and compaction are underway, the Onsite Inspector shall observe the work on a continual basis. 9.9.3 HMA INSPECTIONS The Onsite Inspector shall be present at all times during paving operations. December 2009 9-7 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.9.4 DRAINAGE STRUCTURE INSPECTIONS The Onsite Inspector shall be present at all times during the installation of pipe, pipe zone material, drywells (including the geotextile and drainrock surrounding the drywell barrel), catch basins, and other drainage structures or facilities. 9.9.5 DRAINAGE SWALE AND DRAINAGE FACILITIES INSPECTIONS The Onsite Inspector shall verify that the volume of each finished drainage swale equals or exceeds the design volume of the swale at a 6-inch and 1-foot depth. Additionally, the Onsite Inspector shall verify that there is adequate and continuous grade from the street to the swale for the effective conveyance of runoff. If these items are deficient, the Onsite Inspector shall notify the Contractor and/or Applicant's Engineer to determine a solution. Elevation sensitive aspects of installed materials, such as drywell rims, etc., shall be verified as within normal industry tolerances (i.e., drywell rim elevations+/- 5/100'). At the discretion of the City, a test of the facility may be conducted to demonstrate adequate performance. The test shall be performed in the presence of the Onsite Inspector and Development Inspector. All aspects of the drainage facility, including landscaping, irrigation, and establishment of specified vegetation, shall be completed in accordance with the accepted plans. An exception may be granted for single-family or two-family residential subdivisions where the completion of the swales is not practical until such time as the dwellings are constructed. In these cases, the Applicant shall rough-grade the swales to the required volume, install all drywells, inlets, and curb drops and other structures in accordance with the accepted plans. If the driveway approach width is greater than the width shown in the lot plans, engineering calculations shall be submitted that demonstrate that treatment and storage requirements are met. Erosion control measures shall be implemented to protect the installed drainage structures and to prevent erosion and/or failure of the swale side slopes. This includes, but is not limited to, lining the swale with geo-fabric that can be removed along with accumulated silt, until the swale is final-graded and vegetated. Completion of the landscaping, irrigation, and establishment of specified vegetation shall be required prior to issuance of the final Certificate of Occupancy or final inspection for any associated dwelling. For single and two-family dwellings, it shall be the responsibility of the Builder to satisfy these requirements. Acceptance of performance sureties, in lieu of establishing the vegetation, shall be permitted only when completion of improvements prior to final land action or permanent Certificate of Occupancy is impractical because of cold weather not suitable for the establishment of vegetation. December 2009 9-8 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.9.6 SWALE INSPECTION DURING WARRANTY PERIOD The Applicant's Engineer and the Development Inspector shall monitor performance of swales during the construction and warranty periods for proper percolation. Swales that do not percolate properly shall require corrective work or measures and are the financial responsibility of the Applicant. 9.10 MISCELLANEOUS 9.10.1 CHANGES DURING CONSTRUCTION Changes during construction that affect the scope of the project and/or the accepted individual lot plans shall be submitted for review by the City. The Development Inspector will determine if the change is significant. Minor changes do not require City review, but shall be discussed with the Development Inspector and documented in the daily and weekly inspection reports. The Development Inspector shall review and approve any significant field changes to the design plans and permits that have prior approval. Review and acceptance of any changes to approved plans for utility, site improvements and street right-of-way work shall require the oversight of both the utility operator as well as the Development Inspector. 9.10.2 CONSTRUCTION COMPLAINTS Complaints from citizens regarding the project shall be documented and shared with the Development Inspector and resolved by the Applicant. On more significant or high profile projects, the City may assign a Public Information Officer to notify the public of the project schedule and provide weekly up-dates (See Section 9.6). 9.10.3 CONFLICT RESOLUTION During the construction process, occasional differences may arise between the Applicant's Engineer and/or Contractor and City staff regarding interpretation of policies, standards or guidance documents. When the Applicant's Engineer or Contractor does not agree with an interpretation made by City staff, the Applicant's Engineer may appeal to the Development Services Senior Engineer, as appropriate. The determination by the Development Services Senior Engineer is final. 9.11 FINAL WALK-THROUGH When requested by the Applicant, the Onsite Inspector and Contractor shall prepare a punch list. When the punch list items have been addressed, the Applicant shall schedule a final walk-through with the Development Inspector. December 2009 9-9 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS If no deficiencies are found, the Onsite Inspector shall then prepare a certification package in accordance with Section 9.13. If deficiencies are found, another final walk- through with the Development Inspector is required. The Applicant continues to be responsible for correction of all deficiencies until the City accepts the project unless as noted in Section 9.14. It is suggested that the Applicant consider taking verification photographs immediately following the final walk-through. Verification photographs can be helpful in resolving cases of damage by third parties (utility companies, builders, landscapers). 9.12 RECORD DRAWINGS All construction changes shall be recorded on a set of approved plans with the original approval stamp from the City. After the final walk-through, the Applicant's Engineer or Onsite Inspector shall prepare record drawings for the project. Record drawings shall be stamped and have a signed certification statement saying: "I have reviewed the construction and to my knowledge I find it to be in conformance with the approved plans except as noted". Changes from the originally accepted documents shall be clearly noted with "clouds" on the approved plans and changes shall be noted in the revision block. Revised notes, elevations, grades or other text shall be lined through. Clean new sheets are not desired. Any changes to easements shall be clearly shown on the record drawings. Record drawings shall be marked"Record Drawings." If a change represents a deviation from the design intent or system performance in the judgment of the Applicant's Engineer, then it shall be clearly shown. Spot elevations (on swales, curb, gutter, etc.) to depict final grades should be taken and compared with the final design. Differences shall be noted on the record drawings. Significant changes shall be coordinated with the Applicant's Engineer. Elements of the plans that were not built shall have a design change acceptance from the City prior to final inspection and submittal of record drawings. 9.13 PROJECT CERTIFICATION The Onsite Inspector shall prepare a certification package for the project. The package shall include • Certification letter from Engineer with stamp; • Weekly reports; • Material test reports; • A summary of the test results, including a discussion of how they compare to required specification; • The certification checklist(Appendix 9B); December 2009 9-10 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS • Erosion and Sediment Control Logs (Appendix 9D); • Truck tickets; • All related construction documents including correspondence and communication records; • Copies of the required accreditation for the field testing staff and testing laboratory in accordance with Section 9.8.3; • Copies of drywell registrations; • One set of Mylar record drawings; and, • One paper copy of the stamped Mylar. The City of Spokane Valley will review the certification package within a 2-week period and shall notify the Applicant if the project is accepted to go to warranty. This Notice of Substantial Completion is conditioned upon no further deficiencies becoming evident before the City accepts the project. Upon notification that the project is provisionally accepted and upon receipt of the warranty surety, the warranty period shall begin. 9.13.1 CERTIFICATION OF DRAINAGE FACILITIES Stormwater facilities located in tracts shall be certified prior to final plat approval for plats, short plats and binding site plans. The certification of stormwater facilities located within border easements and right-of-way for single-family and two-family dwellings may be delayed until the issuance of the final Certificate of Occupancy (Refer to Section 9.9.5). Drainage facilities associated with a commercial building permit shall be certified, as specified in Section 9.13, prior to issuing a final Certificate of Occupancy. 9.14 PERFORMANCE SURETY The Applicant shall complete all plan improvements prior to the approval of the final plat, short plat, or binding site plan or the issuance of Certificate of Occupancy. A performance surety may be submitted in lieu of the completion of the actual construction of required improvements prior to the approval of the final plat, short plat, binding site plan or Certificate of Occupancy as described in the sections below. 9.14.1 BUILDING PERMIT A surety in lieu of completion of a specific condition may be allowed if approved by the City, if necessitated by weather or conflicting construction schedules. A completion schedule for the project must be submitted and approved prior to releasing the Certificate of Occupancy. December 2009 9-11 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.14.2 SHORT PLATS, LONG PLATS AND BINDING SITE PLANS No surety in lieu of construction shall be allowed for the construction of utilities or streets, including pavement, curbs, and gutters. A surety in lieu of completion of sidewalks, drainage improvements, or driveway approaches may be allowed if approved by the City, if the following conditions are met: • A completion schedule is submitted and approved; • The improvements are sufficiently complete as to allow proper function and operation of the transportation, sewer, water, and stormwater systems, as determined by the City; • The improvements shall be completed within 18 months of the date of final approval; and, • The Applicant has not had any outstanding improvements that have not been timely completed within other plats, short plats, binding site plans, or building permits. 9.143 PERFORMANCE SURETY AMOUNT The Applicant's Engineer shall submit quantities for the complete nature of the work to be performed within or on the right-of-way, border easements, or on the frontage of City right-of-way. The Development Inspector will enter that information into an updated calculation spreadsheet reflecting a total valuation of the work to be performed. The performance surety shall be for 125 percent of the total work to be performed. Performance surety shall include all construction costs, including erosion and sediment control and inspection costs. The performance surety shall not be less than $10,000.00. 9.14.4 ACCEPTABLE SURETIES The performance surety shall be a letter of credit or cash savings assignment. Bonds are not accepted. Examples of sureties are provided in Appendix 9C. 9.14.5 PERFORMANCE SURETY RELEASE The performance surety shall be released when all of the following conditions have been met: • A certification package is accepted by the City; • The Applicant has paid in full all costs incurred by the City; • All monuments have been reset and referenced by a surveyor; and, • The Applicant has submitted a warranty surety for improvements in the public right-of-way and border easements as specified in Section 9.14. December 2009 9-12 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.15 WARRANTY SURETY All projects with improvements in the public right-of-way or border easements shall submit to the City a warranty surety. The warranty surety shall guarantee against material and/or workmanship defects in street construction, utility work within the right- of-way and border easements, and/or drainage facilities as required by the City. 9.15.1 WARRANTY SURETY AMOUNT The Applicant's Engineer shall submit quantities for the complete nature of the work to be performed within or on the right-of-way, border easements, or on the frontage of City right-of-way. The Development Inspector will enter that information into an updated calculation spreadsheet reflecting a total valuation of the work to be performed. The Development Inspector will then calculate 20 percent of that total work to be performed, but not less than $10,000.00, and request a surety for that amount from the Applicant. 9.15.2 ACCEPTABLE SURETIES The warranty surety shall be a letter of credit or cash savings assignment. Bonds are not accepted. Examples of sureties are provided in Appendix 9C. 9.153 WARRANTY DURATION The surety shall remain in effect for 2 years from the date of provisional acceptance of the streets. Thirty days prior to the expiration of the warranty, the Applicant shall retain an Engineer to inspect the improvements. Any deficiencies noted shall be repaired prior to the release of the surety. If the inspection is not conducted and the deficiencies are not repaired, the warranty surety shall be renewed by the Applicant until this requirement is satisfied. The Development Inspector will conduct a walk- through prior to releasing the warranty surety. 9.15.4 TIME FRAMES TO COMPLETE REPAIR The warranty surety shall be used to correct deficiencies due to materials and/or workmanship. At any time before the end of the warranty period, the City may notify the Applicant of needed repairs. If repairs are considered to be an imminent danger to the public's health, safety, and welfare, the Applicant shall act within 24 hours to complete the repair. If the work is not considered a safety issue, the Applicant has 10 business days to schedule the work, and 60 calendar days to complete the work. Extensions of time may be considered when necessary due to weather constraints. When the project is accepted and in warranty or after releasing the warranty surety, the Builder is responsible for any damage to the improvements along the lot frontage. December 2009 9-13 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS Any deficiencies shall be corrected by the Builder prior to the issuance of the final Certificate of Occupancy for the structure. 9.15.5 FAILURE TO COMPLETE REPAIR If the warranty repairs are not completed in the time frame specified, the City may choose to conduct the necessary repairs. The City will either invoice the Applicant or collect from the surety for all costs for the related work, plus a $500.00 administrative fee. 9.15.6 RESPONSIBILITY FOR MAINTENANCE The Applicant is responsible for maintaining all public improvements, excluding snow plowing, throughout the warranty period. 9.16 STREET ESTABLISHMENT When the project has been certified and accepted, the Applicant can request to receive provisional acceptance after posting a warranty surety in accordance with Section 9.14. The Applicant is responsible to repair failures during the warranty period in accordance with Section 9.15.4. Final acceptance shall be granted after the warranty period assuming all deficiencies have been corrected. The City Manager is responsible for approving the establishment of new streets. When the project receives final acceptance, the Development Services Senior Engineer shall • recommend to the City Manager that the streets be established. December 2009 9-14 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX INDEX Appendix 9A - Minimum Material Testing Frequencies Appendix 9B - Final Certification Checklist—Sample Appendix 9C - Examples of Sureties Appendix 9D - Erosion and Sediment Control Log December 2009 9-15 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9A — Minimum Material Testing Frequencies The following testing frequencies represent the minimum requirements during construction. If individual tests fail to meet specifications, additional testing shall be conducted to assure conformance. Earth Embankment -1 density test per lift per 500 CY placed Road Subgrade -1 density test per 100 LF of lane or equivalent Crushed Rock -1 density test per 100 LF of lane or equivalent per lift Trench Embankment -1 density test per 150 CY with varying test depths Crushed Rock under -1 density test per 100 LF of curb of walk length per lift Curb and Sidewalks (Unless tested as part of the roadway crushed rock) Concrete for Curbs -1 set (4 cylinders) per 100 CY (Minimum 1 set per day) and Sidewalks -1 set of air, slump, temperature, etc. on first truck and with cylinders thereafter Aggregate Quality -1 gradation test -1 sand equivalent test -1 fractured face test Asphalt Pavement -1 Lot=400 tons -5 random density tests per lot (Minimum 5 tests per day) -1 test to verify gradation per 1,000 tons (Minimum 1 test per day) -1 test to verify asphalt content per 1,000 tons (Minimum 1 test per day) -1 test to verify maximum density per 1,000 tons (Minimum 1 test per day) December 2009 9-16 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9B — Final Certification Checklist (Sample) Project: Certification Letter: Statement of intent to certify the project. PE Stamp and Signature. Record Drawings Mylar Drawings: PE Stamp and Signature Lettered certification statement (Section 9.12) Project Documents: Daily Inspection Reports: Field Reports: Inspection of Asphalt Paving: 100% On site inspection during paving Compaction Reports: Sewer trench lifts. Water trench lifts. Utility trench lifts. Crushed Rock lifts. Material Documents: Field and Laboratory Tests: Field Test Lab Test Concrete (Slump, Air Content, (Break Test) Temp). Subgrade: (Compaction) (Gradation, Proctor) Crushed Rock (Compaction, Depth) (Gradation, Proctor) Asphalt (Compaction, (Rice, Gradation, Oil Thickness) Content) On Site Inspections of Drainage Items: Drywells: Gutter Inlets: Culverts: Sidewalk Vaults: Drainage Ditches: Other: Incoming/Outgoing Correspondence December 2009 9-17 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9C — Examples of Sureties December 2009 9-18 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS LETTER OF CREDIT (BANK LETTERHEAD) IRREVOCABLE STANDBY LETTER OF CREDIT Date: Beneficiary: Applicant: City of Spokane Valley Name: 11707 E. Sprague, Suite 106 Address: Spokane Valley, WA 99206 Phone: Attn: Project# & Name: Letter of Credit Number: Expiration Date: Our Counters Presently Located At: Amount: Not exceeding US Dollars . (written dollar amount) Surety is for the following(check one): O Performance surety for public improvements • Performance surety for private improvements • Warranty surety for public improvements Itemized as follows: Roadway Improvement&Inspection: (Amount—numeric and written) This Page 1 forms an integral part of credit number December 2009 9-19 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS We hereby issue this irrevocable standby letter of credit for(project name and number)available by your draft(s) drawn on us and accompanied by the following documents: 1. A signed statement from the Spokane Valley Development Services Senior Engineer's Office reading exactly as follows: "I,the undersigned duly authorized representative of the Spokane Valley Engineer's Office, hereby certify that the draft drawn under this letter of credit represents the amount of money required to complete the installation of street improvements including grading, gravel, paving, curbs, sidewalks, storm drainage, drainage swales, monuments, street signs, inspection, construction engineering and/or other work as is incidental and related thereto in accordance with the acceptable civil plans and specifications as submitted to and approved by the Spokane Valley Engineer's Office on(date of approved plans)". 2. The original of this letter of credit. This Page 2 forms an integral part of credit number December 2009 9-20 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS SPECIAL CONDITIONS 1. Any and all banking charges other than those of the issuing bank are for the account of the beneficiary. 2. It is a condition of this letter of credit that it shall be automatically extended, without amendment, for an additional period of one year from the present expiration date or each future expiration date, unless we have notified you in writing not less than thirty(30) days before such expiration date, that we elect not to renew this letter of credit and have received from the City Engineer a letter approving the non-renewal of this letter of credit. All written notification shall be sent via registered mail. Drafts drawn under this credit must bear the clause: "Drawn under (bank's name and letter of credit number)." This credit is subject to the "Uniform Customs and Practice for Documentary Credits (1993)", International Chamber of Commerce Publication No. 400. We hereby engage with you that draft(s) drawn and/or documents presented and negotiated under and in compliance with the terms of this irrevocable standby letter of credit will be duly honored upon presentation to us. The amount of each drawing must be endorsed on the reverse of this credit by the negotiating bank. A charge of USD25.00 will be deducted from the proceeds of any drawing presented with discrepancies. NAME OF ISSUING BANK Signature and signatory's authority This Page 3 forms an integral part of credit number December 2009 9-21 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS (BANK LETTERHEAD) SPECIAL ACCOUNT ASSIGNMENT FOR CONSTRUCTION SURETY For security purposes only, ("DEVELOPER") has deposited funds in a special account for the purpose of surety for the full and faithful performance by the DEVELOPER of the construction of certain street traffic improvements, monuments and drainage facilities for ("PROJECT") specified in the accepted approved civil plans for said PROJECT on file in the Office of the Spokane Valley Development Services Senior Engineer (City Engineer). Surety is for the following(check one): • Performance surety for public improvements • Performance surety for private improvements • Warranty surety for public improvements The DEVELOPER hereby designates SPOKANE VALLEY, a code City of the State of Washington, as beneficiary of the following: Special Account Number in the face amount of $XXX and held in and by Bank Name Bank of Branch(the"BANK") Funds deposited in this account may be released to the DEVELOPER or any other party only with the prior written consent and agreement of the City Engineer. The undersigned DEVELOPER hereby authorizes the BANK to pay over to SPOKANE VALLEY all, or a sufficient portion of the monies on deposit in the special account referenced hereinabove, upon (1) written documentation being received from the City Engineer indicating that the purposes for which the special account was assigned have not been fully and faithfully performed as required; and (2) a statement from the City Engineer of that amount of money which the CITY deems necessary to complete such obligation. Upon receipt of such written documentation, the DEVELOPER hereby authorizes the BANK to release to Spokane Valley that amount of money requested, up to the maximum amount in the special account. Said SPECIAL ACCOUNT ASSIGNMENT FOR CONSTRUCTION SURETY PURPOSES is made as security for the full and faithful performance by the DEVELOPER to complete the improvements in accordance with the accepted plans. During the construction period, Spokane Valley may request payment from the BANK for the purposes of completion of improvements, by providing documentation to the BANK. Spokane Valley's documentation December 2009 9-22 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS shall indicate that the construction of the improvements has not been performed in accordance with the accepted plans for the PROJECT and therefore the purposes of said SPECIAL ACCOUNT ASSIGNMENT have not been fully and faithfully performed as required. The City Engineer's documentation shall also include a statement of the amount of money that Spokane Valley deems necessary to complete such obligation. Upon the BANK'S receipt of such written documentation, the DEVELOPER hereby authorizes the BANK to release to SPOKANE VALLEY that amount of money requested, up to the maximum amount in the special account. A copy of all such documentation and correspondence with the BANK shall be provided by the City Engineer to the DEVELOPER at the address noted below. DATED this day of , 20_ BANK: ADDRESS: CITY, STATE, ZIP: PHONE: BANK REPRESENTATIVE: NAME: TITLE: State of Washington ) )ss County of Spokane I certify that I know or have satisfactory evidence that (name of person) is the person who appeared before me, and said person acknowledged that(he/she) signed this instrument, on oath stated that(he/she) was authorized to execute the instrument and acknowledged it as the (type of authority. e.g., officer, trustee, etc.)of(name of party on behalf of whom instrument was executed) to be the free and voluntary act of such party for the uses and purposes mentioned in the instrument. Dated Notary Public in and for the State of Washington. My Appointment Expires: DATED this day of , 20 . December 2009 9-23 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS DEVELOPER ADDRESS: CITY, STATE, ZIP: PHONE: State of Washington ) )ss County of Spokane I certify that I know or have satisfactory evidence that (name of person) is the person who appeared before me, and said person acknowledged that (he/she) signed this instrument, on oath stated that(he/she) was authorized to execute the instrument and acknowledged it as the (type of authority, e.g., officer, trustee, etc.) of(name of party on behalf of whom instrument was executed) to be the free and voluntary act of such party for the uses and purposes mentioned in the instrument. Dated Notary Public in and for the State of Washington. My Appointment Expires: k`dfavlgncamt 1199 December 2009 9-24 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9D - EROSION AND SEDIMENT CONTROL LOG The following items are to be included in the daily logs and inspection reports to assure conformance: • Date of Inspection. • When, where and how the BMPs were installed, removed or modified. • Repairs needed or made. • Observations of BMP effectiveness and proper placement. • Recommendations for improving performance of BMPs. • Identify the points where stormwater runoff potentially leaves the site, is collected in a surface water conveyance system, (i.e., road ditch, storm sewer), and enters receiving waters of the state. • If water sheet flows from the site, identify the point at which it becomes concentrated in a collection system. • Inspect for SWPPP requirements including BMPs as required to ensure adequacy. December 2009 9-25 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK • December 2009 9-26 Chapter 9-Inspection&Certification CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 10 — MAINTENANCE n � 4. tea,. 1 - `idJ t • - 09/14/2005:, • Chapter Organization 10.1 Inroduction 1 10.2 Maintenance Responsibility 1 10.2.1 Public Streets 1 10.2.2 Private Streets and Driveways 1 10.3 Required Documents 2 10.3.1 Homeowners' and Property Owners' Associations 2 10.3.2 Operation and Maintenance Manual 2 10.3.3 Financial Plan 3 10.3.4 Conversion from Private to Public Street 4 December 2009 Chapter 10—Maintenance 10-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK December 2009 Chapter 10—Maintenance 10-ii CITY OF SPOKANE VALLEY STREET STANDARDS 10.1 INTRODUCTION This chapter establishes the parties responsible to maintain the public and private infrastructure created with development. In addition, it provides a list of documents required to be submitted during project review. 10.2 MAINTENANCE RESPONSIBILITY 10.2.1 PUBLIC STREETS Upon releasing the warranty surety and acceptance of the public infrastructure, the City maintains all public streets (curb, gutter, and pavement) and public stormwater drainage structures (drywells, inlets and pipes) located within the public right-of-way and within border easements that serve public street runoff. The City does not maintain sidewalks or landscaping of swales and grass strips, even if located within the public right-of-way or border easements. Property owners are responsible for the maintenance of these features. Swale maintenance means preservation of the original area, volume, configuration and function of the stormwater facility as described in the plans. Swale maintenance also includes mowing, irrigating, and replacing when necessary the lawn turf within the swales. The property owners are also responsible for maintaining sidewalks free of obstructions and debris. 10.2.2 PRIVATE STREETS AND DRIVEWAYS The City does not maintain any of the infrastructures located on private streets or private driveways. Private streets and driveways and related facilities shall be contained within a permanently established tract or easement providing legal access to each lot served. The Applicant shall provide arrangements for the perpetual maintenance of the private streets, private driveways and all elements of the stormwater system (including swales within the right-of-way and border easements), and any other related facilities. The City does not furnish, install, or maintain signs for private streets including stop signs or street name signs for private streets intersecting public streets or "No Parking" signs. The owner may install their own signs in accordance with MUTCD, but must have approval from the Senior Traffic Engineer when installing signs at intersections with public streets. Access shall be granted to the City to provide emergency maintenance of private facilities. The cost of emergency maintenance shall be the responsibility of the property owners or the Homeowners' Association in charge of maintenance. December 2009 Chapter 10-Maintenance 10-1 CITY OF SPOKANE VALLEY STREET STANDARDS 10.3 REQUIRED DOCUMENTS The following maintenance-related items shall be submitted for all projects with private streets and/or common areas: • A copy of the conditions, covenants and restrictions (CC&Rs) for the homeowners' association (HOA) or property owners' association (POA) in charge of operating and maintaining all elements of the private street system (see Section 10.3.1); • An operations and maintenance (O&M) manual (see Section 10.3.2); • A financial plan outlining the funding mechanism for the operation, maintenance, repair, and replacement of the private street system, related facilities and/or common areas (see Section 10.3.3); • Street maintenance agreements, as applicable; • Reciprocal use agreements, as applicable; and, • Drainage easements, as applicable. Refer to the Spokane Regional Stormwater Manual for maintenance requirements for stormwater facilities. 10.3.1 HOMEOWNERS' AND PROPERTY OWNERS' ASSOCIATIONS An HOA shall be formed to maintain the private streets, signs, entrance gates, other related facilities and/or common areas. For commercial/industrial and multi-family residential developments with shared access and multiple owners, a POA or similar entity shall be formed, or a reciprocal-use agreement executed. If the HOA or POA has CC&Rs, a draft copy of the CC&Rs for the HOA or POA shall be submitted with the civil and drainage plans. The CC&Rs shall summarize the maintenance and fiscal responsibilities of the HOA or POA, refer to the O&M Manual, and include a copy of the sinking fund calculations and Financial Plan. Annual HOA or POA dues shall provide funding for the annual operation and maintenance of private streets, private driveways, related facilities, and common areas. The sinking fund calculations shall also include costs for the maintenance of the stormwater system and all facilities associated with the stormwater system (Refer to Chapter 11 of the Spokane Regional Stormwater Manual). Homeowners' associations and property owners' associations are to be non-profit organizations accepted by the Washington Secretary of State. A standard business license is not acceptable for this purpose. 10.3.2 OPERATION AND MAINTENANCE MANUAL All projects with private streets and/or common areas used for stormwater management shall have an O&M Manual. Projects with engineered driveways may December 2009 Chapter 10-Maintenance 10-2 CITY OF SPOKANE VALLEY STREET STANDARDS also be required to submit an O&M Manual. The O&M Manual must include, at a minimum: • Description of the entity responsible for the perpetual maintenance, including legal means of successorship; • Description of street maintenance tasks to be performed and their frequency. Street maintenance tasks shall include at a minimum street sweeping, snow plowing, signage repair, crack sealing, pot hole repair, overlay, pavement replacement, etc.; • Description of the stormwater maintenance tasks to be performed and their frequency. Tasks shall include, at a minimum, swale maintenance and removing sediment from drywells, catchbasins, and pipe system. Swale maintenance means preservation of the original area, volume, configuration and function of the stormwater facility as described in the plans. Swale maintenance also includes mowing, irrigating, and replacing when necessary the lawn turf within the swales; • Description of emergency maintenance tasks to be performed and their frequency, such as gate operation, No Parking signs, access to fire hydrants, fire lanes; • Description of the source control best management practices (BMPs) such as street sweeping (refer to Chapter 10 of the Spokane Regional Stormwater Manual); • A list of the expected design life and replacement schedule of each component of the private street and/or stormwater management system; • A general site plan (drawn to scale) showing the overall layout of the site; and, • Contact information for the design engineer. 10.3.3 FINANCIAL PLAN To provide guidance regarding financial planning for maintenance and replacement costs, a Financial Plan is required. The Financial Plan shall include the following items: • A list of all private streets and related facilities, common areas, and/or stormwater management facilities, expected maintenance activities and associated costs; • Sinking fund calculations that take into consideration probable inflation over the life of the infrastructure and estimates for the funds needed to be set aside annually; and, • A mechanism for initiating and sustaining the sinking fund account demonstrating that perpetual maintenance will be sustained. December 2009 Chapter 10-Maintenance 10-3 CITY OF SPOKANE VALLEY STREET STANDARDS 10.3.4 CONVERSION FROM PRIVATE TO PUBLIC STREET The Applicant shall submit written authorization from all property owners, any and all available construction drawings of the subject street, along with an engineer- stamped analysis of the pavement and subgrade as determined from test sites separated no greater than 100 feet apart, or as required by the City. Digital photos at every 50 feet, or as the City requires, shall be submitted with the application. The City shall review the information, visually check the street and determine requirements to bring the street up to current City standards. A letter of requirements shall be issued by the City. The Applicant(s) shall meet the requirements before the street is accepted as a public right-of-way. The Applicant shall prepare a legal description of the street and execute a deed of trust, transferring the property to the City once the physical deficiencies have been corrected and accepted. December 2009 Chapter 10-Maintenance 10-4 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 11 - STANDARD PLANS �' . - �� t , l<st' P Va N{;r 1 N ztkti .y 1 l I �t a r �.. ` � 1 i %<���11 1 C\- , "c \ s � fit' II i1 i M1a1 n r i' ' + 4; s. i ' 7 -- j i u I G I p — rat .'r tr a a• `s. Standard Plans Last Updated Drafting D-100 Drafting Standards—General Survey, Sewer& Line Weights 9/1/09 D-101 Drafting Standards—General Water, Gas, Power, Tele & TV 9/1/09 D-102 Drafting Standards—General Power, Tele, TV & Special Features 9/1/09 D-103 Drafting Standards—Pavement Markings 9/1/09 D-104 Drafting Standards—Line Types and Text 9/1/09 D-105 Drafting Standards—Line Types and Text 9/1/09 Roads/Streets R-102 Curbing 9/1/09 R-103 Sidewalk 9/1/09 R-105 Pedestrian Ramps - Typical 9/1/09 R-106 Pedestrian Ramps - Midblock and Adjacent Sidewalk 9/1/09 R-110 Driveway Approach Separated Sidewalk 9/1/09 R-111 Driveway Approach Swale Inlet 9/1/09 R-112 Driveway Approach Adjacent Sidewalk 9/1/09 R-113 Driveway Approach High Volume 9/1/09 R-114 Driveway Approach Asphalt 9/24/09 R-115 Driveway Approach for Private Streets and Driveways 9/1/09 R-117 Driveways - General Requirements 9/1/09 R-119 Typical Street Section—Half Street 9/1/09 R-120 Typical Street Section Local Residential 9/1/09 R-121 Typical Street Section Local Commercial 9/1/09 December 2009 Chapter 11 —Standard Plans CITY OF SPOKANE VALLEY STREET STANDARDS R-122 Typical Street Section Collector 9/24/09 R-125 Alley Section 9/1/09 R-127 Longitudinal Step Wedge Cold Joint 9/24/09 R-130 Cul-de-Sac—Public Street 9/1/09 R-131 Public Street Turnaround - Future Intersection 9/1/09 R-132 Public Street Turnaround- Future Connection 9/1/09 R-133 Private Street and Driveway Turnarounds 9/1/09 R-140 Street Signs 9/1/09 R-142 Type III Barricade 9/1/09 R-145 Survey Monuments 9/1/09 R-150 Gated Access Requirements 9/1/09 Stormwater S-101 Precast Drywells Placed in Swale 9/1/09 S-102 Precast Drywells Placed in Asphalt 9/1/09 S-103 Drywell Details 9/1/09 S-104 Drywell Frame and Grates 9/1/09 S-105 Precast Drywells & Inlet Details 9/1/09 S-110 Curb Inlet Type 1 9/1/09 S-111 Curb Inlet Type 2 9/1/09 S-112 Catch Basin Type 1 9/1/09 S-113 Concrete Inlet Type 1 9/1/09 S-114 Concrete Inlet Type 2 9/1/09 S-115 Combination Inlet 9/1/09 S-117 Catch Basin & Inlet Installation 9/1/09 S-121 Metal Grate Type 1 (Bypass) 9/1/09 S-122 Metal Grate Type 3 (Low Point) 9/1/09 S-130 Roadside Swales 9/1/09 S-140 Oil Water Separator 9/1/09 Traffic T-101 Traffic Circle 9/1/09 Utilities U-100 Utility Location Detail 9/1/09 U-101 Aboveground Utility Placement 9/1/09 U-102 Fire Department Hydrant Requirements 9/1/09 December 2009 Chapter 11 —Standard Plans SURVEY SYMBOL COSV PLOTTING & PHOTO DRAWING NOTO 54AEY COSRS ARE HEST O COSY PRO101PE ORAmN a PLOWING Pin WY 9 arpAS Aia MUST N COW PROTOTYPE CRAI910&FIDT4G RFS CO WT S IDJSIB BY AD.6USIB BY IM AS l40 AS T1€SSGR!SHAM OGORYAROI 61610. REM SE LL¢R AS l4G I.S L001cWi!91ME 0 A1ICN S HOIl P<•m 9F N•4R U9E NUMBER TIRE FW CO/PARABLE PRESET COLOR SELECTORS RR COJPIRAIDE PRESET 0201 415435 SYMBOL DESCRIPTION (ABBR) REF.# COLOR BLOCK LAYER TM OW OF Wawa VAIUEY NAS CAa6®2°m PIES THAT 4010 IE USED TO AOPEE PREFER • EXIST. PROP. EI6T/PM19 96T/RCP a1n9i�a BOOM�u Caw AR?with TM€D BBYY 02lr�kmc 01? SEa a VALLEY A ♦ ANGLE PONT OP) 11/2 20/12 SAP/SAPP S'KROr333-SW RAMC WORKS + # M101 MAN( (BV) 11/2 110/11 5910911P ST-CTRL-393-SW 009I HAS MEMO LERSI ST='STANDARD'CROOKS'FOR sra0aS&IBIETWE WORN 01 ME PR010 CRAVING a MMnNG STAtOAMM DOCUMENT.USERS SHOED REFRAIN PROS CHANCING THESE o • BLOCK COMER (BC) np 210/12 mC/ma sv-rn¢-3333rn manes P4 PIPE (P) 11/2 210/12 9PJ0PP `-"'$-s" SANITARY/STORM SEWER SYMBOLS • • UOaxENT(SLOLFADD(M4) 11/2 210/12 4014/5IGW sV-rne-539-911 • • 00 000 @I CASE) GAO 11/2 210/11 MIC/SMICP N-c113-33.33-rn NOTE:SANITARY/MN SEYEM COLDS ME 40 AS a CITY PROTOIWE ORAWNO a PLOTTING 91ES aEM(S)MAY BE ADORED BY USER AS WING AS IMCT 0.T a,MME MW.IAMN IS HELD. REA•E ® e Sal B 4G (58) 11/2 210/12 54/a8P SV-a 1n]-rM REARMS NINOE TABLE P4 o(ASBR)E PRESET COLOR SELECTIONS. Aa+EY Pair (SE) DMA nD/ru SSE w,.Ony.-psr sEl SYMBOL DESCRIPTION (ABBR) REF.# COLOR BLOCK LAYER § EXIST. PROP. DST/PROP DST/FRCP A a9 POW. (MS) 11/M 2G/NA a5 BV-C1RL-D5T-SYM o SM.SEVER (M) 11/1 . ea/43 ND/59ATP SA-SICI -rn VP PAT a 012W GE) 11/NA 20/NA WPC SWCn1-D3T-51M .• CLEAN OUT Q PANT OF TANGENT (PT) 11/NA 210/NA SVlr 5V-CTRL-EKT-SW O • sm.SEVER MANIOE(5904) 11/2 00/42 9/4/5900 SA-9133-300-SM ✓ POINT OP PITFNSE0114 (P4) 11MA nGMA APl sv-cm-EPSr-sM 0 • •'� (03) R/2 n/M 210/sc� m-sma-00500 iuni IAYAO� I AOVEIC NAB. OAAM) 11/NA 210/NA SWAG 1V-Cf13-EYST-SN (CITY UPR 1 00/50) a 601 NAL (6W) 11/NA 210/NA SSW BV-0213-DIET-SERA I= 1 3411 (CIA.V0 11/2 01/01 SC/00W W12UN-3313S* x x IN aWXtIE 11/NA 20/NA SOC OV-CTRL-DST-SW Sa'd MAIN (50141) 11/2 61/n2 WMH/S MP m-S1O2�1-SYJ RKE R611SNE x 11/NA 210/NA MIFF SV-G116-DST-SIW ® ® MNHMaE m DRABS,AG/XA9RR 11/11* 210/NA SOW SF-CTRL-DST-SW ® p STOW MAIN CRWEIMO1tO 11/2 11/12 MOW/SODA? 5C-SCR-3333-SW • Hue a ua (NT) n/NA 210/NA S%91W sv-rnU-061-911 ® • •11400-VMFD GRATgw) 11/NA 9/02 musv/ma0 M-STM-933-rn • MBAR OW) 11filA 210/NA RB SV-C13-D6T-"T14 • DEBAR W/CAP a5) 11/"/. 240/NA LS STK1N.-£6T-Si" ® • (OW TPE ( (0) 11/NA 01/03 mn/�P SO -3ISiS11 O CID MBAR a CAP GE) 11/"A 210/111 Ant° sv c1a-FrsT-rn ® • •TYPE 2 CS-nw (m) 11/NA 00/22 21Z/S:C 93-9M-33ID--rn m PR NIL (FK) "/NA 90/NA Plc SV-CALL-E%Sf-SM ® �an (CO 11/4a MAYA s3 SD-STIR-99-SW o RW(NAL (RN) MAYA 210/NA RN SF{IRL-DCFrn (SNUFF C• RAILROAD SPEE (RS) 11/NA 20/11A RRS 54-c -c T-SNJ ® • •TIRE 2 0-040 (C3) 11/NA elm 2T2C) P 91-SRTt-3333-911 ® HN/R® (PM) 11/RA 210/NA SWAM SV-C1RL-DST-51(11 S • •a e 9 GATE (a) 11/11A 61/02 ROTOR/MOM m-STM-3050-5/11 Be BOAT MIS (9S) TI/NA 20/14. 99WK SV-CIRL-E6T-S01 N aoAERSWP TIE (C1) 11/NA 210/NA SOT SF-01111-EYST-SYM •• OMB DM GI= (C4) 11/NA a/"A. 991 915TCR-3333-9M ® • •MOOT-CRATE (CO 11/14. 61/02 22x50/2108? 93-SNi-3351-rn SECTION DATA: m - � .� SEPTIC rule (9) UMA DMA SEPT SA-sra-DST-SIN ® SErn4 CENTER 3 smr sv-MOT-3103-rn yy_ W.- wrAOE ARROW 21/2 61A3 DRAIN-ARROW 91-421lXST-911 14 3 14 1 3 1101014103 SA/SD ftOS RA/E NA/45-a2 ARM 91-01442 -rn Ana owm 2/2 SSC/ssa SVSET-mss-sW 73i2:4 13124 a DST/PROP-ass al STRUCLIRES TO ISE THIS SYM0101200 SINC1U MALL BE CALLED�01 ACTU 9*:1(5). '13 13 WASTER CORNER 2/2 SaMaa' ST-D9,T-S33.3-9U J oo .{•�_ SIMEENs CAMER 1/3 SSC/SSXCP sv-1650-Su-SW „4y C E NT rl 1 4117 3 1 Ml J m9N°caaaR 2/2 mc/ 3 3 5W 4`)0@ W A Sy/h O (aYC ►me MEANDER ma6R (MC) "/1 9IC/9IW SY-n2A-im-SYM 62, [ . y *we •WC WTNDS COWER (DC) 1/2 51.0/589 Sv-S 0T 333-SM Z_ (45133.123) TAX Lot/ASS4a 3 SRN ,V-250-Tan-s 4 / tr Nun USE 9ST/RNS/RAIIG-22A d J SP .0 •c�lt>i V use aa/IOW-am O 4, 36449 q % / " `PCT STHS% tiff /Z/v6 Litt TmRRGP/FOLIVI1E0-100 SS /ORAL'. � 25 RUNT CF WAY PUN 3 SOW sV-RW+0-PROP-001 EXPIRES 91/4 1/z c10 REFERENCE/GENERAL NOTATION SYMBOLS DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED SYMBOL DESCRIPTION (ABER) LINE BLOCK LAYER PoflPUBUCATION /z�oq WIDTH Darne CNL B`3ME 1w W 2 W. CH-CALL-PROP-SW ����I�4 A.,,,, M4°Td DRAWINGS) Spokane MEN-PRO PRCECT ARROW 2 REARM 4-SCa-?RW-S111 2 AM 4-332/-33 -rn a 00 1514.72114 PENT 2 ITP 04-2223-3333-S114 4000 Y a lleyS USE FFARNE NAT-222A "}IQ■■E' IS BONG WAFN90SD • FMC*PI OF -• , PE PC IT a a GENERAL, SURVEY, SEWER, STMEIGIM wRM3 USE u; 12za & LINEWEIGHTS 1@ 9NT-001 -324 EL MO 9O a00 mAT Sla£(GOR Faa0S6 LAYER ST-NRA-334-SW LAYER ST-CAW-33.o-rn SW M P p - STANDARD PLAN NO. D-100 WATER SYMBOLS REFERENCE NUMBER TABLE NOM WRIER=OAS ARE PRESET IN 0654 PROTOttPE DRAWING It PLOT=ALES WT AD1sm BY AS�AS 1De°°R 5 OWE S JATON O HELD. M'¢ME (INCLUDES LINE WIDTHS, COLORS & SHADE R� NUMBER TABLE RA 01@MAOE M@i 6Ytli 4l£LMAS SYMBOL DESCRIPTION (ABBR) REF./. COLOR BLOCK LAYER. REFERENCE NUMBER 101E WON Dun) Ins 5 SHADE EXIST. PROP. D$T/Fxw Mr/PROP I 1 ILES 11 S 0.13 05 I 7 MAP 7 vw COLLO 11/I 150/5 Hw WA-4717-31223-5111 2 0.35 2.a 11.12.a B 0% #O L *t 01210' (R) 11A 150/5 WCOW/WCNPP VAi1R-E4rn 3 0.5 7.8 OS •CP .w GUARD Past (w) 11/1 150/5 WCP/W'9F WA-MT-3213-SW • 0.) _ 4,10 OM D•m PRO ROMER (rE13) 1155 150n WmfwP WA-MT-S533-511 0 0.65 14 0s • TB -TB mai BLOW (18) ail 155/5 WRB/NIIP WA-Fm-3233-SN I 5 0.15 II OR 5-•F. OSP.. SPRINKLER HEW (9) 11/1 150/5 p9R/52PRP WA-fRT-3333rSW I r 0.15 110 10% I 53741 OIM WATER YEIFR (NM) 11/1 150/5 FAS.T/W16IP WA-.051-3133-SIW I 8 015 150 301 I FRE 1MRANIS IRA 150/5 I B 0.13 140 40% I NH 2-50IDE (F11) nA 150/5 WAD'{ 5112P WA-EXIB-3351511 10 0.15 150 605 4m -1b-F11 3-NOULE (FM) Il/I 150/5 W1°/ML3P WA-FRID-3333' m 30.SI.61.50.111. SOL lNIT$ 11A 150/5 11 0.13 113.1 0.210,240.241 (FL I FL FLANGE/Bat Fl.TWIRL R) IIA 150/5 0i1/WFEP WA-FTIT-3333711 COLORS NOM£051110 NILE=TO BE PLOTTED AT SOS SHADE.OYIPE RAW 5E01 ASSCIE0 TO QY DN YEOIANCAL E14.3 11/1 153/5 SWAM" WA-AR 11451 BET O]FUN WIN MEW STANDAI51 LOCATING CCLCRS.SNE uOHRGTgC WERE WALE 10 ALLOW FOR SETNR OSIHCICN 3EI1E01 ELOONTS(E SANITARY SERER FL SUM WATER).BELOW (W1/IS COMB w -CN/H® ILA 150/5 131123/3/FLOP WA-Fm-3333-SN ARE CRY 6 SKEANE VALLEY DRAMS SAIOAIO5 SCREEN COLORS.ROSE MEM=APE PREDEFINED IN THE I I,O IDO 155SAD (LAO) 1111 150/5 WT1/NBP WA-RR-3333 SPOKANE STANDARD FROTOTIPE 1 R1D11540 C6 5T PROPERLY MIEN=ED W W THE CITY OF IR �q VALVES 11/I 150/5 �Y'�, T, All RFIdT (All) 1115 150/5 WMV/NARP WA-VALV-2133-SW3 1B0 IB0 BLOW-OW (30) 11A 155/5 NBOVMNDVP WA-VALV-333-S111 1VSF SU i SADLY (ff) IRA 150/5 WSFVAmw WA-VALV-333'3530 p:p< NA( CHECK (00 /AOOiP WA-VALV-3333-su UTILITY COLORS: COSY DRAINING STANDARDS H GATE/GENERAL (R 11/1 150/3 W0V/W6w WA-VAW-3333-S* UnulY MST CUSS •PROP.CCU= WV MPY PUG VALVE (f1) 11/1 151/5 WA/AI•SP WA-VALV-1117-5I11 GAS.S 1V�CA°E 30 13 51 Ii A0 PT01.FL 1 MA. 11A 150/5 WAfU/SMIE WA-Fm-333-sIM STAN MANAGE 51 81 SANITARY EA14R 115 u �S SURFACE FEATURES 115 USER DEFINE WADER 150 5 -El 00 DEGREE OEM.FL NA 150/5 WaDF/SWE WA-P117-3513-SYM SURVEY 210 12 r `� 'C ' 45 DOME BE10.FL 1155 155/5 WARM WA-FF°-3355-51L POWER TRAIFlO 240 6 1'-I 113 OMNI BEND.FL NA ISO/S R P/SIJIE WA-FIR-3133.51 •PROPOSED MGR NOTE A5)40 COUR IS TO AD M SCREEN MEMO,ACN.LL .{ ri 11.25 COMM BEND.FL. 11/1 150/5 W1H/YN- WA-RR-3555-51 WOW El MOTH) PROPOSED DOE CAN 550.95107 TO USERS OF3DE0 1hC 1,'1{- 00 DEGREE 850.MA 11/I 150/5 119011/54.14 WA-F117-333Yrn IRE PROPOSED It SANITARY:USER MAY USE FINE WM 1.0 ION OR F REWARD, "3 C 'S .45 DECREE BOO.RA ILA 150/5 W45l/S/AC 55-FlTE-5335-5114 DIC3EA£TO 1.5(OR GREATER)10 ALLOW FN PPWOSD LIDS TO DE SEEN. 225 LOME MHO.WL 11/1 150n 1291/541 WAiRF334SAS rC 1125 DEWES EDO.1a 11/1 150/5 3011/5NIE WA-RR-3333-511 I-H MICA.B0.Ft. NA 150/8 W O'/SA14E 113-MT-3333-rn 315F ]+C VERTICAL BON MA 11/I 150/5 WON/SAME WA-RTI-33213-rn REDUCERS: H noun a. NA 150/5 SWARM WA-FDM11nl-5511 • .RC x R6U9L MA 11A 155)5 WOIAVOP WA-ETF3333-rn 34 8510R ua x FT. 11A 150/5 WSem em. WA-Fm-33n-sw D• REDUCER MA t P.E. NA 1`50/5 1W103/WSPP WA-FITT-333-50 (C E N r CC R{ REDUCER.P.E.1 N.1/cL.Y..L 11/I 150/5 wP1AWWw WA-MT-3333-SW A�l Oi 151 AS: O Ds ILK ITK TAPPWO TEE$VALVE FL x MA 11/1 150/5 WFa/SIlNP WA-VALV-3355 Z4, FO,. Z}��o 4 144I ME.FL 11/1 150/5 WP/SALCE WA-MT-3333-SW N. CO dr,'• =o ,y q Y'C D+C TM MA 11/1 15115 WIN/541E WA-MT-1333-SW . -) }2{ DS{ ME.I43 8 FL 11/1 150/5 WMF/SAYE WA-1117-33.13-5114 / V .d": ... VALVES YT>``\ !C�y YC BJNEIULY VALIF.FL W LL.L nA 1sy5 313141/12341.5 WA'VALV 3333-rn Q R 36449 .p V DC BJI1ERFLY VALVE.MA 11/1 150/3 W3w/W31w WA-vALV-554-5211 41 4.0`'Cf S TE4'g(^^ly M IC GATE VALVE FL A RA 11/1 150/3 SOF11/44M1P WA-V/LV-=55 S l 4S) `V /2-JOY (b DC LATE VALVE.MA 1155 150/5 DOWAN'P WA-VALV-.ua+'N !oNAL E (E • •WATER MANHOLE 11/1 15015 WAL1/1459 WA-S1OE-11450 H WA VA A ,Sa .//6P A- LV-4u EXPIRES 9/19/z 0/u 311 CURB BOX NA 150/5 500/W.w WA-VALV-1333351 f3 H IOW.VALVE 005 1,55 150/3 WCVACVF WA-VALV-5351-511.1 DEVELOPMENT SERVICES S3IIOR ENGINEER NOM ARS BOX 11/4L 10550 APO WA-51550523-SL 1 1• •METES 1.1040E 11/1 150/5 WRT/NND# WA-535552-31451 APPROVED FOR PUBLICATION /2/0y -6- +'SN 11113R/IT(TWO SHAMS) 11/I 150/5 WN/W3143P WA-MD-3333-SW Q • •0DW-AF 1N 11/1 150/5 WAw/WAN&P WA-VCR-3333-SW . BRHINIFR READ 11/NA 150/NA 910 WA-FUR-193-51 �(/�� .SPaD]FR 314111.BEY „ALA 150/055 MEW NA_STOi-119-5(1 SpORane ' USE ETSI/PRW-S34J • 550%.N.WRAE STRC IIR NAZIS SC WATER 155300E 1U ACTUAL PLA 10 E$1105, Valley •NUM A9lHD NOM ALL SR O SE WAlES AR 1 RUC PLAN B1F USE GENERAL, WATER, GAS, POWER, TELE, & TV STANDARD PLAN NO. D-101 . GAS/POWER/TEL./CABLE/TV SYMBOLS NOM CAS/POWER•MEW=COLORS NE PRIMO 14 CAN PROIOTYAE DRAV40 k PUTTING FEE& ME NWEFA Tai PSI COOARAE E PRESET CO.W=IFgU01A11O1 6 NOEL REAM . SYMBOL DESCRIPTOR (ABER) REF4 COLOR BLOCK LAYER EXIST. PROP. E36T/PROP E16T/PNO' Qa OAS wvmaE (aE) 11/2 51/2 OWN 4410a-3130-5111 a is OAS IRIEIR (0!) 11/2 51N DIET/aa1P 05-WIR-3133'm 01 a OAS V*LW (c.) 11/2 51/2 0V/OW 1.31-WLV-103-5N _2 OAS WAK07/SG1 (WS) 11/2 51/2 GVS '4'YSa1-01BSW p POWER uNNNLT pow MIN) 1133 240/1 P11W P0-5T0-3323-rn ® ® P0W3t VAULT (POW V) 11/I 240A PV/PWP PO-S1ai-033310 o POEM wE (PP) 11/1 240/1 UPAO PO-STCR-103-10 ' o MIS P0E (PP) HA 240/1 UP/MP PD-S7S-103-10 F WY SERE 11/1 240/1 UPAAPAP P0-sro0 tit'm �A DEC uumRya MUSE) 11/1 240/1 PCUS Po-S CR- -m ryt, LW/INANE POLE (WP) NA 240/1 TSIA PO-SlW-3100-SW 4 P0WO 11513 (PVL) 11/1 240/1 W4142 PO-sRA--m # MONO tm 15tH (P101) 11A 240/1 WISH PO-3IOR-3333-m O O PAO MOONED 11 (P IRAN) 11/1 240A P1ILMAARMF PO-51M-3333-5N ® ® %m mat ORAN!300 nA 240/1 PMIMMW PO-ST0R T-sw O 0 WAN E (m.NM 11/1 OAS TE3MN/IWARP 11-STCR-333-5111 I .T TOEWI HE (TEL us) 1/A 20/13 1WSAW9 1L-31x-3333-Sfu ZO 10 a( GO 16) 133 30/13 PausAwwP I-sRR-351-rn 0 W TELEPHONE rant (DEL R) 1133 30/13 19R/DAP a-5101-3333-5-01 • QT TELEPHONE VAULT (DEL V) 11/1 30/13 WI 11.-ST01-513-10 • © CMOBCA11W W/VALLr HA 30/13 ONV/DitTP IL-OCR-303-SW Ea 0 DFIEPNa2 WWI 1133 31/13 TIB/0WP TL-s1IX-3333-SW • -0- TELEPHONE PCE 11/1 31/13 1PAPP 1L-STs-3313-511 O CABLE VAULT/UN (MI) lift 30/13 GKT 71r51_R-3313310 0 CABLE Wm (aER) 11A 30/13 1113 DL-sDw-a3ss-m Cal CABLE O¢( (COX) 11/1 30/13 OM IL-sIm-5133-m o CADGE PUE COMM 11A 30/13 UP TL-31148-sill-Sfu A CAME WR12R/501(5180 11/1 31/13 COLS 11-5101-33A-SN -0- CASIEAV POLE 11ft 30/13 LP/MP 1L-3100-35110-m 1@ OaTftPT 5 3 J SURFACE FEATURES/LANDSCAPING NOTE s.1FALE FEATURES COLORS ASS WiL£T II COSY PRODODIPE ORARRO&WODTNO Fla C0.0(5) WY BE/1036148 BY 183 AS 1L10 AS UNMOOR"!k SHIM OFSWATW 61830. REAS SEE REFERENCE Nu1BPR TAME FON SAPAZW E pa,00a mS11a8 SYMBOL DESCRIPTOR (ABBR) REF.# COLOR BLOCK LAYER ty C E N y, EXIST. PROP. 031/PRO °i31/ROP Q` RAg kp o 7R BUS STOP 11N SOND SF11S/98'P s-s10E-3333-m * 4,1, 4.. Ysi ILIMAN ENT 11/2 50N0 SPO/SEP SF-F00T-31410 �v („Q t o * ' YI&W% 11/2 S0NO SFO/FUOP S-STCt-3313 /'I ' , �' 9 e RP MP 118 3ONO SMA/5£'P M-17041-3323-SW ' 0�i, COM Ca ROCKERY 11/2 50N0 STR/3RP SF-R00C- 3-rn / V Y /'` �� . arn ABANDON ABM 11/2 wN0 00x1 SF-5101-533110 i ? n;V �G- 0 14/13 PIMP n/i 30N0 1,13,1 W-31315-3731-m G O 4, 36449 9 li x( TARO MO 11/2 50/(10 SFL Po-sTCR-3 -m '�yC1���IBT S4$ �1� ) c. 41 PMOIOO MOT 11/2 50/JO UWE PO -3513-1W SIO P.r�j %\ �2/C/ 4 FLOW UCT 11/2 5ON0 W012 PO-STR-411-m ION 411% r 1 PARKING NETER. 11/2 SONG 3PU/3PIP SF-5101-3333-m Ill 1IFEVR C 11/2 50/U0 Wa4 W 0103ss1-m EXPIRES 7/a9/LOro ly 203 OILS 0451 11/2 50/U0 CID SP-CURB-3333-m el ® ORNEWAY 11/2 SO/LID MOOT SEE D SF-awT/-3313-10 DEVELOPMENT SERVICES SENIOR ENGINEER YtEF1 MEP 11n 50/101 %61[P SF-3131,-1119--3131 APPROVED FOR PUBLICATION /Z/p .E@Y BA R 11/2 50/U0 ERI SF-J00-330-3114 � . •P+5 2 f CATE 11/2 50/U0 COME SUE 0 5FrtOlo-3333-5111 I DO WD SE 11/2 50/U0 RN1E SE-WNF3iFm ' 0 IXMOM 11/2 50NO AYL S'-8000-313-5-01 O OO' O) a(WAIN 11N 50N0 MOMNEE CLASS) SE-lp£-3331-m �pOl4a�e aRNAIOMM.IRE nR SOHO 5W SF-WM-3333-m „� 5106 5_KOE_99 N Walley COTO &RUB ROW 11/2 SO/VD 351 S-GTE-99-10 0 BUSH 11/2 SORT S11a1 S-001-3333-m Oc®D BUSH ROW 11/2 50N0 WMI 4-10X-339-0141 IL SWIM 11/2 50N0 5112W SF-1E0E-3333-SW 1 3105 S COO 11/2 SDNO 0•3 SF-WW-3333-5W GAS,POWER, TELE, TV, I—e.i0.1EICS3 DAR.ACE GOON 11/2 SO/UD OD SF-BLOC-3313-SW &SPECIAL FEATURES (00 COMES'SEER 00100) WEE CUSSES.C1.2A4 am SEES-a1D.ulamtua24.maua ' DST/MCP-33D STANDARD PLAN Na GATE S@S■34At10.12.0111 CARMS DOOR SIZES-8$0.12.lL D-102 PAVEMENT MARKINGS Ip1E PAVUOIT YAWSIC DIMS N2 PRIEST N COSV PMIOTOE°RAMO a PLO111NG RUM 01223(1) MAY BE Alms=EY ISA AS S AS IMEV Q4T a SHADE 1610139/1 614Il RASE D E REFER MI WIDER TA9£FM COLPARME PRIMED C1tl1 Os SYMBOL DESCRIPTION REF.@ COLOR BLOCK LAYER EXIIST. PROP. ECST/PROP DST/PROP /T{ 66 HANDICAP 11/2 241/6 Rq/HYR lF-SIRP-3334-SW 4 + D BEE LANE N 11/2 241/6 @/FWEP TF STRI.-a9-rn 0€0 0,0 NON LANE 11/2 241/0 RNOV/ANQ8 IFSHR-9Sr2N 4 v OiivYYvv 11ff nap 1NE 11/2 241/6 WYC/F1OP 1T SIW sell E1pl 1� 1B.Y 11/2 241/0 PYO/PMOP IF-SIR°-SID-S1A Q E .AHEAD 11/2 241/0 PMA/WAP IT SIRP-143-SW OP STIP 51CP 11/2 241/0 PYS/PMW 17-SIPP-13223-5331 OOYC(O MI Swat 11/2 241/0 FMSC/PIRT 3F-MR-3ID-m XRMI a➢CRO SIC 11/ 241/0 PYf1 QMOP TF-STRP-13213 5Y11 pAVFMENT MARKINGS ARROWS /1 SSRNWT ARROW ,,n 241/8 8 PSAMSAP WFSTW-314-rn /) ifil LEE 1U 4 ARROW 11/2 241/8 INLA/P16AP 1F-SI W-334-SY C E N 4 wes 11`01 t'/k0 0 RI1T RIRN ARROW 11/2 241/0 PMRA/WRAP 1F-STPP-3333-SW r� tNCT�A y����, 240 0 ? �V� C i1 -- v c __z T-SRLIGHT 11/2 241/0 PMLRS/P11SP V.ERE-3113 SN �. � ."p . LERT-(IXNT AMP 11/2 241/0 P10R/MIW 1F -3133-SW OA qE, 36449 ib 'EV �srIONAL��G�� /2-AV III 111]]�� wT� 2-WAY LEFT TUN 11/2 241/0 PMTF/PYNP 3FSIW-1313-rn EXPIRES 5'�2V�2 o%0 �/ 0 DEVELOPMENT SERVICES SENIOR ENGINEER �00/I���� APPROVED FOP PUBLICATION /z Al, WLET-SINMIT ARROW 11/2 241/6 FILS/PMIW IF-51RP-3333 Sall 7 ti> WOE 3R ?AA /2 x /8 PMR/YRSP S -333 S A P 4.0 -Valley RAID IIARKFRS C= O CNI1LTE OIAIER 11/2 241/8 RM®/E313P IF-SINE-3133-rn CH o CIIO 1E BARRER 11/2 241/0 w®TANtsP TE-ma-12333SN PAVEMENT MARKINGS TEEM DO 0 0 NANO DEER 11/2 241/b FLOWIN1W 1F-S1W 3333 EN STANDARD PLAN NO. USE EST/PRO2-3E3 D-103 LINETYPES . NOTE NEMES ME NEWT DI COSY PROTOTYPE DRAWL'&PLDTWAO FILM m OK.NAY BE/DAIS= • DT OM AS LD10 AS MEOW'•9VAE OSQOIAtGI IS IF]D. FS/SE SEE REFERENCE NNW LUXE FOR 6•PMMIE PRESET COLOR SEECDENS UNETYPE DESCRIPTION (ABER) REF.$ COLOR UNETYPE LAYER CNANNPLTAntM • ROAD-EDGE CF ERPE(EAT w CNTNUCS 1F-C P✓ -SST-IN • ROAD-EDGE OF DUPE(FRCP) Ut mNnNUOUS T'0 -ma-aN i PANTED LIND/CHMNa_NO UD cONIDNOUS IFCIM-OST-N , PANTO W6/CANNEL(HRW) LO CC UNUOUl T-CIAN-PCP UI SHOULDER(EN) UD CONTINUOUS 1F-DISH SASA-N SNDDND(FRCP) UD KMNUCS I S1IRFACF FFATURES ALLY-MO(CO 19 SAGA OALLY-DGT-UN A1UEY-FEZ PROP) ID =MUCUS 4-ALLY-NtlY-4s. . DI61WO LNE(EX) UD MOO 4-SOG-DST-RN MEMO UNE(MP) LO CONTINUOUS s-15114-PREP-UN ROADWAY OWWI(DO 10 CRN a-C!N-EssI-• ROADWAY CROWN(PROP) ID ON 4-Cf101-FRGA-UN ASPI LLT-EDC:(DO UD SAC 4-A3H-ImA-IN . ASINALT-ENE(FRCP) AD CNINUCLIS 4-ASHI-PRGA-UN GRAN;ART-ALTO(D) UD 0A91 DF- AVS1U-LLV CUNEL/ONT-EDDE ORM) U0 CYRNUCIS 4-CLAY MCP-UN OYICIDEiD2(CO LO DASH SF-C IC-IDA-LN CWCPRE-OCE(POP) ID WRNWS SFiiY6-PRGA-U1 CPD ON) 15 LE.VeFN 4-41O03-33SiN CND(pRCP) to CNINUOS 4-WRd-PICP-Ui DOOMS(00 iS LEANER 4-WAUFF]ST-IN =WALK(PROF) C0 00015015 W-WALLA-P(ViN ' CUTER(CO 15 LEANDER 4-OUR-EnT-IN UHNROHL ROADWAY(DO UD CLAIM=S 4-UDIP-333A-N UTE OT PS) UD 0CII0LW5 4-18R-19A-NI TRAIL(CO ID SOON 4-TR.LL-DSYJN g1(/DITCH DENIFDDE(DL) UD 01701 s-mA- r-UI - tl✓DNpICH CENIER DE Om N) CD 131a s-.222A-PRGA4N RDEREA /SHOMNE 10 001715025 SF-f' -ETST-LN .. FIELD 1NE(CO UD WANI -UI FENCE(CO 1 115 WEN 4-FTIF10S-C-LN FENCE(FRCP) LO MI 4-FNC-FDP-101 .. .. .. T GUARDRNL ODO RD •ECM 4-0.115)-EST-UN 4VAXFAL PRI� UD •PORI 4-COD-WCPiN LA0/P0113 uD LANE s-IAIR-F15T4N - SWNP/ERAND MOULT" UD WON s-VEIL-DST-UN ' IMF "ROM UD •ND 4-10D-DSC1N l(cE N?P t. WALLS (FRIO FED NOTES) 1 115 DOME s-WW.-SSY-UN A` 01 IASg/•r0 DOW"AAA///C� RETANNO WALL(CO 1 115 •EFM 4-WALL, ST-LDI k' •.t. h'�T t,J • ISTANNO WAIL(FROM U0 •PRN 4-vMUL-FNP-W AZT F I O ? naramc TRMm/v000E HONE(DO UD E EL10 W-m0-Em-&N C /% f O 9 DEOC LINE UD KNIDNCS 4-4t(ESSTaD1 �J • / ~ _ DOCK(a) 1D =MUMS SF-OOIX-EIGFUI L T'< MIL BOX PM UD M111UC6 SF - ST-UI /L 6Y %t f� ME/NOT ORADLHE(D) 1D WASH 4-# €-EST-Ul / p� qe 36449 go 1 V� FPF/NM DWUIE(PROP) 1D CNIDDILS SF-PPE-PROP-UN - 4bA 4./STSE' l.y. fIIOP2 Q]Q LD ESWD SF -DST.N s`�'bONAL�� /Z/L9 SPICE(PROP) UD COME= SF-BROW-PROP-UN • GFTERN.OW.WT.(CO 10 CCHINUCU 4-E05C-ESI-LN GENERAL STRUCT.O'cce) U0 LCITNUDUS SF-UGC-PROP-UN I EXPIRES 9/L`'j/aoit PAINING NUM(AND UD 0CrnNUO6 4-941-0SFUN TAM LNE OD) UD c 41OOLS SF-TANK-DST-IN DEVELOPMENT SERVICES SENIOR ENGINEER WELT AWE(EGA LO MOO 4-WALT-DST-UN APPROVED FOR FIRLICATON /2/09 VEGETATION 11E14®.c ID NIIWCU 4-AESES6T-UN CUT CAT011DE-CUT(PIED) UD •COMO= SF-MC-DST-UN PLL --... CATCH UE-FEL(FEW) UO •CNINWD SF{DFDST-4DI 011 CORMS'USER CEFHU') SCITY CITY OF SPOKANE LINETYPES poFkane ALL UNETYPES IJNES SHOWN ME INCUIDEO IN THE CITY OF SPOKANE VALLEY NO E, VERI.J SINE IS A COMBINATION OF THE CDS&CITY IOU EIYFE FI L ES. SPECIAL FILE TPES � a lieV (INDICATED ONTACTT CITY OF SPOKANE�VALLEY FOR INFORMATIONU11NEi PLEASE N. •-SPECIAL UNE1YPECREATED THROUGH I P%T7PC OWN IcISNb LISP ROUTINE/de)INETYPE um=N DTCH -WHEN CREATING BD(T.PACE TETC&BREAK LINE -221A�'u PM a MCA LINETYPES&TEXT AT NTERVAIS SUFFICIENT FOR CLAWtt 3RD OIDEDI 19A:USE WE n DST SSH:AZ MCP.CUT.FW. MT et -SEC: �YBOT= STANDARD PLAN NO. DST D-104 LINETYPES • NOM LDETYIti ME PIMET H COSY PROIO1W€DRA11510•RLT11)10 FILES CLC(S)WY BE MBLSIEO BY In EA AS LORD AS LNED]R a 900E PFIIWATM IS HEM REAM SEE REFERENCE HIRAM TABLE FOR CaPADA®E PRESET=UR SDECOCNS LINETYPE DEStlmPT1ON (ABBR) REF., COLOR LJNETYPE LAYER CI ANNOJZATTON ROAD-EM CF SIRWW NO 10 CMIWWUS TFO -DST1el ROAD- OX OF SWIPE(MP) UO cwlwlOUS 1F-O4ASR p-UN PABIIED UNES/OUNWI.QYQ UO Nl1NUWS 1F OlM1-EY.ST-IDI PAIN1F➢UNES/IXYIIOL(PROP) UO O O1)IOUS 1F-00W-H0--IS MURDER(E) UD IXYCROWS 1F-04S1-33.1A-LLS . SHOULDER(PROP) 01) C TNUWS it DTI!WT-10 SURFACE FEATURES: NUEY-FOIE(EX) UD XAfP SF-ALLY-DST-UN ALLEY-EDGE(IO2) to 001111N0005 01-ALT DRIP UN BUILONO UNE(Ex) UO MELD E- O--STAN ammo LME QWOP) 00 020210S SF-0.00 PROP-W • ROADWAY[REM(EQ 10 ERN Sf-aN-E a1-UN ROADWAY 000WI QRW) 10 am 4--0iWI-FliW-11/1 ASPHALT (EQ UD xAcT1 4-ASRI SA-LN ASPHALT (PRa') LID cons4uD16 S-ARIA-{R5-4➢A (AMEL/lM(FEOC:(EX) LID OA91 SP-IRAV-39A-111 QAAW.MST-ea(PROP) L0 MTHUOUS ET-CLAN-PREP-LLY CWDSIE-EDT£000 UD DM SF-WC-MLA-UN WIWE:1E-ENE(MP) UD COWNUCus F- C-RCP-UI -_ cum(00 15 IEAISWR S-0S6-Il70-ON CLIPS(PROP) SD mNRIUDUs s-0SO-PROP-W 00EWALK(DO 15 MENDER S-WALK-DST-10 • SIDEWAIN(PRO) I0 CONTINUOUS S-WALX-PROP-LN ILTT'R(EX) 15 WANDER Y-ORR-EYST-UN UNWPROIID ROADWAY(SQ 10 0.YI1BUDLI5 91111u-SIIA-lN UTE ER(SQ TO CONTINUOUS 4-1-SF32:1A-W4 ORAL(000 U0 2191 S-RUT.-EYST-UN QYFD(/CIRH CENTERLINE(FJQ UD DIM 3-LTIA�Sl--IN pa(/1Ra CNIE!i)C(PROP) UD 3101 sE-]1]A-PROP-1IN RWOHIN/91WDLE UD WIRIUOA SF-222B-DST-1.111 FZO UNE(E) UD 219E S-PELD-E3T-IN EOM(50 1 115 MN sF HENc- IST-N FTROE(MP) 10 FBI S'-FENC-PROPTH .P .. CUISR L(50 10 •(001 SF-0110-05f-LLV . cuARIML.(PROP) 10 •PDR M,F.. 11-,E. LAKE/RCM UD LATE SF-LAIC-0:11-1.01 SWAW/BEILNO PERF.13R UD WOE 5:-VER+7aT-UN IIIM RaRCIAD LID •RIRI S-IS - r-IN '+ C E N T WALLS (PROW FIELD NOTES) . 1 115 D/91ED3 S-WALL 19C-LN �A .. Qg WASg/"7O 2Wr =/,= LETALxwD WAIL. 1 115 •FRM F-wALl-os7-1D1 .1.4• 'yC I1TAWN0 WA11 Om') 10 •PM SF-WALL-PROP-1N FQ' % o •S. 1RALER/M06SE NaE(E0 UD DE190 SF-HDO-EST-UN ' p y /1•W..ffre 2 q . 0500 UN! w W4IIMJO15 S-DECK-LSI-UN ^i Yf7 i,.� - 000S()b UD WDWUOIS S-OW(-DST-UN /7 ale" P '�11M-_a5x(ON) w mnwlDUS F-uAE-OSo-ux 44 RPE/NOT DRAINAGE(Et) MI SO9 F-PIPE-EM-UN p J 36449 Q rtV� PIPE/NOT ORANAIE(PROP) LID WIITNUWS SE-PPE-PROP-UN .65,e)) .EGI/STR% �*. '% BRIM(EX) 10 X9D SF-NA0.ESFIN sIONAL " /2/07 BROW(PROP) UD CCNINNWS F-131110-PRIPil CDFR.LL STRICT.(EQ UD Ga1NVOb SF-MSO-OST1N • GENERAL Smug(PROP) UD COMM15 F-LDS- oP-1N ' EXPIRES 47/2.912 z;/0 PARKNo EWER NNE) UD WNTNUalS E-SOLI-ELST-WI TANN WE(EX) VD CMIMUDAS SF-TANK-DST-UN DEVELOPMENT SERVICES SENIOR ENGINEER VAIAT UNE(F}] W TORRID F-VAL.T1:_CST1L1 APPROVED FOR PUBLICATION /2/Q 9 venom LIE/IDOE ID WMD.VOIS F-TECE-E TALI OJT EATER LHE-0R(PROP) 10 •CNR006 F-CRGF031-Ml FILL um LEE-FILL(PROP) UD •MENIIL9 F-CTF-DE1.4N ND MOTES'USER DEWED" C CITY OF SPOKANE LINETYPES Spokane ALL IN LION THE SHOWN ARE LNETTPE FILES.ONE CITY OF SPOKANE Valley® VALLEY UNEIYPE FILE.COSV_UTILITY_VETO.LRI. THE LOIETPE FILE IS A COMBINATION OF THE CBE C LAZY I THRU E FB.Ei SPECIAL FILE TYPES (WOICATED 9Y•)CAN BE CREATED THRU SPEdAL 2ITINES PLEASE TACT COY OF SPOKANE VALLEY FOR INFORMATION. •- SPECIAL NNERPE-CREATED THROUGH IRIPnPF ion pm.. LISP ROUTINE/&UNE(TPE 210=so Q D • ••- WHEN C EEATINO TEXT, PLACE TEXT&DREAK UNE -LLB I USE MT or SHOD LINETYPES&TEXT AT W1ERVALS SUFFICIENT FOR CLARITY SRO WyW -BOLA:USE EDGE or EMT -ST]B I USE CTW.CBOT.1TP. -33.30 �T"� STANDARD PLAN NO. -DSC L USE a- TOOT or an D-105 24" B.1% TYPE"S" L2" RISE QUANTITY = .037037 C.Y. / L.F. SEE NOTE 4 AND 9 PORTLAND CEMENT CONCRETE WEAKENED PLANE JOINT 17" 24'-r GENERAL NOTES 1. PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000, AIR ENTRAINED. 2.WEAKENED PLANE JOINTS FOR PORTLAND CEMENT CONCRETE SHALL BE PLACED AT 2 TIMES SIDEWALK WIDTH OR 10' MAX. AND SHALL MATCH SCORES IN SIDEWALK WHERE APPLICABLE. 3.3/6" EXPANSION MATERIAL SHALL BE PLACED AT ALL CURB RETURNS. 4.TO BE USED ONLY IN SPECIAL CASES WITH APPROVAL OF THE DEVELOPMENT SERVICES SENIOR ENGINEER. 5.95% COMPACTION UNDER CURB. 6.EXPANSION JOINT SHALL BE PLACED AT ALL RADIUS RETURNS. 7.2" MIN. CRUSHED ROCK UNDER ALL CURB. B.FOR "DUMP" CURB APPLICATIONS, GUTTER SHALL SLOPE AWAY FROM CURB AT 8.1% 9.TYPE I INLETS REQUIRED PER SPOKANE REGIONAL STORMWATER MANUAL R=12 TYPE"B" 2" RISE QUANTITY = 0.047657 C.Y. / LF. 2 3/4' ° 2 3/4" R=1' illPAVEMENT CEMENT ND CEMEN TYPE"A" CONCRETE QUANTITY = 0.036025 C.Y./ L.F. SEE NOTE 4 2" MIN. COMPACTED CRUSHED ROCK (SEE NOTE 5) LANE EDGE R=13" TYPE"R" QUANTITY = .041555 C.Y. / LF. SEE NOTE 4 22" 18° R=1" ASPHALT CONCRETE VARIES TYPE"C" QUANTITY = 0.023123 TONS / LF. SEE NOTE 4 PORTLAND CEMENT CONCRETE IEXPIRES 9/a9/a0/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /1/09 Spokane .001/alley CURBING STANDARD PLAN NO. R-102 GENERAL NOTES 1.TOOL JOINTS SHALL BE PLACED EVERY 5 FEET AND MATCH CURB JOINTS. 2.EXPANSION JOINTS SHALL BE PLACED EVERY 20 FEET WITH FELT EXPANSION MATERIAL EXTENDING THE FULL SIDEWALK DEPTH. 3.EXPANSION MATERIAL IS REQUIRED BETWEEN A DRIVEWAY SLAB AND THE SIDEWALK. IT IS ALSO REQUIRED BETWEEN THE SIDEWALK AND THE DRIVEWAY APPROACH. EXPANSION MATERIAL SHALL EXTEND THE FULL DEPTH OF THE SIDEWALK. 4.SIDEWALK SHALL SLOPE TOWARDS THE CURB AT 2X 5.SIDEWALK SHALL BE 4' THICK EXCEPT WHEN PART OF A DRIVEWAY WHERE IT SHALL BE 6" THICK. 6.STREET SIDE TOP OF WALK LEVEL WITH TOP OF CURB. 7.4" MIN. COMPACTED CRUSHED SURFACING TOP COURSE UNDER SIDEWALK. B.90%COMPACTION.UNDER SIDEWALK. • 9.REFER TO TABLES 7.2 k 7.3 IN THE SPOKANE VALLEY STREET STANDARDS FOR SIDEWALK WIDTH. 10.MAX. LONGITUDINAL GRADE OF SIDEWALK IS 5%. 11.PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000, AIR ENTRAINED. SI IN BROOMED FINISH CONTRACTION JOINT EXPANSION JOINT MIN. 4" COMPACTED CRUSHED SURFACING TOP COURSE JOINT AND FINISH DETAIL SEE NOTE 3 3/B OEXPANSION JOINT DETAIL r- 1' MIN. -►{� 1/B' - 1/4' © CONTRACTION JOINT DETAIL EXPIRES 9/29'/20/'0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION Zoo? Stielane ��Valley� SIDEWALK STANDARD PLAN NO. R-103 EXPANSION JOINT SIDEWALK 7 PLA NTER STRIP EXPANSION JOINT 7' PLANTER STRIP SEE CURB PROFILE 4%/// oat,/ 7j�"� / 2'x TACTILE WARNING SURFACE (SEE NOTE 1) CENTER OF CURB ARC SEE CURB PROFILE PLANTER STRIP APPLICATION GENERAL NOTES 1. TACTILE WARNING SURFACES SHALL BE FEDERAL YELLOW, CAST IN PLACE DETECTABLE UNITS AS MANUFACTURED BY ARMOR TILE TACTILE SYSTEMS, OR AN APPROVED EQUAL. TRUNCATED DOME SIZE AND SPACING SHALL COMPLY WITH THE ACCESS BOARD GUIDELINES FOR PUBLIC RIGHTS-OF-WAY (SECTION R304). UNITS SHALL BE INSTALLED PER MANUFACTURERS RECOMMENDATIONS. 2.TACTILE WARNING SURFACES SHALL BE 24" MIN. IN THE DIRECTION OF TRAVEL. 3.A 4' LANDING SHALL BE PROVIDED BEHIND ALL PEDESTRIAN RAMPS. 4.NO DRAINAGE STRUCTURES SHALL BE PLACED IN FRONT OF RAMPS. 5,CURB FRONTING PEDESTRIAN RAMPS SHALL BE AT A SUFFICIENT GRADE TO PREVENT PUDDING. 6.RAMPS SHALL CONFORM TO ALL APPUCABLE A.D.A. GUIDEUNES, WITH A MAX. DX SLOPE. BROOM FINISH PARALLEL TO CURB EXPANSION TYPE 'A' OR JOINT 'B' CURB EXPANSION JOINT 3 10' SWALE SEE CURB PROFILE immons SIDEWALK 10' SWALE SEE CURB PROFILE SWALE APPLICATION 2'x4' TACTILE WARNING SURFACE (SEE NOTE 1) BROOM FINISH PARALLEL TO CURB TYPE 'A' OR 'B' CURB CENTER OF CURB ARC —I 3 le- CENTER OF CURB ARC 7.PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000, AIR ENTRAINED. CURB & GUTTER CURB PROFILE 5' THICK RAMP, WINGS, AND LANDING 4' COMPACTED CRUSHED SECTION A-A SURFACING TOP COURSE, 90X MODIFIED PROCTOR. /2 An? EXPIRES 9/29/2 o/t DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /09 Spokane ®f ValleyN PEDESTRIAN RAMPS TYPICAL STANDARD PLAN NO. R-105 TYPE 'A' CURB <SEE STD PLAN R-102) SINGLE CROSSING APPLICATIONS GENERAL NOTES 1. TACTILE WARNING SURFACES SHALL BE FEDERAL YELLOW, CAST IN PLACE DETECTABLE UNITS AS MANUFACTURED BY ARMOR TILE TACTILE SYSTEMS, OR AN APPROVED EQUAL. TRUNCATED DOME SIZE AND SPACING SHALL COMPLY WITH THE ACCESS BOARD GUIDEUNES FOR PUBLIC RIGHTS-OF-WAY (SECTION R304). UNITS SHALL BE INSTALLED PER MANUFACTURERS RECOMMENDATIONS. 2.TACTILE WARNING SURFACES SHALL BE 24" MIN. IN THE DIRECTION OF TRAVEL. 3.A 4' LANDING SHALL BE PROVIDED BEHIND ALL PEDESTRIAN RAMPS. EXPANSION JOINT 4' EXPANSION JOINT SEE CURB PROFILE BROOM FINISH PARALLEL TO CURB TYPE 'A' OR 'B' CURB CENTER OF CURB ARC SIDEWALK SEE CURB PROFILE 2'x4' TACTILE WARNING SURFACE <SEE NOTE 1) ADJACENT SIDEWALK APPLICATION 3�CENTER OF CURB ARC il°Y 'EXPIRES 7/2-41/20./0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /a°/ 6 k 6 -I k-6 I 6 Spokane CURB PROFILE ao5Valley. NO LIP 4.NO DRAINAGE STRUCTURES SHALL BE PLACED IN FRONT OF RAMPS. CURB 8. 5,CURB FRONTING PEDESTRIAN RAMPS SHALL BE AT A SUFFICIENT GUTTER GRADE TO PREVENT PUDDLING. 6.RAMPS SHALL CONFORM TO ALL APPUCABLE A.D.A. GUIDEUNES, WITH A MAX. 8% SLOPE. 7.PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000. AIR ENTRAINED. 8' DEPTH 5' THICK RAMP, WINGS, AND LANDING 4' COMPACTED CRUSHED SECTION A-A SURFACING TOP COURSE, 90X MODIFIED PROCTOR. PEDESTRIAN RAMPS MIDBLOCK AND ADJACENT SIDEWALK STANDARD PLAN NO. R-106 (EXPIRES y/2.q/20 10 3/8' EXPANSION JOINT VARIES 2% VARIES MAX. a SEE NOTE 6" PORTLAND CEMENT CONCRETE GENERAL NOTES L EXPANSION JOINT MATERIAL SHALL BE PLACED IN THE CENTER OF ALL DRIVEWAYS OVER 20' IN WIDTH. 2.EXPANSION JOINT REQUIRED IF POUR INCLUDES ADDITIONAL DRIVEWAY AREA. 3.PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000, AIR ENTRAINED. 4.ALL EXTERNAL EDGES TO BE TROWELLED WITH 1/4" RADIUS EDGER. 5.SIDEWALK TO BE SCORED EVERY 5'. 3/8" EXPANSION JOINT TO BE INSTALLED AT LOCATIONS WHERE SIDEWALK INTERSECTS OTHER SIDEWALKS AND DRIVEWAYS. 6.FOR ROADSIDE SWALE APPLICATIONS, INSTALL 12" CULVERT UNDER APPROACH PER SPOKANE REGIONAL STORMWATER MANUAL ENDS SHALL BE BEVELED TO MATCH SWALE SLOPE. 7.MIN. 4" THICK COMPACTED CRUSHED SURFACING TOP COURSE LAYER UNDER DRIVE APPROACH. B.FIRST 2' OF DRIVE APPROACH (AT CURB SIDE) SHALL BE THICKENED TO MATCH BOTTOM OF CURB. THROAT WIDTH —PROJECTED TOP OF CURB ELEVATION 6" SECTION A—A DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /Z/0 SD�o%ane P Valley° DRIVEWAY APPROACH SEPARATED SIDEWALK STANDARD PLAN NO. R-110 MIGINEUMI MOM COMM. 30' 40' RES. 16' 30' —PROJECTED TOP OF CURB ELEVATION 6" SECTION A—A DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /Z/0 SD�o%ane P Valley° DRIVEWAY APPROACH SEPARATED SIDEWALK STANDARD PLAN NO. R-110 CONCRETE APRON ` , (SEE NOTE 8 AND DETAIL) _ads* T HR49T 1/4Id2,6,free q8�., 3/8' EXPANSION JOINT "C 5' 10' PROJECTED TOP OF CURB ELEVATION GENERAL NOTES 1. EXPANSION JOINT MATERIAL SHALL BE PLACED IN THE CENTER OF ALL DRIVEWAYS OVER 20' IN WIDTH. 2.EXPANSION JOINT REQUIRED IF POUR INCLUDES ADDITIONAL DRIVEWAY AREA. 3.PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000, AIR ENTRAINED. 4.ALL EXTERNAL EDGES TO BE TROWELLED WITH 1/4" RADIUS EDGER. 5,SIDEWALK TO BE SCORED EVERY 5'. 3/8" EXPANSION JOINT TO BE INSTALLED AT LOCATIONS WHERE SIDEWALK INTERSECTS OTHER SIDEWALKS AND DRIVEWAYS. 6.THIS APPUCATON IS FOR RESIDENTIAL USE ONLY. 7,MIN. 4" THICK COMPACTED CRUSHED SURFACING TOP COURSE LAYER UNDER DRIVE APPROACH. 8.APRON SHALL EXTEND TO SWALE BOTTOM AND BE SECURED TO DRIVE APPROACH WITH TWO 12" #4 REBAR, EMBEDDED 6". THROAT WIDTH tallalESIELYS COMM. 30 40' RES. 16' 30' 15' MIN.-1 L15' MIN. 1' MIN. APRON DETAIL 6" PORTLAND CEMENT CONCRETE SECTION A-A 1-5/8" BELOW GUTTER FLOWJNE 'EXPIRES 9/29 o/o DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PURLICATIN /2/O If Spokane �Valleya DRIVEWAY APPROACH SWALE INLET STANDARD PLAN NO. R-111 TRANSITION AREA 3/8' EXPANSION JOINT F3.5' 3' 3' 2% —PROJECTED TOP OF CURB ELEVATION 1r r1/2" LIP 6" PORTLAND CEMENT CONCRETE SECTION A—A GENERAL NOTES 1. EXPANSION JOINT MATERIAL SHALL BE PLACED IN THE CENTER OF ALL DRIVEWAYS OVER 20' IN WIDTH. 2.EXPANSION JOINT REQUIRED IF POUR INCLUDES ADDITIONAL DRIVEWAY AREA. 3.PORTLAND CEMENT CONCRETE SHALL BE CLASS 3000, AIR ENTRAINED. 4.ALL EXTERNAL EDGES TO BE TROWELLED WITH 1/4" RADIUS EDGER, 5.SIDEWALK TO BE SCORED EVERY 5'. 3/8" EXPANSION JOINT TO BE INSTALLED AT LOCATIONS WHERE SIDEWALK INTERSECTS OTHER SIDEWALKS AND DRIVEWAYS. 6.MIN. 4" THICK CRUSHED SURFACING TOP COURSE LAYER UNDER DRIVE APPROACH. 7.FIRST 2' OF DRIVE APPROACH (AT CURB SIDE) SHALL BE THICKENED TO MATCH BOTTOM OF CURB. THROAT WIDTH DISTANCES larallallIllallill COMM. 30 40 RES. 16' 30' IEXPIRES q/2_9/2o/o I DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /2/op Spol�ane �ValleyW DRIVEWAY APPROACH ADJACENT SIDEWALK STANDARD PLAN NO. R-112 TYPE'A'CURB PEDESTRIAN TRAVELWAY SHALL MEET ALL APPLICABLE A.D.A.GUIDELINES MAX.2%SLOPE R.30' --4—THROAT WIDTH(SEE TABLE) —14- A 6'THICK CONCRETE APPROACH 4 SIS • 4 PED.RAMP PER STANDARD PLAN R-106 SIDEWALK R.30' TYPE'B'CURB CROSS OUTTER PLAN MIN. 2% THROAT WIDTH DISTANCES TYPE MIN. CO 301 40' GENERAL NOTES 1. ONLY TO BE USED WITH APPROVAL BY DEVELOPMENT SERVICES SENIOR ENGINEER. 2.CONCRETE FOR DRIVEWAYS SHALL BE CLASS 3000 AIR ENTRAINED. 3.ALL EXTERNAL EDGES TO BE TROWELLED WITH 1/4" RADIUS EDGER. 4.MIN. 4" THICK COMPACTED (95%) CRUSHED SURFACING TOP COURSE UNDER DRIVE APPROACH. SECTION A-A EXPIRES 9/2s/20-t01 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FON PUBLICATION /a /G Spokane jValley� DRIVEWAY APPROACH HIGH VOLUME STANDARD PLAN NO. R-113 R/W — 12" CULVERT (SEE NOTE 3) THROAT WIDTH (SEE TABLE PLAN GENERAL NOTES 1. ONLY TO BE USED IN APPUCA11ONS WHERE CURB IS NEITHER EXISTING OR REQUIRED. 2. SHALL BE CONSTRUCTED OF MIN. 3" ACP OVER 6" CRUSHED SURFACING TOP COURSE. 3. INSTALL 12" CULVERT UNDER APPROACH PER SPOKANE REGIONAL STORMWATER MANUAL. ENDS SHALL BE BEVELED TO MATCH DITCH SLOPE. 5' MIN. PROPERTY LINE DITCH FLOW UNE — R/W THROAT WIDTH SiEira® MMINia TYPE IIIMNIZIWAI COMM. 30 40' RES. 16 30 IEXPIRES 9//29/2D/0 I DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /Z/a/ Spo°Fkane FValley- DRIVEWAY APPROACH ASPHALT STANDARD PLAN NO. R-114 NOTE 1 24' MIN. 30'(SEE NOTE 1) SID EWALK DRIVE APPROACH PER DESIGN PUBLIC STREET CURB GENERAL NOTES 1.FIRST 30' OF ENGINEERED PRIVATE DRIVEWAY OR PRIVATE ROAD SHALL HAVE A MIN. 24' WIDE TRAVELWAY. WIDTH BEYOND FIRST 30 SHALL BE IN CONFORMANCE WITH APPUCABLE SWEET STANDARDS. ANY WIDTH REDUCTION SHALL BE SYMMETRICAL 2.PRIVATE ROAD/DRIVEWAY PLACEMENT SHALL CONFORM WITH STANDARD PLAN R-116. EXPIRES 9'/19/20/o DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION l2/V9 Spokane .000Valleya DRIVE APPROACH FOR PRIVATE STREETS AND DRIVEWAYS STANDARD PLAN NO. R-115 B/EDGE OF AS 2' MIN. PROPERTY UNE LOT A STRUCTURE 2' MIN. w 0 STRUCTURE 4 • 20' MIN. LOT3 ROW w LOT C STRUCTURE PROPERTY LINE 5' MIN. 5' MIN. SIDEWALK WING (TYP.) CURB SEPARATED SIDEWALK (R-110 R-1111 THROAT WING (TYP.) SIDEWALK CURB THROAT III ADJA NT SIDEWALK (R-1121 ARC (TIP.) PAVEMENT EDGE APPROACH PER DESIGN (TYP.) END OF / CURB/EDGE OF ASPHALT RETURN J I 15' MIN. RESIDENTIAL, 75' MIN. COMMERCIAL GENERAL NOTES 1.LOT "A" DIMENSIONS ARE FOR CORNER LOTS. 2.LOT "B" DIMENSIONS ARE FOR DRIVEWAYS EQUAL TO OR IN EXCESS OF 150' MEASURED FROM CURB/EDGE OF ASPHALT TO FRONT DOOR OF STRUCTURE. SEE STANDARD PLAN R-133 FOR MINIMUM TURNAROUND DIMENSIONS. 3.LOT "C" DIMENSIONS ARE FOR ALL OTHER APPUCATIONS. 4. PROPERTY UNE OFFSETS ARE TO EDGE OF THROAT AT ROW UNE (SEE THROAT DEFINITIONS MOVE). 5.SEE STANDARD PLANS R-110 TO R-114 FOR ALLOWABLE DRIVE APPROACH TYPES. B.NO DRIVEWAY SHALL ACCESS AN INTERSECTION CURB ARC. 7.TOTAL WIDTH OF APPROACHES CANNOT BE GREATER THAN 50% OF TOTAL LOT FRONTAGE WIDTH. B.COMMERCIAL PROJECTS SHALL PROVIDE STACKING LENGTH PER CHAPTER 7 OF THE STREET STANDARDS. 9.ONE DRIVEWAY ACCESS PER LOT IS ALLOWED ON ARTERIAL STREETS. TWO DRIVEWAY ACCESSES ARE ALLOWED ON RESIDENTIAL/LOCAL ACCESS STREETS. 10.SPACING BETWEEN APPROACHES IS MEASURED AT THE CURB/EDGE OF ASPHALT, AND SHALL CONFORM WITH CHAPTER 7 OF THE STREET STANDARDS. DRIVE APPROACH STREET EDGE OF STREET w o �z oW \2 3 uwi CC Li HZ MAXIMUM DRIVEWAY GRADES 0% THROAT RURAL'(R-1141 EXPIRES Wa9/2c./o DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /Z/09 Spokane Valley® DRIVEWAYS GENERAL REQUIREMENTS STANDARD PLAN NO. R-117 PROJECT SIDE —BORDER EASEMENT ROW PER STREET CLASSIFICATION --1' riscv,\ 2 \y , , ,.\\ /'/ \ 4' UNDEVELOPED SIDE MIN. 28' TOTAL PAVING WIDTH —PAVING WIDTH PER STREET CLASSIFICATION-a- 29. 28 3 1' MIN. GRAVEL SHOULDER SIDEWALK WIDTH PER STREET CLASSIFICATION SWALE/PLANTER STRIP PER DESIGN SECTION PER STREET CLASSIFICATION GENERAL NOTES 1.RIGHT-OF-WAY WIDTHS AND EASEMENTS SHOWN ARE MINIMUM REQUIREMENTS FOR NEW STREETS. MEASUREMENTS MAY NEED TO BE ADJUSTED TO MATCH EXISTING FACILITIES. 2.PAVED WIDTH IS MEASURED FROM EDGE OF GUTTER. SWALE PER J DRAINAGE DESIGN ROW (VARIES) 5' MIN. 'EXPIRES 4/2...q/2oio DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUULIGATION /a/oq �p®one TYPICAL STREET SECTION HALF STREET STANDARD PLAN NO. R-119 'M IV PLANTER STRIP SECTION SWALE SECTION BORDER(EASEMENT —1' 4' 2-3% 5' SIDEWALK 7' PLANTER STRIP BORDER 161SEMENT HMA CLASS 1/2" (MIN. 3", SEE NOTE 3) C.S.B.C./C.S.T.C. (MIN. 6", SEE NOTE 3) APPROVED SUBGRADE 95%MODIFIED PROCTOR GENERAL NOTES 1.RIGHT-OF-WAY WIDTHS AND EASEMENTS SHOWN ARE MINIMUM REQUIREMENTS FOR NEW STREETS. MEASUREMENTS MAY NEED TO BE ADJUSTED TO MATCH EXISTING FAOUTIES. 2.PAVED WIDTH IS MEASURED FROM EDGE OF CUTTER. 3.MAY BE INCREASED BASED ON GEOTECHNICAL EVALUATION AND PAVEMENT DESIGN. 10' SWALE 5' SIDEWALK EXPIRES 9/Z9/2c/o DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBIIGATION /E Ac/IN S iiikane Walley- TYPICAL STREET SECTION LOCAL RESIDENTIAL STANDARD PLAN NO. R-120 BORDER(EASEMENT -1' 4' PLANTER STRIP SECTION R W SWALE SECTION 6' SIDEWALK PAVI 2-3% NG 2-3% 7' PLANTER STRIP HMA CLASS 1/2° (MIN. 4°, SEE NOTE 3) C.S.B.C./C.S.T.C. (MIN. 6", SEE NOTE 3) APPROVED SUBGRADE 95% MODIFIED PROCTOR GENERAL NOTES 1.RIGHT-OF-WAY WIDTHS AND EASEMENTS SHOWN ARE MINIMUM REQUIREMENTS FOR NEW STREETS. MEASUREMENTS MAY NEED TO BE ADJUSTED TO MATCH EXISTING FACILITIES. 2.PAVED WIDTH IS MEASURED FROM EDGE OF GUTTER. 3.MAY BE INCREASED BASED ON CEOTECHNICAL EVALUATION AND PAVEMENT DESIGN. BORDER(EASEMENT 4' 1' 10' SWALE / `6' SIDEWALK EXPIRES 9/29/'2°1° I DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /2101 oe �Valley� TYPICAL STREET SECTION LOCAL COMMERCIAL STANDARD PLAN NO. R-121 BORDER EASEMENT --1' Q. PLANTER STRIP SECTION 46' SWALE SECTION ROW 51-0? eSliaa 6' SIDEWALK (SEE NOTE 4) 7' PLANTER STRIP 2L37'. -37° PA NG 2-3% HMA CLASS 1/2° (MIN. 4°, SEE NOTE 3) C.S.B.C./C.S.T.C. (MIN. 6", SEE NOTE 3) APPROVED SUBGRADE 853 MODIFIED PROCTOR GENERAL NOTES 1.RIGHT-OF-WAY WIDTHS AND EASEMENTS SHOWN ARE MINIMUM REQUIREMENTS FOR NEW STREETS. MEASUREMENTS MAY NEED TO BE ADJUSTED TO MATCH EXISTING FACILITIES. 2.PAVED WIDTH IS MEASURED FROM EDGE OF GUTTER. 3.MAY BE INCREASED BASED ON GEOTECHNICAL EVALUATION AND PAVEMENT DESIGN. 4.IN RESIDENTIAL AREAS, SIDEWALK WIDTH MAY BE 5'. BORDER 11A. EASEMENT 10' SWALE / \-8' SIDEWALK (SEE NOTE 4) !EXPIRES 9/29/20/0 I DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /2-/0 Spokane- .00Valley TYPICAL STREET SECTION COLLECTOR STANDARD PLAN NO. R-122 ROW 3" HMA (SEE NOTE 1) 2% MIN. MIN. 20' PAVING WIDTH 2% MIN. AIWISSAPPAISSAISIVS SAVAPPSAISSAISSAW AI 411/ 41r v rare. TaatalerterstOra1, ei_ttllw "LK"lei rtes'ra i elneei� �j T.&Te TILE vialeg I�Xaelereobie BOIES:_ 1. PAVING COURSES -3 HMA CLASS 1/2" OVER 6" CRUSHED SURFACING BASE COURSE, OR CRUSHED SURFACING TOP COURSE. 2.THICKNESSES MAY BE INCREASED BASED ON GEOTECHNICAL EVALUATION AND PAVEMENT DESIGN. 3.STORMWATER TREATMENT AND STORAGE SHALL BE PROVIDED PER SPOKANE REGIONAL STORMWATER MANUAL 4.CROWNED SECTION MAY ALSO BE USED. ROW 2' 6" COMPACTED CRUSHED SURFACING (SEE NOTE 1) IEXPIRES W29/2070I DEVELOPMENT SERVICES SENIOR ENGUVEER APPROVED FOR PUBLICATION /2/0 Spokane Valley• ALLEY SECTION STANDARD PLAN NO. R-125 HMA WEARING COURSE 0.0625' - 0.075' EXISTING BASE (TYP.) NOTFG• 1. THE LONGITUDINAL JOINT SHALL BE A CONTINUOUS STEP WEDGE LOCATED ON CENTERLINE OF ROADWAY. 2.THE SLOPED PORTION OF THE WEDGE JOINT SHALL BE UNIFORMLY COMPACTED. 3.THE WEDGE JOINT SHALL RECEIVE TWO SEPARATE APPUCATIONS OF AN APPROVED TACK COAT PRIOR TO PLACEMENT OF THE ABUTTING PAVEMENT. 4.ALL OTHER LONGITUDINAL JOINTS SHALL BE HOT LAP JOINTS, CONSTRUCTED BY USE OF MULTIPLE PAVERS. S.SHALL BE USED AT STREET CENTERLINE JOINT FOR ALL ARTERIALS AND CAPITAL IMPROVEMENT PROJECTS, AND AT OTHER LOCATIONS AS REQUIRED BY THE PUBUC WORKS DIRECTOR. IEXPIRES 9/aq/?oiol DEVELOPMENT SERVICES SENIOR ENGINEER APPlOVED FOR PUOUCATION ! • /e g Spokane ®#Valleys LONGITUDINAL STEP WEDGE COLD JOINT STANDARD PLAN NO. R-127 OFFSET CUL- DE- SAC TYPICAL CUL- DE- SAC GENERAL NOTES 1.CUL-DE-SACS SHALL BE DESIGNED TO DIRECT DRAINAGE TO THE CONNECTING SWEET. 2.SIDEWALK SHALL BE ADJACENT TO THE CURB AROUND THE CUL-DE-SAC RADIUS. 3.RADIUS SHOWN IS TO FACE OF CURB. 4.THE WIDTH OF RIGHT-OF-WAY AND THE STREET DIMENSIONS SHALL CONFORM TO THE CLASSIFIED STREET SECTION. 5.MINIMUM CURB GRADES ON CUL-DE-SACS SHALL BE 174 [EXPIRES <f/29/2o/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOP PUBLICATION /2/09 Spokane 4. 0Valleyo CUL-DE-SAC PUBLIC STREET STANDARD PLAN NO. R-130 TYPE III BARRICADE • PROPERTY LINE TYPE III BARRICADE 60' MIN. 60' MIN t 18.5' MIN. EDGE OF ASPHALT TO FACE OF CURB SEE NOTE 3 i 20' ROW NOTE 1 NOTE 1 SEE NOTES 1 AND 4 JO' GENERAL NOTES 1.EXTEND IMPROVEMENTS TO 1' OF PROPERTY LINE. 2.HAMMERHEAD SHALL BE SIGNED "NO PARKING". 3.MAY BE WIDER DEPENDING ON STREET CONFIGURATION. 4.ROW AND BORDER EASEMENT TO EXTEND TO PLAT BOUNDARY/PROPERTY LINE EDGE OF ASPHALT 16.51 MIN. EDGE OF ASPHALT TO FACE OF CURB SEE NOTE 3 TYPE III BARRICADE 30' MIN. NOTE 3 EXPIRES q/29/z eves I DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR R19LICATION /VC 9 SpoFkane Valley. PUBLIC STREET TURNAROUND FUTURE INTERSECTION STANDARD PLAN NO. R-131 ASPHALT (SEE NOTE 1) a N 24' ACCESS EASEMENT APPROACH PER DESIGN . I SEE NOTE 4 60' MIN. PROPERTY LINE SIDEWALK SEE NOTE 4 c. 60' MIN. EDGE OF ASPHALT GENERAL NOTES 1.TEMPORARY TURNAROUND ASPHALT SHALL BE MIN. 2' HMA OVER 6" COMPACTED CRUSHED SURFACING BASE COURSE. 2.TURNAROUND TO BE WITHIN PUBLIC ACCESS EASEMENT DEDICATED TO THE CITY OF SPOKANE VALLEY. 3.TURNAROUND TO BE SIGNED 1N0 PARKING, PUBLIC STREET TURNAROUND". 4.STREET SHALL BE SIGNED "NO PARKING" FOR 20' ADJACENT TO DRIVE APPROACH. 5.TURNAROUND I5 NOT TO BE USED AS A DRIVEWAY, OR FOR DRIVEWAY ACCESS. w z TYPE III BARRICADE EXPIRES 9/29/20 0 1 DEVELOPMENT SERVICES SENIOR ENGINEER/ APPROVED FOR PUBLICATION , 49 Spokane aona11eyD PUBLIC STREET TURNAROUND FUTURE CONNECTION STANDARD PLAN NO. R-132 20 o- EDGE OF ASPHALT ZTTO EDGE OF ASPHALT -01 20. s z "NO PARKING" SIGN (TYPICAL) EDGE OF ASPHALT GENERAL NOTES o- EDGE OF ASPHALT PARALLEL PARKING REQUIREMENT 1.CUL-DE-SAC IS THE PREFERRED OPTION. REMOVED FROM NOTE 1. 2.TURNAROUND HAMMERHEAD AND DRIVEWAY SHALL BE SIGNED NO PARKING" IN LOCATIONS SHOWN. 3.ALL ASPHALT EDGES SHALL BE MIN. 2' FROM PROPERTY LINES. 4.HAMMERHEAD LEG AREAS SHALL NOT BE USED AS DRIVEWAYS. 5.ONE LOT ACCESS IS ALLOWED PER HAMMERHEAD LEG. EXPIRES 1/29/20/c DEVELOPMENT SERVICES SENIOR ENGINEER JVED FOR MISMATCH /2/ p o/ Spokane _ Walleye PRIVATE STREET AND DRIVEWAY TURN AROUNDS STANDARD PLAN NO. R-133 • ' R=1" 1/2. 22000 VARIES -t- PUBLIC STREETS GENERAL NOTES 1.SIGNS SHALL MEET SPECIFICATIONS FOR FLAT PLATE ALUMINUM. 0.08° THICK, ALODINE 1200 OR EQUAL 2.THE SIGN SURFACE SHALL BE WHITE LETTERS ON A GREEN BACKGROUND. WHITE LETTERS AND GREEN BACKGROUND SHALL BE HIGH INTENSITY RETROREFLECTIVE SHEETING. 3,LETTERS SHALL BE A BLOCK TYPE FONT. 4.THE ROADWAY LABEL MAY BE OMITTED FOR "STREET°, "ROAD", AND "AVENUE'. ALL OTHER ROADWAYS SHALL INCLUDE THE ABREMATED LABEL (IE - COURT - CT. - DRIVE - DR.. ETC.) ROADWAY LABELS SHALL BE UPPERCASE. 5 SIGN INSTALLATION SHALL CONFORM TO THE CURRENT EDITION OF THE M.U.T.C.D. 6.SIZED PER M.U.T.C.D. 1/2" SEE NOTE 8 s Sullivan VARIES PUBLIC STREETS t j /PRIVATE STREET 1 22000 I° 5/B"u MAINLINE LN VARIES PRIVATE STREETS R= 2 1/4" t3" t 4 1/2." R= 2 1/4" 2" �4. CROSS-SECTION Sullivan 22000 MARION STEEL 3 LB. POWDERCOATED RIB-BAK POST SAFE SIGN SUPPORT SYSTEMS TYPICAL SIGN INSTALLATION EXPIRES 57/2.9/z /0 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PODUCATION /2/0/ Spokane ,#Valley STREET SIGNS STANDARD PLAN NO. R-140 4'-0•MIN.r.S'-0•MAIC O O O O O 0 O O O O O 00"-000 Firrtrttei rttArtI 6'rm..)I ELEVATION • 0M4-1 END CP ROADWAY MARKER (TIP.) PERMANENT, WEATHERPROOF LETTERING 3/4" ACX PLYWOOD PANEL ORANGE AND WHITE REFLECTIVE SHEETING ASTM D4956-TYPE III OR N (SEE NOTE 2) 4"z4" TREATED POST TYPE III BARRICADE 1-1/4" MIN. LETTER HEIGHT THIS STREET WILL BE EXTENDED WITH FUTURE DEVELOPMENT FOR MUTE WFORMATON CONTACT CRY CF SPOKANE VALLEY CUM(UNn DEVELOPMENT DEPARTMENT mo-ml-1000 1 3/4" MIN. LETTER HEIGHT FUTURE CONNECTION SIGN DETAIL FINISH GRADE ISOMETRIC VIEW GENERAL NOTES 1. ALL FASTENERS SHALL BE ZINC PLATED, GALVANIZED OR STAINLESS STEEL. ALL STEEL ANGLE AND TUBULAR STEEL SHALL BE HOT-ROLLED, HIGH CARBON STEEL. PAINTED OR GALVANIZED. 2. STRIPES ON BARRICADE RAILS SHALL BE ALTERNATING ORANGE AND WHITE RETROREFLECTIVE STRIPES (SLOPING DOWNWARD AT AN ANGLE OF 45 DEGREES IN THE DIRECTION TRAFFIC 15 TO PASS). 3. WHEN A SIGN 15 MOUNTED ON THE BARRICADE, IT SHALL BE SECURELY BOLTED TO AT LEAST TWO PLYWOOD PANELS. THE TOP OF THE SIGN SHALL NOT BE HIGHER THAN THE TOP PANEL OF THE BARRICADE. 4. FUTURE CONNECTION SIGN SHALL BE MOUNTED ADJACENT TO'BARRICADE PER STANDARD PLAN R-140. IEXPIRES 9/29/2 c/o 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUOLM'TION �2/0/ Spokane 4000fraValley TYPE 1I1 BARRICADE STANDARD PLAN NO. R-142 3 1/8" 1" 4 5/8" PLAN VIEW OF COVER 4 5/B'R. 51 3/4' 1 1/2" 2iiiiiiZ'iA► 5/8" ID 5 3/4" 10"RADIUS MONUMENT MINIMUM 3/4" I.D. IRON PIPE OR 5/8" STEEL REINFORCING ROD, 24" IN LENGTH SECTION ASPHALT PAVEMENT 3 MAX. FILL VOID WITH NON-SHRINK GROUT CLASS 3000 CONCRETE RO0( BASE BRASSSOUCAP R RECESSED 1/2' BELOW SURFACE 5/8"x24'REBAR OR 1/2'I.D. x24' GALV.PIPE MONUMENT STREET CENTERLINE 3/16" 1/4" I SECTION OF LETTER r 1/8" GENERAL NOTE: 1. THE CASTINGS SHALL BE GREY IRON CASTINGS, AASHTO DESIGNATION M-105, CLASS 308. THE COVER AND SEAT SHALL BE MACHINED SO AS TO HAVE CONTACT AROUND THE ENTIRE CIRCUMFERENCE AND FULL WIDTH OF BEARING SURFACE. 2.WHEN THE MONUMENT CASE AND COVER ARE PLACED IN CEMENT CONCRETE PAVEMENT THE CONCRETE BASE IS NOT NEEDED. (EXPIRES 9'/Z9/26/o DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FORPUeUCATION /2/'o9 Spokane 4 ' Valley SURVEY MONUMENTS STANDARD PLAN NO. R-145 PLAN GENERAL NOTES TEMPORARY ACC SS RESTRICTIONS DURING CONSTRUCTION • TEMPORARY GATES ON REQUIRED FIRE LANE ACCESS ROADWAYS MAY BE PROVIDED WITH A CHAIN AND LOCK. THE CHAIN LINK WILL BE SEVERED IN THE EVENT OF NEEDED USE BY THE FIRE DEPARTMENT. PERMANENT ACC 5 RESTRICTING f.ATES. • CLEAR UNOBSTRUCTED MINIMUM ACCESS WIDTH OF AUTOMATIC GATES SHALL BE 20' ON A SINGLE GATED ROADWAY WHEN FULLY OPENED; OR 14. ON EACH SIDE OF A DIVIDED ENTRY GATED ROADWAY WHEN FULLY OPENED. GATES SHALL BE DESIGNED ID REMAIN FULLY OPEN ONCE ACTIVATEDBY THE FIRE DEPARTMENT UNTIL CLOSED BY THE FIRE DEPARTMENT (UNLESS STAFFED 24 HOURS/DAY, 364 DAYS/YEAR). • SWINGING GATES SHALL SWING IN THE DIRECTION OF TRAVEL AND SHALL NOT INTERFERE WITH MINIMUM EMERGENCY VEHICLE TURNING RADIUS. • PERMANENT AUTOMATIC UNATTENDED GATES ON REQUIRED FIRE LANE ACCESS ROADWAYS SHALL BE PROVIDED WITH A KNOX KEY SWITCH UNLESS PROVIDED WITH AN OPTICOM COMPATIBLE STROBE ACTIVATED OPENING DEVICE. • ANY FAILURES OF REQUIRED GATE SWITCHES SHALL RESULT IN THE REQUIREMENT THAT THE GATE REMAIN IN THE OPEN POSITION UNTIL REPAIRS ARE COMPLETED. • ELECTRICALLY OPERATED GATES SHALL BE MANUALLY OPERABLE IN THE EVENT OF POWER FAILURE UNLESS SUPPLIED WITH BACKUP EMERGENCY POWER. • IN THE EVENT A GATE FAILS TO OPERATE, REQUIRING THE FIRE DEPARTMENT TO FORCE THE GATE OPEN FOR ACCESS, THE FIRE DEPARTMENT SHALL NOT BE RESPONSIBLE FOR DAMAGE CAUSED BY OPENING THE GATE. • PLANS AND SPECIFICATIONS OF GATE ASSEMBLY AND LOCATION SHALL BE SUBMITTED FOR REVIEW, APPROVAL, AND INSPECTION PRIOR TO CONSTRUCTION. IN THE EVENT THAT A CONFLICT EXISTS IN ACCESS REQUIREMENTS WITH CITY OF SPOKANE VALLEY, THE MORE RESTRICTIVE REQUIREMENT SHALL PREVAIL GATES SHALL BE APPROVED BY THE FIRE DEPARTMENT AND THE CITY OF SPOKANE VALLEY. • FINAL APPROVAL OF GATE IS CONTINGENT ON FIRE DEPARTMENT TESTING AND ACCEPTANCE. FIRE MARSHAL WILL ARRANGE FOR EMERGENCY APPARATUS TESTING PRIOR TO APPROVAL IEXPIRES 9/Z9/Zo/u 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUOLICATON 72/'0/ Spokane ® #Valley GATED ACCESS REQUIREMENTS STANDARD PLAN NO. R-150 GENERAL NOTES 1.GRAVEL BACKFILL QUANTITY FOR DRYWELLS TYPE °A" - 30 CUBIC YARDS MINIMUM /42 TONS. TYPE "B" - 40 CUBIC YARDS MINIMUM / 56 TONS. OR AS SPECIFIED ON ROAD PLANS. 2.SPECIAL BACKFILL MATERIAL FOR DRYWELLS SHALL CONSIST OF WASHED GRAVEL GRADED FROM 1" TO 3" WITH A MAXIMUM OF 5%PASSING THE U.S. No. 200 SCREEN, AS MEASURED BY WEIGHT. A MAXIMUM OF 10% OF THE AGGREGATE, AS MEASURED BY WEIGHT, MAY BE CRUSHED OR FRACTURED ROCK. THE REMAINING 90% SHALL BE NATURALLY OCCURRING UNFRACTURED MATERIAL 3.FABRIC SHALL BE MODERATE SURVIVABILITY AS OUTLINED IN WASHDOT STANDARD SPECIFICATION 9-33. FABRIC SHALL NOT BE WRAPPED AROUND DRYWELL BARRELS. 4.CONCRETE SLAB SHALL BE CLASS 3000 CONCRETE. 5.SEE STANDARD PLANS SHEETS 5-103 TO 5-105 FOR PRECAST CONCRETE DETAILS. 6.ADJUSTMENT BLOCKS SHALL BE CEMENT CONCRETE. 7.PRECAST RISER MAY BE USED IN COMBINATION WITH OR IN ULU OF ADJUSTING BLOCKS. 8.WHEN PVC PIPE IS USED A PVC ADAPTER SHALL BE INSTALLED. 9.PIPES SHALL BE GROUTED INTO DRYWELLS. METAL FRAME TYPE 4 CRATE TYPE 4 SEE 5-104 MORTAR IN PLACE SEE NOTES 7 AND 8 ABRIC UNER UNDISTURBED SOIL DRYWELL - TYPE 'A' SWALE WATERPROOF NON-SHRINK GROUT RYWELL BARREL OR CATCH BASIN WALL PIPE (TYP.) ASKET VC ADAPTER PVC ADAPTER (SAND COLLAR) METAL FRAME TYPE 4 GRATE TYPE 4� SEE 5-104 NOTE PVC PIPE ADAPTERS AND GASKET MAY VARY IN SHAPE AND SIZE, AND SHALL MEET ASTM D-303H-78 SDR35 SPECIFICATIONS. TOPSOIL MAY BE MOUNDED AROUND FRAME (TYP.) �sS MORTAR IN PLACE '1`-MORTARED ADJUSTMENT RINGS NLET PIP Wrgals C= C= o = O UNDISTURBED SOIL DRYWELL - TYPE 'B' SWALE ABRIC LINER (EXPIRES 9/29/2c.,/ea DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /2/09 Spokane _. oValley° PRECAST DRYWELLS PLACED IN SWALE STANDARD PLAN NO. S-101 b GENERAL NOTES 1. GRAVEL BACKFILL QUANTITY FOR DRYWELLS • TYPE "A" — 30 CUBIC YARDS MINIMUM /42 TONS. TYPE "B" — 40 CUBIC YARDS MINIMUM / 56 TONS. OR AS SPECIFIED ON ROAD PLANS. 2.SPECIAL BACKFLL MATERIAL FOR DRYWELIS SHALL CONSIST OF WASHED GRAVEL GRADED FROM 1" TO 3" WITH A MAXIMUM OF 5%PASSING THE U.S. No. 200 SCREEN, AS MEASURED BY WEIGHT. A MAXIMUM OF 10% OF THE AGGREGATE, AS MEASURED BY WEIGHT, MAY BE CRUSHED OR FRACTURED ROCK. THE REMAINING 90% SHALL BE NATURALLY OCCURRING UNFRACTURED MATERIAL 3.FABRIC SHALL BE MODERATE SURVIVABILITY AS OUTLINED IN WASHDOT STANDARD SPECIFICATION 9-33. FABRIC SHALL NOT BE WRAPPED AROUND DRYWELL BARRELS. 4.CONCRETE SLAB SHALL BE CLASS 3000 CONCRETE. 5.SEE STANDARD PLANS SHEETS S-103 TO 5-105 FOR PRECAST CONCRETE DETAILS. 6.ADJUSTMENT BLOCKS SHALL BE CEMENT CONCRETE. 7.PRECAST RISER MAY BE USED IN COMBINATION WITH OR IN LIEU OF ADJUSTING BLOCKS. 8.WHEN PVC PIPE 15 USED A PVC ADAPTER SHALL BE INSTALLED. 9.PIPES SHALL BE GROUTED INTO DRYWELLS. SOLID COVER FINISHED GRADE SEE 5-104 (PAVEMENT) WZIATAMOZA iii iii"A/AAA A/4 ZiiAAiiiiiiiiiOMOiiiSiiiMA/ ZA, • MORTAR IN PLACE Hti (;r;'1...-M MORTARED " RINGS ADJUSTMENT SEE GEENERAL 8. b! • WATERPROOF NON—SHRINK GROUT NLET PIPE NOIS1UBBD W1 DRYWELL - TYPE 'A' 7 AND B ABRIC LINER RYWELL BARREL OR CATCH BASIN WALL PIPE (TYP.) ASKET VC ADAPTER PVC ADAPTER (SAND COLLAR) SOLID COVER SEE S-104 NOTE PVC PIPE ADAPTERS AND GASKET MAY VARY IN SHAPE AND SIZE, AND SHALL MEET ASTM D-30311-78 50R35 SPECIFICATIONS. FINISHED GRADE (PAVEMENT) ow/.wzoomio. T.. MORTAR IN PLACE ;A (ITS -MORTARED ADJUSTMENT` RINGS z iV NLET PIPE yy llraVHAY SEE NOTES 7 MID UNDISTURBED SOIL DRYWELL - TYPE 'B' UNERC (EXPIRES q/29/20/0 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBUOATION /2/O/ Sritkane .Va11eyo PRECAST DRYWELLS PLACED IN ASPHALT STANDARD PLAN NO. S-102 W 4-D'DIA. ® ® -f ® I= ® u. laIEE:I Lag DRYWELL BARREL (ELEVATION) (TYP.) Ow.) 1 1/r CLEARANCE µEMS 0 10' EACH WAY 4-S'DIA. 1 DRYWELL BASE (ELEVATION) (TYP.) DRAINAGE PORT DRAIN HOLES DRYWELL BARREL BASE DRAIN HOLE DETAIL (PLAN) (PLAN) -1 4' SECTION D-D GENERAL NOTES 1. CONCRETE DRYWELL ITEMS SHALL BE CONSTRUCTED WITH THE BARRELS AND CONES REINFORCED WITH 0.12 S0. IN. STEEL GRADE 40, PER LINEAL FOOT OF WALL. 2.TOLERANCE OF DIMENSIONS FOR DRAINAGE PORTS 3.EACH BARREL SECTION SHALL HAVE A MINIMUM OF 6 ROWS OF DRAINAGE PORTS VERTCALLY AND A MINIMUM OF 10 DRAINAGE PORTS AROUND THE CIRCUMFERENCE OF THE BARREL. DRAINAGE PORT EXPIRES 9/Z9/J 6/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPIOVEO FOR P119UCATION /2/C9 Spokane flValleys DRYWELL DETAILS STANDARD PLAN NO. S-103 L1-1/4" S0. 3/16° 1/2" COVER SKID DESIGN DETAIL 27 5 4 34 116" SECTION A-A -•IF-1/2. -1 +I1+1" 1 7/6""-°I 1^- �l�o� 1 1/8" -11•-1/2" SECTION J-J 26 3/18° 3/4" °— 2 7/32" F1 2° •sue+ -siH1/2" 3/8" SECTION H-H GENERAL NOTES 1. FRAME SHALL BE GRAY IRON CONFORMING TO A.S.T.M. A48-90. GRADE 30. THE GRATE SHALL BE DUCTILE IRON CONFORMING TO A.S.T.M. A536-84. CLASS 80-55-06. 2. METAL FRAME AND GRATE TYPE 4 SHALL ONLY BE USED WHERE SHOWN ON THE CONSTRUCTION PLANS. IT SHALL NOT BE USED AT A CURB LINE. 3. DRAINAGE SLOTS SHALL BE PLACED PARALLEL TO THE DIRECTION OF FLOW. 4. FIT TOLERANCE SHALL BE 1/8°. 5. WELDING 15 NOT PERMITTED. 26 3/16" 5/5 a _ I Ir 2 1/6 VS'35/8 2 7/S• 1/4-.11•- 15/8" NON-SKID PATTERN TO BE CAST INTERAL ON TOP OF COVER. MIN. WFJGHT 168 LBS. FRAME - TYPE 4 GRATE - TYPE 4 B SECTION B-B 3° TO C OF PICK HOLE (1" DIA.) STORM SOLID COVER MIN. WEIGHT 116 LB5. IEXPIRES ?/79/Z 0/0 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR%IBLIGTON /2/O9 Spokane ��Va11ey¢ DRYWELL FRAME AND GRATES . STANDARD PLAN NO. S-104 4 5/8° a 263 4" 34 116" SECTION A-A -•IF-1/2. -1 +I1+1" 1 7/6""-°I 1^- �l�o� 1 1/8" -11•-1/2" SECTION J-J 26 3/18° 3/4" °— 2 7/32" F1 2° •sue+ -siH1/2" 3/8" SECTION H-H GENERAL NOTES 1. FRAME SHALL BE GRAY IRON CONFORMING TO A.S.T.M. A48-90. GRADE 30. THE GRATE SHALL BE DUCTILE IRON CONFORMING TO A.S.T.M. A536-84. CLASS 80-55-06. 2. METAL FRAME AND GRATE TYPE 4 SHALL ONLY BE USED WHERE SHOWN ON THE CONSTRUCTION PLANS. IT SHALL NOT BE USED AT A CURB LINE. 3. DRAINAGE SLOTS SHALL BE PLACED PARALLEL TO THE DIRECTION OF FLOW. 4. FIT TOLERANCE SHALL BE 1/8°. 5. WELDING 15 NOT PERMITTED. 26 3/16" 5/5 a _ I Ir 2 1/6 VS'35/8 2 7/S• 1/4-.11•- 15/8" NON-SKID PATTERN TO BE CAST INTERAL ON TOP OF COVER. MIN. WFJGHT 168 LBS. FRAME - TYPE 4 GRATE - TYPE 4 B SECTION B-B 3° TO C OF PICK HOLE (1" DIA.) STORM SOLID COVER MIN. WEIGHT 116 LB5. IEXPIRES ?/79/Z 0/0 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR%IBLIGTON /2/O9 Spokane ��Va11ey¢ DRYWELL FRAME AND GRATES . STANDARD PLAN NO. S-104 GENERAL NOTES 1. 1. CONCRETE ITEMS SHALL BE CONSTRUCTED IN ACCORDANCE WITH ASTM C 478 (AASHTO M199) & ASTM C 890 UNLESS OTHERWISE SHOWN ON PLANS OR NOTED IN THE PROJECT SPECIAL PROVISIONS. SECTION E-E E 2 1/2" V-13" 5' .5"E, t•-z 1/2° SECTION F-F 2—#3 REBAR SECTION E-E SECTION F-F SIM F .WPilW! ri PRECAST CONCRETE aV• P.WP1,0414;:gigq. E 2 1/2' 2-5 1/2" 1/2" BENDING RISER, TYPE 1 5" SECTION C-C 2 1/2" CLEAR TYPICAL 1-ip REBAR 2'—O 1 5" V-1011 SECTION D-D 2 1/2" CLEAR TYPICAL 1 #3 REBAR RISER, TYPE 2 24" PRECAST CONCRETE 46" CONCENTRIC CONE [EXPIRES 9/Z.9/2_C./C/ 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED POE PUBLICATION /z AD CITY 0f Spokane 0004"%ft., PRECAST DRYWELL &INLET DETAILS STANDARD PLAN NO. S-105 ►1'z" 1 CONCRETE SPILLWAY CURB CUT CURB CURB DRAINAGE SWALE 0.5' MIN. TOP OF SOD GUTTER PAN #4 x 12" REBAR EMBED 6" TOOL JOINT A TOP VIEW GENERAL NOTES 1.CURB INLET SHALL BE CONSTRUCTED IN ACCORDANCE WITH ASIR C 476 (AA5HTO M 199) & ASTM C 890 UNLESS OTHERWISE SHOWN ON PLANS OR NOTED IN THE PROJECT SPECIAL PROVISIONS. 2.TOP SURFACE TO BE BROOM FINISHED. 3.ALL EXTERNAL EDGES NOT LABELED SHALL BE TROWELLED WITH 1/4' RADIUS EDGER. 4.WIDTH TO BE DETERMINED BY DESIGN ENGINEER. 5.INLET SHALL EXTEND TO SWALE BOTTOM. N. 18", SEE NOTE 4 12" DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /2/6,9 EXPIRES 9/Z9/20/o SECTION A-A 4" PORTLAND CEMENT CONCRETE Spokane .Valley CURB INLET TYPE 1 STANDARD PLAN NO. S-110 CURB UNE GUTTER FLOW UNE 3/4" TAPER ALLOWED FOR FORM RELEASE. SECTION B-B REBAR PLACEMENT SPECIAL CURB INLET r1,- 8" SPECIAL CURB INLET( TYPE B CURB (SEE STANDARD PLAN R-102 REBAR 0 10"° E.W. TYPICAL-TOP k BOTTOM SIDEWALK PAY UMITS CONCRETE CURB INLET PAY UMITS SIDEWALK PAY UMITS TOP OF CURB 2' 41- 8" GUTTER FLOW UNE BACK OF WALK L GUTTER DEPRESSION DETAIL 1/2" PRE MOLDED JOINT FILLER OUTLET SWALE GRADING DETAIL GENERAL NOTE: 1. PRECAST CURB INLETS SHALL BE CONSTRUCTED IN ACCORDANCE WITH ASTM C 478 (AASHTO M 199) & ASTM C 890. 2.TOP SURFACE TO BE BROOM FINISHED. 3. ALL EXTERNAL EDGES NOT LABELED SHALL BE TROWELLED WITH 1/4" RADIUS EDGER. SECTION C-C ONSTRUCTION DINT co (EXPIRES 9/27/2 0/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUOLICATICN /2/O / Spokane ®�Ualleyal CURB INLET TYPE 2 STANDARD PLAN NO. s-111 4'- 8• C-' r B .. JI 3'- 10" 5"I_ SECTION C-C ONSTRUCTION DINT co (EXPIRES 9/27/2 0/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUOLICATICN /2/O / Spokane ®�Ualleyal CURB INLET TYPE 2 STANDARD PLAN NO. s-111 ?0• 30. PIPE ALLOWANCES MAXIMUM PIPE DIAMETER ER DIAMETER REINFORCED OR 14• PLAIN CONCRETE ALL METAL PIPE 15" CPSSP • (STD. SPEC. 9-05.20) 12' SCUD WALL PVC 15• SID. SPEC. 9-05.121)) PROFILE WALL PVC f 5' (SID. SPEC. 9-05.12(2)) *CORRUGATED POLYETHYLENE STORM SEWER PIPE S• 6' OR 12" ONE P3 BAR HOOP FOR 8" HEIGHT TWO #3 BAR HOOPS FOR 12" HEIGHT RECTANGULAR ADJUSTMENT SECTION 83 BM EACH CORNER #3 BM EACH SIDE #3 BM EACH WAY PRECAST BASE SECTION $3 BAR EACH CORNER 18 MIN. 73 BAR HOOP GENERAL NOTES 1.AS ACCEPTABLE ALTERNATIVES TO THE REBAR SHOWN IN THE PRECAST BASE SECTION. FIBERS (PLACED ACCORDING TO THE STANDARD SPECIFICATIONS), OR WIRE MESH HAVING A MINIMUM AREA OF 0.12 SQUARE INCHES PER FOOT SHALL BE USED WITH THE MINIMUM REQUIRED REBAR SHOWN IN THE ALTERNATE PRECAST BASE SECTION. WIRE MESH SHALL NOT BE PLACED IN THE KNOCKOUTS. 2.THE KNOCKOUT DIAMETER SHALL NOT BE GREATER THAN 20". KNOCKOUTS SHALL HAVE A WALL THICKNESS OF 2" MINIMUM TO 2.5" MAXIMUM. PROVIDE A 1.5" MINIMUM GAP BETWEEN THE KNOCKOUT WALL AND ME OUTSIDE OF THE PIPE. AFTER THE PIPE I5 INSTALLED, FILL THE GAP WITH JOINT MORTAR IN ACCORDANCE WITH STANDARD SPECIFICATION 9-04.3. 3.THE MAXIMUM DEPTH FROM THE FINISHED GRADE TO THE LOWEST PIPE INVERT SHALL BE 5'. 4.THE FRAME AND GRATE MAY BE INSTAI I FO WITH THE FLANGE UP OR DOWN. THE FRAME MAY BE CAST INTO THE ADJUSTMENT SECTION. 5.1HE PRECAST BASE SECTION MAY HAVE A ROUNDED FLOOR, AND THE WALLS MAY BE SLOPED AT A RATE OF 1:24 OR STEEPER. 6.THE OPENING SHALL BE MEASURED AT THE TOP OF THE PRECAST BASE SECTION. 7.ALL PICKUP HOLES SHALL BE GROUTED FULL AFTER THE BASIN HAS BEEN PLACED. SEE NOTE 1 ALTERNATIVE PRECAST BASE SECTION IEXPIRES y/Zq/Zorb 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION 2/07 SCITY #Valley. CATCH BASIN TYPE 1 STANDARD PLAN NO. S-112 6" OR 12" ONE 13 BAR HOOP FOR 8" HEIGHT TWO I)3 BAR HOOPS FOR 12" HEIGHT RECTANGULAR ADJUSTMENT SECTION b3 BAR EACH CORNER 13 BAR EACH SIDE PRECAST BASE SECTION PIPE ALLOWANCES MAXIMUM PIPE DIAMETER INSIDE pIIM ETER REINFORCED OR 12' PLAIN CONCRETE ALL METAL PIPE 15" CPSSP * (STD. SPEC. 9-05.20) 12 SOLID WALL PVC 15" STD. SPEC. 9-05.12(1)) PROFILE WALL PVC 15 (SW. SPEC. 9-05.12(2)) *CORRUGATED POLYETHYLENE STORM SEWER PIPE (/3 BAR EACH CORNER 18" MIN. #3 BAR HOOP GENERAL NOTES 1.CONCRETE INLET SHALL BE CONSTRUCTED IN ACCORDANCE WITH ASTM C 478 (AASHTO M 199) & ASTM C 890 UNLESS OTHERWISE SHOWN ON PLANS CR NOTED IN THE PROJECT • SPECIAL PROVISIONS. 2.REINFORCED STEEL SHALL BE GRADE 40 OR 60. 3.CONCRETE INLETS SHALL BE SET ON A COMPACTED OR UNDISTURBED LEVEL FOUNDATION. 4.AS AN ACCEPTABLE ALTERNATIVE TO REBAR WELDED WIRE FABRIC HAVING A MIN. AREA OF .12 SQUARE INCHES PER FOOT MAY BE USED. WELDED WIRE FABRIC SHALL COMPLY TO ASTM A 497 (AASHTO M 221). WIRE FABRIC SHALL NOT BE PLACED IN THE KNOCKOUTS. 5.WHEN PVC PIPE 15 USED, A SAND COLLAR SHALL BE INSTALLED. 6.INLET PIPE SHALL BE GROUTED INTO CONCRETE INLET, WITH WATERPROOF NON-SHRINK GROUT. 7.KNOCKOUTS SHALL BE ON ALL 4 SIDES WITH MAX. DIAMETER OF 17°. KNOCKOUTS SHALL BE ROUND. PIPE SHALL BE INSTALLED IN FACTORY PROVIDED KNOCKOUTS. ALTERNATIVE PRECAST BASE SECTION EXPIRES 9/2-9/zero 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUALICATION /2/0 9 Spokane ®'Walley' CONCRETE INLET TYPE 1 STANDARD PLAN NO. S-11.3 ONE X�4}3 BAR HOOP FOR 8" HEIGHT TWO //3 BAR HOOPS FOR 12" HEIGHT RECTANGULAR ADJUSTMENT SECTION NIN #3 BAR EACH CORNER TABLE PIPE DIAMETER 'H" 10" 2'-4" 12' 2'-51/2" 15' 2'-9' 18' S-0' 18 MIN j 0°� I DAR HOOP 13 BM EACH SIDE - + #3 BAR EACH CORNER PRECAST BASE SECTION GENERAL NOTES 1.CONCRETE INLET SHALL BE CONSTRUCTED IN ACCORDANCE WITH ASTM C 478 (AASHTO M 199) d: ASTM C 890 UNLESS OTHERWISE SHOWN ON PLANS OR NOTED IN THE PROJECT SPECIAL PROVISIONS. 2.REINFORCED STEEL SHALL BE GRADE 40 OR 80. 3.CONCRETE INLETS SHALL BE SET ON A COMPACTED OR UNDISTURBED LEVEL FOUNDATION. 4.AS AN ACCEPTABLE ALTERNATIVE TO REBAR, WELDED WIRE FABRIC HAVING A MIN. AREA OF .12 SQUARE INCHES PER FOOT MAY BE USED. WELDED WIRE FABRIC SHALL COMPLY TO ASTM A 497 (AASHTO M 221). WIRE FABRIC SHALL NOT BE PLACED IN THE KNOCKOUTS. 5.WHEN PVC PIPE 15 USED, A SAND COLLAR SHALL BE INSTALLED. 8.INLET PIPE SHALL BE GROUTED INTO CONCRETE INLET, WITH WATERPROOF NON-SHRINK GROUT. 7.KNOCKOUTS SHALL BE ON ALL 4 SIDES WITH MAX. DIAMETER OF 17". KNOCKOUTS SHALL BE ROUND. PIPE SHALL BE INSTALLED IN FACTORY PROVIDED KNOCKOUTS. ALTERNATIVE PRECAST BASE SECTION EXPIRES 7729/20)o 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPIAVED FOB PUBLCAT II /2/0 SEPokane Valley. CONCRETE INLET TYPE 2 STANDARD PLAN NO. S-114 HOOD 1/ a 5 1/2" 1 R 0 TO 1" CLR. SEE NOTE 3 OPENING HEIGHT 4" MIN. TOP OF GRATE SAFEiy BAR DEBRIS GUARD 5/13 MIN. DLAM. STEEL ROD SEE NOTE 2 z - pp SEE NOTE 4 F (TYP•! OTE E HOLE OR SLOT FOR ATTACHING HOOD (TYP.) F rn TOP VIEW FRAME DETAIL DETAIL SECTION A CATCH BASIN Ed 7" (a 0.5 FACE OF a 0257 CURB GRATE SEE NOTE 1 SECTION A FRAME GENERAL NOTES: 1. THE ASYMMETRY OF THE COMBINATION INLET SHALL BE CONSIDERED WHEN CALCULATING THE OFFSET DISTANCE FOR THE CATCH BASIN. 2. THE DIMENSIONS OF THE FRAME AND HOOD MAY VARY SLIGHTLY AMONG DIFFERENT MANUFACTURERS. THE �ET SE TSUPPORT GRATE GUARD. HOOD UNITS SHALL MOUNT E OF THE FRAME THE MEIHODS FOR FASTENING THE SAFETY BAR / DEBRIS GUARD ROD TO THE HOOD MAY VARY. THE H00D MAY INCLUDE CASTING LUGS. THE TOP OF THE HOOD MAY BE CAST WITH A PATTERN. 3. ATTACH THE HOOD TO THE FRAME WITH TWO 3/4" " 2" HEX HEAD BOLTS, NUTS, MD OVERSIZE WASHERS. THE WASHERS SHALL HAVE DIAMETERS ADEQUATE TO ASSURE FULL BEARING ACROSS THE SLOTS. 4. WHEN BOLT-DOWN GRATES ARE SPECIFIED IN THE CONTRACT, PROVIDE TWO HOLES IN THE FRAME THAT ARE VERTICALLY ALIGNED WITH THE GRATE SLOTS. TAP EACH HOLE TO ACCEPT A 5/8" • - 11 NC . 2" ALLEN HEAD CAP SCREW. LOCATION OF BOLT-DOWN HOLES VARIES AMONG DIFFERENT MANUFACTURERS. , 5. ONLY DUCTILE IRON VANED GRATES SHALL BE USED. SEE STANDARD PLANS 5-121 AND S-122. 6. PRODUCT. IT IT 1INTENDED OT THEOINTENT OFETHIS PLAN TO SHOW THE SPECIFICFD MANUFACTURED NECESSARY TO FABRICATE THE CAS11NGS SHOWN ON THIS DRAWING. CURB OR CURB AND GUTTER MATCH TOP OF HOOD TO TOP OF CURB HOOD SAFETY BAR /DEBRIS GUARD 20" X 24" VANED GRATE FRAME ISOMETERIC VIEW COMBINATION INLET FRAME. HOOD AND VANED GRATE (EXPIRES 9/2 J/zo 'c DEVELOPMENT SERVICES SENIOR ENGINEER APPtVED FOR PUBLICATION /2/0 9 Spokane _,#Valley COMBINATION INLET STANDARD PLAN NO. S-115 GENERAL NOTES 1. THE TOP OF GRATE SHALL BE INSTALLED 1" LOWER 1HAN THE PROJECTED CUTTER GRADE. 2. THE PRECAST CONCRETE INLET SHALL BE PLACED ON THE SAME GRADE AS THE CURB. 3. RISER TYPE 2 TO BE USED WITH CATCH BASIN. PROJECTED ROAD CROSS SLOPE MORTARED CONCRETE ADJUSTING RISERS (MINIMUM ONE RISER. SEE NOTE 3) PROJECTED ROAD CROSS SLOPE CATCH BASIN & INLET TYPE 1 CATCH BASIN & INLET TYPE 2 EXPIRES 7/Z9/2o/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUR ICATI]N /Z/G 9 *Wane Wa P Valley CATCH BASIN& INLET INSTALLATION STANDARD PLAN NO. S-117 1 1/4 1 5/8 1/8 — 24" 2 1/2"I 2 3/4° 2 3/4"1 2 3 4" 2 3/4 1/8"R. 2 3/4" 2 3/4° 2 3/4" 1' j 8" 2 1/4'� 2 3/4" ALTERNATE (SEE NOTE 7) 5. 7/8" SECTION B-B 3 1/2"R. 9/16°R. w loo to N 1 5/8"(TOLERANCE -+0", —1/16") 1 3/e° TOP VIEW APPROXIMATE WEIGHT-101 LBS. N '0 N VIM GENERAL NOTES: 1.THE NAME OF THE MANUFACTURER AND DIRECTION OF FLOW SHALL BE EMBOSSED ON THE TOP SURFACE OF EACH GRATE. Lu IEKING TO BE RECESSED 1/16". 2.FRAME SHALL BE CRAY IRON, AND GRATE SHALL BE DUCTILE IRON. BOTH SHALL CONFORM TO AASHTO M-306. 3.DIMENSIONS SHALL HAVE E1/16" TOLERANCE, EXCEPT AS NOTED. 4.EDGES SHALL HAVE 1/8" RADIUS, 1/8" CHAMFER OR COMPLETE DEBURRING. 5.WELDING I5 NOT PERMITTED. D.AS AN ALTERNATE, 8 PADS 1 1/2" X 3/4" X 1/8", INTEGRALLY CAST WRH THE GRATE, MAY BE USED. E '0 11IIIIIIIII 1/8" 1 5/8" SECTION A-A IEXPIRES q/2977c/c DEVELOPMENT SERVICES SENIOR ENGGGWEER APPROVED FOR Pu04GATION /0/c / Sp®lie ®SValleya METAL GRATE TYPE 1 (BYPASS) STANDARD PLAN NO. S-121 Old t' J v FLOW TOP VIEW APPROXIMATE WEIGHT-101 LBS. N '0 N VIM GENERAL NOTES: 1.THE NAME OF THE MANUFACTURER AND DIRECTION OF FLOW SHALL BE EMBOSSED ON THE TOP SURFACE OF EACH GRATE. Lu IEKING TO BE RECESSED 1/16". 2.FRAME SHALL BE CRAY IRON, AND GRATE SHALL BE DUCTILE IRON. BOTH SHALL CONFORM TO AASHTO M-306. 3.DIMENSIONS SHALL HAVE E1/16" TOLERANCE, EXCEPT AS NOTED. 4.EDGES SHALL HAVE 1/8" RADIUS, 1/8" CHAMFER OR COMPLETE DEBURRING. 5.WELDING I5 NOT PERMITTED. D.AS AN ALTERNATE, 8 PADS 1 1/2" X 3/4" X 1/8", INTEGRALLY CAST WRH THE GRATE, MAY BE USED. E '0 11IIIIIIIII 1/8" 1 5/8" SECTION A-A IEXPIRES q/2977c/c DEVELOPMENT SERVICES SENIOR ENGGGWEER APPROVED FOR Pu04GATION /0/c / Sp®lie ®SValleya METAL GRATE TYPE 1 (BYPASS) STANDARD PLAN NO. S-121 1 24' 1 1 2 5/8"I 2 5/8'I 2 5/6' 2 5/8" 2 5/8'1 2 5/8'I 2 5/8'I 2 5/8"I 1' r, 1/2" 1 5/8' —1 5/8"(TOLERANCE= +0',-1/18") SECTION B-B TOP VIEW 1/8' TO PAD GENERAL NOTES: 1.THE NAME OF THE MANUFACTURER AND DIRECTION OF FLOW SHALL BE EMBOSSED ON THE TOP SURFACE OF EACH GRATE. LETTERING TO BE RECESSED 1/16". 2.FRAME SHALL BE GRAY IRON, AND GRATE SHALL BE DUCTILE IRON. BOTH SHALL CONFORM TO PASHTO M-306. 3.DIMENSIONS SHALL HAVE *1/16" TOLERANCE, EXCEPT AS NOTED. 4.EDGES SHALL HAVE 1/8" RADIUS, 1/8" CHAMFER OR COMPLETE DEBURRING. 5.WELDING I5 NOT PERMITTED. 6.AS AN ALTERNATE, 8 PADS 1 1/2" X 3/4" X 1/8', INTEGRALLY CAST WITH THE GRATE, MAY BE USED. 1/8' 1 5/a" SECTION A-A EXPIRES 9/29/2o'° 1 DEVELOPMENT SERVICES SENIOR ENGINEER MPflJVEO FOR PUBLICATION /2/0 Sp®kane _Valleym ' METAL GRATE TYPE 3(LOW POINT) STANDARD PLAN NO. S-122 il II - - ii II TOP VIEW 1/8' TO PAD GENERAL NOTES: 1.THE NAME OF THE MANUFACTURER AND DIRECTION OF FLOW SHALL BE EMBOSSED ON THE TOP SURFACE OF EACH GRATE. LETTERING TO BE RECESSED 1/16". 2.FRAME SHALL BE GRAY IRON, AND GRATE SHALL BE DUCTILE IRON. BOTH SHALL CONFORM TO PASHTO M-306. 3.DIMENSIONS SHALL HAVE *1/16" TOLERANCE, EXCEPT AS NOTED. 4.EDGES SHALL HAVE 1/8" RADIUS, 1/8" CHAMFER OR COMPLETE DEBURRING. 5.WELDING I5 NOT PERMITTED. 6.AS AN ALTERNATE, 8 PADS 1 1/2" X 3/4" X 1/8', INTEGRALLY CAST WITH THE GRATE, MAY BE USED. 1/8' 1 5/a" SECTION A-A EXPIRES 9/29/2o'° 1 DEVELOPMENT SERVICES SENIOR ENGINEER MPflJVEO FOR PUBLICATION /2/0 Sp®kane _Valleym ' METAL GRATE TYPE 3(LOW POINT) STANDARD PLAN NO. S-122 GENERAL NG7ES 1. SWALES WITH LONGITUDINAL SLOPE GREATER THAN 1R REQUIRE CHECK DAMS. 2. DRY WELLS NOT TO BE 1MTHIN 5' OF INLETS. 3. NO MORE THAN 4' OF TOP SOIL OVER UNCOMPACTED NATIVE SOIL. 4. NO COMPACTION IN SWALE BOTTOM. 5. SWALES ARE TO BE GRASSED AND IRRIGATED. 6. SWALES SHALL BE CONSTRUCTED IN CONFORMANCE WITH SPOKANE REGIONAL STORMWATER MANUAL. SECTION A-A !EXPIRES y/2-9 4.cio DEVELOPMENT SERVICES SENIOR ENOWEER APPROVED FOR PUBLICATION /z/o9 SpoRane ® • Valler ROADSIDE SWALES STANDARD PLAN NO. S-130 GENERAL NOTES: 1. SHALL BE CONSTRUCTED IN CONFORMANCE WITH SPOKANE REGIONAL STORMWATER MANUAL z. THREADED REMOVABLE CAP FLOW SITE SPECIFIC MANHOLE/ ------------------9--•.. • VAULT, PER DESIGN ENGINEER Z MIN. 4 12" (MIN.) 24" SUMP (MIN.) 1 FLOW z-- 12" MIN. DIA. STORM PIPE OIL-WATER SEPARATOR SECURE TO WALL WITH STAINLESS STEEL BANDS (MIN. 2" WIDE) AND 1/2" BOLTS OPEN END (EXPIRES Wen/aoio-I DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLIC/MON /2/09 Spoin OF #Valleys OIL WATER SEPARATOR STANDARD PLAN NO. S-140 SIDEWALK PER STD. PLAN R-103 (TYP.) STREET NAME SIGN PED. RAMPS PER STD. PLAN R-106 (TYP.) $30"X30" R=30 • • • nun TYPE "A" CURB 5' 2% 6" THICK CONCRETE TRUCK APRON SECTION A-A STREET NAME SIGN /I■■■■■ SEE STD. PLAN R-120 24"X30 30"X30" lar nom., 4 .1_ :IIIIIIII1 • • • R=20' 50' ®30"X30" "NO PARKING" ZONE SEE NOTE 4 STREET NAME SIGN GENERAL NOTES 1.SIGNAGE PER M.U.T.C.D., LATEST EDIMON. 2.ALL RADIUS DIMENSIONS ARE TO FACE OF CURB. 3.ONLY TO BE USED ON RESIDENTIAL STREETS. 4.50' NO PARKING ZONE APPUES TO EACH LEG OF INTERSECTION, B0111 SIDES OF STREET. R7-1 SIGNS WITH DOUBLE ARROWS PER M.U.T.C.D. 5.CENTER ISLAND LANDSCAPING TO BE PLACED IN CONFORMANCE WITH APPUCABLE S.V.M.C. REQUIREMENTS. STREET NAME SIGN • • 1 TYPE "R" DUMP CURB (EXPIRES 9/29/20/° 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPEOVED FOR PUBLICATION /Z/V% Spokane _ #Va11ey� TRAFFIC CIRCLE STANDARD PLAN NO. T-101 R/W SOUTH AND WEST NORTH AND EAST UTILITY OLE FRONT FACE OF ELECTRICAL VAULT R/W EASEMENT UTILITY 6' 6' POLE 3'-0" ••00 ELECTRIC TELEPHONE AND T.V. CABLE fn (.(. T" . . ..1�H�Vi�'.Y•hGk t•.YEY4%C�.44S�V�AR4..`F.:'.kU."."' ��/f.%'O%i./%'/..\ y�ii.•.g:'e.;.:V!:,�.�:W:.�.a1 f•�.!•3i"i::q i'.vq.:✓'.�2�II 0 GAS GENERAL NOTE: 1. THIS PLAN SHOWS NORMAL LOCATIONS FOR ALL UTIUTY INSTALLATIONS. 2.LOCATIONS OF EXISTING UTILITIES MUST BE FIELD LOCATED WITH THEIR RESPECTIVE OWNERS BEFORE MAKING NEW CONNECTIONS. 3.TELEPHONE PEDESTAL SHALL BE LOCATED JUST INSIDE R/W LINE. 4.UTILTY DEPTHS TO BE DETERMINED BY RESPECTIVE AGENCY AND/OR PROVIDER. O WATER 0 SEWER O STORM DRAIN 2'-0° MIN. ELECTRIC TELEPHONE AND T.V. CABLE IEXPIRES .7/2 9/8 oio DEVELOPMENT SERVICES SENIOR GI ENGINEER APPROVED FOR PUOLICATHN /OA/ ®• Valley. UTILITY LOCATION DETAIL STANDARD PLAN NO. U-100 PRE HYDRANT (SEE STANDARD PLAN U-103 FOR NOTES AND CROSS-SECTION) GENERAL NOTES 1.WHENEVER POSSIBLE, HYDRANTS SHALL BE LOCATED NEAR 3' DIAM. CLEAR ZONE INTERSECTIONS. 2.PLACEMENT TO MEET ALL APPLICABLE CLEAR ZONE REQUIREMENTS. POWER POLE 1 1, 1 f ) r 2' MIN. CURB STREETS WITH ADJACENT SIDEWALK UTILITIES NOT TO BE LOCATED IN SIDEWALK FIRE HYDRANT (SEE STANDARD PLAN U-103 FOR NOTES AND CROSS-SECTION) 3' DIAM. CLEAR ZONE 3' MIN. IF 6' MAX. POWER POLE 2' MIN. 1 FACE OF CURB BACK OF CURB STREETS WITH SEPARATED SIDEWALK UTILITIES NOT TO BE LOCATED IN SIDEWALK EXPIRES y/Z�//2o/D 1 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /Z./b9 ►��Ol6 lie ®"�Valleym ABOVEGROUND UTILITY PLACEMENT STANDARD PLAN NO. U-101 GENERAL NOTES 1.HYDRANTS SHALL STAND PLUMB. THE TRAFFIC BREAKAWAY FLANGE 15 TO BE SET WITHIN 2° AT THE FINISHED CURB/GRADE ELEVATION WITH THE LOWEST OUTLET OF THE HYDRANT NO LESS THAN 20° ABOVER THE CURB GRADE. THERE SHALL BE A CLEAR AREA AROUND THE HYDRANT OF NOT LESS THAN 36" AS MEASURED FROM THE OUTSIDE EDGE OF THE BARREL OR OUTLET PORTS, WHICHEVER 15 GREATER. HYDRANTS SHALL BE A MINIMUM OF 36° FROM THE FACE OF CURB AND NO MORE THAN 120° FROM THE FACE OF CURB. 2.HYDRANTS SHALL BE LOCATED AT ROADWAY INTERSECTIONS WHENEVER POSSIBLE. 3.ALL FIRE HYDRANTS SHALL HAVE A MINIMUM OF THREE OUTLETS, ONE 4-1/2-INCH INSIDE DIAMETER OUTLET AND TWO 2-1/2 INCH INSIDE DIAMETER OUTLETS. THREADS ON ALL OUTLETS SHALL BE NATIONAL STANDARD THREAD (NST). 4.THE 4-1/2-INCH PORT SHALL FACE THE STREET. WHERE THE STREET CANNOT BE CLEARLY DEFINED (SUCH AS PARKING LOTS) THE PORT SHALL FACE THE MOST LIKELY ROUTE OF APPROACH (E.G., FIRE LANE) AND LOCATION OF THE FIRE APPARATUS WHILE PUMPING. AS DETERMINED BY SPOKANE VALLEY FIRE DEPARTMENT. 5.HYDRANT COLORS SHALL BE AS FOLLOWS: I. CHROME YELLOW - HYDRANTS OWNED BY DISTRICTS II. RED - PRIVATELY OWNED HYDRANTS 6.CLEAR ZONE SHALL BE FREE OF ALL OBSTRUCTIONS, INCLUDING BOLLARDS, FENCING, TREES, AND SHRUBS. 7 CLEAR ZONE (SEE NOTE 1) -\ 2" MIN., 12" MAX. 3' MIN., 6' MAX. -1.- i APPROX. 20" i TOP OF CURB ELEVATION, OR FINISHED GRADE (FOR SWALE APPUCATION) HYDRANT SECTION FACE OF CURB 'EXPIRES q/29/2°/0 DEVELOPMENT SERVICES SENIOR ENGINEER APPROVED FOR PUBLICATION /2/6v Spokane .0.0Valley FIRE DEPARTMENT HYDRANT REQUIREMENTS STANDARD PLAN NO. U-102