(a) 
Generally.
The arrangement, character, extent, width, grade and location of all streets shall conform to the city’s thoroughfare plan and TCSS, and shall be considered in their relation to existing and planned streets or driveways (whether within the city, within its exterritorial jurisdiction area, or within adjacent municipal or county areas), to topographical conditions, to public safety, and in their appropriate relation to the proposed uses of the land to be served by such streets. Reserve or residual strips of land controlling access to or egress from other property, or to or from any street or alley, or having the effect of restricting or damaging the adjoining property for subdivision purposes, or which will not be taxable or accessible for improvements shall not be permitted in any subdivision unless such are required by the city in the public interest (such as to enhance public safety or other public interest). All streets shall be constructed in accordance with article 28.05 of this chapter and with the city’s TCSS.
(b) 
Street layout.
Proposed streets shall provide a safe, convenient and functional system for vehicular and pedestrian circulation, shall be properly related to the thoroughfare plan and any amendments thereto, and shall be appropriate for the particular traffic characteristics of each proposed subdivision or development. All streets shall be open and unobstructed at all times. The layout of the street network shall, to the greatest extent possible, be sited and aligned along natural contour lines, and shall minimize the amount of cut and fill on slopes in order to minimize the amount of land area that is disturbed during construction, thereby helping to reduce stormwater runoff and preserve natural, scenic characteristics of the land.
(c) 
Adequacy of streets and thoroughfares.
(1) 
Responsibility for adequacy of streets and thoroughfares.
The property owner shall assure that the subdivision is served by adequate streets and thoroughfares, and shall be responsible for the costs of rights-of-way and street improvements, in accordance with the policies and standards in this subsection (c), and subject to the city’s cost participation policies on oversized facilities.
(2) 
General adequacy policy.
Every subdivision shall be served by improved streets and thoroughfares adequate to accommodate the vehicular traffic to be generated by the development. Proposed streets shall provide a safe, convenient and functional system for traffic circulation; shall be properly related to the city’s thoroughfare plan, road classification system, comprehensive plan and any amendments thereto; and shall be appropriate for the particular traffic characteristics of each development.
(3) 
Road network.
New subdivisions shall be supported by a road network having adequate capacity, ingress/egress, and safe and efficient traffic circulation. The adequacy of the road network for developments of 100 or more dwelling units, or for developments generating 1,000 or more “one-way” trips per day, or for developments involving collector or arterial streets not appearing on the city’s adopted thoroughfare plan, shall be demonstrated by preparation and submission, prior to or along with the construction plat application, of a traffic impact analysis prepared in accordance with subsection (f) of this section, which takes into consideration the need to accommodate traffic generated by the development, land to be developed in common ownership and other developed property. In the event that the property to be developed is intended as a phase in a larger development project, or constitutes a portion of the land to be ultimately developed, the city council may require a demonstration of adequacy pursuant to this section for additional phases or portions of the property as a condition of approval for the proposed construction plat. In the event that the applicant submits a traffic impact analysis for an entire phased development project, the city may require an update of the study for each subsequent phase of the development which reflects any applicable changed conditions. If the construction plat is in conformance with the thoroughfare plan and if the construction plat is for a development of less than 100 dwelling units or for a development generating less than 1,000 “one-way” trips per day, then a traffic impact analysis is not required.
(4) 
Approach roads and access.
All subdivisions must have at least two points of vehicular access (primarily for emergency vehicles), and must be connected via improved roadways to the city’s improved thoroughfare and street system by one or more approach roads of such dimensions and improved to such standards as are hereinafter set forth. Requirements for dedication of right-of-way and improvement of approach roads may be increased depending upon the size or density of the proposed development, or if such need is demonstrated by traffic impact analysis.
(A) 
“Two points of vehicular access” shall be construed to mean that the subdivision has at least two improved roads accessing the subdivision from the city’s improved thoroughfare system, and the subdivision has at least two road entrances. The city council may, at its discretion and upon a finding that such will not compromise public safety or impede emergency access, accept a single median divided entrance from the city’s improved thoroughfare system provided that the median extends into the subdivision for an unbroken length of at least 100 feet to an intersecting internal street which provides at least two routes to the interior of the subdivision. For example, the entrance street is not a dead-end or cul-de-sac, and it does not create a “bottleneck” allowing only one emergency route into the interior of the subdivision. Residential lots may not front onto any median divided street section, and residential driveways may not be located in front of a median. (Also see subsection (u) of this section.)
(B) 
The subdivision shall be designed to provide adequate emergency access for public safety vehicles. Each residential lot in the subdivision shall have a minimum frontage on a dedicated public street as required by applicable zoning or 35 feet, whichever is greater, unless other provisions have been authorized through planned development approval. Each nonresidential lot shall have a minimum frontage on a dedicated public street as required by applicable zoning or 50 feet, whichever is greater, unless other provisions have been authorized through planned development approval.
(5) 
Off-site improvements.
Where traffic impact analysis demonstrates the need for such facilities, or where the city believes public safety is at risk, the property owner shall make such improvements to off-site collector and arterial streets and intersections as are necessary to mitigate traffic impacts generated by the development or in conjunction with related developments. The city may participate in the costs of oversized improvements with the property owner as set out herein, and subject to the city’s cost participation policies on oversized improvements.
(6) 
Street dedications.
(A) 
Dedication of right-of-way.
The property owner shall provide all rights-of-way required for existing or future streets, and for all required street improvements, including perimeter streets and approach roads, as shown in the thoroughfare plan and as required by the TCSS or by other valid development plans approved by the city council. In the case of perimeter streets, half of the total required right-of-way width for such streets shall be provided unless the proposed development is on both sides of the street, in which case the full right-of-way width shall be provided, or unless there is some other compelling reason to require more than half of the right-of-way width (such as avoiding the infringement upon or demolition of existing structures, avoiding crossing a creek or floodplain or some other obstacle, or other similar circumstance). In some instances, more than half of the required width shall be required when a half street is impractical or unsafe and depending upon the actual or proposed alignment of the street, such as in the case of a curved street, as may be required by the city council.
(B) 
Perimeter streets.
Where an existing half-street is adjacent to a new subdivision or addition, the other half of the street shall be dedicated, and an appropriate amount of the street shall be improved, by the developer of the new subdivision or addition.
(C) 
Slope easements.
The dedication of easements, in addition to dedicated rights-of-way shall be required whenever, due to topography, additional width is necessary to provide adequate earth slopes. Such slopes shall be no steeper than three feet horizontal run to one foot vertical height, or a three-to-one slope.
(7) 
Street construction.
All streets and thoroughfares shall be constructed and paved to city standards and within rights-of-way as required by the thoroughfare plan and this chapter, and in accordance with the TCSS and other city standards as may be from time to time amended or adopted.
(8) 
Intersection improvements and traffic-control devices.
These devices shall be installed as warranted in accordance with the traffic impact analysis required by subsection (f) of this section, or as may be required by the city for traffic safety and efficiency. Construction and design standards shall be in accordance with city standards and the TCSS.
(9) 
Phased development.
Where a subdivision is proposed to occur in phases, the applicant, in conjunction with submission of the construction plat, shall provide a schedule of development. The schedule shall set forth the intended plan of development and dedication of rights-of-way for streets and street improvements, whether on-site or off-site, intended to serve each proposed phase of the subdivision. The city council shall determine whether the proposed streets and street improvements are adequate pursuant to standards herein established, and may require that a traffic impact analysis be submitted for the entire project or such phases as the city council determines to be necessary to adjudge whether the subdivision will be adequately served by streets and thoroughfares.
(10) 
Private streets.
New subdivisions may not be constructed with private streets, nor may an existing subdivision’s public streets be converted to private ownership. Any private street subdivisions that were in existence (i.e., platted of record at the county) on the effective date of the ordinance from which this chapter is derived shall be allowed to remain as private street subdivisions provided that the conditions of the private streets and the maintenance thereof continues to meet or exceed city standards, and provided that a viable homeowners’ association (HOA) continues to exist to maintain the private streets and all appurtenances. The city will not assist in enforcing deed restrictions. The city may periodically inspect private streets, and may require any repairs necessary to ensure efficient emergency access and to protect the public health, safety, convenience and welfare.
(A) 
Private streets: Construction and maintenance cost.
The city shall not pay for any portion of the cost of constructing or maintaining a private street.
(B) 
Private streets: Traffic-control devices.
All private traffic-control devices and regulatory signs shall conform to the “Texas Manual of Uniform Traffic Control Devices,” as amended, and to city standards.
(C) 
Private streets: Restricted access.
The entrances to all private streets shall be clearly marked with a sign, placed in a prominent and visible location, stating that the streets within the subdivision are private, and that they are not maintained nor regularly patrolled by the city. All restricted access entrances shall be manned 24 hours every day, or they shall provide a reliable, alternative means of ensuring access into the subdivision by the city, by emergency service providers, and by other utility or public service providers, such as postal carriers and utility companies, with appropriate identification. The method to be used to ensure city and emergency access into the subdivision shall be approved by the city’s fire department and by any other applicable emergency service providers. If the association fails to maintain reliable access as required herein, the city may enter the private street subdivision and remove any gate or device which is a barrier to access at the sole expense of the association.
(D) 
Private streets: Waiver of services.
Certain city services may not be provided for private street subdivisions. Among the services which may not be provided are: routine law enforcement patrols, enforcement of traffic and parking regulations, and preparation of accident reports. Depending upon the characteristics of the development and upon access limitations posed by the design of entrances into the subdivision, other services (such as sanitation) may not be provided, as well.
(E) 
Private streets: Petition to convert to public streets.
The property owners’ association may petition the city to accept private streets and any associated property as public streets and right-of-way upon written notice to all association members and upon the favorable vote of a majority of the membership. However, in no event shall the city be obligated to accept said streets as public. Should the city elect to accept the streets as public, then the city has the right to inspect the private streets and to assess the lot owners for the expense of needed repairs concurrent with the city’s acceptance of the streets. The city shall be the sole judge of whether repairs are needed. The city may also require, at the association’s or the lot owner’s expense, the removal of any guard houses, access control devices, landscaping or other aesthetic amenities located within the street lot or within any other common area.
(F) 
Private streets: Hold harmless.
The property owners’ association, as owner of the private streets and appurtenances, shall release, indemnify, defend and hold harmless the city, any other governmental entity, and any public utility entity for damages to the private streets that may be occasioned by the reasonable use of the private streets by same, and for damages and injury (including death) arising from the condition of the private streets, out of any use of access gates or cross-arms, or out of any use of the subdivision by the city or governmental or utility entity.
(d) 
Escrow policies and procedures.
(1) 
Request for escrow.
Whenever this chapter requires a property owner to construct a street or thoroughfare, or other type of public improvement, the property owner may, if there exist unusual circumstances, such as a timing issue due to pending roadway improvements by another agency such as the state department of transportation or the county, that would present undue hardships or that would impede public infrastructure coordination or timing, petition the city to construct the street or thoroughfare, usually at a later date, in exchange for deposit of escrow as established in this section. If more than one street or thoroughfare must be constructed in order to meet adequacy requirements for roadways, as demonstrated by a traffic impact analysis, the city manager (or designee) may prioritize roadways for which escrow is to be accepted and require the deposit of all funds attributable to the development in escrow accounts for one or more of such affected roadways. The city council shall review the particular circumstances involved (a traffic impact analysis may be required to facilitate the city council’s deliberations on the matter), and shall determine, at its sole discretion, whether or not provision of escrow deposits will be acceptable in lieu of the property owner’s obligation to construct the street or thoroughfare with his or her development.
(2) 
Escrow deposit with city.
Whenever the city council agrees to accept escrow deposits in lieu of construction by the owner of the property under this chapter, the property owner or developer shall deposit in escrow with the city an amount equal to his share of the costs of design, construction, permits, reviews and approvals, inspections, any additional land acquisition, and an appropriate (and realistic) inflation factor to ensure that the actual “future dollar” costs will be covered when actual construction occurs in the future. Such amount shall be reviewed and approved by the city manager (or designee) and by the city engineer, and shall be paid prior to release of engineering plans by the city engineer. The obligations and responsibilities of the property owner shall become those of the property owner’s transferees, successors and assigns; and the liability therefor shall be joint and several.
(3) 
Determination of escrow amount.
The amount of the escrow shall be determined by using the maximum comparable “turnkey” bid price of construction of the improvements (including design, permits, reviews and approvals, inspections and any additional land acquisition that may be needed). Such determination of the escrow amount shall be made as of the time the escrow is due hereunder, and shall be subject to the review and approval of the city manager (or designee) and the city engineer.
(4) 
Termination of escrow.
Escrows, or portions of escrowed amounts, which have been placed with the city under this section and which have been held for a period of ten years from the date of such payment or agreement, in the event that the city has not authorized the preparation of plans and specifications for construction of such roadway facilities for which the escrow was made, shall, upon written request, be returned to the property owner, along with one-half of its accrued interest. Such return does not remove any obligations of the property owner for construction of the required facilities if a building permit has not been issued on the subject lot or if a new building permit is applied for.
(5) 
Refund.
If any street or highway for which escrow is deposited is constructed by a party other than the city, or is reconstructed by another governmental authority at no cost to the city, the escrowed funds and accrued interest shall be refunded to the property owner or applicant who originally paid the escrow amount after completion and acceptance of the public improvements. In the event that a portion of the cost is borne by the city and the other portion of the cost by another party or governmental authority, the difference between the property owner’s actual proportionate cost and the escrowed funds, including accrued interest, if any, shall be refunded after completion and acceptance of the improvements.
(6) 
Interest limitation.
If money is refunded within six months of deposit, only the principal will be refunded. Monies returned after this date will be refunded with one-half of its accrued interest.
(e) 
Traffic impact analysis.
Any proposed development project or plat involving a significant change to a proposed roadway alignment from that shown on the city’s thoroughfare plan (or involving a development of 100 or more dwelling units, or for developments generating 1,000 or more “one-way” trips per day) shall be preceded by submission, city staff and planning and zoning commission review, and city council approval of a traffic impact analysis as specified in subsection (f) of this section. Such a proposed roadway alignment change shall also be preceded by (or simultaneous with) an amendment to the city’s thoroughfare plan showing the new proposed alignment. Failure to provide for such approvals prior to submission of a construction plat (or concurrently with the construction plat application) shall be grounds for denial of the plat application.
(f) 
Required components of traffic impact analysis.
Whenever this chapter (or the city council, in unique instances which do not necessarily meet the above criteria but which may significantly affect the public health, safety or welfare, such as a proposed subdivision that will only be accessed via substandard roadways which may pose an impediment to emergency response vehicles) require submission and city council approval of a traffic impact analysis, the following elements shall be included:
(1) 
General site description.
The traffic impact analysis shall include a detailed description of the roadway network within one mile of the site, a description of the proposed land uses, the anticipated states of construction, and the anticipated completion date of the proposed land development shall be provided. This description, which may be in the form of a map, shall include the following items:
(A) 
All major intersections;
(B) 
All proposed and existing ingress and egress locations;
(C) 
All existing roadway widths and rights-of-way;
(D) 
All existing traffic signals and traffic-control devices; and
(E) 
All existing and proposed public transportation services and facilities within a one-mile radius of the site.
(2) 
Proposed capital improvements.
The traffic impact analysis shall identify any changes to the roadway network within one mile of the site that are proposed by any government agency or other developer. This description shall include the above items as well as any proposed construction project that would alter the width or alignment of roadways affected by the proposed development.
(3) 
Roadway impact analysis.
(A) 
Transportation impacts.
(i) 
Trip generation.
The average weekday trip generation rates (trip ends), the average weekend trip generation rates (for uses other than residential or institutional), the highest average a.m. and p.m. hourly weekday trip generation rates, and the highest hourly weekend generation rates (for uses other than residential or institutional) for the proposed use shall be determined based upon the trip generation rates contained in the most recent edition of the Institute of Transportation Engineers’ Trip Generation book; or shall be based upon data generated by actual field surveys of area uses compatible to the proposed use and approved by the city manager (or designee) and the city engineer.
(ii) 
Trip distribution.
The distribution of trips to arterial and collector roadways within the study area identified in subsection (f)(1) of this section (general site description) shall be in conformity with accepted traffic engineering principles, taking into consideration the land use categories of the proposed development; the area from which the proposed development will attract traffic; competing developments (if applicable); the size of the proposed development; development phasing; surrounding existing and anticipated land uses, population and employment; existing and projected daily traffic volumes; and existing traffic conditions identified pursuant to subsection (f)(1) of this section.
(B) 
Adequacy determination.
The roadway network included within the traffic impact analysis shall be considered adequate to serve the proposed development if existing roadways identified as arterials and collectors can accommodate the existing service volume, and the service volume of the proposed development, and the service volume of approved but unbuilt developments holding valid, unexpired building permits at a level of service “C” or above.
(4) 
Intersection analysis.
(A) 
Level of service analysis.
For intersections within the roadway traffic impact analysis area described in subsection (f)(1) of this section (general site description), a level of service analysis shall be performed for all arterial to arterial, arterial to collector, collector to arterial, and collector to collector intersections, and for any other pertinent intersections identified by the city manager (or designee) or by the city engineer. Also, level of service analyses will be required on all proposed site driveway locations for all nonresidential developments. The city may waive analysis of minor intersections and site driveway locations within the one-mile radius. The level of service analysis shall be based upon the highest hourly average a.m. or p.m. peak weekday volume or highest average hourly peak weekend volume as determined from a two-day survey of weekday volumes and, where necessary, a one-day survey of weekend volumes. The level of service analysis shall take into consideration the lane geometry, traffic volume, percentage of right-hand turns, percentage of left-hand turns, percentage (and typical size) of trucks, intersection width, number of lanes, signal timing and progression, roadway grades, pedestrian and bicycle flows, school routes, number of accidents, and peak hour factor.
(B) 
Adequacy analysis.
The intersections included within the traffic impact analysis shall be considered adequate to serve the proposed development if existing intersections can accommodate the existing service volume, the service volume of the proposed development, and the service volume of approved but unbuilt developments holding valid, unexpired building permits at level of service “C” or above.
(5) 
Effect of adequacy determination.
If the adequacy determination for roadways and intersections indicates that the proposed development would cause a reduction in the level of service for any roadway or intersection within the study area identified in subsection (f)(1) of this section that would cause the roadway to fall below the level of service required hereto, the proposed development shall be denied unless the developer agrees to one of the following conditions:
(A) 
The deferral of building permits until the improvements necessary to upgrade the substandard facilities are constructed;
(B) 
A reduction in the density or intensity of development;
(C) 
The dedication or construction of facilities needed to achieve the level of service required herein; or
(D) 
Any combination of techniques identified herein that would ensure that development will not occur unless the levels of service for all roadways and intersections within the traffic impact analysis study are adequate to accommodate the impacts of such development.
(g) 
Arrangement of streets not shown on the thoroughfare plan.
For streets that are not shown on the city’s thoroughfare plan, such as local residential streets, the arrangement of such streets within a subdivision shall:
(1) 
Provide for the continuation or appropriate projection of existing streets from or into surrounding areas;
(2) 
Conform to a plan for the neighborhood approved or adopted by the city council to meet a particular situation where topographical or other conditions make continuance or conformity to existing streets impractical;
(3) 
Provide for future access, such as by stubbing streets for future extension, to adjacent vacant areas which will likely develop under a similar zoning classification or for a similar type of land use; and
(4) 
Not conflict in any way with existing or proposed driveway openings (including those on the other side of an existing or planned median-divided arterial, in which case new streets shall align with such driveway openings such that median openings can be shared).
(h) 
Residential collector streets and minor residential streets.
Streets shall be laid out such that their use by through traffic will be discouraged, such as via circuitous routes or multiple turns or offsets, but such that access is provided to adjacent subdivisions.
(1) 
Wherever the right-of-way width of a collector or residential street must transition to a greater or lesser width, such transition shall occur along the front, side or rear lot lines of adjacent lots (for a reasonable distance) and shall not occur within the street intersection itself. In other words, the right-of-way width shall be the same on both sides of the street intersection.
(2) 
To the greatest extent possible, the number of lots fronting along residential collector streets shall be minimized in order to ensure adequate traffic safety and efficiency. No more than 20 percent of the total centerline length of a collector street may have residential lots fronting onto the collector on each side of the street. For example, a collector street having a total centerline length (from one terminus to another) of 1,000 feet may have lots fronting onto it with a total frontage distance of 200 feet on each side of the street. Calculations shall be submitted with the construction plat application (and provided to the city planner and city engineer) verifying that lots fronting onto a collector street do not exceed the provisions in this subsection.
(3) 
At least 50 percent of the total centerline length of all streets (including collector streets) within a residential subdivision (or within each phase of a residential subdivision, unless otherwise approved by the city council to apply to the subdivision in its entirety rather than each individual phase) shall be curvilinear in design (per Plano’s standards) except the minimum centerline radius for residential streets shall be 150 feet. Calculations shall be submitted with the construction plat application (and provided to the city planner and city engineer) verifying that the above curvilinear street requirement is being met.
(i) 
Subdivision containing arterial street.
Where a subdivision abuts or contains an existing or proposed arterial street, the city council may require marginal access streets, reverse frontage (lots which back onto the arterial), deep lots with rear service alleys, or such treatment as may be necessary for adequate protection of residential properties and to afford separation of through and local traffic.
(j) 
Reserve strips.
Reserve strips controlling access to streets shall be prohibited except where their control is required by the city and approved by the city council.
(k) 
Centerline offsets.
Intersecting, undivided streets with centerline offsets of less than 150 feet shall be avoided. Intersecting streets onto an existing or future divided roadway must be configured such that the centerline offset will accommodate the appropriate median opening and left-turn lanes (with required transition and stacking distances) on each divided roadway, and shall be aligned with any existing or proposed streets or driveways on the opposite side of the divided roadway (in order to share the median opening).
(l) 
Street intersections.
A street intersection with a major thoroughfare shall be at a 90-degree angle and shall be tangent to the intersecting street for at least 100 feet. All other street intersections shall be laid out so as to intersect as nearly as possible at a 90-degree angle or radial to the centerline of the intersecting street for the full right-of-way width of the intersecting street, and tangent to the intersecting street for at least 50 feet. No street shall intersect at an angle that is less than 85 degrees.
(m) 
Street right-of-way widths.
Street right-of-way widths shall be as shown on the thoroughfare plan and as defined by the corresponding roadway cross-sections on the thoroughfare plan and in the city’s TCSS manual.
(n) 
Half streets.
Construction of half streets shall be prohibited, except when essential to the reasonable development of the subdivision in conforming with the other requirements of this chapter and the thoroughfare plan, and where the city council makes a determination that there is no immediate benefit to be gained by constructing the full street section since no access from the street will be needed by the subdivision in question. The city council may also find that it would be more practical, or cost effective, to delay construction of the other half of a street until when the adjoining property is developed. If the property owner is responsible for one-half of the street, then the property owner shall either construct the facility along with his development or shall provide escrow for the construction cost of his share of the facility (including all applicable street appurtenances such as median openings, left-turn lanes into the development, sidewalks with barrier-free ramps, drainage structures and the like) unless the city participates in the construction of the facility. Whenever a partial street has been previously platted along a common property line, the other portion of the street right-of-way shall be dedicated such that the right-of-way is increased to the street’s ultimate planned width. Improvements shall be made to all on-site facilities as defined herein (see definitions, section 28.01.013).
(o) 
Maximum length of blocks or street segment.
The maximum length of any block or street segment (including a looped street) shall be 1,600 feet and the minimum length of any block or street segment shall be 400 feet, as measured along the street centerline and between the point of intersection with other through, but not dead-end or cul-de-sac, streets.
(p) 
Maximum length of cul-de-sac.
A cul-de-sac street shall not be longer than 600 feet, and at the closed end shall have a turnaround bulb with an outside pavement diameter of at least 80 feet and a right-of-way diameter of at least 100 feet. The length of a cul-de-sac shall be measured from the centerline of the intersecting street to the centerline of the cul-de-sac bulb.
(q) 
Waiver or suspension for overlength streets or cul-de-sacs.
The commission may recommend, and the city council may approve, waivers/suspensions for overlength streets or cul-de-sacs, whether temporary or permanent, upon considering the following:
(1) 
Alternative designs which would reduce street or cul-de-sac length;
(2) 
The effect of overlength streets upon access, congestion, delivery of municipal services, and upon convenience to residents of the subdivision in traveling to and from their homes; and
(3) 
Means of mitigation, including but not limited to additional midblock street connections, limitation on the number of lots to be served along an overlength street segment or cul-de-sac, temporary (or permanent) points of emergency access, and additional fire protection measures.
(r) 
Dead-end streets.
Except in unusual cases, no dead-end streets will be approved unless such dead-end streets are provided to connect with future streets on adjacent land. In the case of dead-end streets which will eventually be extended into the adjacent subdivision, no more than one lot (per side) can front onto the dead-end street stub unless a temporary turnaround bulb (with the appropriate temporary street easement) is provided at the end. A temporary dead-end street shall not exceed the maximum allowed length of a normal cul-de-sac, and the temporary turnaround bulb must be constructed like a cul-de-sac, as provided in subsection (p) of this section (the city engineer may authorize the use of asphalt or durable paving material other than concrete for the arc, or “wing,” portions of the temporary turnaround bulb in order to minimize the cost of removing those portions later on). A note shall be placed on the final plat clearly labeling any temporary dead-end streets (if any) that will at some point be extended into the adjacent property, and signage shall be placed at the end of the constructed street stub, such as on the barricade, also stating that the street will be extended in the future. Signage and lettering must be large enough to be legible by a person with normal vision at a 20-foot distance. Any required temporary turnaround easements shall be shown on the final plat along with their appropriate recording information, if they are off-site or established by separate instrument.
(s) 
Names of new streets.
New streets which extend existing streets shall bear the names of the existing streets, and shall be dedicated at equal or greater right-of-way widths than the existing streets for an appropriate transition length, if applicable.
(t) 
Construction of streets.
All streets shall be constructed in accordance with paving widths and specifications as set forth in the TCSS of the city at the time at which the construction plat application is officially submitted and deemed a complete application.
(u) 
Points of access.
All subdivisions shall have at least two points of access from improved public roadways (also see subsection (c)(4) of this section). All residential developments shall provide no less than one entrance for every 50 lots, or portion thereof, including temporary dead-end stubbed streets that will eventually provide connections into adjacent future developments and thence to an arterial or collector street. Driveway access onto roadways shall be provided and designed in accordance with the city’s TCSS and construction standards that are in effect at the time the construction plat application is officially submitted and deemed a complete application. Residential driveway cuts shall not be allowed on roadways that are larger than a residential collector street (60-foot right-of-way) unless specifically approved by the city council with the construction plat application.
(2006 Code, sec. 70-71; Ordinance 02-09-549, sec. 3.1, adopted 9/3/02; Ordinance adopting 2015 Code)
(a) 
Minimum right-of-way and pavement width.
Service alleys in nonresidential districts, if provided or constructed by the developer, shall be a minimum right-of-way width of 30 feet and a pavement width of 24 feet.
(b) 
Standards.
In the interest of reducing stormwater runoff and resultant erosion, sedimentation and conveyance of nonpoint source pollutants, residential alleys shall be prohibited in single-family subdivisions within the city and its extraterritorial jurisdiction, and shall only be permitted or required in instances where a subdivision must connect into existing alleys for the purpose of providing continuity or convenience. If alleys are permitted or required, the following standards shall be met: In residential districts, alleys shall be parallel, or approximately parallel, to the frontage of the street. Alleys in residential districts shall provide a minimum of 15 feet of right-of-way and ten feet of pavement.
(c) 
General design standards for alleys (if provided).
(1) 
Alleys shall be paved in accordance with the city TCSS and construction standards that are in effect at the time the construction plat application is officially submitted and deemed a complete application.
(2) 
Where the deflection of alley alignment occurs, the design of the paving and property line shall be as established by the TCSS.
(3) 
Dead-end or “hammerhead” alleys shall not be allowed. Alleys must have adequate turnouts and street entrances such that vehicular traffic flow is continuous and efficient. Where a temporary dead-end alley situation is unavoidable, a temporary turnaround bulb or turnout onto a street, either of which will need a temporary easement for street or alley purposes, shall be provided as determined by the city engineer.
(4) 
Alleys may not exceed a maximum length of 1,600 feet, as measured along the centerline of the alley and between intersections with other alleys or entrances onto streets (at the right-of-way line of the street at the alley entrance). The commission may recommend, and the city council may approve, waivers/suspensions for overlength alleys upon consideration of the following:
(A) 
Alternative designs which would reduce alley length;
(B) 
The effect of overlength alleys upon access, congestion, delivery of municipal services, and upon convenience to residents of the subdivision in accessing rear driveways and in driving around to the front of their homes; and
(C) 
Means of mitigation, including but not limited to additional mid-block alley turnouts, limitation on the number of lots to be served along a single alley segment, temporary points of access, and additional fire protection measures.
(5) 
Alley intersections shall be perpendicular and at a 90-degree angle or radial to the intersecting alley centerline for the full alley right-of-way width, and intersection pavement shall be of sufficient width and inside radius to accommodate waste collection and emergency vehicles. Intersections shall be three-way wherever possible, and four-way intersections shall be avoided. No alley intersection serving more than four directions shall be allowed.
(2006 Code, sec. 70-72; Ordinance 02-09-549, sec. 3.2, adopted 9/3/02)
(a) 
The minimum width for city utility easements shall be 15 feet or as otherwise required by the city engineer. The minimum width for city drainage easements shall be as required by the city engineer. The width of easements for other utility providers, such as for gas, electric, telephone or cable television, shall be as required by that particular entity. It shall be the applicant’s responsibility to determine appropriate easement widths required by other utility companies (also see section 28.03.008). Wherever possible, easements shall be centered or along front or side lot lines rather than across the interior or rear of lots, particularly where no alleys will be provided behind the lots.
(b) 
Where a subdivision is traversed by a watercourse, drainageway or channel, there shall be provided a storm drainage easement or right-of-way conforming substantially with such course and of such additional width as may be designated by the city engineer, subject to determination according to proper engineering considerations. The required width shall conform to the requirements set forth by the Federal Emergency Management Agency (FEMA), the U.S. Army Corps of Engineers, and/or the city. Parallel streets or parkways shall be required adjacent to certain portions of creeks or drainageways to provide maintenance access and/or public access and visibility into public open space or recreation areas (see article 28.04 of this chapter). The number of lots that back or side onto creeks, drainageways, public parks and open spaces, and public school sites shall be severely limited, and possibly prohibited, such that public access, visibility, safety and security within these areas are maximized. Other utilities may be permitted within a drainage or floodway easement only if approved by the city engineer and any other applicable entity requiring the drainage or floodway easement.
(c) 
A lot’s area shall be computed inclusive of all easements. However, there shall be a minimum buildable area, exclusive of required easements, buffer zones and setbacks for each lot. The minimum buildable area shall be an area one-half of the required minimum lot size. If the city disputes the buildable area of any lot, the applicant shall submit verification in writing that the buildable area is adequate for the type of housing product (or nonresidential building) proposed for that lot. Final approval of the allowed buildable area for any lot shall be by the city.
(d) 
Where alleys are not provided in a residential subdivision, a minimum ten-foot-wide utility easement shall be provided along the front of all lots, adjacent to and flush with the street right-of-way line for the potential placement of utility facilities.
(e) 
For new development, all necessary on-site easements shall be established on the subdivision plat and not by separate instrument, and they shall be labeled for the specific purpose, and to the specific entity if other than the city, for which they are being provided. Examples include, but are not limited to, the following: a water, sanitary sewer or drainage easement, which is dedicated to the city for a water or sanitary sewer line or for a drainage structure; an access easement, which is dedicated to the public for unrestricted access purposes; a fire lane easement, which is dedicated to the city and its fire suppression and emergency medical service providers for access purposes; an electrical, gas or telephone easement, which is dedicated to the specific utility provider that requires the easement; and so on.
(2006 Code, sec. 70-73; Ordinance 02-09-549, sec. 3.3, adopted 9/3/02; Ordinance 15-06-994, sec. 6, adopted 6/2/15)
(a) 
The length, width and shapes of blocks shall be determined with due regard to:
(1) 
Provision of adequate building sites suitable to the special needs of the type of use contemplated;
(2) 
Zoning requirements as to lot sizes, setbacks and dimensions (if within the city’s corporate limits); and
(3) 
Needs for convenient access, circulation, control and safety of street traffic and for pedestrians or bicyclists traveling to a public park or school site or other facility within or close to the neighborhood.
(b) 
Intersecting streets, which determine the lengths and widths of blocks, shall be provided at such intervals as to serve cross-traffic adequately, to provide adequate fire protection, and to conform to customary subdivision practices. Where no existing subdivision or topographical constraints control, the block lengths shall not exceed 1,600 feet in length. Where no existing subdivision or topographical constraints control, the blocks shall not be less than 400 feet in length; however, in cases where physical barriers or property ownership creates conditions where it is appropriate that these standards be varied, the length may be increased or decreased (through issuance of a waiver/suspension by the city council with plat approval) to meet the existing conditions having due regard for connecting streets, circulation of traffic and public safety.
(2006 Code, sec. 70-74; Ordinance 02-09-549, sec. 3.4, adopted 9/3/02)
(a) 
Pedestrian concrete walkways (sidewalks) not less than four feet wide shall be required within a residential subdivision on both sides of residential and collector streets, and sidewalks not less than five feet wide shall be provided within all nonresidential developments and along all perimeter arterials, for both residential and nonresidential developments, as set forth in the city’s TCSS. Root barriers may be required underneath, and along with the construction of, all public sidewalks per the city’s TCSS, particularly in locations where trees are (or will be) in close proximity to the sidewalk. Barrier-free ramps shall be constructed at all street intersections and at any other locations deemed appropriate by the city due to anticipated pedestrian travel patterns. Sidewalks shall be constructed within the street right-of-way, one foot away from the right-of-way line, and at least five feet away from the street curb in a curvilinear manner within nonresidential zoning districts and along major arterials. In certain instances, the city council may, at its sole discretion, approve placement of the sidewalk adjacent or closer than five feet to the curb provided that such placement benefits the general public by allowing more space for landscaping, such as for street trees, screening shrubs, and decorative walls and fences, and provided that the width is increased to a minimum of five feet and a maximum of eight feet of sidewalk pavement or to such a width as may be needed to comply with the parks master plan along major arterials (i.e. North Murphy Road, South Murphy Road, State Highway 544 and Betsy Lane) in the interest of public safety.
(b) 
All sidewalks along a perimeter roadway or arterial are considered part of the overall development’s required public improvements and shall be installed prior to acceptance of the subdivision by the city and prior to final plat approval, unless surety is provided, per article 28.06 of this chapter. In any event, a certificate of occupancy will not be issued for any lot within the subdivision until the required sidewalks are in place or appropriate surety is provided. The cost and provision of any perimeter sidewalks, such as along major thoroughfares, may be escrowed as a part of a developer’s agreement, if approved by the city council. The city has the right, but not the obligation, to refuse escrow and to require paving of the sidewalks if, in its sole opinion, immediate provision of the sidewalks is necessary for safe pedestrian circulation or if it would otherwise protect the public health, safety, convenience or welfare.
(2006 Code, sec. 70-75; Ordinance 02-09-549, sec. 3.5, adopted 9/3/02; Ordinance 03-07-580 adopted 7/7/03)
(a) 
Lots shall conform to the minimum requirements of the established zoning district, if located within the city’s corporate limits.
(b) 
Each lot on a subdivision plat shall front onto a dedicated, improved public street unless platted as an approved private street subdivision in accordance with this chapter (see section 28.03.001(c)(10)). Lot width and access shall conform with the provisions of the city’s zoning ordinance set out in chapter 30 (if within the city’s limits), comprehensive plan, and any other applicable city code or ordinance. In all cases, single-family residential lots shall have a minimum of 35 feet of frontage, and nonresidential lots shall have a minimum of 50 feet of frontage, along a dedicated, improved street.
(c) 
Irregular-shaped lots shall have sufficient width at the building line to meet lot width and frontage requirements of the appropriate zoning district (if within the city’s limits), and shall provide a reasonable building pad without encroachment into front, side or rear yard setbacks or into any type of easement. Also, the rear width shall be sufficient to provide access for all necessary utilities, including access for driveways and solid waste collection when alleys are present (minimum 20-foot alley frontage). In general, triangular, severely elongated or tapered “flag” or “panhandle” lots shall be avoided, and the city reserves the right to disapprove any lot which, in its sole opinion, will not be suitable or desirable for the purpose intended, which is an obvious attempt to circumvent the purpose and intent of lot configuration or lot width minimums, or which is so oddly shaped as to create a hindrance to the logical lot layout of surrounding properties.
(d) 
Side lot lines shall be at 90-degree angles or radial to street right-of-way lines to the greatest extent possible. The city reserves the right to disapprove any lot which, in its sole opinion, is shaped or oriented in such a fashion as to be unsuitable or undesirable for the purpose intended, or which is not attractively or appropriately oriented toward its street frontage.
(e) 
Double frontage lots shall be avoided, except where they may be essential to provide separation of residential development from traffic arterials, as defined in section 28.03.001, or to overcome a specific disadvantage or hardship imposed by topography or other factors. Where lots have double frontage, building setback lines shall be established for each street side, and rear yard screening shall be provided in accordance with section 28.05.007. Residential lots shall not back onto any residential street or collector street within a residential area or neighborhood, and shall not have more than one-half of its perimeter boundaries along streets.
(2006 Code, sec. 70-76; Ordinance 02-09-549, sec. 3.6, adopted 9/3/02)
Front and street side building lines shall be shown on a concept plan and on any type of plat for all lots, and shall be consistent with the zoning ordinance requirements set out in chapter 30 for the district in which the development is located (if subject to the city’s zoning regulations) and with any other applicable city ordinance, respectively. For property that is not subject to the city’s zoning regulations, such as property that lies within the city’s extraterritorial jurisdiction, the minimum front building line (for a residential or nonresidential lot) shall be 40 feet.
(2006 Code, sec. 70-77; Ordinance 02-09-549, sec. 3.7, adopted 9/3/02)
(a) 
Definitions.
For purposes of this section, the following meanings shall apply:
Feeder or feeder/lateral line.
High-voltage supply electric lines carrying more than 69,000 volts that emanate from substations used to distribute power through an area to an unspecified number of customers.
Lateral lines.
Those electric or telephone lines used to distribute power from a feeder line to a single subdivision. These electric lines are normally connected to a feeder line through a sectionalizing device such as a fuse.
Service lines.
Those electric lines used to connect between the utilities’ supply system or lateral lines and the end user’s meter box.
Utility services.
The facilities of any person, firm or corporation providing electric, natural gas, telephone, cable television, or any other such item or service for public use approved but not provided by the city.
(b) 
Easement requirements; verification of acceptance; letters of commitment.
All subdivision plats and engineering plans submitted to the city for approval shall provide for utility services such as electrical, gas, telephone and cable television utility lines, including lateral or service distribution lines, and wires to be placed underground. Feeder and other major transmission lines may remain overhead within the appropriate easements. However, an applicant shall endeavor and, whenever practical, the city shall require that feeder lines are placed away from major or minor thoroughfares or arterials, as shown on the thoroughfare plan. Whenever practical, feeder lines which are to be placed overhead shall not be placed along both sides of the street right-of-way. Verification of acceptance of easement locations and widths by the public utilities shall be provided to the city, by the applicant, prior to final plat approval by the city council, and all easements shall be reviewed by the utility companies and by the city engineer (for those to the city) prior to granting final approval for any residential subdivision affected by this section. The applicant shall also, prior to final plat approval, provide a letter of commitment from each utility provider, such as those providing electricity, gas, telephone and cable television, who will serve the development that said utility providers will ensure the provision of necessary infrastructure and service to all portions of the proposed development within 12 months following final plat approval. Failure to submit such letters of commitment from utility providers shall constitute grounds for denial of the final plat application on the basis that there is no written assurance that the development can be served by essential utility services.
(c) 
Administrative policies and criteria; cost reimbursement.
Each of the utility companies shall be responsible for developing administrative policies, criteria for easement size, and cost reimbursement procedures for the installation and extension of their underground utilities. Nothing herein shall prohibit or restrict any utility company from recovering the difference in cost of overhead facilities and underground utilities from the property owner in accordance with the provisions of such utility’s approved tariff. No utility company shall be required or permitted to begin construction of underground facilities unless and until the property owner or developer of the subdivision has made arrangements satisfactory to the specific utility company for the payment of such difference between the cost of overhead facilities and underground facilities.
(d) 
Utility installations.
All electrical and telephone support equipment, including transformers, amplifiers and switching devices necessary for underground installations, shall be pad-mounted or ground-mounted, or shall be placed underground and not overhead, unless the subdivision is served from perimeter overhead electrical facilities. Pad-mounted or ground-mounted utility equipment shall be completely screened from view of any public roadway, and shall not be located within any required visibility area, such as at street intersections or corners or at driveway openings.
(e) 
Temporary construction service.
Temporary construction service may be provided by overhead electric lines and facilities without obtaining a waiver/suspension or special exception, provided that when the underground utility service to any portion of a subdivision is completed, such overhead electric lines and facilities are promptly removed.
(f) 
Undergrounding of existing facilities.
Nothing in this section shall be construed to require any existing facilities in place prior to the effective date of the ordinance from which this chapter is derived to be placed underground.
(g) 
Metering of utilities.
The metering for utilities such as water, gas and electricity shall be located on the individual lots to be served, not grouped together in a centralized location, such as “gang-box” style metering stations, which shall not be permitted.
(h) 
Determination of easements.
The locations, widths and configurations of easements for any utility service provider other than the city shall be determined, approved and acquired (if necessary) by the applicable utility service provider.
(i) 
Inspection.
All utility installations shall be subject to inspection by the city, and shall be in conformance with any applicable city design standards related to their placement within public rights-of-way, within easements, or elsewhere in the city (including on private property).
(2006 Code, sec. 70-78; Ordinance 02-09-549, sec. 3.8, adopted 9/3/02)
(a) 
All new subdivisions shall be connected with the city’s water system, and shall be capable of providing water for health and emergency purposes, including fire protection. An alternative source of water may be used for irrigation purposes only and for a nonresidential use only (e.g., a public park, a public school, and the like), subject to city approval and provided that all appropriate permits are procured from the city, the U.S. Army Corps of Engineers, the TCEQ, NTMWD, and any other applicable agency. Such alternative water source may not be used as a potable (i.e., drinking) water supply under any circumstances. The design and construction of water system improvements and alternative water sources shall comply with the following standards:
(1) 
Design and construction of a water source on the site shall be in accordance with applicable regulations of the state commission on environmental quality (TCEQ).
(2) 
Design and construction of water service from the city shall be in accordance with the standards in the city’s TCSS manual, and in accordance with TCEQ and NTMWD standards, whichever is the most stringent requirement.
(3) 
Design and construction of a fire protection and suppression system shall be in accordance with the standards in the TCSS manual, and in accordance with the city’s fire department and fire code.
(b) 
All new subdivisions shall be served by the city’s wastewater collection and treatment system. The design and construction of the wastewater system improvements shall be in accordance with the standards in the city’s TCSS manual, and in accordance with TCEQ and NTMWD standards, whichever is the most stringent requirement.
(c) 
The subdivider shall be responsible for:
(1) 
Phasing of development or improvements in order to maintain adequate water and wastewater services;
(2) 
Extensions of utility lines (including any necessary on-site and off-site lines) to connect to existing utility services;
(3) 
Providing and/or procuring all necessary easements for the utilities (whether on-site or off-site);
(4) 
Providing proof to the city of adequate water and wastewater service;
(5) 
Providing provisions for future expansion of the utilities if such will be needed to serve future developments, subject to the city’s oversize participation policies, if applicable;
(6) 
Providing all operations and maintenance of the utilities, or providing proof that a separate entity will be responsible for the operations and maintenance of the utilities;
(7) 
Providing all fiscal security required for the construction of the utilities;
(8) 
Obtaining approvals from the applicable utility providers if other than the city; and
(9) 
Complying with all requirements of the utility providers, including the city.
(d) 
Extension of water and wastewater lines shall be made along the entire frontage of the subdivision adjacent to a street or thoroughfare. If the subdivision is not adjacent to a thoroughfare, the extension of utilities shall be accomplished in such a manner as to allow future connections to said utilities by new subdivisions. If new subdivisions will never be constructed beyond a developing subdivision due to physical constraints, the city council may waive the requirement for adjacent utility line construction at the time of construction plat approval and prior to construction of the subdivision.
(e) 
Installation, operations and maintenance of utilities not specifically referenced herein shall comply with regulations of the TCEQ, the NTMWD, and with any other applicable state rules and regulations, whichever is the most stringent requirement.
(2006 Code, sec. 70-79; Ordinance 02-09-549, sec. 3.9, adopted 9/3/02)
(a) 
System design requirements.
Drainage improvements shall accommodate runoff from the upstream drainage area in its anticipated maximum “build-out” condition, and shall be designed to prevent overloading the capacity of the downstream drainage system. The city may require the phasing of development, the use of control methods such as retention or detention, or the construction of off-site drainage improvements in order to mitigate the impact of the proposed development. No stormwater collection system shall be constructed unless it is designed in accordance with the city’s TCSS manual by a licensed professional engineer, and unless it is reviewed and approved by the city engineer. All plans submitted to the city engineer for approval shall include a layout of the drainage system together with supporting calculations for the design of the system.
(b) 
All erosion and sedimentation controls shall conform to the TCSS manual. For erosion and sedimentation control, the city uses the latest edition of “Stormwater Quality Best Management Practices for Construction Activities in North Central Texas” (by the NCTCOG), a copy of which is on file at the city.
(c) 
No person, individual, partnership, firm or corporation shall deepen, widen, fill, reclaim, reroute or change the course or location of any existing ditch, channel, stream or drainageway without first obtaining written permission of the city engineer and any other applicable agency (such as FEMA or the U.S. Army Corps of Engineers) having jurisdiction. The city engineer may, at his or her discretion, require preparation and submission of a FEMA or flood study for a proposed development if there are concerns regarding storm drainage on the subject property or upstream or downstream from the subject property. The costs of such study, if required, shall be borne by the developer.
(d) 
In order to help reduce stormwater runoff, and resulting erosion, sedimentation and conveyance of nonpoint source pollutants, the layout of the street network, lots and building sites shall, to the greatest extent possible, be sited and aligned along natural contour lines, and shall minimize the amount of cut and fill on slopes in order to minimize the amount of land area that is disturbed during construction.
(e) 
No cross-street flow (i.e., perpendicular to traffic flow) of stormwater runoff shall be permitted unless approved by the city engineer. When and if such drainage flow is allowed, it must be across a concrete street (i.e., valley gutter) and as approved by the city engineer.
(f) 
All stormwater retention or detention facilities which are not located underground shall be designed using materials and techniques as established in the city’s TCSS manual or as may be required by the city engineer.
(2006 Code, sec. 70-80; Ordinance 02-09-549, sec. 3.10, adopted 9/3/02)