Chapter 30.24
GENERAL DEVELOPMENT STANDARDS - ACCESS AND ROAD NETWORK

Sections:

30.24.005    Purpose and applicability.

30.24.010    General requirements.

30.24.020    Connection of road network elements.

30.24.025    Connections to schools.

30.24.030    Establishing or altering vehicular and pedestrian access.

30.24.040    Access and road network requirements for proposed development on lots not created through a subdivision, short subdivision, or binding site plan.

30.24.050    Access and road network requirements to a proposed subdivision, short subdivision, binding site plan, or single-family detached unit development (SFDU).

30.24.055    Access and road network requirements to individual lots within a proposed subdivision, short subdivision or binding site plan development or to proposed SFDU units.

30.24.060    Access and road network requirements for lots included in a proposed boundary line adjustment (BLA).

30.24.070    Access and road network requirements for a proposed development in the Urban Center (UC) zone and subject to the requirements of chapter 30.34A SCC.

30.24.080    Pedestrian facility requirements.

30.24.090    Drive aisle requirements.

30.24.100    Fire lane (fire apparatus access road) requirements.

30.24.110    Shared court requirements.

30.24.120    Alley requirements.

30.24.130    Shared driveway requirements.

30.24.135    Requirements for access permit and license across a railroad company right-of-way or county-owned trail.

30.24.140    Requirements for dedication, deeding, establishing or reserving right-of-way.

30.24.145    Requirements for locating utilities within a right-of-way.

30.24.150    Requirements for public access to publicly-owned or controlled water bodies.

30.24.170    Recommendations of the county engineer.

30.24.005 Purpose and applicability.

This purpose of this chapter is to establish minimum access and county road network requirements to promote vehicular and pedestrian safety. This chapter shall apply to all development applications except for the following where no new access is created:

(1) Any remodel of an existing single-family detached, duplex or attached single-family structure.

(2) Site-specific rezones that are not accompanied by another permit or approval.

(3) Construction of an accessory apartment.

(4) Construction of an accessory or non-accessory storage structure that does not require a conditional use permit.

(5) Construction of a detached private accessory or non-accessory garage that does not require a conditional use permit.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.010 General requirements.

The following regulations shall pertain to all development unless exempted pursuant to SCC 30.24.005 or more specific regulations are established within this chapter:

(1) Road networks and their associated stormwater facilities shall be designed and constructed according to titles 30 and 13 SCC, the EDDS and any other applicable local, state and federal requirements.

(2) The overall road network, including stormwater drainage facilities associated with a road network element shall be subject to approval of the county engineer, except when these powers are delegated to the department pursuant to SCC 13.01.020(3) and (4).

(3) Road network elements shall be connected pursuant to SCC 30.24.020.

(4) Road network connectivity, including the extension of opened or unopened right-of-way that abut a proposed development, shall be required unless the county engineer determines that unique circumstances of the site make extension of the road network impractical or infeasible. Unique circumstances of the site may include topography, the surrounding road network, soils, hydrology, or maintenance requirements.

(5) Internal road networks shall be designed to provide:

(a) Access and circulation that comply with SCC 30.66B.420;

(b) Emergency vehicle access consistent with the requirements of SCC 30.24.100 and 30.53A.512; and

(c) A connected road network rather than long, irregular loops with deadends and cul-de-sacs, except as provided for in SCC 30.24.010(4).

(6) Maintenance of private road network elements shall be the responsibility of:

(a) The applicable owners;

(b) A homeowners association; or

(c) Any other legal entity made up of all benefited property owners.

(7) Building and structural setbacks from road network elements shall be required pursuant to chapter 30.23 SCC unless otherwise modified.

(8) All privately owned road network elements, except for a drive aisle or driveway, shall be located in a tract or easement.

(9) All road network elements shall be clearly identified on site plans.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.020 Connection of road network elements.

(1) Connections between road network elements are allowed according to SCC Table 30.24.020(1), subject to the county engineer’s approval.

(2) A private road, drive aisle or shared driveway may not make a direct, in-line connection between two sections of public road.

Table 30.24.020(1)

Connections to a Road Network Element

How to use the Table. Start in "column A" with the road network element that is being proposed. Move over to column B to the road network element that the connection is proposed from. If there is an "A" in the box, the connection is allowed. If the box is blank, the connection is not allowed.

Column A

Column B

Road Network Element Being Proposed

Road Network Element the Connection is Proposed To

