Article  
31
Article 31. Network, Cross-Access, & Driveway Regulations
Article  
31
Download PDF
contents-31

Article 31. Network, Cross-Access, & Driveway Regulations

31.1 BLOCK AND NETWORK DESIGN STANDARDS

This section contains specifications for street networks, external connectivity, internal connectivity, block length, cross-access, and driveway and street access.

  1. Street Network
    1. A network of interconnected public streets providing both external and internal connectivity is required for new development. The Subdivision, Streets, and Infrastructure Administrator (SSI Administrator), in consultation with the Charlotte Department of Transportation (CDOT), may allow network-required private streets for external and/or internal connectivity in consideration of the conditions below. Any such network-required private street shall have a recorded public access easement.
      1. Site conditions require street geometry not allowed for a public street.
      2. A public street is not needed to enhance the existing public street network.
      3. The proposed street does not stub into an adjacent property.
      4. The proposed street does not connect to an existing street on an adjacent property.
      5. A Charlotte Water line that connects to an adjacent property is not located or proposed to be located within the street right-of-way.
    2. Cemeteries, places of worship, and educational facilities are exempt from the street network requirements. However, if any of these uses are part of a mixed-use development, this exemption shall not apply.
  2. External Connectivity
    1. Existing Street Stubs
      1. Existing adjacent street stubs shall be extended into the development on the stub street’s proper projection.
      2. Any existing and abutting paper street stubs shall be extended into the development on the stub street’s proper projection.
    2. Block Length
      Requirements for additional new collector and local streets shall be determined as follows, using the preferred block length for the applicable Place Type.
      1. The following process shall determine the required number of blocks along the boundary of the development:
      2. Step 1. Identify the applicable Place Type in Table 31-1: Preferred Block Length.
      3. Step 2. Measure the length of each property boundary and for each measurement divide by the preferred block length spacing from Table 31-1.
PROPERTY LINE LENGTH
      1. Step 3. When a fractional number results, round the result down to the nearest whole number.
      2. Step 4. When the result is less than two, but the boundary exceeds the maximum block length (Table 31-2: Maximum Block Length), one local street is required.

Table 31-1: Preferred Block Length

Place TypePreferred Block Length Along Property Boundary
Neighborhood 1600’
Neighborhood 2600’
Neighborhood Center500’
Community Activity Center500’
Regional Activity Center400’
Innovation Mixed Use500’
Manufacturing and Logistics1,500’
Commercial600’
Campus500’
Parks and Preserves1,000’

Table 31-2: Maximum Block Length

Place TypeMaximum Block Length
Neighborhood 1800’
Neighborhood 2650’
Neighborhood Center650’
Community Activity Center650’
Regional Activity Center600’
Innovation Mixed Use650’
Manufacturing and Logistics2,000’
Commercial650’
Campus650’
Parks and Preserves1,500’
      1. Where an odd-shaped parcel has a series of property line lengths shorter than the preferred block length, but separate blocks would be required if the site was measured across (as opposed to along the boundary segments), then a new street or streets shall be required.
      2. Where the extension of non-local and adjacent local streets creates a street network that meets the required number of blocks, no additional new streets are required. However, if the distance from a parcel boundary to the nearest adjacent street exceeds the maximum block length in Table 31-2, then a new street or streets shall be required unless the SSI Administrator determines that a new street or streets are infeasible due to factors such as significant topographical constraints, unusual site-specific conditions related to the land, significant utility constraints, design of the existing street network, and location of existing driveways.
      3. New collector and local streets, if required, shall be located to create the blocks calculated in this section, including any required street stubs.
        1. Align where possible, with existing streets or existing driveways to create four-way intersections.
        2. All new development should provide for more than one access for ingress and egress at the time of development, if feasible.
        3. New street stubs shall be public and shall not be required to stub to existing lots if the SSI Administrator, in consultation with CDOT, determines that the size or shape of the lot makes a future street extension infeasible and/or of little functional value.
      4. The average block length, when measured from centerline to centerline, for an entire site shall not exceed the maximum block length in Table 31-2. No individual block length created by the addition of a new street, except in the Parks and Preserves or Manufacturing and Logistics Place Types, shall exceed 1,000 feet. In the Parks and Preserves Place Type, no individual block length shall exceed 1,500 feet. In the Manufacturing and Logistics Place Type no individual block length shall exceed 2,000 feet.
  1. Internal Connectivity
    1. Once the external connectivity has been established, the external streets shall be connected to create an internal network.
    2. The average block length, when measured from centerline to centerline, for an entire site shall not exceed the maximum block length in Table 31-2. No individual block length, except in the Parks and Preserves or Manufacturing and Logistics Place Types, shall exceed 1,000 feet. In the Parks and Preserves Place Type, no individual block length shall exceed 1,500 feet. In the Manufacturing and Logistics Place Type no individual block length shall exceed 2,000 feet. Exceptions to the maximum individual block length may be allowed as noted in item D below.
    3. The average block length for an entire site, measured from street centerline to street centerline, shall not exceed the maximum block length shown in Table 31-2: Maximum Block Length.
      1. The following streets are not included in the calculation for average block length:
        1. Cul-de-sac streets.
        2. Street stubs.
        3. Streets whose length is determined by the depth of an individual or back-to-back residential lots.
    4. Exceptions to the maximum individual block length may be allowed as noted in Item D below. When an exception for the maximum individual block length has been granted in the Parks and Preserves Place Type, the length of the block will be included in the block averaging calculation based on its length or 1,500 feet, whichever is smaller. When an exception for the maximum individual block length has been granted in the Manufacturing and Logistics Place Type, the length of the block will be included in the block averaging calculation based on its length or 2,000 feet, whichever is smaller. For all other Place Types, when an exception has been granted for the maximum individual block length, the length of the block will be included in the block averaging calculation based on its length or 1,000 feet, whichever is less.
STREETS ELIGIBLE FOR BLOCK AVERAGING CALCULATION
  1. Exceptions to Block Lengths
    1. The SSI Administrator, in consultation with CDOT, may modify the maximum individual block length, eliminating the need for a street stub or paper street when any of the following conditions exist:
      1. A man-made physical barrier to a connection exists, such as a freeway, railroad line, rapid transit line, or gas pipeline.
      2. A natural physical barrier exists, such as areas of steep slopes, wetlands, floodplain, creeks, or streams.
      3. An industrial use is located adjacent to a proposed residential property, allowing future traffic to said industrial use to traverse the residential property to reach a non-local street.
      4. The shape of the property does not allow the requirements to be met.
      5. There are right-of-way, sight distance, or access constraints to providing the recommended spacing.
      6. Accessibility to the subject property or an adjacent property requires modification of the spacing requirements.
      7. Manufacturing, distribution, warehousing, industrial, or security functions do not allow the spacing requirements to be met. Block lengths in the Manufacturing and Logistics Place Type may extend beyond a 2,000 feet individual block length to accommodate for the design of buildings exceeding that length.
      8. It is advantageous to the street network to align a new street with an existing street, major driveway, or traffic signal.
    2. Public parks may, in lieu of providing new streets, provide off-street public paths. This exception does not apply for new arterials and limited access streets indicated on the City of Charlotte Streets Map.
  2. Block Widths
    Block widths shall be sufficient to allow two tiers of lots except where a single tier of lots will facilitate nonresidential development, the separation of nonresidential and residential developments, or the separation of residential development from arterials.