Public Road

Private Road

Drive Aisle

Alley

Shared Court

Shared Driveway

Driveway

Public Road

A

 

 

 

 

 

 

Private Road

A

A

 

 

 

 

 

Drive Aisle

A

A

A

 

 

 

 

Alley

A

A

 

A

 

 

 

Shared Court

A

A

 

 

 

 

 

Shared Driveway

A

A

 

 

 

 

 

Driveway

A

A

A

A

A

A

 

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.025 Connections to schools.

When new residential development of three or more dwelling units is proposed on a site that abuts a constructed public school, the department shall consult with the affiliated school district to determine if the district would like a pedestrian connection to be provided between the proposed development and the school. If the school district requests a connection, the development shall be required to connect the pedestrian facilities within the development to the school property boundary with a privately owned ADA compliant pedestrian facility unless the department determines that such a connection is not feasible.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.030 Establishing or altering vehicular and pedestrian access.

Decisions by the county engineer in establishing or altering the location, width, number and design of any vehicular or pedestrian access from a road network element shall be made in accordance with SCC 13.01.020(2) and shall not be subject to the provisions of title 30 SCC.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.040 Access and road network requirements for proposed development on lots not created through a subdivision, short subdivision, or binding site plan.

Access for proposed development on a lot or lots not created through a subdivision, short subdivision, or binding site plan shall be provided according to the provisions of this section.

(1) The provisions of SCC 30.24.040(2) and (3) shall apply when:

(a) No access exists to the property subject to the proposed development;

(b) Access exists but new access is proposed to the property subject to the proposed development;

(c) The proposed development changes the use on the property to a use that will result in an increase in vehicular traffic over the existing use; or

(d) The proposed development adds a use to the property that will result in an increase in vehicular traffic.

(2) Access to such lots shall be provided by a road network element that connects to road network elements as permitted in SCC Table 30.24.020(1).

(3) Where access to a lot is provided by a road network element that does not meet the requirements of this chapter and the EDDS, the road network element shall meet and be constructed to the:

(a) Applicable requirements of this chapter, unless a variance is approved pursuant to chapter 30.43B SCC; and

(b) EDDS, unless an EDDS deviation is obtained pursuant to the EDDS.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.050 Access and road network requirements to a proposed subdivision, short subdivision, binding site plan, or single-family detached unit development (SFDU).

Access to a proposed subdivision, short subdivision or binding site plan development or to a proposed SFDU shall meet the requirements of this section.

(1) Access to a proposed subdivision, short subdivision, or binding site plan development or to a proposed SFDU in the urban area shall be provided by a public road, except a private road network element may be requested as a variance pursuant to chapter 30.43B SCC if unique circumstances of the site, such as topography, the surrounding road network, soils, hydrology or maintenance requirements make the extension of the public road to the development impractical or infeasible.

(2) Access to a proposed subdivision, short subdivision, or binding site plan development in the rural area may be provided by a private road network element as provided for in this chapter, except when the county engineer, in accordance with chapter 30.66B SCC, determines that a public road is required to provide for the public health, safety and welfare or connectivity of the public road system.

(3) Where access by an existing private road network element is permitted, the existing private road network element shall be constructed to a standard acceptable to the county engineer. The standard set by the county engineer shall be based upon existing and the anticipated traffic volumes generated by the proposed development.

(4) Where access by a private road network element is permitted, and the proposed private road network element has the potential for serving more than nine lots or 90 average daily trips, the county engineer may require that the road be designed to enable future conversion to a public road. The land use approval shall, to the extent possible, include a condition that the conversion to a public road may not be protested.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.055 Access and road network requirements to individual lots within a proposed subdivision, short subdivision or binding site plan development or to proposed SFDU units.

Access to lots within a proposed subdivision, short subdivision or binding site plan development or to proposed SFDU units shall meet the requirements of this section.

(1) Access to individual lots, tracts or easements within a proposed subdivision or short subdivision in the urban area shall be by a public road, except a private road network element:

(a) May be allowed for unit lot subdivisions pursuant to SCC 30.41A.205(8), except when the county engineer, in accordance with chapter 30.66B SCC, determines that a public road is required to provide for the public health, safety and welfare or connectivity of the public road system;

(b) May be allowed if serving nine lots or fewer with traffic generation of 90 average daily trips or less, except when the county engineer, in accordance with chapter 30.66B SCC, determines that a public road is required to provide for the public health, safety and welfare or connectivity of the public road system; and