BLOCK WIDTHS
  1. Street Offsets
    Where there is an offset in the alignment of a street across an intersection, the offset of the centerlines shall conform to the standards of the Charlotte Land Development Standards Manual (CLDSM). The SSI Administrator, in consultation with CDOT, may modify this requirement based on analysis of safety and operational conditions.
  2. Cul-De-Sacs and Dead-End Streets
    1. Cul-de-sacs and other permanent dead-ends on public or network-required private streets are subject to SSI Administrator approval and shall only be allowed when supporting documentation shows either:
      1. A natural or man-made barrier, such as a waterway, railroad, any portion of a Rapid Transit Corridor alignment that has been adopted by the Metropolitan Transit Commission (MTC), limited-access expressway, or unusual topography exists which prevents connection; or
      2. When a connection is infeasible due to the site design or land use of abutting property.
    2. Cul-de-sacs shall not be longer than the preferred street spacing in Table 31-1.
    3. A pedestrian and bicycle connection through a cul-de-sac shall be required in the following instances:
      1. When a vehicular connection is impractical, or when environmental conditions make a vehicular connection impractical; or
      2. When a new pedestrian and bicycle connection through a cul-de-sac would connect to an existing pedestrian and bicycle pathway.
      3. The requirement for a pedestrian and bicycle connection through a cul-de-sac, and the associated standards in Section 33.4.C, may be modified or eliminated if the developer/owner can document, and it can be confirmed by the Planning Department in consultation with CDOT, that there are significant topographical or unusual conditions related to the land.
    4. No cul-de-sacs are permitted for properties that are within a ½ mile walk of an existing rapid transit station and zoned IMU, NC, CAC-1, CAC-2, RAC, TOD-TR, TOD-NC, TOD-CC, or TOD-UC. In addition, no cul-de-sacs are permitted for any property zoned UC or UE.
    5. Permanent dead-end streets shall provide for vehicular turn-around mobility consistent with CLDSM standards.
  3. Partial Streets
    On a lot that abuts an existing partial street with new construction of a principal building, the project shall construct the remainder of the partial street. New partial streets shall meet the standards of Tables 34-2 and 34-4.
  4. Traffic Calming
    Wherever a street exceeds the maximum block length provided in Table 31-2, the following conditions shall apply:
    1. For residential wide or office/commercial wide, provide at least one pair of midblock curb extensions, as described in the CLDSM, or another approved slow point.
    2. For all other street types, the developer shall consult with the SSI Administrator about the possible use of other traffic calming devices as available in the CLDSM, or as approved by the CDOT Director.
  5. For traffic calming desired on streets not exceeding the maximum block length the developer shall receive approval from the SSI Administrator, in consultation with CDOT, for use of traffic calming devices as available in the CLDSM, or as approved by the CDOT Director

31.2 CROSS-ACCESS

  1. Purpose and Intent
    1. Cross-access provides direct access between adjacent parcels in order to improve connectivity so that motorists and/or pedestrians do not need to reenter arterial streets in order to gain access to an adjacent site, or to provide safer multi-modal mobility, as determined by the CDOT Director.
    2. Cross-access between adjacent properties reduces vehicular conflicts between motorists on public streets and motorists entering and leaving driveways. Reduced traffic conflicts result in fewer accidents and improved traffic flow on the public streets. The intent of this section is to provide for cross-access between adjacent parcels in order to reduce the number of vehicular trips from arterial streets and improve multi-modal mobility, thereby improving safety for all modes.
  2. Parcels Requiring Cross-Access
    1. Abutting parcels which each front on an arterial street shall provide cross-access between the parcels when the following conditions occur:
      1. Subdivision as defined by Section 30.3.A; or
      2. Construction of a new principal structure.
    2. When a parcel fronting either a collector or a local street abuts a corner lot which has frontages on both the collector or local street and an arterial street, both parcels shall provide cross-access to each other when either actions listed in items B.1.a or B.1.b above occur.
    3. If an abutting parcel is undeveloped or does not currently have cross-access, a cross-access stub connection shall be constructed in order to provide for a future cross-access connection.
    4. Cross-access requirements, and the associated standards found in Section 33.5, may be modified or eliminated by the CDOT Director when it is determined that:
      1. A significant obstruction exists due to a significant natural feature or existing infrastructure; or
      2. Significant topographical differences between abutting parcels prevents potential cross-access connections; or
      3. Existing site conditions make cross-access infeasible and/or present other safety and security factors that give little functional value to cross-access; or
      4. All on-site parking is located within a parking structure and all vehicular access leads directly to the parking structure; or
      5. As provided in Section 32.2.A, the required cross-access is not related to the proposed development’s anticipated transportation impacts or is not roughly proportional to those anticipated impacts.
  3. Exceptions
    The following are excepted from cross-access requirements:
    1. Residential development on properties in the N1-A, N1-B, N1-C, N1-D, or N1-E Zoning Districts.
    2. Development activities in the Parks and Preserves Place Type, the Manufacturing and Logistics Place Type, the Regional Activity Center Place Type located within the I-277 loop, and the TOD-CC, TOD-NC, and TOD-UC Zoning Districts.
    3. Connections between sites in the Manufacturing and Logistics Place Type and sites in the Neighborhood 1 Place Type or Neighborhood 2 Place Type.
  4. Easements
    1. A cross-access easement shall be recorded on the final plat for property involving a subdivision or recorded by separate instrument when no plat is proposed.
    2. Property owners subject to cross-access requirements are responsible for maintaining safe and useable cross-access conditions for pedestrians and vehicles on their site.
    3. Cross-access connections shall not be blocked or obstructed in such a way as to prevent intended pedestrian and vehicular traffic during agreed upon times of access.
    4. Applicants are not required to seek cooperation or permission from the adjacent property owner(s).