(c) May be requested as a variance pursuant to chapter 30.43B SCC if unique circumstances of the site, such as topography, the surrounding road network, soils, hydrology or maintenance requirements make the extension of the public road within the development impractical or infeasible.

(2) Access to individual lots, tracts or easements, within a proposed subdivision, short subdivision, or binding site plan development in the rural area may be provided by a private road network element as provided for in this chapter, except when the county engineer, in accordance with chapter 30.66B SCC, determines that a public road is required to provide for the public health, safety and welfare or connectivity of the public road system.

(3) Access to individual dwelling units within a SFDU shall be provided by a drive aisle, unless the county engineer, in accordance with chapter 30.66B SCC, determines a public road is required to provide for the public health, safety and welfare or connectivity of the public road system.

(4) Where access by a private road network element is permitted, and the private road network element has the potential for serving more than nine lots or 90 average daily trips, the county engineer may require the private road to be designed to enable future conversion to a public road and the final subdivision, short plat or binding site plan shall contain a provision that the conversion to a public road may not be protested.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013; Amended by Amended Ord. 13-006, Feb. 27, 2013, Eff date Mar. 15, 2013; Amended by Ord. 13-075, Oct. 23, 2013, Eff date Nov. 4, 2013; Amended by Amended Ord. 16-073, Dec. 21, 2016, Eff date Feb. 19, 2017).

30.24.060 Access and road network requirements for lots included in a proposed boundary line adjustment (BLA).

Access to lots within a proposed BLA shall meet the requirements in this section.

(1) Lots created through a subdivision, short subdivision, or binding site plan that are included in a proposed BLA shall meet all requirements of this chapter except SCC 30.24.040, 30.24.070, 30.24.080, 30.24.140 and 30.24.150.

(2) Lots not created through a subdivision, short subdivision, or binding site plan that are included in a proposed BLA shall meet all requirements of this chapter except SCC 30.24.010(7) and (8), 30.24.070, 30.24.080, 30.24.140 and 30.24.150.

(3) Any new primary access shall be constructed from the nearest open, constructed and maintained public or private road prior to recording of the BLA when:

(a) The access will be from a new or different road network element;

(b) The BLA involves three or more lots; and

(c) The access is not constructed to a standard determined appropriate by the county engineer for the existing and anticipated traffic volumes to be generated by the lots reconfigured in the BLA.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.070 Access and road network requirements for a proposed development in the Urban Center (UC) zone and subject to the requirements of chapter 30.34A SCC.

Proposed development in the UC zone that is subject to the requirements of chapter 30.34A SCC must comply with following additional vehicular and pedestrian circulation system requirements:

(1) Proposed urban center developments shall be designed to provide for future vehicular connections to adjacent parcels, where applicable.

(2) The internal vehicular circulation system shall:

(a) Be clearly identifiable, pedestrian friendly and promote connectivity within the existing development;

(b) Be coordinated with the pedestrian circulation system of the development to minimize conflicts;

(c) Include loading and service areas that are separate from pedestrian circulation and parking areas.

(3) The pedestrian circulation system shall:

(a) Comply with the requirements of SCC 30.24.080;

(b) Connect to existing or planned transit stops and stations; and

(c) Connect to existing or previously approved pedestrian facilities on abutting urban center developments; or provide a pedestrian stub at the property line of the abutting property when it is zoned UC and not developed as an urban center. The connections shall be designed to be consistent with other connections of the pedestrian circulation system.

(4) As a condition of approval, a property owner may be required to provide for joint vehicular access to and/or from adjacent parcels. Joint vehicular access must be accomplished through easements or joint use agreements on forms approved by the county.

(5) Curb cuts from a public right-of-way allowed at the time of development may be temporary and subject to closure when more suitable access is developed on adjacent sites. Specifically, the county engineer may require temporary curb cuts for site access. When an adjacent site is developed, the new development may be required to close temporary curb cuts and provide access for adjoining properties through an access located on the new development site. Alternatively, one or more of the adjacent sites may be required to provide its access through a permanent curb cut required on the first site.

(6) If there is a conflict between the provisions of this section and other chapters within title 30 SCC or the EDDS, the county engineer shall determine the appropriate regulation or standard.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.080 Pedestrian facility requirements.

The intent of this section is to improve the pedestrian environment by providing facilities to make it easier, safer, and more comfortable to walk as a means of transportation by providing pedestrian connections to transit stops, between businesses and residences, through parking areas, and to all on-site activities.

(1) Pedestrian facilities shall be required:

(a) In existing or proposed right-of-way, as frontage improvements, when required by the county engineer in accordance with chapter 30.66B SCC and the EDDS;

(b) Within the development in accordance with subsection (3) of this section and applicable EDDS standards;

(c) Off-site when required by chapter 30.66B SCC and the EDDS; and

(d) In any abutting state, city, town or other county’s right-of-way, in accordance with chapter 30.66B SCC.

(2) Pedestrian facilities shall include infrastructure and equipment to accommodate or encourage pedestrian mobility.

(3) Pedestrian facilities shall form a network providing mobility from dwelling units or other buildings to:

(a) Other dwelling units or buildings;

(b) Community facilities;

(c) Central mailboxes;

(d) Parking areas;

(e) On-site recreation spaces; and

(f) Other pedestrian facilities.

(4) Pedestrian facilities shall comply with American Disabilities Act (ADA) specifications and applicable standards for accessibility.

(5) Pedestrian facilities shall not be required for permanent dead-end road network elements that are 150 feet or less in length which serve 90 average daily trips or less.

(6) Pedestrian facilities shall be prohibited in an alley.

(7) Pedestrian facilities required for a public road may be located outside of the right-of-way if an EDDS deviation is approved.

(8) Additional circulation requirements may be required by the county engineer to ensure pedestrian safety or pedestrian connectivity pursuant to this chapter, title 13 SCC, and the EDDS.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.090 Drive aisle requirements.

Drive aisles are permitted subject to the following requirements.

(1) Connection of a drive aisle to an element of the road network shall be allowed according to SCC 30.24.020.

(2) A drive aisle designated as a fire lane shall meet the requirements of SCC 30.24.100 and 30.53A.512.

(3) Drive aisles shall be:

(a) Owned in common by all the property owners utilizing the drive aisle;

(b) Not located within a tract or easement, except when located within a unit lot subdivision or short subdivision; and

(c) Designated an alley if the drive aisle provides access to the rear of a structure, lot or use.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013; Amended by Amended Ord. 12-115, Jan. 30, 2013, Eff date March 1, 2013; Amended by Amended Ord. 16-073, Dec. 21, 2016, Eff date Feb. 19, 2017).

30.24.100 Fire lane (fire apparatus access road) requirements.

In addition to the fire lane requirements in SCC 30.53A.512, the following requirements shall apply to all development:

(1) All elements of a road network shall be designated a fire lane, except:

(a) A driveway;

(b) A shared driveway that provides primary access to no more than two dwelling units, or two Group U occupancies;

(c) An alley that does not provide the only vehicular access to the structure, lot, or use; and

(d) A road network element that is not needed or required to provide fire apparatus access to buildings and facilities within a proposed development according to SCC 30.53A.512.

(2) Fire lanes shall be designed according to SCC 30.53A.512 to provide fire apparatus access to buildings and facilities within proposed development.

(3) When pedestrian facilities are required, the minimum driving surface width for a drive aisle or shared court may include a pedestrian facility on one side that is constructed with rolled curb and meets emergency vehicle load specifications.

(4) Parking facilities shall be prohibited within the minimum driving surface width.

(5) When a parking lane is provided on only one side of a fire lane, fire hydrants shall be located on the opposite side.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.110 Shared court requirements.

Shared courts are permitted subject to the following requirements.

(1) Connection of a shared court to an element of the road network shall be allowed according to SCC 30.24.020.

(2) A shared court shall be designed according to the following minimum requirements as depicted in SCC Figure 30.24.110(1):

(a) The length of the shared court shall not exceed 150 feet (Distance A1 to any A2) as measured along the centerline of the shared court panhandle, from the face of the curb line or edge of pavement, where there is no curb, of the intersecting public or private road or drive aisle (Point A1) to the farthest opposite edge of the shared court (Point A2). The maximum length of the shared court shall not be increased by either a variance pursuant to chapter 30.43B SCC or an EDDS deviation in accordance with EDDS section 1-05.

(b) The shared court area, excluding the shared court panhandle, shall provide sufficient area for joint use activities and vehicle movement. The minimum area of the court shall be the greater of:

(i) One thousand nine hundred square feet; or

(ii) Three hundred square feet per dwelling unit, whose access is from the shared court, including the court’s panhandle.