31.3 DRIVEWAYS AND STREET ACCESS

  1. Plan Approval Required
    1. No driveway to a public street or network-required private street shall be constructed, relocated, or altered without a plan approval by CDOT. Access to a North Carolina Department of Transportation (NCDOT) maintained street or roadway shall also require an NCDOT Driveway Permit. Single-family uses are exempt from obtaining a driveway plan approval but shall comply with the Charlotte Streets Manual (Streets Manual) and CLDSM and item B.1.c. below.
    2. All driveway design, placement, and construction shall comply with the Streets Manual and CLDSM.
    3. Driveway plan approval shall be required for existing driveways when any of the below actions occur. Any approved driveway plan may also require associated improvements to the driveway itself, the site, and/or roadways.
      1. Subdivision as defined per Section 30.3.A; or
      2. Construction of a new principal structure; or
      3. Change of use for a structure of 5,000 square feet or more in gross floor area or change of use that creates more than 20 additional daily trips; or
      4. Expansion of an existing building by 1,000 square feet; or
      5. Changes to on-site parking layout or on-site circulation.
  2. Access Management
    1. Driveway Location and Placement
      1. An approved driveway location and access shall be determined based upon the Streets Manual.
      2. Driveways shall be in a location with limited negative impact on the traffic flow and operations of the street.
      3. Driveways shall be in a location that does not conflict with or negatively impact the storm drainage system. If other standards require driveway placement in a location such that the storm drainage system would be negatively impacted, the developer is responsible for making alterations to the storm drainage system to mitigate or eliminate the impact. See Section 24.3.A.2 for additional drainage requirements.
      4. Driveways near an un-signalized intersection shall be located a minimum of 75 feet from the intersection. CDOT may reduce this requirement based on analysis of safety and operational conditions of the intersection.
      5. Driveways near a signalized intersection shall be located a minimum of 200 feet from the intersection. If the property frontage is less than 200 feet, CDOT may reduce this requirement based on analysis of safety and operational conditions of the intersection.
      6. CDOT may require existing driveway(s) to be relocated or closed in conjunction with any of the activities pursuant to item A.3 above. Required new curb, amenity zone/planting strip, and/or sidewalk/shared-use path shall be provided where the driveway(s) was previously located. Where sidewalk is added and new or relocated sidewalk is not required along an entire frontage, per Article 32, sidewalk shall be located according to the standards of Article 33 or shall match the adjacent sidewalk along the parcel frontage.
      7. An existing curb cut may be relocated to a new location approved by CDOT if the existing curb cut is eliminated, new curb is constructed, and an amenity zone/planting strip and sidewalk/shared-use path is provided where the driveway was previously located.
      8. A new driveway is prohibited for an existing development that already has access to a street from an existing driveway, unless CDOT determines there is a significant operational or circulation issue.
    2. Access Restrictions
      1. Plan approval may include imposing driveway access restrictions that limit vehicular movements to less than full-movement in order to provide safe and efficient street operations.
      2. Driveway access shall be limited to less than full movement under any of the following conditions:
        1. The proposed access location is within 200 feet of a signalized intersection.
        2. The proposed access location is within the physical limits of existing or future single or dual left-turn lanes.
        3. The proposed access is near an intersection or street section where a safety and/or street operations problem exists.
        4. The proposed access does not meet sight distance requirements of item D below.
        5. Other circumstances where full movement at the proposed access location will negatively impact safe and efficient street operations, as determined by CDOT.
      3. CDOT may reduce access restrictions based on analysis of safety and operational conditions.
  3. Driveway Alignment and Internal Access
    1. Channelization and design of internal access shall comply with the Streets Manual.
    2. The angle of a driveway intersection with the public or network-required private street shall be 90 degrees. A reduced angle of no less than 75 degrees may be approved by CDOT if any of the following conditions exist:
      1. Topographical challenges.
      2. Natural features.
      3. Existing right-of-way constraints.
      4. Existing building(s) to remain.
    3. New driveways shall align with existing streets and existing driveways where possible to create four-way intersections.
  4. Sight Distance
    1. General
      1. All driveways shall provide sight distance as described in the Streets Manual.
      2. All driveways shall meet American Association of State Highway and Transportation Officials (AASHTO) Intersection Sight Distance Requirements.
    2. Required Sight Triangles at Public Street Intersections
      The standards below regulate sight triangles for intersections of public streets, network-required private streets, and Type III driveways with connections to public streets.
      1. Dimension of Sight Triangles
        A sight triangle applies to land abutting these intersections as follows:
        1. A sight triangle bounded on two sides by curb, measured in each direction along the back of curb for 50 feet from the midpoint of the radius of the back of curb, and on the third side by a diagonal line connecting the ends of each measured 50 foot side. Where there is no curb, the pavement edge shall be used for these measurements.
        2. In addition to the above, in other than 90 degree intersections or where grades mandate, the Charlotte Department of Transportation (CDOT) may impose additional sight triangles under the standards adopted by the American Association of State Highway Transportation Officials (AASHTO).
SIGHT TRIANGLE AT PUBLIC STREET INTERSECTION
      1. Restrictions for Sight Triangles at Public Street Intersections
        Within established sight triangles, no structure, sign, parking space, landscaping, tree, berm, fence, wall, or other object of any kind shall be installed, constructed, set out, or maintained so as to obstruct visibility at a level between 30 and 72 inches above the level of the center of the intersection.
      2. Exceptions to Restrictions for Sight Triangles at Public Street Intersections
        1. The sight triangle restriction shall not apply to:
          1. Existing natural grades, which, by reason of natural topography, rise 30 or more inches above the level of the center of the adjacent intersection.
          2. Trees having limbs and foliage trimmed in such a manner that no limbs or foliage extend into the area between 30 and 72 inches above the level of the center of the abutting intersection.
          3. Fire hydrants, public utility poles, street markers, and traffic control devices.
          4. The sight triangles at street intersections shall not apply to structures located in the N2-C, NC, CAC-2, RAC, UC, UE, TOD-UC, TOD-NC, TOD-CC, IMU, IC-2, and RC Zoning Districts.
      3. Additional Sight Distance Requirements at Public Street Intersections
        Additional sight distance requirements may apply per the CDOT Director or North Carolina Department of Transportation (NCDOT) standards, as applicable.
    1. Required Sight Triangles for Other Connections
      The standards below regulate sight triangles for driveway connections to public or network-required private streets.
      1. Dimension of Sight Triangles at Other Connections
        A sight triangle applies to land abutting these intersections as follows:
        1. A ten foot by ten foot sight triangle shall be established on each side of a connection.
        2. The sight triangle shall be measured from the edge of the public right-of-way or the back of the sidewalk, whichever is greater, and the closest edge of a connection. Where public right-of-way does not exist, the sight triangle shall be measured from the back of the required sidewalk and the closest edge of the connection.
SIGHT TRIANGLE AT OTHER CONNECTIONS
      1. Restrictions for Sight Triangles at Other Connections
        Within established sight triangles, no structure, sign, parking space, landscaping, tree, berm, fence, wall, or other object of any kind shall be installed, constructed, set out, or maintained so as to obstruct visibility at a level between 30 and 72 inches.
        1. Landscape and/or decorative walls may be in a sight triangle but shall not exceed 30 inches in combined overall height.
        2. The sight triangle restriction shall not apply to trees having limbs and foliage trimmed in such a manner that no limbs or foliage extend into the area between 30 and 72 inches above the level of the center of the abutting intersection.
    1. Authority
      The Director of the Charlotte Department of Transportation may waive all or part of the requirements in items 2 and 3 above, where a waiver would not constitute a traffic hazard or a condition dangerous to public safety. The Director of the Charlotte Department of Transportation shall also investigate violations, issue notices and orders, and perform other required enforcement duties related to the requirements in items 2 and 3 above.
  1. RESERVED
  2. Turn Lanes
    Turn lanes for driveways shall be required as described in the Streets Manual.
  3. Payment for Traffic Signal Installation or Modifications
    If a plan approval related to a driveway requires modifications to an existing traffic signal or installation of a new traffic signal, the property owner/developer shall pay for the traffic signal improvements. Additionally, the property owner/developer shall obtain, if necessary, and dedicate the associated right-of-way. Details shall be defined in a Signal Agreement, as described in the Streets Manual.
  4. Restrictions on Residential Driveways
    Driveway access to arterials shall be prohibited from single-family, duplex, triplex, or quadraplex lots that also front on a collector or local street.