(c) The court shall be configured to provide a minimum backing up distance of 24 feet from the end of each driveway. This distance shall be measured perpendicular to the edge of the court from the point where it intersects the driveway centerline (Distance B1 to B2).

(d) The width of the court panhandle (Distance C1 to C2) shall meet the minimum width requirement for a fire lane according to SCC 30.53A.512.

(3) No parking shall be allowed within the shared court except in separate designated parking areas. These areas shall not be included in the minimum court area required by subsection (2)(a) of this section.

(4) A shared court shall be located entirely within a tract or easement unless the development is a commercial, multiple-family residential or single-family detached unit development on one site.

Figure 30.24.110(1)

Shared Court

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.120 Alley requirements.

Alleys are permitted subject to the requirements of this section.

(1) Connection of an alley to an element of the road network shall be allowed according to SCC 30.24.020.

(2) Alleys shall have a minimum of two connections to a public or private road, except one connection is allowed when an alley serves as a secondary access to residential dwellings and the alley does not exceed 150 feet in length.

(3) The minimum width of an alley that is not designated as a fire lane shall be 16 feet.

(4) Parking and pedestrian facilities are prohibited in an alley.

(5) The alley may be located in a right-of-way if approved by the county engineer.

(6) An alley may serve as the only vehicular access for residential dwellings when pedestrian access is provided to the front of the lot and the alley is designated, designed and constructed as a fire lane.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.130 Shared driveway requirements.

Shared driveways are permitted subject to the following requirements.

(1) Connection of a shared driveway to an element of the road network shall be allowed according to SCC 30.24.020.

(2) A shared driveway shall have a minimum 10-foot-wide driving surface and easement width.

(3) A shared driveway designated as a fire lane shall meet the requirements of SCC 30.24.100 and 30.53A.512.

(4) A shared driveway that provides access to more than two dwelling units or Group U occupancies must meet the fire lane requirements in SCC 30.24.100 and 30.53A.512.

(5) Parking is prohibited within a shared driveway designated as a fire lane.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.135 Requirements for access permit and license across a railroad company right-of-way or county-owned trail.

(1) When access to a lot is proposed that will cross a railroad company right-of-way or county-owned trail, the applicant, prior to the issuance of development permits, shall provide the department a copy of the document issued by the railroad company or by the Snohomish County department of parks and recreation, that grants access over the railroad company right-of-way or county-owned trail. Such document shall be recorded with the county auditor.

(2) When access to multiple lots is proposed that will cross a railroad company right-of-way or county-owned trail, the owner(s) may collectively enter into an incorporated homeowners association for the benefit of the multiple lots. The articles of incorporation and bylaws shall be recorded with the county auditor.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.140 Requirements for dedication, deeding, establishing or reserving right-of-way.

(1) An applicant for proposed development shall be required to dedicate, deed or establish right-of-way to the county along any abutting county right-of-way for road purposes pursuant to SCC 30.66B.510.

(2) In cases where the dedication, deeding, or establishment of additional right-of-way cannot be reasonably required as a direct result of the proposed development, but such right-of-way is determined by the county engineer to be necessary for future expansion of the public road system, the county engineer shall establish a reserve area reservation line and all building setback and all other zoning code requirements will be established with respect to the reservation line rather than the existing right-of-way line.

(3) If dedication of right-of-way in a short subdivision is required under this title and that dedication results in the loss of one or more lots, SCC 30.23.230(3) may apply to the development.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.145 Requirements for locating utilities within a right-of-way.

(1) Utilities located within a right-of-way shall be installed according to title 13 SCC and the EDDS.

(2) As a condition of approving a proposed development, utility easements that comply with the requirements of the applicable utility district may be required.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.150 Requirements for public access to publicly owned or controlled water bodies.

Public access to publicly owned or controlled water bodies shall be provided according to the Snohomish County Shoreline Management Program and chapter 30.44 SCC.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).

30.24.170 Recommendations of the county engineer.

(1) Recommendations of the county engineer concerning the requirements of chapter 30.24 SCC on development applications shall include written findings of fact and conclusions.

(2) Decisions made by the county engineer pursuant to SCC 30.24.030 shall be made in accordance with SCC 13.01.020(2) and shall not be subject to the provisions of title 30 SCC.

(Added by Amended Ord. 12-049, Oct. 3, 2012, Eff date Jan. 1, 2013).