HomeMy WebLinkAboutAgenda UDCAC 09.14.2016Notice of Meeting for the
Unified Dev elopment Code Adv isory Committee
of the City of Georgetown
September 14, 2016 at 3:00 PM
at Historic Light and Water Works Building, 406 W. 8th Street, Georgetown, Texas
78626
The City o f G eo rgeto wn is committed to comp lianc e with the Americans with Dis abilities Ac t (ADA). If yo u
req uire as s is tanc e in participating at a p ublic meeting d ue to a disability, as d efined und er the ADA, reas onab le
as s is tance, ad ap tatio ns , or acc o mmo d ations will b e provid ed up o n req uest. P leas e c o ntact the City Sec retary's
Office, at leas t three (3) days prior to the sc hed uled meeting d ate, at (512) 930-3652 o r City Hall at 113 Eas t 8th
Street fo r add itional info rmation; TTY us ers ro ute through Relay Texas at 711.
Regular Session
(This Regular S es s io n may, at any time, b e rec es s ed to convene an Exec utive S es s io n fo r any p urpose
authorized b y the Op en Meetings Act, Texas Go vernment Co d e 551.)
A Call to Ord er
Public Wishing to Address the Board
On a sub ject that is pos ted on this agend a: Pleas e fill out a speaker regis tration form which c an b e found at the
Bo ard meeting. C learly p rint yo ur name, the letter o f the item o n which yo u wis h to s p eak, and present it to the
Staff Liais o n, p referab ly p rio r to the s tart of the meeting. You will be called forward to speak when the Board
cons id ers that item.
On a sub ject not pos ted on the agend a: Pers ons may add an item to a future Bo ard agenda b y filing a written
req uest with the S taff Liaison no later than one week prior to the Board meeting. T he req uest mus t inc lude the
s p eaker's name and the s p ecific to p ic to b e ad d res s ed with sufficient information to info rm the b o ard and the
p ublic . For Board Liais on c o ntact info rmatio n, pleas e lo gon to
http://go vernment.georgetown.o rg/category/b o ard s -commissions /.
B As of the d ead line, no persons were signed up to s peak on items other than what was posted on the
agenda.
Legislativ e Regular Agenda
C Overview and d is cus s io n regarding amend ment proc es s and go als for the meeting. Jo rd an Mad d o x and
Valerie Kreger
D Dis cus s ion regard ing proposed amendments to C hapter 2, Review Autho rity. Jo rd an Mad d o x
E Dis cus s ion regard ing proposed amendments to C hapter 3, Ap p licatio ns . Valerie Kreger
F Dis cus s ion regard ing proposed amendments to C hapter 6, Residential Development Standards. Valerie
Kreger
G Dis cus s ion regard ing proposed amendments to C hapter 7, Non-res id ential Develo p ment S tand ard s .
Valerie Kreger
Page 1 of 131
H Dis cus s ion regard ing proposed amendments to C hapter 9, Off-Street P arking. Jo rd an Mad d o x
I Dis cus s ion regard ing proposed amendments to C hapter 11, Environmental Protectio n. Jo rd an Mad d ox
J Dis cus s ion regard ing proposed amendments to C hapter 12, P ed es trian and Vehicle Circ ulatio n. Jo rd an
Maddox
K Dis cus s ion regard ing proposed amendments to C hapter 13, Infras tructure and P ublic Improvements .
Jo rd an Maddox
L Dis cus s ion regard ing proposed amendments to C hapter 16, Definitio ns. Jordan Maddox
M Dis cus s ion regard ing next step s in the proc es s . Sofia Nelson
Adjournment
CERTIFICATE OF POSTING
I, Shelley No wling, C ity S ecretary fo r the C ity of Geo rgeto wn, Texas , d o hereby c ertify that this Notice of
Meeting was p o s ted at City Hall, 113 E. 8th Street, a p lace read ily acc es s ible to the general p ublic at all times ,
on the ______ d ay o f __________________, 2016, at __________, and remained so p o s ted fo r at leas t 72
c o ntinuo us ho urs p receding the sc heduled time o f s aid meeting.
____________________________________
S helley No wling, City Sec retary
Page 2 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Overview and dis c us s ion regard ing amend ment p ro ces s and goals fo r the meeting. Jordan Maddox and
Valerie Kreger
ITEM SUMMARY:
Staff will provide an o verview o f the goals and des ired o utcomes o f the meeting. T he intent is to
s ummarize the p ro p o s ed amend ments to eac h c hapter, disc uss any c hanges s inc e the last meetings , clarify
any c o nc erns or o uts tand ing ques tions , and identify any b ig-ticket items that either need work or there is
d is agreement. Staff ’s intent is to s ched ule a vote on eac h chap ter at the Oc to b er meeting.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
Page 3 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 2, Review Autho rity. Jordan Maddox
ITEM SUMMARY:
Chap ter 2 is the review authority chap ter o f the c o d e and the Committee has no t yet s een amend ments this
cycle. Pro p os ed amendments inc lude the remo val o f the Acc es s Po int Exemp tion proc ed ure; c hange to
Lic ense to Enc ro ac h to have the Decision-Maker be the Development Engineer ins tead of Planning
Direc tor; addition of Sub d ivision Varianc e, whic h will inc lude s o me sto rmwater p ro visions and encompas s
the exis ting Plat Waiver p ro cess; c o mb ine role o f Drainage Engineer into Develo p ment Engineer.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
Chapter 2 for UDCAC 9.14.16 Backup Material
Page 4 of 131
Page 1 of 4
Chapter 2 Review Authority
Section 2.01 General
2.01.020 Summary of Review Authority
The following Table summarizes the decision-making authority of each review body for the City of
Georgetown.
Table 2.01.020: Summary of Review Authority
Procedure
Pl
a
n
n
i
n
g
Di
r
e
c
t
o
r
Bu
i
l
d
i
n
g
Of
f
i
c
i
a
l
De
v
e
l
o
p
.
En
g
i
n
e
e
r
Ur
b
a
n
Fo
r
e
s
t
e
r
Hi
s
t
o
r
i
c
Pr
e
s
e
r
v
a
t
i
o
n
Of
f
i
c
e
r
HA
R
C
ZB
A
P&
Z
Ci
t
y
C
o
u
n
c
i
l
City Council Action
Access Point Connection Exemption R R R <DM>
Annexation R <DM>
Comprehensive Plan Amendment R <R> <DM>
Conservation Subdivision /Site Analysis Map R R DM
Development Agreement R <R> <DM>
Historic Overlay District Designation R R <R> <R> <DM>
Historic Landmark Designation R <R> <DM>
Rezoning (Zoning Map Amendment) R <R> <DM>
Special Use Permit R <R> <DM>
UDC Text Amendment R <R> <DM>
Administrative Action
Administrative Exception DM A A*
Administrative Plat (minor or amend plat) DM R A
Administrative Certificate of
Appropriateness DM A
Construction Plans DM A
Courthouse View Height Determination DM A
Driveway Permit DM A
Final Plat DM R A
Heritage Tree Protection Priority DM R R A
Heritage Tree Pruning Permit A DM
Heritage Tree Removal DM A
License to Encroach DM DM A
Master Sign Plan DM A
Sign Permit DM A
Site Development Plan DM R A
Stormwater Permit DM A
Temporary Use Permit DM A
Traffic Impact Analysis DM A
Historic and Architectural Review Commission (HARC) Action
Certificate of Appropriateness R <DM> A
Page 5 of 131
Page 2 of 4
Procedure
Pl
a
n
n
i
n
g
Di
r
e
c
t
o
r
Bu
i
l
d
i
n
g
Of
f
i
c
i
a
l
De
v
e
l
o
p
.
En
g
i
n
e
e
r
Ur
b
a
n
Fo
r
e
s
t
e
r
Hi
s
t
o
r
i
c
Pr
e
s
e
r
v
a
t
i
o
n
Of
f
i
c
e
r
HA
R
C
ZB
A
P&
Z
Ci
t
y
C
o
u
n
c
i
l
HARC Exception (Building Height/ Setback
variations pursuant to Section 4.08) R <DM>
A
Master Sign Plan R <DM> A
Zoning Board of Adjustment (ZBA) Action
Appeal of Administrative Decision <DM>
Special Exception R <DM>
Variance <DM>
Planning and Zoning Commission
Heritage Tree Protection Priority R R R DM A
Minor or Final Plat w/Waiver R R DM A
Plat Waiver R R DM A
Preliminary Plat R R DM A
Subdivision Variance (floodplain &
stormwater) R R <DM> A
Variance [water quality regulations
(Section 11.07.003)] R <DM> A
R – Review or Recommendation DM – Decision Making Authority A – Appeal Authority
< > - Public Hearing * Administrative Exceptions related to Chapter 8 items are sent to the City Council, all others are
appealed to ZBA.
Section 2.02 Administrative Officials
2.02.010 Director of Planning and Development Department (Director)
A. Appointment
The City Manager shall appoint a Director of the Planning and Development Department
(Director) to be the administrator of this Unified Development Code. In the absence of a Director
of the Planning and Development Department, the Community Development Director shall serve
in that capacity.
B. Powers and Duties
The Director of Planning and Development Department has the following powers and duties:
1. Final Action
The Director is responsible for taking final action on the following procedures described in
this Code, subject to the specific criteria for each procedure as described in the Code.
a. Administrative Exceptions
b. Administrative Plats
c. Final Plats
d. Site Development Plans
Page 6 of 131
Page 2 of 4
2. Review and Report
The Director shall review and make either a report or recommendation to the Zoning Board
of Adjustment, Planning & Zoning Commission, or City Council on the following
procedures, subject to the terms and conditions set forth for such procedures in this Code.
a. Access Point Connection Exemption
b. Comprehensive Plan Amendment
c. Development Agreement
d. Historic District Designation
e. Preliminary Plat
f. Rezoning (Zoning Map Amendment)
g. Special Exception
h. Special Use Permit
i. Subdivision Variance
ij. Unified Development Code Text Amendment
jk. Zoning Variance
2.02.020 Development Engineer
A. Designation
The Director shall appoint a Development Engineer to function as described in this Code. The
Development Engineer must be an engineer licensed by the State of Texas. For the purposes of
this Code, the Development Engineer is also designated as the Drainage Engineer.
In the absence of a Development Engineer, the Drainage Engineer shall serve in that capacity.
B. Powers and Duties
The Development Engineer shall review and make reports to the Director or other final action
authorities on all Site Plans and plats, and shall have final authority for approving construction
plans, stormwater permits, and driveway permits.
C. Compliance with Rules and Procedures
1. The Development Engineer shall comply with any specific procedures or technical criteria
described in this Code.
2. The Development Engineer shall develop additional procedures or technical criteria to
clarify implementation of this Code, providing that additional procedures do not violate any
other provisions of this Code.
Page 7 of 131
Page 4 of 4
2.02.030 Drainage Engineer
A. Designation
The City Manager may appoint a Drainage Engineer to function as described in this Code. The
Drainage Engineer must be an engineer licensed by the State of Texas.
B. Powers and Duties
The Drainage Engineer shall review and make reports to the Director or other final action
authorities on all Site Plans and plats, and shall have final authority for approving Stormwater
Permits. In the absence of a Drainage Engineer the Development Engineer shall serve in that
capacity.
C. Compliance with Rules and Procedures
1. The Drainage Engineer shall comply with any specific procedures or technical criteria
described in this Code.
2. The Drainage Engineer may develop additional procedures or technical criteria to clarify
implementation of this Code, providing that additional procedures do not violate any other
provisions of this Code.
Page 8 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 3, Applic ations . Valerie Kreger
ITEM SUMMARY:
Since the last d is c us s io n o n Chap ter 3, staff has mad e a few minor changes , s pec ifically to the p latting
exemptio ns, ad d ing c larificatio n language to c ons tructio n p lans, and removing the requirement for a pre-
ap p licatio n meeting for a Licens e to Enc ro ac h.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 3 Cover Memo
Page 9 of 131
Page 1 of 35
Chapter 3 Applications and Permits
Section 3.01 General
3.01.010 Purpose
The purpose of this Chapter is to establish application procedures, internal review procedures, public
notice and hearing procedures, and review criteria for the processing of applications and actions that
affect the development and use of property subject to the jurisdiction of the City.
3.01.020 Applicability of Procedures
The following Table shows which review procedures, applications and permits apply in the City and
its extraterritorial jurisdiction.
Table 3.01.020 Applicability of Procedures
City Limits Extraterritorial Jurisdiction
Prior to Subdivision, Platting and any Development
Annexation (Voluntary) X
Comprehensive Plan Amendment X X
Rezoning (Zoning Map Amendment) X
Historic Overlay District Designation X
Historic Landmark Designation X
Special Use Permit X
Development Agreement X X
Access Point Connection Exemption X X
Subdivision & Platting of Land
Recording Plats X X
Preliminary Plat X X
Construction Plans X X
Plat Vacation X X
Plat WaiverSubdivision Variance X X
Development Application Process
Site Development Plan X
Zoning Verification Letter X
Legal Lot Verification LetterCertification
Regarding Compliance with Platting X X
Temporary Use Permit X
Master Sign Plan X X
Certificate of Appropriateness X
Appeal of an Administrative Decision X X
License to Encroach X X
Zoning Variance X
Administrative Exception X
Special Exception X
Stormwater Permit X X
Driveway Access Permit X X
Sign Permit X X
Courthouse View Height Determination X
Page 10 of 131
Page 2 of 35
3.01.030 Simultaneous Submission of Related Applications
A. Submission of different applications related to the same development may be made
simultaneously, within each application group listed below. although Approval consideration
of the different applications, however, must shall remain occur in the following sequence: as
listed.
1. Policy Applications
a. Annexation (Voluntary)
b. Development Agreement
c. Comprehensive Plan;
d. Zoning;
e. Preliminary Plat
Exception: A preliminary plat shall not be submitted until final approval of a Planned
Unit Development (PUD) zoning request.
2. Development Applications
a. Construction Plans
b. Final Plat
c. Certificate of Appropriateness; then
d. Site Development Plan.
3. Building Permits
An application for a Building Permit shall not be submitted to the City until review of the
first submittal of the corresponding Site Development Plan has been completed by staff and
the comments have been forwarded to the applicant.
B. Any application submitted simultaneously is subject to approval of all other related
applications. Denial or, disapproval or reconsideration of any concurrently submitted
application shall stop consideration of any related applications.
C. An applicant may withdraw any individual application from a group of simultaneously
submitted applications.
Section 3.03 Public Hearing and Notice
3.03.010 Provision of Public Notice
A. Summary of Notice Required
Notice shall be required for application review as shown in the following Table.
Page 11 of 131
Page 3 of 35
Table 3.03.010: Summary of Notice Requirements
Procedure Published Mailed Posted
Annexation (Voluntary) X
Access Point Connection Exemption X X X
Certificate of Appropriateness X
Certificate of Appropriateness for relocation,
removal or demolition, or setback
modification
‡ ‡
Development Agreement * * *
Historic Overlay District Designation X X X
Historic Landmark Designation X X X
Replat without Vacating (§212.0145) X X
Rezoning (Zoning Map Amendment) X X X
Special Exception X X X
Special Use Permit X X X
Subdivision Variance X X X
UDC Text Amendment X
Variance X X X
X = Notice Required
* = Notice to be determined by Development Agreement Committee per Section 3.20
‡ = Only applicable to Certificate of Appropriateness applications that require consideration by the
Historic and Architectural Review Commission
B. Published Notice
1. A Public Notice shall be published at least once in a local newspaper of general circulation,
as designated by the City Council, within the City prior to the meeting. The Notice shall
contain the time and place of such Public Meeting or Hearing and a brief description of the
agenda items that may be considered or reviewed.
2. A published notice shall be published at least 15 days in advance of the Public Meeting or
Hearing.
C. Mailed Notice
1. Generally
A Notice of Public Hearing shall be sent by U.S. mail to owners of record of real property
within 200 feet of the boundary of the property under consideration, as determined by the
most recent municipal tax roll information. The notice may be served by its deposit in the
municipality, properly addressed with postage paid, in United States mail at least 15 days
prior to the date set for the Public Hearing or as otherwise required by the Texas Local
Government Code, as amended.
2. Special Mailed Notice Required for Certain Replats
Replats containing any area or lot that, during the preceding five years, was limited by an
interim or permanent zoning classification to residential use for not more than two
residential units per lot or in the preceding plat was limited by deed restrictions to
residential use for not more than two residential units per lot, require mailed notice to all
owners of lots that are part of the original subdivision and located within 200 feet of the
Page 12 of 131
Page 4 of 35
boundary of the property to be replatted, in the same manner as prescribed in Section
3.03.010.C.1 above and in accordance with §212.015 of the Texas Local Government Code,
as amended.
3. Special Mailed Notice Required for PUD Modification
a. For purposes of mailed notice, the boundary of a PUD Modification shall be the
boundary of any tract of land for which PUD standards or requirements are proposed
to change due to the modification.
b. In addition to the requirements of Paragraph 1 above, mailed notice shall also be
provided all owners of property within the entire PUD boundary, not otherwise
notified.
D. Posted Notice
1. Notice shall be posted in a format approved by the Director on the subject property, along
rights‐of‐way contiguous to the proposed development according to the following
standards:
a. One sign for tracts of less than 300 feet of right‐of‐way frontage;
b. One sign at each interval of 1,000 feet; and
c. The total number of signs shall not be required to exceed a total of four signs per right‐
of‐way.
2. Notice of application shall be posted at the project site such that it is visible from the public
right‐of‐way, including contact information and meeting date.
3. The applicant shall be responsible for posting and maintaining the sign on a format
approved by the Director, and for removing the sign within five days following the Public
Hearing on the application.
4. Posted notice shall be posted not less than 15 days prior to the scheduled Public Hearing.
E. Content of Notice
Published or mailed notices shall contain at least the following specific information:
1. The general location of land that is the subject of the application, including a location map
with the mailed notice only;
2. The legal description or street address;
3. The substance of the application, including the type of proposed development and the
current Zoning District;
4. The time, date, and location of the Public Hearing;
5. A phone number to contact the City; and
6. A statement that interested parties may appear at the Public Hearing.
F. Constructive Notice
Minor defects in notice shall not impair the notice or invalidate proceedings pursuant to the
notice if a bona fide attempt has been made to comply with applicable notice requirements.
Page 13 of 131
Page 5 of 35
3.03.020 Required Public Hearing
The following Table identifies the types of applications requiring a Public Hearing and the review
body responsible for conducting the Hearing.
Table 3.03.020: Summary of Required Public Hearing
Type of Application HARC Zoning Board
of Adjustment
Planning &
Zoning
City
Council
Annexation (Voluntary) X (2)
Access Point Connection Exemption X
Appeal of Admin. Decision X
Certificate of Appropriateness ‡
Comprehensive Plan Amendment X X
Development Agreement * X
Historic Overlay District Designation X X X
Historic Landmark Designation X X
Replat (Resubdivision) X X
Rezoning (Zoning Map Amendment) X X
Special Exception X
Special Use Permit X X
Subdivision Variance X
UDC Text Amendment X X
Variance X
X = Public Hearing Required
* = Public Hearing to be determined by Development Agreement Committee per Section 3.20
‡ = Only applicable to Certificate of Appropriateness applications that require consideration by the Historic
and Architectural Review Commission
3.03.030 Conduct of Public Hearings
A. Modification of Application at Public Hearing
1. The applicant may agree to modify the application, including the plans and specifications
submitted, in response to questions or comments by persons appearing at the Public
Hearing or to suggestions or recommendations by the recommending or decision‐making
body holding the Public Hearing.
2. Unless such modifications are so substantial that the recommending or decision‐making
body cannot reasonably be expected to perceive the nature and impact of the proposed
changes without revised application materials before it, the recommending or decision‐
making body may approve or recommend approval of the application with the condition
that the approval or recommendation of approval will not be applicable until materials
reflecting the agreed upon changes are submitted to the Director. No application may
proceed until the revisions have been made.
Page 14 of 131
Page 6 of 35
3. Where deemed appropriate by the decision‐making body, modifications to an application
may be referred back to the recommending body for reconsideration, prior to further action
by the decision‐making body.
4. Modification of an application that causes the consideration of that application to be
substantially different than that which was provided in the public notice shall require a
new Public Hearing by the recommending and decision‐making bodies with new notice in
accordance with Section 3.03.010. Such modifications shall include, but not be limited to, a
change to a zoning district that was not otherwise included in the public notice and
increasing the acreage of the area under consideration. Decreasing the acreage of the area
under consideration shall not cause the application to require a new Public Hearing.
B. Evidence
All findings and conclusions necessary to the permit or decision shall be based upon reliable
evidence. Competent evidence (evidence admissible in a Court of Law) shall be preferred
whenever reasonably available, but in no case may findings be based solely upon incompetent
evidence unless competent evidence is not reasonably available, the evidence in question
appears to be particularly reliable, and the matter at issue is not seriously disputed.
C. Record
1. An audio tape recording and/or written minutes shall be made of all required Public
Hearings and such audio recordings shall be kept for two years.
2. All documentary evidence presented at a Hearing as well as all other types of physical
evidence shall be made a part of the record and shall be kept by the City for two years.
3.03.040 Postponement of Application
A. Postponement of Public Hearing after Public Notice
The applicant shall be required to pay for all re‐notice fees for a scheduled and noticed Public
Hearing that is postponed at the request of the applicant.
B. Postponement of Application after Recommendation
For applications where a recommendation is required by the Planning and Zoning Commission,
an applicant may request the City Council Public Hearing to be postponed to the next regular
meeting following the date of the scheduled City Council Public Hearing. The Director may
approve, for good cause shown, a postponement of up to 30 days from the date of the
scheduled City Council Public Hearing. Public Notice of the new Public Hearing shall be
required in accordance with Section 3.03.010.
3.03.050 Administrative Review Process
Administrative reviews occur when the Director or another City employee is responsible for final
action on any application.
A. Applicability
An Administrative Review shall be required for any permit or application that requires final
action from an administrative official, as described in Table 2.01.020.
Page 15 of 131
Page 7 of 35
B. Review Process
Administrative Reviews shall occur within the standard review periods established by the
Director. The Director or other authority responsible for final action may establish procedures
necessary to ensure compliance with this Code and state statute.
1. Initiation
Initiation of an Administrative Review may be made upon:
a. Recommendation of the Director;
b. Recommendation of other administrative official responsible for final action on the
permit being initiated; or
c. Submission of a complete application by the property owner or their authorized agent.
2. Application
Application must be made in a format consistent with Section 3.02.020.
3. Completeness Determination
Upon submission of an application for any administrative review, the Director shall
determine whether the application is complete, as described in this Code.
4. Staff Review
Once an application is determined complete, the Director or Final Action Authority shall
review the application, considering any applicable criteria for approval. The Director or
Final Action Authority may assign staff to review the application and make a report to the
Director or Final Action Authority.
C. Administrative Final Action
Upon completion of the administrative review, the Director or other responsible Final Action
Authority shall make a final determination and notify the applicant in writing. The Director or
other Final Action Authority may take one of the following final actions:
1. Approve the application.
2. Approve the application, with modifications that the Director or Final Action Authority
deems necessary to meet any criteria for approval. An approval with modifications shall be
considered agreed to by the applicant unless the applicant appeals the final action.
3. Disapprove the application. Such disapproval must include specific reasons for
disapproval. If the Director determines that an Administrative Plat should be disapproved,
the Director must forward the application to the Planning & Zoning Commission for final
action.
4. Prior to making a final decision, the Director or other Final Action Authority may hold a
meeting with the applicant to discuss and attempt to resolve any issues that become
evident during administrative review.
D. Criteria for Approval – Generally
1. An application shall be approved administratively when all of the following criteria are
met:
a. A complete application and fee have been submitted.
Page 16 of 131
Page 8 of 35
b. The application and content of the application are consistent with the provisions of this
Unified Development Code, the Comprehensive Plan, and any other applicable City
regulations.
c. The application and content of the application are consistent with any Administrative
Rules established by the Director, and any prior written interpretations of this Code.
2. Additional criteria for approval that apply to specific administrative procedures may be
provided in the specific descriptions of those procedures in Chapter 3. An administrative
procedure that does not have specific criteria for approval shall be considered using the
general criteria provided above.
E. Appeals
1. If an aggrieved person is appealing a final action that was disapproved, only the basis for
disapproval may be appealed.
2. Because the Director may not disapprove an Administrative Plat, any final action taken by
the Director on an Administrative Plat Review may not be appealed. If the Director is
unable to approve an Administrative Plat, the Planning & Zoning Commission will take
final action.
3. A person may not appeal a denial for the purpose of continuance, an extension agreed to
by the applicant and the Director or a determination that an application is not complete.
Section 3.08 Subdivision of Land
3.08.010 Plat Required
A. Pursuant to the authority granted in Texas Local Government Code Chapter 212 and the City
Charter, prior to the subdivision, resubdivision, assembly or development of any land within
the City or its extraterritorial jurisdiction, all a subdivision plats and, where public
improvements are proposed, construction plans for public improvements must first be
approved in accordance with these regulationsthis Chapter.
B. The owner of a tract of land located within the City limits or the extraterritorial jurisdiction who
divides the tract in two or more parts to lay out a subdivision of the tract or to lay out streets,
parks, or other parts of the tract intended to be dedicated to public use or for development of
the propertythe use of purchasers or owners of lots fronting on or adjacent to the streets, parks,
or other parts must shall have submit a plat of the subdivision preparedin accordance with this
Chapter.
C. A subdivision plat shall be required in accordance with the procedures outlined in this Chapter
for the development of land where new public infrastructure is required.
C.D. A division of a tract under this Section includes a division regardless of whether it is made by
using a metes and bounds description in a deed of conveyance or in a contract for a deed, by
using a contract for sale or other executory contract to convey or by using any other method.
D.E. No Site Development Plan, Stormwater Permit, Building Permit, Certificate of Occupancy, or
utility services may be approved or issued for the construction or development of any parcel or
tract of land unless such property is in conformity with the provisions of this Code.
Page 17 of 131
Page 9 of 35
E.F. The division of any lot or any parcel of land by the use of metes and bounds description for
the purpose of development is prohibited.
3.08.020 Exemptions from Required Plat
The following situations shall not require review by the City under the subdivision provisions, but
may require a Certification Regarding Compliance with Plat Requirements per Section 3.08.030.
However, Williamson County may still require subdivision approval under its regulations for
subdivisions located in the City’s ETJ.
A. Land constituting a single tract, lot, site, or parcel for which a legal deed of record describing
the boundary of said tract, lot, site, or parcel was filed of record in the deed records of
Williamson County, Texas, on or before May 10, 1977, provided that such parcel or tract of land
has not thereafter been subdivided into two or more parcels or tracts of land.;
B. A division of land into parts greater than five acres, where each part has at least 25 feet of
frontage on a public street access and no public improvement, including right‐of‐way,
easement, or physical improvement of any kind intended for public use, is being proposed or is
required to be dedicated; and where no development is proposed. However, prior to any future
development, other than a single‐family residence, or further division, a plat meeting the
requirements of this Chapter shall be approved and recorded.
C. A division of land created by order of a court of competent jurisdiction, including the probate of
an estate, provided, however, that prior to construction of improvements,any future
development, other than a single‐family residence, or further division, a plat meeting the
requirements of this Chapter shall be approved and recorded prior to the issuance of permits;.
D. Construction of additions or alterations to an existing building where no public utility extension
or public improvement, drainage, street, parking increase, or street access change is required to
meet the standards of this Code for such building addition or alterations;.
E. Operation of existing cemeteries complying with all state and local laws and regulations; and.
F. Acquisition of land by the City, County, or State for a governmental purpose or public facilities
by dedication, condemnation, or easement.
3.08.030 Certification Regarding Compliance with Plat Requirements
An application for Certification certification regarding of a tract’s compliance with the platting
requirements of this Chapter may be requested submitted as outlined in Section 3.10.020for an
existing tract of land or proposed division of land within the City’s jurisdiction, but shall be required
for tracts of land created via the exemptions outlined in Sections 3.08.020.A – 3.08.020.B. In
compliance with Local Government Code Subsection 212.0115, the Director, or their designee, shall
provide written determination of the following:
A. Whether a plat is required under this Chapter for the tract of land or the proposed division of
land or whether an exemption to platting under Section 3.08.020 applies; and
B. If a plat is required, whether a plat has been reviewed and approved by the applicable
approving body.
Page 18 of 131
Page 10 of 35
3.08.040 Plat Types
The following table summarizes types of plats required by this Code as well as their corresponding
process. When a proposed division is subject to more than one description within a plat type, the
more restrictive process is applicable.
Table 3.08.030 Plat Summary
Plat Type Description Public
Hearing
Final
Action Expiration
Preliminary
Plat
Required when the extension of public infrastructure,
including public utilities and roadways, is required or
proposed
No P&Z 24 months from approval date unless
Final Plat recorded within that time.
Phased Preliminary Plats expire 24
months from date last Final Plat recorded.Preliminary Plat that includes existing platted property See Replat P&Z
Amendment to approved Preliminary Plat No P&Z Maintains expiration date of original
Preliminary Plat being amended
Re
c
o
r
d
i
n
g
P
l
a
t
s
Final Plat
Final Plat of approved Preliminary Plat No Director
Must be recorded within 24 months from
approval date
Plat with more than 4 lots, but with no required or
proposed public infrastructure No P&Z
Combined Preliminary and Final Plat is available when plat
that could qualify as Minor Plat requires land or utility
dedication
No P&Z
Final Plat that proposes qualified Minor Deviations from the
approved Preliminary Plat No Director
Final Plat that proposes qualified Major Deviations from the
approved Preliminary Plat No P&Z
Final Plat processed concurrently with Plat Waiver No P&Z
Minor Plat
Plat involving 4 or fewer lots that does not require or
propose public infrastructure or land or utility dedication No Director Must be recorded within 24 months from
approval date Minor Plat processed concurrently with Plat Waiver No P&Z
Develop-
ment
Plat
Plat required at time of development for property not
previously platted or exempted from platting at time of
division that also requires or proposes public infrastructure
or land or utility dedication
No P&Z Must be recorded within 24 months from
approval date
Plat required at time of development for property not
previously platted or exempted from platting at time of
division that does not require or propose public
infrastructure or land or utility dedication
No Director Must be recorded within 24 months from
approval date
Replat
A resubdivision of all or part of an existing plat, involving
more than 4 lots Yes P&Z
Must be recorded within 24 months from
approval date
A resubdivision of all or part of an existing plat, involving 4
lots or less No Director
A Replat involving property that is or has been subject to
single or two-family restrictions or zoning within last 5 years Yes P&Z
A Replat that is processed concurrently with a Plat Waiver No P&Z
Amended
Plat
Plat meeting the standard qualifications of Amended Plat
(i.e. corrections to previous plat, moving lot line, etc.) No Director Must be recorded within 24 months from
approval date
3.08.050 Submission Requirements
The applicant shall submit all of the information required in the UDC Development Manual as
specified on the corresponding plat application checklist. A plat is not considered filed for the
purposes of §212.009 of the Texas Local Government Code until the Director determines that the
application meets all applicable requirements of this UDC and is accepted for consideration and
acknowledges such by notifying the applicant of such acceptance and either placing the plat on the
next available Planning and Zoning Commission agenda for their consideration, or, in the case of
administratively approved plats, proceeding to final action. The final copy of Preliminary and
Page 19 of 131
Page 11 of 35
Recording Plats shall be prepared and submitted in conformance with the UDC Development
Manual.
3.08.060 Staff Review
A. The Director may establish procedures for administrative review of plat applications necessary
to ensure compliance with this Code and state statute.
B. The Director may assign staff to review the plat application and make a report to the Director.
C. Once the Director determines the application is accepted for consideration, the Director shall
prepare a report to the Planning and Zoning Commission, if applicable. The Director’s report
may include a recommendation for final action.
3.08.070 Preliminary Plats
A. Applicability
1. Approval of a Preliminary Plat, showing the proposed layout of the subdivision, shall be
required before approval of any division of land or platting activity that requires or
proposes the extension of public infrastructure, including, but not limited to, public utilities
and roadways.
2. Any Preliminary Plat that includes the further subdivision of all or part of a recorded plat
that has not otherwise been vacated, must also follow the procedures set forth for Replats
as outlined in Section 3.08.070.D.
B. Unlawful to Record Preliminary Plat
It shall be unlawful to cause any Preliminary Plat of land within the City limits or
extraterritorial jurisdiction of Georgetown to be recorded with the County Clerk, except as
otherwise established for a Combined Preliminary and Final Plat.
C. Approval Criteria
1. The Preliminary Plat shall not be considered for final action until the Director has
determined the Preliminary Plat is acceptable for consideration, meaning the application is
complete and the information contained within the application is correct and sufficient to
allow adequate consideration and final action.
2. No Preliminary Plat shall be approved without a determination that the plat conforms to
the following:
a. The plat meets or exceeds the requirements of this Unified Development Code and any
applicable local or state laws.
b. The plat is consistent with the City’s Comprehensive Plan and any other adopted plans
as they relate to:
i. The City’s current and future streets, sidewalks, alleys, parks, playgrounds, and
public utility facilities; and
ii. The extension of the City or the extension, improvement or widening of its roads,
taking into account access to and extension of sewer and water mains and the
instrumentalities of public utilities.
c. Any subdivision design and improvement standards adopted by the City pursuant to
Texas LGC § 212.002 or Texas LGC § 212.044, governing plats and subdivision of land
Page 20 of 131
Page 12 of 35
within the City’s jurisdiction to promote the health, safety, morals or general welfare of
the City and the safe orderly, and healthful development of the City.
d. The tract of land subject to the application is adequately served by public
improvements and infrastructure or will be adequately served upon completion by the
applicant of required improvements.
3. Phasing Plan
In lieu of recording the entirety of a proposed division of a property at one time, and
therefore constructing all public improvements required by the division at once, an
applicant may propose a plan for phasing the subdivision as follows:
a. The Phasing Plan shall indicate the boundaries and order of final platting and
construction of associated improvements.
b. Phasing Plans shall not propose more than 10 phases. The Director may approve
phasing in excess of this number if the applicant can provide justification for such. The
number of phases herein is exclusive of any increase in phases due to the splitting of
phases as allowed per Section 3.080.B.1.c.
c. Each proposed phase of a Phasing Plan for a single‐family residential development
shall include at least 4 lots, except that lots shown on a Phasing Plan for nonresidential
uses, such as lots for parkland, neighborhood amenity centers, or commercial out lots,
or any similar uses as determined by the Director, may be shown as a single lot phase.
d. The proposed order of phasing shall follow a logical progression and, in the event
subsequent phases are not built, meet the minimum requirements of this Code,
including, but not limited to, public infrastructure, parkland dedication, connectivity,
and dedication of adjacent street rights‐of‐way.
e. Changes to a Phasing Plan shall meet the requirements of this Section and follow the
procedures for such as permitted in Sections 3.08.070.F and 3.08.080.B.1.c.
D. Responsibility for Final Action
1. The Planning and Zoning Commission shall consider the Preliminary Plat application, the
Director’s report, state law, and compliance with this Unified Development Code, and take
final action.
2. Any of the following actions by the Commission shall be considered the Commission’s
final action:
a. Approval of the Preliminary Plat;
b. Approval of the Preliminary Plat with conditions, subject to the following:
The Preliminary Plat shall be considered approved only once such conditions
are satisfied; and
Failure to satisfy the stated conditions within 6 months shall cause the
conditional approval of the Preliminary Plat to convert to denial;
Denial of the Preliminary Plat.
3. The Commission may postpone final action on a Preliminary Plat only when an applicant
submits a written request to waive any rights under Texas LGC §212.009 and postpone
such action to a specific future Commission meeting.
Page 21 of 131
Page 13 of 35
E. Expiration of Preliminary Plat
1. A Preliminary Plat that is proposed to be developed in a single phase shall become null and
void 24 months after its approval unless a Final Plat is recorded for all of the Preliminary
Plat within that time.
2. A Preliminary Plat that includes an approved Phasing Plan shall become null and void 24
months after its approval unless a Final Plat for the first phase is recorded within that time.
The recording of a Final Plat for the first phase of the project shall extend the expiration
date for the remaining portion of the original Preliminary Plat for a period of 24 months
after the date of recordation of the Final Plat. Recordation of each subsequent Final Plat
within 24 months of the date of recordation of the preceding Final Plat shall extend the
expiration date for the portion of the original Preliminary Plat for which no Final Plats have
been approved for an additional 24 months from the date of recordation of such Final Plat.
a. Each 24‐month extension period for the expiration of the original Preliminary Plat runs
from the date of the latest Final Plat recordation. Extension periods are not cumulative.
b. If a Final Plat is not recorded during the 24‐month extension period, the approval of the
original portion of the Preliminary Plat that has not been recorded, together with any
unrecorded Final Plat applications, lapses.
F. Changes to Approved Preliminary Plats
Changes to an approved Preliminary Plat that do not otherwise qualify as a deviation to the
approved Preliminary Plat as defined in Section 3.08.080.B.1.c, shall be processed as either an
amendment to the original Preliminary Plat or as a new Preliminary Plat application as follows:
1. Changes to a Preliminary Plat may be processed as an amendment to the original
Preliminary Plat if:
a. The proposed amendment does not alter the purpose and intent of the original
Preliminary Plat (i.e., commercial subdivision, single‐family residential large lot
subdivision);
b. The general design and layout of the original Preliminary Plat is maintained;
c. The proposed development density does not substantially increase or decrease; and
d. The amendment does not propose the removal or addition of an arterial level roadway.
2. The Director shall review the proposed changes, including any changes to the Phasing
Plan, in the same manner prescribed for the original Preliminary Plat approval.
3. Planning and Zoning Commission shall consider and take final action on an amendment to
a Preliminary Plat in the same manner prescribed for the original Preliminary Plat
approval.
4. Approval of a Preliminary Plat amendment shall not cause the expiration date established
with the original Preliminary Plat approval to be extended.
5. The development regulations in effect for the original Preliminary Plat approval shall be
applicable to the Preliminary Plat amendments.
6. All other changes to an approved Preliminary Plat that do not meet the provisions of this
Section, as determined by the Director, shall require submittal and approval of a new
Page 22 of 131
Page 14 of 35
Preliminary Plat application (including new fees, new review process, new approval dates,
etc.).
3.08.080 Recording Plats
Recording plats are those subdivision plats that are to be a document of legal record and include
Final Plats, Minor Plats, Development Plats, Replats, and Amending Plats.
A. Approval of Recording Plats
Except as otherwise required within this Chapter, recording plats are acted upon
administratively by the Director. The Director, at their discretion, may choose to forward a plat
to the Planning and Zoning Commission for final action. If the Director cannot approve the
plat, the plat must be forwarded to the Planning and Zoning Commission for final action.
B. Final Plats
1. Applicability
Final Plats are technically complete, recordable versions of an already approved
Preliminary Plat. Except as otherwise noted within this Section, no Final Plat may be
considered or approved unless the Preliminary Plat for the same land has been approved
and has not expired and the Final Plat is consistent with such Preliminary Plat or revision
thereof. The Final Plat must incorporate all changes from the Preliminary Plat that were
considered and approved by the Planning and Zoning Commission or the Director. Final
Plat review is used to ensure that a final recorded plat application includes final
engineering diagrams and descriptions that conform to the Preliminary Plat and the “as‐
built” infrastructure on the site. Exception to these requirements is allowed as follows:
a. No Public Infrastructure Proposed
A Final Plat may be approved without approval of a Preliminary Plat for the same
project if the division of land would otherwise qualify as a Minor Plat, but proposes
more than 4 lots. A Final Plat under this provision may not include the dedication of
land or require or propose the extension of any public infrastructure, including, but not
limited to, public utilities or roadways. Final Plats under this provision shall be
forwarded to the Planning and Zoning Commission for final action.
b. Combined Preliminary and Final Plat Option
Any division of land or platting activity that requires any of the following, but would
otherwise meet the definition of a Minor Plat, may be processed as a Combined
Preliminary and Final Plat, subject to the criteria of this Section and Section 3.08.070.
Any utility dedication; or
Any dedication of land.
The Director shall have the authority to determine if a plat meets the criteria to be
processed as a Combined Preliminary and Final Plat. This combined plat shall be titled
and processed as a Final Plat except that the Planning and Zoning Commission shall
have final action.
c. Deviations from the Approved Preliminary Plat
Minor Deviations
Page 23 of 131
Page 15 of 35
During review of the Final Plat, the Director may consider and approve minor
deviations from what was proposed on the approved Preliminary Plat.
Deviations that affect another proposed phase of the Preliminary Plat or that
affect property off‐site of the Preliminary Plat or any deviations that increase the
density of development shall not be considered minor. The deviations shall meet
any approval criteria applicable to the approved Preliminary Plat. A draft of the
proposed changes to the Preliminary Plat shall be provided to the Planning
Department as part of the application submission for the Final Plat. Approval by
the Director of such Final Plat shall be considered approval of the amendments
to the Preliminary Plat and shall cause an updated final copy of the Preliminary
Plat to be provided to the Planning Department prior to recordation of the Final
Plat. The Director may, at their discretion, choose to send proposed deviations to
the Planning and Zoning Commission for their consideration and final action.
The following deviations from the Preliminary Plat may be considered minor:
(a) Adjustments in alley, local, or collector street alignments or widths that do
not affect another proposed phase of the Preliminary Plat or adjacent
property;
(b) Changes to the lot lines, sizes, or configuration provided that the total
number of lots does not increase and the changes do not affect approved
infrastructure;
(c) Decreases in the number of lots by up to 10% or one lot, whichever is
greater, provided any minimum density requirements continue to be met,
if applicable;
(d) The splitting of a proposed phase of the Preliminary Plat into two phases if
the separation does not affect access or utilities to a later phase;
(e) The combining of adjacent proposed phases of the Preliminary Plat;
(f) A change in the order of adjacent phases of the Preliminary Plat, provided
adequate public infrastructure is available and is maintained for
subsequent phases; and
(g) Other similar changes as determined by Director.
Major Deviations from the Approved Preliminary Plat
Any Final Plat that proposes major deviations from the approved Preliminary
Plat shall be forwarded to the Planning and Zoning Commission for
consideration and final action. The deviations shall meet any approval criteria
applicable to the approved Preliminary Plat. A draft of the proposed changes to
the Preliminary Plat shall be provided to the Planning Department as part of the
application submission for the Final Plat. Approval by the Commission of such
Final Plat shall be considered approval of the amendments to the Preliminary
Plat and shall cause an updated final copy of the Preliminary Plat to be provided
to the Planning Department prior to recordation of the Final Plat.
The following deviations from the Preliminary Plat are considered major:
(a) Adjustments in Arterial roadway alignments or widths that do not affect
another proposed phase of the Preliminary Plat or property off‐site;
Page 24 of 131
Page 16 of 35
(b) Adjustments to lot lines, sizes, or configurations that do not increase or
decrease the total number of lots by more than 10% or one lot, whichever is
greater;
(c) Modification to proposed parkland;
(d) Changes in the location of the boundary line of a phase of the Preliminary
Plat to include part of another phase, provided no change in the layout of the
streets and lots of adjacent phases is required;
(e) Reordering of proposed phases of the Preliminary Plan, provided adequate
public infrastructure is maintained and the reordering does not affect
planned infrastructure off‐site; and
(f) Other similar changes as determined by Director.
All Other Changes
All other changes that affect property off‐site of the Preliminary Plat, or
otherwise do not fall within the limitations herein, shall not be processed as
deviations and shall follow the procedures of Section 3.08.070.F.
Determination
The Director shall make a determination of whether proposed deviations are
deemed to be minor or major.
2. Approval Criteria
A Final Plat shall not be considered for final action until the Director has determined the
following:
a. The Final Plat is acceptable for consideration, meaning the application is complete and
the information contained within the application is correct and sufficient to allow
adequate consideration and final action.
b. The Final Plat is consistent with an approved Preliminary Plat, except as provided for
in Section 3.08.080.B.1.
c. The Final Plat is consistent with any City‐approved construction plans for any required
or agreed improvements.
d. The Final Plat meets any subdivision design and improvement standards adopted by
the City pursuant to Texas Local Government Code §212.002 or Texas Local
Government Code §212.044, governing plats and subdivision of land within the City’s
jurisdiction to promote the health, safety, morals, or general welfare of the City and the
safe, orderly, and healthful development of the City.
e. The tract of land subject to the application is adequately served by public
improvements and infrastructure, including water and wastewater or will be
adequately served upon completion by the applicant of required improvements.
C. Minor Plats
1. Applicability
a. A Minor Plat is a plat for four or fewer lots fronting on an existing street and not
requiring the creation of any new street or the extension of municipal facilities and not
otherwise considered a Replat or Amending Plat.
Page 25 of 131
Page 17 of 35
b. Any plat that requires public improvements per this Unified Development Code, any
utility dedication or any dedication of land shall not be processed as a Minor Plat and
shall be processed in accordance with Section 3.08.070 or 3.08.080.B.1.b as applicable.
2. Approval Criteria
A Minor Plat shall not be considered for final action until the Director has determined the
following:
a. The Minor Plat is acceptable for consideration, meaning the application is complete and
the information contained within the application is correct and sufficient to allow
adequate consideration and final action.
b. The plat meets or exceeds the requirements of this Unified Development Code and any
applicable state or local laws.
c. The plat is consistent with the City’s Comprehensive Plan and any other adopted plans
as they relate to:
i. The City’s current and future streets, sidewalks, alleys, parks, playgrounds, and
public utility facilities; and
ii. The extension, improvement, or widening of City roads, taking into account
access to and extension of sewer and water mains and the instrumentality of
public utilities.
d. The plat meets any subdivision design and improvement standards adopted by the
City pursuant to Texas LGC § 212.002 or Texas LGC § 212.044, governing plats and
subdivision of land within the City’s jurisdiction to promote the health, safety, morals,
or general welfare of the City and the safe, orderly and healthful development of the
City.
e. The tract of land subject to the application is adequately served by public
improvements and infrastructure.
f. A Plat Waiver may be requested as a companion application to the consideration of a
Minor Plat, according to the provisions detailed in Section 3.22 of this Code. Such
Waivers and the Minor Plat shall be required to be approved by P&Z.
D. Development Plats
1. Applicability
For purposes of this Section, the term “development” means the new construction of any
building or structure not including construction of any building or improvement used for
agricultural, single‐family or two‐family purposes. Development Plats shall not include the
further division of the tract. A Development Plat shall be required prior to development of
any tract of land within the City or ETJ which was created or is proposed to be created via
an exemption outlined in Sections 3.08.020.A – 3.08.020.B or that has otherwise not been
platted, excluding the following:
a. Where another type of subdivision plat is otherwise required to be submitted per this
Chapter;
b. Construction of any building or improvement used for agricultural, single‐family or
two‐family purposes; or
Page 26 of 131
Page 18 of 35
c. Permits for repair or remodeling of an existing structure or for site improvements
(parking areas, driveways, etc.) which involve no increase in square footage.
2. Approval Criteria
A Development Plat shall not be considered for final action until the Director has
determined the following:
a. The Development Plat is acceptable for consideration, meaning the application is
complete and the information contained within the application is correct and sufficient
to allow adequate consideration and final action.
b. The Development Plat meets or exceeds the requirements of this Unified Development
Code and any applicable state or local laws.
c. The Development Plat is consistent with the City’s Comprehensive Plan and any other
adopted plans as they relate to:
i. The City’s current and future streets, sidewalks, alleys, parks, playgrounds, and
public utility facilities; and
ii. The extension, improvement, or widening of City roads, taking into account
access to and extension of sewer and water mains and the instrumentality of
public utilities.
d. The Development Plat meets any subdivision design and improvement standards
adopted by the City pursuant to Texas LGC § 212.002 or Texas LGC § 212.044, governing
plats and subdivision of land within the City’s jurisdiction to promote the health, safety,
morals, or general welfare of the City and the safe, orderly and healthful development of
the City.
e. The tract of land subject to the application is adequately served by public improvements
and infrastructure, including water and wastewater or will be adequately served upon
completion by the applicant of required improvements.
3. Responsibility for Final Action
The Planning Director shall have final decision whether to approve, approve with
conditions, or deny the Development Plat, except that a Development Plat that requires or
proposes the extension of public improvements, including utility easements or right‐of‐way
dedication, or any other public dedication of land shall be forwarded to the Planning and
Zoning Commission for final action.
D.E. Replats
1. Applicability
A property owner who proposes to further subdivide all or part of a recorded plat, without
first vacating that plat, must obtain approval for a Replat as outlined in the procedures
prescribed for the resubdivision of land under these regulations and Texas LGC Chapter
212.
2. Approval Criteria
A Replat shall not be considered for final action until the Director has determined the
following:
Page 27 of 131
Page 19 of 35
a. The Replat is acceptable for consideration, meaning the application is complete and the
information contained within the application is correct and sufficient to allow adequate
consideration and final action.
b. The plat meets or exceeds the requirements of this Unified Development Code and any
applicable state or local laws.
c. The plat is consistent with the City’s Comprehensive Plan and any other adopted plans
as they relate to:
i. The City’s current and future streets, sidewalks, alleys, parks, playgrounds, and
public utility facilities; and
ii. The extension, improvement, or widening of City roads, taking into account
access to and extension of sewer and water mains and the instrumentality of
public utilities.
d. The plat meets any subdivision design and improvement standards adopted by the
City pursuant to Texas LGC § 212.002 or Texas LGC § 212.044, governing plats and
subdivision of land within the City’s jurisdiction to promote the health, safety, morals,
or general welfare of the City and the safe, orderly, and healthful development of the
City.
e. The tract of land subject to the application is adequately served by public
improvements and infrastructure.
f. A Plat Waiver may be requested as a companion application to the consideration of a
Replat, according to the provisions detailed in Section 3.22 of this Code. Such Waivers
and the Replat shall be required to be approved by P&Z.
g. A Replat may not amend or remove any covenants or restrictions and is controlling
over the preceding plat.
3. Responsibility for Final Action
Pursuant to Texas LGC §212.0065, the Director of Planning and Development shall have
administrative authority for approval of a Replat, without Public Hearing, unless the
proposed Replat meets any of the following criteria. In such case, the Planning and Zoning
Commission, after a Public Hearing on the matter, is responsible for final action on the
Replat, except as otherwise noted.
a. The Replat involves more than 4 lots; or
b. Any lot proposed by the Replat does not front on an existing streets; or
c. The Replat does not require or propose the creation of any new street (requires
approval of a Plat Waiver pursuant to Section 3.22); or
d. The Replat requires or proposes the extension of municipal facilities (requires approval
of Preliminary Plat pursuant to Section 3.08.070); or
e. The area covered by the Replat is subject to the requirements of Paragraph 4Section
3.08.080.E.4 below; or
f. The Replat is companion to a request for Plat Waiver, per Section 3.22.
4. Additional Requirements for Certain Replats
Replats containing any area or lot that, during the preceding five years, was limited by an
interim or permanent zoning classification to residential use for not more than two
Page 28 of 131
Page 20 of 35
residential units per lot or in the preceding plat was limited by deed restrictions to
residential use for not more than two residential units per lot, require compliance with
Texas LGC §212.015 and shall meet the additional requirements outlined below.
a. Written notice of the Public Hearing required in Paragraph 3 above shall be mailed, in
accordance with Section 3.03.010.C, no less than 15 days prior to the Public Hearing, to
all owners of lots that are part of the original subdivision and located within 200 feet of
the boundary of the property to be replatted.
b. If the Replat application is accompanied by a Plat Waiver application, per Section 3.22,
and is legally protested in accordance with this Section, approval of the Replat shall
require the affirmative vote of at least three‐fourths of the voting members of the
Commission present at the meeting. For purposes of this Section, a protest is legal if it
is made in writing and signed by the owners of at least 20% of the area of the lots or
land (including streets and alleys) that was subject to the written notification required
above and filed with the Commission prior to the close of the Public Hearing on the
Replat.
E.F. Amending Plats
1. Applicability
An Amending Plat is any plat meeting the definition in Texas LGC §212.016.
2. Approval Criteria
An Amending Plat shall not be considered for final action until the Director has determined
the following:
a. The Amending Plat is acceptable for consideration, meaning the application is complete
and the information contained within the application is correct and sufficient to allow
adequate consideration and final action.
b. The plat meets the requirements of §212.016 of the Texas LGC.
c. The plat meets or exceeds the requirements of this Unified Development Code and any
applicable state law.
d. The plat is consistent with the recorded subdivision it is amending.
F.G. Recordation Requirements for Recording Plats
1. The recording plat is the instrument to be recorded in the Office of the County Clerk when
all requirements have been met. The plat is ready for recordation only after the following
has occurred:
a. The Director or the Planning and Zoning Commission has approved the plat;
b. For Final Plats, the Development Engineer has approved the Construction Plans;
c. For Final Plats, the subdivider has either filed a “financial guarantee of performance” or
completed required construction of infrastructure and public improvements;
d. The Director or the Chair and Secretary of the Planning and Zoning Commission have
signed the plat; and
e. Support documentation as required by the County Clerk’s office for plat recordation has
been provided to the Planning Department, including the filing fees.
2. The subdivider shall be responsible for paying all record filing fees.
Page 29 of 131
Page 21 of 35
G.H. Expiration of Recording Plats
An approved recording plat that has not been filed in the appropriate records of Williamson
County within 24 months of its approval shall expire and be considered null and void.
H.I. Vacation of Recorded Plat
In accordance with Texas LGC §212.013, after a plat has been recorded with the County, the plat
or any portion of the plat may be vacated by application of all the owners of property within the
original plat in the same manner as would be currently prescribed under this Code for approval
of the original plat (i.e. administrative, public hearing required, etc.).
3.08.090 Extension and Reinstatement of Approved Subdivision Plats
A. Extension of Approved Subdivision Plat
Prior to expiration of an approved Subdivision Plat, including Preliminary Plats and Recording
Plats, an applicant may request a one‐time extension of the Subdivision Plat approval for a
period of 24 6 months if the Director determines such extension will have no negative impacts
on the surrounding area and would not be contrary to the public interest. Approval of an
extension for a Final Plat that is subject to the requirement for a Preliminary Plat may only be
granted if the approval of the Preliminary Plat for such is also extended, if applicable. A
request for Subdivision Plat extension shall follow the procedures set forth for such in the UDC
Development Manual.
B. Reinstatement of Approved Subdivision Plat
In the event an approved Subdivision Plat, including Preliminary Plats and Recording Plats,
expires, an applicant may seek a one‐time reinstatement of the approved Subdivision Plat,
without modification, subject to the provisions below. Such reinstatement may be granted by
the Director for a period not to exceed 24 months. Approval of a reinstatement for a Final Plat
that is subject to the requirement for a Preliminary Plat may only be granted if the approval of
the Preliminary Plat for such is also reinstated, if applicable. A request for Subdivision Plat
reinstatement shall follow the procedures set forth for such in the UDC Development Manual.
1. The reinstatement must be requested within 24 months of the expiration date of the
approved Subdivision Plat.
The regulations applicable to the plat per the Code currently in effect may not be
determined to be significantly different from those applied to the original approval of the
Site Plan, such that a new application for the same plan would be substantially the same.
The circumstances of the subject property, roadways and adjacent properties shall have
remained the same, so as to not change the requirements applicable to the property. Such
circumstances could include, but not be limited to, a change in the boundary of the subject
property or a change in classification of the adjacent.
CB. The Director shall have the authority to determine if a Subdivision Plat Extension or
Reinstatement meets the criteria for processing and approval.
Page 30 of 131
Page 22 of 35
3.08.100 Construction Plans
A. Applicability
Construction plans conforming to the City’s Construction Specifications and Standards Manual
and this Code must be submitted to the Development Engineer for all existing or proposed
streets, sidewalks, drainage, and utility improvements, and any other infrastructure or public
improvements that are required or proposed to be constructed, reconstructed, improved or
modified to serve the development. Where the Final Plat is for property being developed in
phases, the required construction plans must include the improvements specified in the
Preliminary Plat to serve the phase being platted. The construction plans are intended to
provide detailed engineering drawings for all improvements required to serve the
development. The construction plans shall be kept as a permanent record of the City.
B. Construction or Financing of Public Improvements
1. After approval of a Preliminary Plat, Preliminary Final Plat, or a Development Plat
requiring public improvements, the subdivider shall notify the Development Engineer as to
the construction procedure the subdivider proposes to follow. One of the following
procedures shall be used:
a. The subdivider may file construction plans, and, upon approval of the construction
plans by the Development Engineer, proceed with construction of streets, alleys,
sidewalks, and utilities that the subdivider is required to install.
b. The subdivider may elect to file a “financial guarantee of performance” as provided in
Section 13.08, in which case the guarantee of performance shall be filed with the City.
2. Upon completion of construction the subdivider shall deliver to the City a onetwo‐year
maintenance bond for guarantee of workmanship and materials as provided in Section
13.098.
3. A conditional Construction Permit for a model home may be issued once the streets to the
subdivision have been constructed to sub‐grade and water service and a fire hydrant are
located within 500 feet of the lot on which the model home is located. The Building Official
shall note on the permit that the property owner accepts all responsibility for commencing
construction prior to completion of the public improvements and City acceptance of the
subdivision. The Certificate of Occupancy for the model home will not be issued until the
subdivision and all public improvements have been accepted by the City, a Final Plat has
been filed with the County and all utilities are connected to the home.
4. The construction documents, when duly signed by the Development Engineer, are authority
to proceed with the construction of streets and utilities.
C. Responsibility of Subdivider’s Engineer
The professional engineer representing the subdivider is responsible for the accuracy,
completeness, and conformance to the City’s Construction Specifications and Standards
Manual, this Code and all applicable City standards. The City has no project design or
engineering responsibility.
D. Approval Criteria
The purpose of the Development Engineer’s review is to ensure conformance to City policies
and standards. However, the Development Engineer’s review is limited to facts as presented on
Page 31 of 131
Page 23 of 35
submitted plans. The Drainage Engineer shall review any stormwater‐related issues and
comment to the Development Engineer.
1. The Development Engineer shall approve construction plans that are submitted and
sufficiently show compliance with any City‐approved or adopted design or construction
criteria manuals or in the absence of City‐approved or adopted design requirements,
standard engineering practices.
2. The City reserves the right to require corrections to actual conditions in the field that are
found to be contrary to or omitted from submitted plans.
3. The Development Engineer shall not approve construction plans that do not adequately
represent construction of the approved infrastructure and public improvements included in
the approved Preliminary Plat, Preliminary Final Plat, or Development Plat.
E. Responsibility for Final Action
The Development Engineer is responsible for final action on construction plans.
Section 3.09 Site Development Plan
3.09.010 Applicability
A. An approved, valid Site Development Plan is required prior to the construction, expansion, or
removal of any improvements to a property, as defined in Section 16.2 of this Code and
including driveways, sidewalks, drainage structures and utility improvements, within the
City’s limits, except as follows:
1. Single‐family and Two‐family structures, accessory structures, and fences on individually
platted lots; and
2. Agricultural buildings for the purposes of farming, ranching or sheltering of animals.
B. All improvements reflected on approved Site Development Plans must be constructed at the
time of development. All terms and conditions of Site Development Plan approval must be met
at the time of development.
C. The Site Development Plan may not be approved unless the lot on which the improvements are
proposed is legally platted or the subject tract is determined to be exempt from the platting
requirements of Section 3.08.
D. Where Site Development Plan approval is required, no Building Permit approval shall be issued
for any development of land and no site construction may commence until such property has
received final Site Development Plan approval and is in conformity with the provision of this
Code.
E. The provisions of this Section relating to Site Development Plans are adopted in accordance
with the Texas Local Government Code Chapter 211 and the City Charter.
3.09.020 Review Process
Review of a Site Development Plan shall follow the procedures set forth in Section 3.03.040 for
administrative review and shall be processed as follows:
Page 32 of 131
Page 24 of 35
A. Application Completeness
1. The applicant shall submit all of the information required in the UDC Development Manual
as specified on the Site Development Plan application checklist.
2. The Director shall determine that a complete application has been submitted with all
material necessary to review the Site Development Plan’s conformance with applicable
criteria for approval.
B. Staff Review
1. The Director shall review the application, considering any applicable criteria for approval,
and notify the applicant of any necessary corrections.
2. The Director may establish procedures for administrative review necessary to ensure
compliance with this Code and state statutes.
3. The Director may assign staff to review the application.
C. Responsibility for Final Action
The Director is responsible for final action on Site Development Plans.
3.09.030 Criteria for Approval
A Site Development Plan shall be approved if it is in compliance with the following criteria:
A. A complete application and fee have been submitted.
B. The application and content of the application are consistent with the provisions of this Unified
Development Code, the Comprehensive Plan, and any other applicable City regulations.
C. The application and content of the application are consistent with the UDC Development
Manual, City’s Construction Specifications and Standards Manual, this Code and any written
interpretations of this Code.
D. Site Development Plans may not be approved on any parcel of land not otherwise in
conformance with Section 3.08 of this Chapter.
DE. Compliance with any approved plat, Development Agreement or other agreement or
ordinance governing the parcel of land to which the Site Development Plan is related.
EF. Compliance with any additional Site Development Plan approval criteria required for Overlay
Districts or any Site Development Plan approval criteria adopted as part of a special area plan.
FG. Prior to final approval of any plan within the City Limits, the applicant must certify to the
Drainage Engineer that all City Drainage Manual requirements for a Stormwater Permit are met
by the Site Development Plan. Approval of the Site Development Plan constitutes approval of
the Stormwater Permit.
GH. The Site Development Plan shall conform to standard engineering practices and must be
sealed by a Professional Engineer licensed in the State of Texas, except as otherwise provided
for in this Section.
Page 33 of 131
Page 25 of 35
HI. The materials, embedment, and testing of all private main utility lines 6‐inches and above in
diameter shall meet the requirements of the City’s Construction Specifications and Standards
Manual and/or the approved City Building Codes.
3.09.040 Components of a Site Development Plan
All Site Development Plans shall include the following components demonstrating compliance with
the provisions of this Code and the UDC Development Manual, unless otherwise provided for within
this Section:
A. Cover Sheet;
A. Dimensional Site Plan;
B. Architectural Plan;
C. Lighting Plan;
D. Landscape Plan;
E. Tree Preservation Plan;
F. Utility Plan;
G. Grading Plan; and
H. Drainage Plan.
3.09.050 Site Development Plan Area of Development
A Site Development Plan shall include the entire area within the legal boundaries of the tract for
which it is proposed; however, the area included in a Site Development Plan may be reduced to
reflect the actual area of development in the situations listed below. The new artificial boundary
shall be the same used for all components of the Site Development Plan and shall be scaled such that
all requirements applicable to the Site Development Plan can be met within that boundary.
A. The area of development is part of a much larger tract whereby the area encompasses less than
50% of the total tract;
B. The proposed improvements are part of a larger campus where the areas are designed to
function relatively independent of each other;
C. The excluded area is to remain undeveloped and in its natural state;
D. The improvements are proposed to be added to an existing site, provided:
1. No improvements are proposed to the excluded area;
2. Review of the excluded area is not necessary for review of the area of development;
3. The improvements proposed within the area of development are not dependent on
improvements located within the excluded area; and
4. No retrofitting of existing site improvements is required pursuant to the provisions
applicable to the expansion of a nonconforming structure or site in Chapter 14; and
E. Other similar circumstances as determined by the Director.
Page 34 of 131
Page 26 of 35
3.09.060 Site Development Plan Phasing
When development is proposed for a larger site with multiple buildings, an applicant may choose to
partition the site and construct the improvements in a series of phases as follows:
A. The Site Development Plan submittal shall include a Phasing Plan indicating the boundaries of
each phase and the order of construction of associated site improvements.
B. No Phasing Plan shall propose more than 5 phases or exceed a period of 10 years. The Director
may approve phasing in excess of this number if the applicant can provide justification for such.
C. The proposed order of phasing shall follow a logical progression and, in the event subsequent
phases are not built, must meet the minimum requirements of this Code, including, but not
limited to, parking, landscaping, tree mitigation, fire access and stormwater management.
D. Changes to a Phasing Plan shall meet the requirements of this Section and follow the
procedures established for revisions of Site Development Plans.
3.09.070 Minor Site Development Plan
Where the scope of required or proposed site improvements is limited, as herein defined, a Minor
Site Development Plan review process may be utilized subject to the provisions below.
A. Determination of Minor Site Development Plan Review
1. A Minor Site Development Plan submittal may be considered when the extent, type or size
of the site improvements is such that review of all standard Site Development Plan
components, as identified in Section 3.09.040, is not necessary, as determined by the
Director. Typical situations qualifying for Minor Site Development Plan review may
include, but not be limited to, improvements required by Chapter 14 due to a change in use,
a small addition to a building over existing impervious coverage, installing parking lot
striping on an existing parking lot, replacement of a site’s landscaping, or where only one
component of a Site Development Plan, as outlined in Section 3.09.040, is required.
2. A Minor Site Development Plan review shall not be utilized when:
a. Site improvements are proposed to a property where no development has otherwise
occurred, except in unique situations as determined by the Director;
b. The proposed project requires preparation of a Traffic Impact Analysis (TIA);
c. The proposed project requires preparation of a stormwater drainage study, although
some drainage information may be reviewed as part of a Minor Site Plan;
d. A new building(s) in excess of 1,000 square feet is proposed;
e. A building addition is proposed in excess of 1,000 square feet or 20% of the existing
building‘s square footage, whichever is less;
f. The intended project requires or proposes more than 6 parking spaces; or
g. Similar situations are proposed as determined by the Director.
B. Components of a Minor Site Development Plan
The components required with a Minor Site Development Plan application shall be those
determined by the Director to be applicable to the particular situation and necessary to verify
the conformance of the proposed site improvements with the provisions of this Code. The
Page 35 of 131
Page 27 of 35
Director may determine an engineer is not required to prepare the plans under the Minor Site
Development Plan provisions if the proposed improvements do not warrant such.
3.09.080 Revisions to Approved Site Development Plans
Any modifications to an approved Site Development Plan must be resubmitted to the Director for
consideration as follows:
A. Modifications to an approved Site Development Plan which do not substantially change the
design or nature of the original Site Development Plan and have no significant adverse impact
upon neighboring properties, the public or persons who will occupy or use the proposed
development may be processed as a Site Development Plan Amendment. An application for
Site Development Plan Amendment following the requirements of the UDC Development
Manual shall be submitted to the Planning Department identifying the requested revisions and /
or modifications. Any changes approved by the Director shall be shown on the revised Site
Development Plan.
B. The Director may determine a correction or a modification is so minuscule or insignificant that
it does not warrant review of a Site Development Plan Amendment and cause the change to be
directly updated and included in the original file.
C. All other revisions or modifications to an existing Site Development Plan that do not meet the
provisions of Sections 3.09.080.A or 3.09.080.B above shall be processed as a new Site
Development Plan application.
D. Approval of a new or revised Site Development Plan application shall void the previously
approved Site Development Plan.
3.09.060 Expiration
A. A Site Development Plan shall expire 24 months after the date that the Site Development Plan
was approved, unless:
1. A Building Permit application has been approved or, if no Building Permit is required, a
Certificate of Occupancy has been issued.
2. In case of projects where more than one building or phase is to be built, the applicant may
submit a series of Building Permit applications. The first application must be approved
within 24 months from the date Site Development Plan approval is granted. Each
subsequent application must be approved within 24 months from the date of issuance of a
Certificate of Occupancy, conditional or otherwise, by the Building Official for the previous
phase of the development.
3. Except as provided for within this Section, a lapse of a period greater than those set forth
above causes the related approvals or permits to expire and be of no further force and effect.
Any further action shall require a new application and approval.
B. Site Development Plan Extension
Prior to expiration of an approved Site Development Plan, an applicant may request a one‐time
extension of the Site Development Plan approval for a period of 24 months if the Director
determines such extension will have no negative impacts on the surrounding area and would
Page 36 of 131
Page 28 of 35
not be contrary to the public interest. A request for Site Development Plan extension shall
follow the procedures set forth for such in the UDC Development Manual.
C. Site Development Plan Reinstatement
In the event a Site Development Plan approval expires, an applicant may seek a one‐time
reinstatement of the approved Site Development Plan, without modification, subject to the
provisions below. Such reinstatement may be granted by the Director for a period not to exceed
24 months. A request for Site Development Plan reinstatement shall follow the procedures set
forth for such in the UDC Development Manual.
1. The reinstatement must be requested within 24 months of the expiration date of the
approved Site Development Plan.
2. The regulations applicable to the project per the Code currently in effect may not be
determined to be significantly different from those applied to the original approval of the
Site Development Plan, such that a new application for the same plan would be
substantially the same.
3. The circumstances of the adjacent properties, roadways and subject property shall have
remained the same, so as to not change the requirements applicable to the property. Such
circumstances could include, but not be limited to, a change of zoning in the subject or
adjacent properties, a change in the boundary of the subject property, a change in
classification of the adjacent roadway or neighboring construction affecting landscape
buffers.
D. The Director shall have the authority to determine if a Site Development Plan Extension or
Reinstatement meets the criteria for processing and approval.
Section 3.10 Letters of Regulatory ComplianceZoning Verification
Letter
3.10.010 Applicability
A Letter of Regulatory ComplianceZoning Verification Letter, as defined in 3.10.020 A and B, may be
obtained upon written request as outlined in the Development Manual.
3.10.020 Types of Letters of Regulatory ComplianceZoning Verification Letter Defined
A. Zoning Verification Letter
A Zoning Verification Letter is a letter that indicates to a property owner that a specified use, clearly
identified in the application, is permitted within the Zoning District. A Zoning Verification Letter
does not authorize the property owner to proceed with a development; does not specify requirements
that must be met for future development; and does not include a determination that a tract of land
may be developed.
B. Legal Lot Verification Letter
An application may be made requesting the Director, or their designee, to provide a
determination of the legal platting status of a tract of land. The determination shall be provided
in written format in compliance with Local Government Code Subsection 212.0115. The
Director shall determine the following:
Page 37 of 131
Page 29 of 35
1. Whether a plat is required under this Chapter for the tract of land; and
If a plat is required, whether it has been prepared and whether it has been reviewed and
approved by the appropriate approving body.
Section 3.17 Stormwater Permit
3.17.010 Applicability
A To ensure conformance to the stormwater management provisions of this Code, a Stormwater
Permit is required prior to any land disturbance, as defined in Section 16.02, except for a single or
two‐family structure on a legal lot over one (1) acre or greater in the within the City limits or the
City’s extraterritorial jurisdiction (ETJ)to ensure conformance to the stormwater management
provisions and other applicable requirements of this Unified Development Code. Approval of a Site
Development Plan or Subdivision Construction Plans within the City Limits constitutes approval of a
Stormwater Permit for that specific development. The provisions of this Section related to
Stormwater Permitting are adopted pursuant to the authority conferred by the U.S. Environmental
Protection Agency, the Texas Commission on Environmental Quality, The Texas Local Government
Code Chapters 211 and 212, and the City Charter.
3.17.020 Review Process
Review of a Stormwater Permit shall follow the procedure set forth in Section 3.03.040.
3.17.030 Criteria for Approval
A. The applicant must ensure that the application for a Stormwater Permit was prepared or
reviewed, approved, and sealed by a Professional Engineer licensed in the State of Texas prior
to submission to the City, and that the application meets the requirements of the UDC
Development Manual.
B. A Stormwater Permit will be issued after the Drainage Development Engineer has determined
that the development meets the stormwater and pollution management requirements of
Chapter 11.
C. A Stormwater Permit is conditional upon all applicable related permits required from the Texas
Commission on Environmental Quality, the U.S. Environmental Protection Agency or any other
state or federal agency being issued by that agency.
C.D. A Grading Permit, processed and reviewed as a Stormwater Permit may be considered
by the Development Engineer for vegetation clearing and site grading during consideration of a
Site Development Plan in the city limits. Such a permit may be issued at the discretion of the
Development Engineer for specific activities such as understory removal and rough grading,
and shall not include removal of protected trees, utility work, paving or foundation. The
Development Engineer may revoke the permit and issue a stop‐work order if non‐compliant.
3.17.040 Responsibility for Final Action
The Drainage Development Engineer is responsible for final action on Stormwater Permits.
Page 38 of 131
Page 30 of 35
3.17.050 Expiration
A Stormwater Permit shall expire 24 months after the date that the permit was issued if the
stormwater facilities are not constructed in a manner consistent with improvements identified in the
permit are not constructed.
Section 3.19 Driveway Access Permit
3.19.010 Purpose
The purpose of a driveway Driveway Access permit Permit is to determine the safety, mobility, and
operational impacts that a proposed access connection will have on the roadway system.
3.19.020 Applicability
Driveway Access Permits are required for the following:
A. New driveway locations on roadways within the jurisdictional limits of the City of Georgetown;
B. Existing driveways on roadways within the jurisdictional limits of the City of Georgetown for
those developments which represent a change in property usage or zoning.
C. For the purposes of this Section the jurisdictional limits of the City of Georgetown shall include
properties within the municipal limits of the City as well as the Extraterritorial Jurisdiction
(ETJ).
D. The alteration of a public street curb or drainage facility, if not associated with an approved
Construction Plan or Building Permit. Such request shall comply with Chapter 12.08, Street
Excavations, of the Georgetown Municipal Code.
3.19.030 Pre-Application Conference
Pursuant to Section 3.02.010, a Pre‐application Conference is required prior to the issuance of a
permit application.
3.19.0340 Review Process
Review of a Driveway Access Permit shall follow the Administrative Review procedures set forth in
Section 3.03.040, subject to the Criteria for Approval set forth below.
3.19.0450 Criteria for Approval
No Driveway Access Permit will be denied unless it is determined by the Development Engineer that
the proposed location of the driveway will have an adverse effect upon the public safety. In making
this determination the following will be evaluated:
A. Existing driveways;
B. Land use (including but not limited to the intensity of development and trip attraction /
generation potential, mix of vehicles, and turning movements);
C. Function of public street (including but not limited to the number of lanes, medians, median
openings, vertical and horizontal curvature, sight distance, operating speeds, traffic volumes,
entrance / exit ramps, and frontage roads);
D. The location of nearby streets and driveways;
Page 39 of 131
Page 31 of 35
E. The site plan (including but not limited to on‐site circulation, delineation of the intended paths,
parking stalls, location of buildings, location of loading areas);
F. Actual or anticipated excessive increase in vehicular traffic being routed onto streets occurring
as a result of any such permit;
G. Physical constraints on the site including topography and site distance(s);
H. Unusual lot configurations;
I. Potential traffic movements which are unsafe or have an adverse effect on traffic operations;
J. Joint access at the time of subdivision or site plan approval for abutting lots which have
insufficient frontage to allow a driveway approach for each lot; and
K. That strict enforcement of the criteria for approval would result in a denial of access for the site.
3.19.0560 Submission Requirements
The Development Engineer will determine during the Pre‐application Conference Meeting if further
studies will be required. Such studies may include, but shall not be limited to, the following:
A. Engineering Study
1. An Engineering Study may be required based upon the determination of the Development
Engineer. In all cases the City will require only those elements of an engineering study that
are necessary to answer the specific questions that arise during the review process. The
engineering study shall conform to standard engineering practices and must be sealed by a
Professional Engineer licensed in the State of Texas. The Development Engineer will review
the following information in the determination to require an Engineering Study:
a. Compliance with the minimum spacing requirements of this Code;
b. Deceleration or acceleration lane required;
c. Traffic volumes and classification of the intersecting street at the proposed driveway
location;
d. Sight distance or physical obstructions and / or constraints that will result in a safety
problem;
e. Environmental or hydraulic issues associated with the proposed driveway(s); and
f. Lot configuration.
2. An Engineering Study shall contain the following information:
a. Trip Generation based upon the latest edition of the ITE Trip Generation Manual unless
there is acceptable data that supports the use of another trip generation source.
b. Trip Distribution, to be performed with input from the City.
c. Traffic assignment to determine the forecasted turning movements attributable to the
proposed development.
d. Traffic volumes if determined by the Development Engineer and subject to the following
criteria:
The existing traffic counts will be grown using an annual growth rate as agreed
to by the City to the build‐out year of the proposed development;
Page 40 of 131
Page 32 of 35
The resulting traffic volumes will be used as background traffic volumes, and the
assigned forecasted turning movements will be added to the background traffic
volumes resulting in the total traffic volumes; and
The total traffic volumes will be used to determine the need for left‐turn and
right‐turn lanes.
B. Traffic Impact Analysis (TIA)
1. A TIA may be required based upon the determination of the Development Engineer. In all
cases the City will require only those elements of a TIA that are necessary to answer the
specific questions that arise during the permitting process.
2. A TIA shall contain the following information:
a. All of the information outlined in Section 3.19.060.A.2 above.
b. Operational analysis (Level Of Service, Capacity, etc.) for the determined study
intersections.
c. Recommendations for mitigation measures should the impact of the proposed access
point(s) result in unacceptable levels of service.
3.19.0670 Responsibility for Final Action
The Development Engineer is responsible for final action on driveway Driveway Access
permitsPermits.
3.19.0780 Expiration
A driveway Driveway Access permit Permit will expire 18 months after issuance if the driveway is
not constructed in a manner consistent with the permit.
Section 3.21 License to Encroach
3.21.010 Purpose
The purpose of a License to Encroach is to determine the potential impacts of proposed
improvements, structures, facilities, and encroachments into a public street, roadway, sidewalk,
right‐of‐way, or easement in order to maintain their safety, mobility, and operational functionality.
3.2122.020 Applicability
A. A License to Encroach, in the procedures provided for in this section, is required for the
following:
1. New improvements, structures, facilities, and encroachments into a public street, roadway,
sidewalk, or right‐of‐way within the city limits and easements located within the city limits
or the extra‐territorial jurisdiction.
2. Existing improvements, structures, facilities and encroachments into a public street,
roadway, sidewalk, or right‐of‐way within the city limits and easements located within the
city limits or the extra‐territorial jurisdiction.
B. Those improvements, as defined in (A) above, that encroach into a public street, roadway, or
sidewalk shall obtain approval from the City Council, in addition to this License.
Page 41 of 131
Page 33 of 35
3.21.030 Pre-Application Conference
Pursuant to Section 3.02.010, a Pre‐Application Conference is required prior to the application for a
License to Encroach.
3.2122.040 030 Review Process
Review of a License to Encroach shall follow the Administrative Review procedures set forth in
Section 3.03.040, subject to the Criteria for Approval set forth below.
3.2122.050 040 Criteria for Approval
No License to Encroach will be denied unless it is determined by the Director Development Engineer
that the proposed location or type of improvement will negatively impact the function of the public
street, roadway, sidewalk, right‐of‐way, or easement or have an adverse effect upon the health,
safety, or welfare of the general public. In making this determination, the following will be
evaluated:
A. The proposed encroachment into a public street, roadway, sidewalk, right‐of‐way, or easement
by any person shall not interfere with the lawful use thereof.
B. Any proposed construction within a public street, roadway, sidewalk, right‐of‐way, or
easement shall be in accordance with this Code, the City’s adopted Construction Standards, and
any other applicable ordinances and regulations.
C. At any time during the construction of any structure within a public street, roadway, sidewalk,
right‐of‐way, or easement:
1. The applicable public street, roadway, or sidewalk shall be kept open for vehicular and
pedestrian traffic in a reasonable manner and sidewalks shall not be obstructed as to
prevent the use thereof by pedestrians;
2. Dirt and other material removed from the construction of any structure within a public
street, roadway, sidewalk, right‐of‐way or easement shall not be allowed to remain on the
street or sidewalk and shall be removed immediately at the sole cost, risk, liability, and
expense of the Licensee;
3. All excavations and obstructions of any kind that take place during the period of the
Licensee’s construction shall be properly barricaded and well‐illuminated during the night,
subject to the approval of the Building Official.
3.2122.060 050 Submission Requirements
Staff will may determine during the Pre‐Application Conference whether further studies will be
required. Such studies may include, but are not limited to, an Engineering Study, which may be
required at the determination of the Development Engineer. Only the elements of an engineering
study that are necessary to answer specific questions that arise during the review process will be
required for submittal.
3.2122.070 Responsibility for Final Action
The Director Development Engineer is responsible for final action on Licenses to Encroach into a
public easement. For those requests that encroach into a public street, roadway, or sidewalk, or right‐
Page 42 of 131
Page 34 of 35
of‐way, the Director may not approve the License to Encroach until final approval is shall be obtained
from the City Council.
3.2122.080 Expiration
A. The License shall expire if the encroachment allowed per the License is not installed within 24
months of the date of License approval.
B. The City shall provide written notice at least 180 days in advance to the Licensee, its
representatives, successors, or assigns, to take possession of and use all or any part of the licensed
area in the event that such use be reasonably desired or needed by the City for street, sewer,
transportation, or any other public or municipal use or purpose. During such time, it is the
responsibility of the Licensee, its representatives, successors or assigns to remove the
encroachment(s). In such an event, the City shall have the right to cancel the revocable license as to
that portion of the licensed area so designated and required by the City.
Section 3.22 Plat Waiver Subdivision Variance
3.2223.010 Applicability
A waiver variance of the certain subdivision standards of this Code, as allowed by this
Sectionprovided for within this Code, may be considered concurrently with a Preliminary Plat, Final
Plat, Minor Plat, or FinalDevelopment Plat, or Replat to address unforeseen circumstances or other
difficulties in developing a property under the specific provisions of this Code. A Subdivision
VariancePlat Waiver application may be filed without a companion plat application in very limited
circumstances if the granting of the variance would eliminate the requirement of the plat, as
determined by the Director. Justification for the Subdivision VariancePlat Waiver shall be submitted
and demonstrated, following the provisions of Section 3.23.070. The Waiverariance(s) may be
approved, conditionally approved or disapproved by the Planning and Zoning Commission. Any
approved Waiverariance shall be noted on the corresponding plat. A Waiver does not constitute nor
equal a Variance, the provisions of which are detailed in Section 3.15 of this Code.
3.22.020 Eligible Provisions
The provisions of this Code that are considered eligible for a plat waiver are listed below. A request
may be made for each specific provision in only these sections:
A. Section 6.02.010
A. Section 6.02.030
B. Section 6.02.040
C. Section 7.02.010
D. Section 7.02.030
E. Section 7.02.040
3.2223.030 020 Initiation
Initiation of the Plat WaiverSubdivision Variance may be made upon submittal of a complete
application by a property owner or their designated agent.
Page 43 of 131
Page 35 of 35
3.2223.040 030 Application and Completeness Determination
The applicant shall submit all of the information required in the UDC Development Manual. The
Director is responsible for determining the completeness of an application submitted, pursuant to
Section 3.02.040.
3.2223.050 040 Staff Review
A. The Director shall review the application, considering applicable criteria for approval, and
prepare a report to the Planning and Zoning Commission.
B. The Director may establish procedures for administrative review necessary to ensure
compliance with this Code and state statute.
C. The Director may assign staff to review the application and make a report to the Director.
D. The Director’s report may include a recommendation for final action.
3.2223.060 050 Planning and Zoning Final Action
Following notice in accordance with Section 3.03, the Commission shall hold a public hearing in
accordance with its rules and state law and consider the Plat WaiverSubdivision Variance, Director’s
report, state law, and compliance with this Code, and take final action. Approval of a Subdivision
Variance shall require a super‐majority vote of the members present. Any approved Subdivision
Variance shall be noted on all corresponding plats, if applicable.
3.2223.070 060 Approval Criteria
A Plat WaiverSubdivision Variance may be approved, conditionally approved, or disapproved. At
least three four of the following factors are required for approval:
A. That the granting of the waiver will not be detrimental to the public health, safety or welfare or
injurious to other property in the area or to the City in administering this Code.
B. That the granting of the waiver would not substantially conflict with the Comprehensive Plan
and the purposes of this Code.
C. That the conditions that create the need for the waiver do not generally apply to other property
in the vicinity.
D. That application of a provision of this Code will render subdivision of the land impossible.
E. Where the literal enforcement of these regulations would result in an unnecessary hardship.
3.2223.080 Expiration of Plat WaiverSubdivision Variance
The Subdivision VariancePlat Waiver(s) shall expire if the Preliminary, Administrative, or Final
Platcorresponding plat expires, according to the timing specified in Section 3.08 of this Code. The
Subdivision VariancePlat Waiver(s) shall have no authority beyond the recorded plat note(s).
Page 44 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 6, Res id ential Develo p ment S tand ard s . Valerie
Kreger
ITEM SUMMARY:
Since the last d is c us s io n o n Chap ter 6, staff has ad d ed provis io ns fo r a Subdivis io n Variance fo r minimum
lo t width and frontage and increased the street-fac ing s etbac k fo r garages to 25 feet.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 6 Cover Memo
Page 45 of 131
Page 1 of 32
Chapter 6 Residential & Agriculture Zoning Districts: Lot,
Dimensional & DesignDevelopment Standards
Section 6.01 General
6.01.010 Authority
The provisions of this Chapter are adopted pursuant to the Texas Local Government Code Chapter 211
and 212 and the City Charter.
6.01.020 Purpose and Intent
The Residential Lot, Dimensional and Design StandardsThis Chapter establishes regulations
development standards for residential developmentresidential properties within the city limits and ETJ
of the City of Georgetown in any Residential Zoning District (see Table 4.01.010 for list of Residential
Zoning Districts), development in any other zoning districts as required elsewhere in this Code, and
minimum requirements for development within the City’s extraterritorial jurisdiction (ETJ).
The standards in this Chapter allow for a variety of housing types and development standards while
maintaining the overall character of Georgetown. The standards are established to regulate the
manner in which land is developed, minimize adverse effects on surrounding properties and the
general public, and ensure that high quality development is maintained throughout the community.
The approach to development standards has several public benefits:
1. It allows for development that is more sensitive to the environment.
2. It allows for the preservation of open and natural areas.
3. It promotes better site layout and opportunities for recreational areas.
4. It promotes energy-efficient development.
6.01.030 Applicability
A. Within the Extraterritorial Jurisdiction (ETJ)
All residential development within the City’s ETJ is subject to the following sections:provisions of
1. Section 6.02.010.
2. Section 6.02.020, if fire services are provided by the City of Georgetown.
B. Within the City Limits
1. All residential development within the City Limits isa Residential Zoning District shall be
subject to all the provisions of this Chapter.
2. All residential development within a Non-residential Zoning District shall be subject to the
provisions of Sections 6.05 and 6.06 in addition to the development standards of the zoning
district in which it is located.
3. All non-residential development within a Residential Zoning District or the Agriculture
District shall be subject to the Building Design Standards set forth in Section 7.04 and the
Page 46 of 131
Page 1 of 32
Lighting Standards set forth in Section 7.05 in addition to the development standards of the
zoning district in which it is located.
Section 6.02 Uniform Development Standards
6.02.010 General Lot Requirements
No building permits or other development approvals shall be issued for development that does not
meet the following minimum requirements:
A. All new development shall be located on a legal lot or tract meeting the requirements of Section
3.08 of this code.
B. All new lots or tracts within the city limitsdevelopment (with the exception of open space or
drainage lots) shall have a minimum lot width and streetdirect access and frontage on one of the
following:along a
1. A public street in accordance with the zoning district in which it is located. All new lots or
tracts in the ETJ shall have a minimum lot width and street frontage along a public street; or
2. A public street via a public alley.
C. All development applications submitted after October 27, 2009, shall meet the provisions of
Paragraph (B), above, at a minimum width of 25 feet. A Subdivision Variance varying or waiving
these requirements may be requested pursuant to Section 3.22 of this Code.
D. Intersection visibility shall comply with the provisions set forth in Section 12.03.050.
E. Side lot lines shall intersect rights-of-way at an angle between 60 and 90 degrees on a straight
street or from the tangent of a curved street.
F. All lots must be numbered consecutively within each block, phase and plat.
G. No building or structure shall be constructed across lot lines.
6.02.020 Fire Code Compliance
C. All development within the city limits and areas of the ETJ where the City provides fire
protection services shall comply with the applicable standards contained in the International Fire
Code, as adopted in the City of Georgetown Code of Ordinances, Chapter 8.04. When such
standards conflict with any lot, dimensional, and design standards of this Code, the International
Fire Code standards shall apply.
6.02.030 Lot Standards
A. Structures per Lot
No more than one principal structure may be erected on a single lot or parcel, except as otherwise
specifically provided in this Chapter or under the criteria in Section 5.03.
B. Existing Structures
The subdivision or re-subdivision of a tract or lot shall not cause an existing permanent structure
to violate the standards of this Code.
Page 47 of 131
Page 1 of 32
C. Structures Crossing Lot Lines
Lots with an existing building or other permanent structure built across a shared lot line shall be
treated as a single lot, with the shared lot line not considered for measurement of all dimensional
standards. All required dimensional standards, including required setbacks and lot coverage
standards shall be applied as if the two individual lots were a single lot. No portion of the two
lots may be replatted if such replatting would cause the combined lots to become noncompliant
with any provisions of this Code or the City Code of Ordinances or any other City requirement.
The provisions of this Section apply only to buildings or permanent structures that were in
existence on or before March 11, 2003, and no new building or structure shall be constructed
across lot lines.
D. Double Frontage
1. Residential lots shall not have frontage on two non-intersecting local or collector streets,
unless access is restricted to the street with the lower classification.
2. Residential lots shall not take vehicular access from an arterial street if access to a local street
is available.
3. Non-Residential development in Residential Districts on lots with double frontage shall have
offset access points from the opposing streets to inhibit cut-through traffic.
6.02.040 Blocks
A. Width
Blocks shall have sufficient width to provide for two tiers of lots except where a single tier may:
1. Separate lots from an incompatible use;
2. Accommodate a requirement for single loaded streets;
3. Allow for unusual topographical conditions; or
4. When located adjacent to the outer perimeter of a subdivision.
B. Length
Block lengths shall not exceed 20 lots or be longer than 1,320 feet, whichever is shorter. Block
lengths shall be ended only by the intersection of a public street except where there is no public
street intersection due to the presence of parks, open spaces or other similar uses with at least 100
feet of street frontage on the relevant block.
Section 6.03 Development Standards
6.03.010 General
A. In addition to the lot, dimensional, and design standards in this Chapter, all residential
development in a Residential Zoning District or in the Agricultural District shall comply with any
applicable requirements contained in other Chapters of this Code.
B. In addition to the provisions of this Code identified in Section 6.03.010.A, all Non- Residential
development in a Residential Zoning District or in the Agricultural District shall also comply
Page 48 of 131
Page 4 of 32
with the Building Design and Site Design standards set forth in Sections 7.04 and 7.05 of this
Code.
C. In the case of any conflict between the lot, dimensional or design standards in this Chapter and in
any other provision of this Code, the City Code of Ordinances or any national or international
code as adopted by the City of Georgetown (e.g., Fire Code, Building Code) the more restrictive
or stringent provision shall apply.
6.0302.020 AG – Agriculture District
The Agriculture District (AG) is intended to allow large rural residential development, agricultural,
and farming uses and may include lands that are relatively undeveloped. The AG District is also the
default district for land newly annexed into the City, but not yet placed in an appropriate zoning
classification. For these reasons, the AG District may contain a wide variety of residential and non-
residential uses. The AG District may take on characteristics of either a residential or a non-residential
zoning district and certain design criteria may be required depending on the use.
A. Lot and Dimensional Standards
AG - Agriculture
Lot Size, minimum 2 acres
Lot Width, minimum feet 100
Corner Lot Width, minimum feet 100
Front Setback, minimum feet 25
Side Setback, minimum feet 10
Rear Setback, minimum feet 20
Side/Rear Street Setback, minimum feet 20
Street Facing Garage Setback, minimum feet 250
Unloaded Street Setback, minimum feet 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Single-family, detached (minimum lot size: 2 acres).
2. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowed in the
AG District.
3. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the AG District.
4. Those accessory uses identified in Section 5.01.020.E of this Code that may be compatible
with the primary uses allowed in the AG District.
Page 49 of 131
Page 5 of 32
C. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet the lot and dimensional standards of the AG District,
in addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure. However, accessory structures associated with a non-residential use allowed in
Table 5.07.010 (Agricultural Uses) may exceed the height of the principal structure provided
the maximum building heights of the district are not exceeded.
D. Other Requirements of This Chapter
1. Dimensional Interpretations and Exceptions, Section 6.0504.
2. Accessory Structures, Garages and CarportsSite Design Standards, Section 6.0605.
6.0302.030 RE - Residential Estate District
The Residential Estate District (RE) is intended for areas of very low density Single-family residential
use and associated uses. The District has a lot size minimum of 1 acre to retain a rural character and is
appropriate where topography or lack of public utilities and services may necessitate a low density.
A. Lot and Dimensional Standards
RE - Residential Estate
Lot Size, minimum 1 acre
Lot Width, minimum feet 100
Corner Lot Width, minimum feet 100
Front Setback, minimum feet 25
Side Setback, minimum feet 10
Rear Setback, minimum feet 20
Side/Rear Street Setback, minimum feet 20
Street Facing Garage Setback, minimum feet 250
Unloaded Street Setback, minimum feet 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Single-family, detached (minimum lot size: 1 acre).
2. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowed in the
RE District.
3. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the RE District.
Page 50 of 131
Page 6 of 32
4. Those accessory uses identified in Section 5.01.020.E of this Code that may be compatible
with the primary uses allowed in the RE District.
C. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet the lot and dimensional standards of the RE District, in
addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
D. Other Requirements of This Chapter
1. Dimensional Interpretations and Exceptions, Section 6.0504.
2. Accessory Structures, Garages and CarportsSite Design Standards, Section 6.0605.
6.0302.040 RL - Residential Low Density District
The Residential Low Density District (RL) is intended for areas of low density Single-family residential
use and associated uses. The RL District is intended to allow larger lots than in the RS District with a
minimum of 10,000 square feet. The pattern of residential development and land use closely matches
that of the Residential RS District.
A. Lot and Dimensional Standards
RL - Residential Low Density
Lot Size, minimum square feet 10,000
Lot Width, minimum feet 70
Corner Lot Width, minimum feet 70
Front Setback, minimum feet 20
Side Setback, minimum feet 10
Rear Setback, minimum feet 10
Side/Rear Street Setback, minimum feet 15
Street Facing Garage Setback, minimum feet 250
Unloaded Street Setback, minimum feet 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Single-family, detached (minimum lot size: 10,000 sq. ft.).
2. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowed in the
RL District.
3. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the RL District.
Page 51 of 131
Page 7 of 32
4. Those accessory uses identified in Section 5.01.020.E of this Code that may be compatible
with the primary uses allowed in the RL District.
C. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet the lot and dimensional standards of the RL District, in
addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
D. Other Requirements of This Chapter
1. Dimensional Interpretations and Exceptions, Section 6.0504.
2. Accessory Structures, Garages and CarportsSite Design Standards, Section 6.0605.
6.0302.050 RS - Residential Single-family District
The Residential Single-family District (RS) is intended for areas of medium density with a minimum
lot size of 5,500 square feet. The RS District contains standards for development that maintain Single-
family neighborhood characteristics. The District may be located within proximity of neighborhood-
friendly commercial and public services and protected from incompatible uses. All housing types in
the RS District shall use the lot, dimensional and design standards of the District.
A. Lot and Dimensional Standards
RS - Residential Single-family
Lot Size, minimum square feet 5,500
Lot Width, minimum feet 45
Corner Lot Width, minimum feet 55
Front Setback, minimum feet 20
Side Setback, minimum feet 6
Rear Setback, minimum feet 10
Side/Rear Street Setback, minimum feet 15
Street Facing Garage Setback, minimum feet 250
Unloaded Street Setback, minimum feet 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Single-family, detached (minimum lot size: 5,500 sq. ft.).
2. Single-family, attached (provided that the requirements in Section 6.02.050.C.2 are met).
3. Single-family, zero lot line (provided that the requirements in Section 6.02.050.C.3 are met).
Page 52 of 131
Page 8 of 32
4. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowed in the
RS District.
5. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the RS District.
6. Those accessory uses identified in Section 5.01.020.E of this Code that may be compatible
with the primary uses allowed in the RS District.
C. Residential Design Standards
The design standards below apply to all development in the RS District in addition to the Site
Design Standards in Section 6.0605.
1. Similarity Restrictions
Except as provided in subsection (a) below, no new dwelling that is similar in appearance to
a neighboring dwelling is permitted. The standards to determine such similarity are set forth
below and shown by example in the illustrations contained in this section.
a. Exemptions
The following shall be exempt from these provisions:
i. Dwellings for which a Building Permit was approved before March 11, 2003.
ii. Dwellings within a Housing Diversity Development, where a unified plan
containing similarity of architectural form and style among dwellings is integral to
such a plan.
b. Differences in Appearance
i. Differences in bulk and massing shall be reviewed for the lots on either side of the
proposed dwelling on the same side of the street, as shown in the following
illustrations.
ii. Where lots are interrupted by an intervening street, public parkland, or similar
feature of at least 50 feet in width, no review shall be necessary.
iii. The proposed building shall be considered different from any vacant lot for which
no Building Permit has been issued without requiring further documentation.
c. Differentiation
The proposed dwelling shall differ from other applicable dwellings in at least two of the
five criteria listed below.
i. The dwelling is a different housing type.
• Single-family detached;
• Single-family attached; or
• Single-family, Zero lot line.
ii. The dwelling differs in the number of full stories.
• Single-story; or
Page 53 of 131
Page 9 of 32
• Two-story.
iii. The dwelling has a different type of garage.
• Front-loaded garage (one or two-car);
• Side-loaded garage; or
• Detached garage.
iv. The dwelling has a different roof type.
• Gable;
• Hip;
• Gambrel;
• Mansard; or
• All of the above roof types are rotated 90 degrees.
v. The dwelling has variation in the front façade.
• The garage is set back a minimum of 4 feet from the front façade;
• A covered, open-walled porch at least 6 feet in depth extends a minimum of 33%
of the width of the front façade; or
• Other articulation of the front façade at least 4 feet in depth extends at least 33%
of the width of the front façade.
d. Application Review
i. Acceptable documentation may include photographs of the other structures in
question (no building elevations are required).
ii. A subdivision or phase thereof may be reviewed as a whole for conformity with
this requirement, provided that adequate documentation to ensure conformity is
submitted with the plat. Such documentation is not required to be recorded as part
of the plat.
iii. The Building Official shall review the submitted documentation and any
previously-approved Building Permits and make a determination. Where the
Building Official finds that a dwelling for which a Building Permit is being
requested is similar in appearance based on the standards above, the Building
Permit shall be denied.
2. Single-family, Attached
A Single-family, attached dwelling is allowed using the lot and design standards of the RS
District, in addition to the following criteria:
a. Both dwellings shall be located on separate legal lots;
b. The side setback between two Single-family attached lots may be reduced to zero feet;
and
c. Single-family, attached dwellings are not allowed in the Old Town Overlay District.
Page 54 of 131
Page 10 of 32
3. Single-family, Zero-Lot Line
A Single-family, zero-lot line dwelling is allowed using the lot and design standards of the
RS District, in addition to the following criteria:
a. The zero-lot line shall not be the lot line adjacent to:
i. A lot not containing or planned for zero-lot line dwellings;
ii. A highway frontage road; or
iii. A garage or carport taking access from a side street.
b. A minimum building separation of 12 feet is provided between all zero-lot line
dwellings.
c. The eaves on the side of a house with no side setback may project no more than 18 inches
over the adjacent property line and a perpetual easement or deed restriction for the eave
projection is recorded for the lot where the projection occurs.
d. No structure extends into a public easement.
e. Any rain gutters are positioned to drain only onto the lot of the house to which they are
attached.
f. A recorded easement or deed restriction is provided to allow for maintenance or repair
when the eaves or side wall of the house are within 4 feet of the adjacent property line.
The easement or deed restriction on the adjacent property must provide at least 5 feet of
unobstructed space between the furthermost projection of the structure(s) and the edge
of the easement.
g. No windows or other openings on the side of the structure on or within 3 feet of the lot
line with no setback are allowed, except for windows that do not allow or restrict
visibility of the adjacent lot, such as clerestory or translucent windows.
D. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet the lot and dimensional standards of the RS District, in
addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
E. Other Requirements of This Chapter
1. Dimensional Interpretations and Exceptions, Section 6.0504.
2. Accessory Structures, Garages and CarportsSite Design Standards, Section 6.0605.
6.0302.060 TF - Two-family District
The Two-family District (TF) is intended for Two-family dwellings that are located on one lot. The TF
District also includes Single-family attached and Single-family detached development and associated
uses. Two-family and Single-family dwellings are permitted on individual lots, but the lot,
dimensional and design standards are intended for two dwellings in one structure on a single lot. The
Page 55 of 131
Page 11 of 32
TF District is a moderate density District that may be used to separate residential areas zoned RE, RL
or RS from higher density residential and commercial areas.
In the TF District, a maximum of two units per structure may be erected on a single lot.
A. Lot and Dimensional Standards
TF - Two Family
Lot Size, minimum square feet 7,000
Dwelling Size, minimum square feet 3,500
Dwellings per Structure, maximum 2
Lot Width, minimum feet 70 (C.1)
Corner Lot Width, minimum feet 780
Front Setback, minimum feet 20
Side Setback, minimum feet 6
Rear Setback, minimum feet 10
Side/Rear Street Setback, minimum feet 15
Street Facing Garage Setback, minimum feet 250
Unloaded Street Setback, minimum feet 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Two-family.
2. Single-family, detached.
3. Single-family, attached (provided that the requirements of Section 6.02.060.C.2 are met).
4. Single-family, zero lot line (provided that the requirements of Section 6.02.060.C.3 are met).
5. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowed in the
TF District.
6. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the TF District.
7. Those accessory uses identified in Section 5.01.020.E of this Code that may be compatible
with the primary uses allowed in the TF District.
C. Residential Design Standards
The design standards below apply to all dwellings in the TF District in addition to all Site Design
standards in Section 6.0605.
Page 56 of 131
Page 12 of 32
1. Minimum Lot Width Reduction
The minimum lot width for a Two-family dwelling may be reduced to 60 feet, 30 feet per
dwelling, when the required off-street parking is located behind each dwelling with
approved rear access.
2. Single-family, Attached
A single-family, attached dwelling is allowed using the lot and design standards of the TF
District, in addition to the following criteria:
a. Both dwellings shall be situated on separate legal lots;
b. The minimum lot size is 4,500 square feet;
c. The side setback between two single-family, attached lots may be reduced to zero feet;
d. The minimum lot width for a single-family, attached dwelling is 45 feet, although the
width may be reduced to 35 feet when the required off-street parking is located behind
the dwelling with approved rear access; and
e. Single-family, attached dwellings are not allowed in the Old Town Overlay District.
3. Single-family, Zero-Lot Line
A Single-family, zero-lot line dwelling is allowed using the lot and design standards of the
TF District, in addition to the following criteria:
a. The zero-lot line shall not be the lot line adjacent to:
i. A lot not containing or planned for zero-lot line dwellings;
ii. A highway frontage road; or
iii. A garage or carport taking access from a side street.
b. A minimum building separation of 12 feet is provided between all zero-lot line
dwellings.
c. The eaves on the side of a house with no side setback may project no more than 18 inches
over the adjacent property line and a perpetual easement or deed restriction for the eave
projection is recorded for the lot where the projection occurs.
d. No structure extends into a public easement.
e. Any rain gutters are positioned to drain only onto the lot of the house to which they are
attached.
f. A recorded easement or deed restriction is provided to allow for maintenance or repair
when the eaves or side wall of the house are within 4 feet of the adjacent property line.
The easement or deed restriction on the adjacent property must provide at least 5 feet of
unobstructed space between the furthermost projection of the structure(s) and the edge
of the easement.
g. No windows or other openings on the side of the structure on or within 3 feet of the lot
line with no setback are allowed, except for windows that do not allow or restrict
visibility of the adjacent lot, such as clerestory or translucent windows.
Page 57 of 131
Page 13 of 32
D. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet the lot and dimensional standards of the TF District, in
addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
E. Other Requirements of This Chapter
1. Dimensional Interpretations and Exceptions, Section 6.0504.
2. Accessory Structures, Garages and CarportsSite Design Standards, Section 6.0605.
6.0302.070 TH – Townhouse District
The Townhouse District (TH) is intended for townhouse and attached single-family development. The
TH District is appropriate for infill development as well as a transition from residential areas to non-
Residential areas. This District is also appropriate in areas designated on the Future Land Use Plan as
one of the Mixed Use Land Use Categories.
In the TH District, townhomes shall be located on individual lots. A townhouse row shall not include
more than six connected units.
A. Lot and Dimensional Standards
TH - Townhouse
Townhouse Lot Size, minimum square feet 2,000
Dwelling Units per Row, maximum 6
Townhouse Lot Width, minimum feet 22
Corner Lot Width, minimum feet 32
Front Setback, minimum feet 15
Non-shared Wall Side Setback, minimum feet 10
Shared Wall Side Setback, minimum feet 0
Rear Setback, minimum feet 15
Side/Rear Street Setback, minimum feet 15
Street Facing Garage Setback, minimum feet 250
Unloaded Street Setback, minimum feet 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Townhouse (individual lots).
2. Single-family, attached (provided that the requirements in Section 6.0302.070.C.6 are met).
Page 58 of 131
Page 14 of 32
3. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowed in the
TH District.
4. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the TH District.
5. Those accessory uses identified in Section 5.01.020.E of this Code that may be compatible
with the primary uses allowed in the TH District.
C. Residential Design Standards
The design standards below apply to all dwellings in the TH District in addition to all Site Design
standards in Section 6.0605.
1. Required Setbacks
a. Except as otherwise provided herein, the minimum front setback shall be 15 feet. A
minimum front setback of 10 feet is permissible when off-street parking access is limited
to the rear of the property.
b. A minimum side setback of 10 feet is required for a building if it is on a corner lot or at
the end of a row of townhouses.
2. Building Design
Townhouse development shall comply with the Building Materials requirement in Section
7.04.040 and contain variation through articulation of the front façade, using at least one of
the following:
a. A garage that is set back at least 4 feet from the front façade;
b. A covered, open-walled porch of at least 6 feet in depth extends at least 50% of the width
of the front façade; or
c. Other articulation of the front façade at least 4 feet in depth that extends at least 50% of
the width of the front façade.
3. Private Open Space
For townhouse development, each dwelling unit shall be provided with a private yard or
open space of not less than 150 square feet, which shall be immediately accessible and
functional to the dwelling that it serves. Such open space may be at the front, rear or side of
the dwelling unit and shall be in addition to the required setbacks or common amenity area
requirements.
4. Common Amenity Area
Common Amenity Areas are required for townhouse development in accordance with
Section 6.06.020.
5. Bufferyards
A Low Level Bufferyard is required for development in the TH District adjacent to the AG,
RE, RL and RS Districts. When internal to a Housing Diversity Development (Section
6.07.020), bufferyards shall not be required. See Section 8.04.060 for Bufferyard requirements.
Page 59 of 131
Page 15 of 32
6. Single-family, Attached
Single-family, attached dwellings are allowed using the lot and design standards of the TH
District, except as stated below:
a. Both dwellings are situated on separate legal lots.
b. The minimum area per dwelling is 4,500 sq. ft.
c. The minimum lot width for a Single-family, attached dwelling is 45 feet, although the
width may be reduced to 35 feet when the required off-street parking is located behind
the dwelling with approved rear access.
d. Single-family, attached dwellings are not allowed in the Old Town Overlay District.
D. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet all of the lot and dimensional standards of the TH
District, in addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
E. Other Requirements of This Chapter
1. Dimensional Interpretations and Exceptions, Section 6.0504.
2. Site Design StandardsAccessory Structures, Garages and Carports, Section 6.0605.
3. Common Recreation Amenity Area, Section 6.06.020.
6.0302.080 MF-1 - Low Density Multi-family District
The Low Density Multi-family District (MF-1) is intended for attached and detached multi- family
residential development, such as apartments, condominiums, triplexes, and fourplexes, at a density not
to exceed 14 dwelling units per acre. The MF-1 District is appropriate in areas designated on the Future
Land Use Plan as High Density Residential or one of the Mixed-Use categories, and may be
appropriate in the Moderate Density Residential area based on location, surrounding uses, and
infrastructure impacts. Properties zoned MF-1 should have convenient access to major thoroughfares
and arterial streets and should not route traffic through lower density residential areas. The MF-1
District is appropriate adjacent to both residential and non- residential districts and may serve as a
transition between single-family districts and more intense multi-family or commercial districts.
Page 60 of 131
Page 16 of 32
A. Lot and Dimensional Standards
MF-1 - Low Density Multi-family
Lot Size, minimum square feet 12,000
Dwelling Units per acre, maximum 14
Apartment Units per structure, maximum 12
Lot Width, minimum feet 50
Front Setback, minimum feet 20
Side Setback, minimum feet 10
Side Setback to Residential District, minimum feet 20
Rear Setback, minimum feet 10
Rear Setback to Residential District, minimum feet 20
Side/Rear Street Setback, minimum feet 15
Unloaded Street Setback 20
Building Height, maximum feet 35
Impervious Cover, maximum % See Section 11.02
B. Allowed Uses
1. Multi-family, detached dwelling units.
2. Multi-family, attached dwelling units.
3. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowable in
the MF-1 District.
4. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the MF-1 District.
5. Those accessory uses that may be compatible with the primary uses allowed in the MF-1
District per Section 5.01.020.E of this Code.
C. Residential Design Standards
The design standards below apply to all residential development in the MF-1 District in addition
to the provisions of Sections 6.05 04 and 6.06 05 of this Chapter.
1. All development within the MF-1 District shall also comply with the Building Design
standards of Section 7.04 and the Lighting Design standards of Section 7.05 of this Code.
2. A minimum building separation of 15 feet is required between all buildings on the site.
3. Landscape bufferyards are required between the MF-1 District and adjacent AG, RE, RL and
RS Districts. See Section 8.04.060 for Bufferyard requirements.
4. Common Amenity Areas are required for development in the MF-1 District in accordance
with Section 6.06.020.
Page 61 of 131
Page 17 of 32
D. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet all of the lot and dimensional standards of the MF-1
District, in addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
E. Other Requirements of this Code
1. Dimensional Interpretations and Exceptions, Section 6.0504
2. Accessory Structures, Garages and Recreation AreasCarports, Section 6.0605
3. Common Recreation Amenity Area, Section 6.06.020
4. Chapter 8, Tree Preservation, Landscaping, and Fencing
5. Chapter 9, Off-Street Parking and Loading
6.0302.090 MF-2 - High Density Multi-family District
The High Density Multi-family District (MF-2) is intended for attached multifamily residential
development, such as apartments and condominiums, at a density not to exceed 24 dwelling units per
acre. The MF-2 District is appropriate in areas designated on the Future Land Use Plan as high density
residential or mixed-use. Properties zoned MF-2 should have direct access to major thoroughfares and
arterial streets and should not route traffic through lower density residential areas. The MF District is
appropriate adjacent to both Residential and Non- Residential Districts and may serve as a transition
between single-family districts and more intense commercial districts.
A. Lot and Dimensional Standards
MF-2 - High Density Multi-family
Lot Size, minimum 2 acres
Dwelling Units per acre, maximum 24
Apartment Units per structure, maximum 24
Lot Width, minimum feet 50
Front Setback, minimum feet 25
Side Setback, minimum feet 15
Side Setback to Residential District, minimum feet 30
Rear Setback, minimum feet 15
Rear Setback to Residential District, minimum feet 30
Side/Rear Street Setback, minimum feet 20
Unloaded Street Setback 20
Building Height, maximum feet 45
Impervious Cover, maximum % See Section 11.02
Page 62 of 131
Page 18 of 32
B. Allowed Uses
1. Multi-family, attached dwelling units.
2. Those residential uses identified in the Use Tables in Chapter 5 of this Code as allowable in
the MF-2 District.
3. Those non-residential uses identified in the Use Tables in Chapter 5 of this Code as allowed
in the MF-2 District.
4. Those accessory uses that may be compatible with the primary uses allowed in the MF-2
District per Section 5.01.020.E of this Code.
C. Residential Design Standards
1. The design standards below apply to all residential development in the MF-2 District in
addition to the provisions of Sections 6.05 04 and 6.06 05 of this Chapter.
2. A minimum building separation of 15 feet is required between all buildings on the site.
3. Landscape bufferyards are required between the MF-2 District and adjacent AG, RE, RL and
RS Districts. See Section 8.04.060 for bufferyard requirements.
4. Common Amenity Areas are required for development in the MF-2 District in accordance
with Section 6.06.020.
D. Non-Residential and Accessory Design Standards
1. Non-residential structures shall meet all of the lot and dimensional standards of the MF-2
District, in addition to the requirements of Sections 7.04 and 7.05.
2. Residential accessory structures shall meet the requirements of Section 6.0605.010.
3. Residential accessory structures shall not exceed the height of the principal residential
structure.
E. Other Requirements of this Code
1. Dimensional Interpretations and Exceptions, Section 6.0504
2. Accessory Structures, Garages and Amenity AreasCarports, Section 6.0605
3. Common Amenity Area, Section 6.06.020
4. Chapter 8, Tree Preservation, Landscaping, and Fencing
5. Chapter 9, Off-Street Parking and Loading
6.0302.0100 MH-Manufactured Housing District
The Manufactured Housing District (MH) is intended for the development of manufactured, HUD-
Code mobile home parks and subdivisions. Manufactured /mobile home subdivisions include
individually platted lots for the placement of manufactured /mobile homes and also includes
manufactured housing parks, as that term is defined in this Code. The Manufactured Housing District
establishes special area and design requirements for both parks and subdivisions, as well as setback
requirements for individual lots. Both parks and subdivisions provide open space and recreational
areas appropriate for the acreages and number of units contained.
Page 63 of 131
Page 19 of 32
More than one structure housing a permitted principal use may be erected on a single lot or building
plot, but setback and other requirements of this Code must be met for each structure as though each
were on an individual lot.
The Manufactured Housing District includes mobile-home parks and manufactured housing on
individual lots. Specific site design and development standards for MH are described in this Section.
A. Allowed Uses
1. Manufactured Housing, individual lots
2. Manufactured Housing Park
3. Those residential or non-residential uses identified in the Use Tables in Chapter 5 of this
Code as allowed in the MH District.
4. Those accessory uses identified in the Use Tables in Chapter 5 of this Code that may be
compatible with the primary uses allowed in the MH District.
B. Design Standards for Housing Manufactured Off-Site
All single-family or two-family housing manufactured off-site, including manufactured and
modular housing, are subject to the following standards and requirements.
1. The unit shall be the only habitable structure upon the lot on which it is placed.
2. The unit shall have a label or documents certifying that it is constructed in compliance with
the National Manufactured Housing Construction and Safety Standards Act of 1974.
3. The wheels, axles, tongue, towing apparatus, and transporting lights shall be removed prior
to final installation of the unit.
4. The unit shall be placed on a permanent foundation consisting of masonry or concrete and
constructed to the standards of the applicable Building Codes adopted by the City of
Georgetown.
5. Crawl space shall be provided under each unit with access and ventilation as required by the
Building Code adopted by the City of Georgetown.
6. The unit shall be located so that its longer dimension is parallel to the street on which the lot
fronts.
7. Steps to the ground level with handrails and a permanent landing shall be provided at each
outside doorway in compliance with the requirements of the applicable Building Code
adopted by the City of Georgetown.
8. All electrical service equipment shall be mounted on the structure in compliance with the
conditions imposed by Exceptions No. 1 and No. 2 under Section 550-23(a) of the National
Electric Code (NEC), latest edition, as adopted by the City of Georgetown.
9. The exterior finish cannot have a high-gloss finish. The exterior walls shall look like wood or
masonry, regardless of the actual composition.
10. Maximum Height – Two stories
a. All accessory buildings shall be limited to one story in height.
Page 64 of 131
Page 20 of 32
b. The roof shall be pitched with a minimum vertical rise of 2½ feet for every 12 feet of
horizontal run.
c. The roof shall have eaves that project a minimum of 12 inches from the exterior wall.
11. Size of Setback:
a. Minimum Front Setback – 20 feet from a dedicated street; 15 feet from any private street
or drive;
b. Minimum Interior Side Setback – 5.5 feet; 20 feet between units; 20 feet from Zoning
District line;
c. Minimum Exterior Side Setback – 25 feet from a dedicated street; 15 feet from any private
street or drive;
d. Minimum Rear Setback – 7 feet; 20 feet from any Zoning District line;
e. If a garage is provided, the garage shall have a 25-foot front setback.
12. Size of Lot:
a. Minimum Lot Size – 3,500 square feet per unit;
b. Minimum Lot Width - 35 feet;
c. Minimum Lot Depth – 110 feet.
13. Minimum Dwelling Size – 900 square feet.
14. Maximum Impervious Coverage – See Section 11.02 for Impervious Cover limitations.
15. Minimum Parking Requirement – 2 spaces per unit.
16. Minimum Area for Manufactured Housing Subdivision (one unit on one platted lot) – 5,500
square feet.
17. Minimum Area for Manufactured Housing Park – 2 acres.
C. Design Standards for Manufactured Housing Park
1. Tenant Parking: Each parking space shall be concrete in accordance with City standards and
located to eliminate interference with access to parking areas provided for other
manufactured /mobile homes and for public parking in the park.
2. Visitor and Supplemental Parking: In addition to parking spaces required for each
manufactured /mobile home unit there shall be parking provided for the manufactured
/mobile home community in general:
a. One visitor parking for every 3 manufactured home spaces;
b. One supplemental parking or vehicle storage space for the parking or storage of boats,
campers and similar vehicles or equipment for every 6 manufactured / mobile home
spaces;
c. Supplemental spaces may be located anywhere within the manufactured /mobile home
community provided that no manufactured /mobile home space shall be situated further
than 150 feet from a visitor space;
Page 65 of 131
Page 21 of 32
d. No parking space shall be less than 9 feet by 18 feet, which is not to be included in the lot
size.
3. Access: Each manufactured /mobile home community shall have direct access from a public
street or an internal street. Where an internal private street provides access, the same shall
be concrete in accordance with City standards dedicated to the public as an emergency
access or fire lane easement to allow for the rapid and safe movement of vehicles used for
the purpose of providing emergency health or public safety services. Each emergency access
easement shall have a clear unobstructed width of 24 feet, shall connect to a dedicated public
street, and shall have a turning area and radii a minimum of 50 feet to permit free movement
of emergency vehicles. Dead end streets are not allowed. Cul-de-sac streets shall not exceed
500 feet in length. Fire lane easements shall be maintained by the manufactured /mobile
home park.
4. Walkways: Designated concrete walkways a minimum of five feet (5’) in width shall be
provided on both sides of roadways or streets.
5. Street Names and Signs: Within each manufactured /mobile home park, all streets shall be
named, and manufactured /mobile homes numbered in a logical and orderly fashion. Street
signs shall be of a color and size contrasting with those on public streets and roadways so
that there is no confusion regarding which are private and which are public streets. These
signs and numbers shall be of standard size and placement to facilitate location by
emergency vehicles.
6. Other Signs: Along all sections of emergency access easements, the owner or agent shall erect
metal signs prohibiting parking.
7. Intersections: Internal streets shall intersect adjoining public street at approximately 90
degrees and at locations which will eliminate or minimize interference with traffic on those
public streets.
8. Street Lighting: Street lighting within the manufactured/mobile home park shall be provided
and maintained by the owners of the manufactured/mobile home park.
9. Drainage and Soil Protection: The ground surface in all parts of the park shall be graded and
equipped to drain all surface water in a safe, efficient manner. Each manufactured /mobile
home space shall provide adequate drainage for the placement of a manufactured /mobile
home. Exposed ground surfaces in all parts of every manufactured /mobile home park shall
be paved and /or covered with stone, brick paving or other similar solid material or
protected with a vegetative growth (such as grass) capable of preventing soil erosion and
eliminating dust.
10. Anchorage: To insure against natural hazards such as tornadoes, high winds, and electrical
storms, anchorage at each manufactured /mobile home shall be provided at the time of
installation, according to the Building Code.
11. Skirting: Skirting or a curtain wall, unpierced except for required ventilation and access
door, shall be installed and maintained so that it encloses the area under the structure. The
skirting or foundation must be a continuous, complete, opaque, and rigid surface that lends
permanency to the appearance of the unit and totally screens the crawl space under the unit.
The foundation skirting or curtain wall shall be of brick or stucco only. Material used for the
Page 66 of 131
Page 22 of 32
skirting shall be erected so as not to create a fire hazard and maintained in a good state of
repair.
12. Usable Open Space Requirements: Each parcel of land, developed under the MH standards,
shall provide 280 square feet of usable open space per unit.
13. Single-family dwellings constructed in this District shall conform to the standards as set
forth in the RS District.
14. Open storage is prohibited.
Section 6.0403 Mixed Use
The Mixed Use District (MU), established in Section 4.11, is intended for residential and non- residential
development to promote a dense and active mixed use urban environment. As established in the MU
guidelines, a project zoned or proposed to be zoned MU may be completely residential and contain
varying housing types and densities in a well-planned setting. Incentives available for developments in
this district, along with guidelines, development standards and process for using the MU District can be
found in Section 4.11 of this Code, attached as a separate document found at the City of Georgetown
Planning and Development Department office or at http://udc.georgetown.org.
Section 6.0504 Dimensional Interpretations and Exceptions
6.0504.010 Minimum Lot Exceptions
A. Minimum Lot Size
No Building Permit or development approval may be issued for a lot that does not meet the
minimum lot size requirements of this Chapter except as specified in the following cases:
1. Nonconforming lots may be used in accordance with the provisions set forth in Chapter 14.
2. Utilities using land or an unmanned building less than 1,000 square feet of site area shall be
exempt from the minimum lot size requirements.
3. The following types of lots, as defined in Section 16.02, are exempt from the minimum lot
size requirements in all Residential Zoning Districts:
a. Open Space Lots;
b. Landscape Lots;
c. Drainage Lots;
d. Median Lots; and,
e. Access Lots.
B. Minimum Lot Width
1. The minimum lot width for lots fronting a cul-de-sac may be reduced to a minimum of 30
feet at the front property line provided that the minimum required lot width is provided at
the front setback line.
2. The minimum lot width may be reduced to 40 feet with approved rear access for any district.
Page 67 of 131
Page 22 of 32
3. The following types of lots, as defined in Section 16.02, are exempt from the minimum lot
width requirements in all Residential Zoning Districts:
a. Open Space Lots;
b. Landscape Lots;
c. Drainage Lots;
d. Median Lots; and
e. Access Lots.
6.0504.020 Setbacks
The setback provisions in this Section apply to lots in the Agriculture District and all Residential
Districts, unless otherwise specified in this Chapter.
A. General
1. No building, structure, or other development feature shall be located within a required
setback or yard unless otherwise specified in this Section.
2. No part of a setback or other open space required in connection with any building, lot or use
for the purpose of complying with this Code shall be included for any other building, lot, or
use as part of a setback or open space.
3. When determining the setbacks for corner lots, the front line shall be adjacent to the shortest
street dimension of the lot. In instances where the lot is relatively square or otherwise
unusually shaped, a request may be made to the Director for a determination of the front lot
line.
4. When determining the setback for lots with more than one street frontage, other than corner
lots, the Planning Director shall determine the front lot line on the basis of street
classification, lot dimensions, building orientation, access, traffic flow, proximity of building
to the street, and other best planning practices.
B. Setback Reductions and Exceptions
1. Alleys
a. When residential driveway access is taken from an alley, the garage setback to the alley
may be reduced to 10 feet.
b. On lots with where driveway access is only permitted via an alleyapproved rear access,
the minimum front setback may be reduced to 15 feet.
c. 2. On lots with an approved private rear access easement, rear setbacks shall be
measured from the nearest boundary of the easement. For all other lots, rear setbacks
shall be measured from the rear property line.
3. A minimum side setback of 10 feet shall be provided along all side lot lines that parallel a
public street, except as follows:
a. The side setback shall be 25 feet when adjacent to a roadway classified in this Code as a
freeway or the frontage road of a freeway.
Page 68 of 131
Page 24 of 32
b. The side setback shall be 20 feet for a garage or carport taking access from a side street.
(See Section 6.06.010)
42. Where the front, side and rearlot setbacks reduce the buildable width or depth of an existing
corner lot to less than 40 feet, the Director is authorized to reduce the required front setback
on the longer street side as much as necessary to increase theto provide a minimum
buildable width or depth of to 40 feet. In the event that the street sides of the lot are of equal
length, the reduction shall be made on the side which lies on the shorter side of the block.
53. When an existing setback is reduced because of a conveyance to a federal, state or local
government for a public purpose and the remaining setback is at least 50% of the required
minimum setback for the District in which it is located, then that remaining setback will be
deemed to satisfy the minimum setback requirements of this Code.
64. Properties in the Old Town Overlay District may request a Certificate of Appropriateness for
setback exception in accordance with Section 3.13 of this Code.
5. Adjacent lots with a building or other permanent structure built across the shared lot line on
or before March 11, 2003, shall be treated as a single lot, with the shared lot line not
considered for measurement of all dimensional standards.
C. Features Allowed Within Required Setbacks
The following features are allowed tomay be located within a required setback:
1. Landscape features (as defined in Chapter 16).
2. Driveways located:
a. in a front setback, provided that the driveway does not run parallel to a public street;
b. in a side setback, if serving a side-loaded or detached rear garage or other parking area;
or
c. in a rear setback, if accessed by a rear alley or public street.
3. Sidewalks, fences, and walls, meeting the requirements of Section 8.07.
4. Uncovered patios provided that:
a. The patio is located entirely within the side and/or rear yard, except that an uncovered
patio may be located within a front yard if:
i. the surface area of the uncovered patio within the front yard does not exceed 10%
of the total calculated area within the front setback;
ii. the uncovered patio is set back at least 15 feet from all street property lines;
iii. no built-in structures, such as grills or fire pits, are included in any portion of the
uncovered patio within the front yard; and
iv. the patio is screened from street view by a knee-wall or short seating bench not
exceeding 30 inches in height and made of materials consistent with the
architecture/materials of the home, a natural berm, a solid shrub wall, or a
combination thereof; and
Page 69 of 131
Page 25 of 32
b. The patio is set back at least 3 feet from side and rear property lines, except as otherwise
provided for in this Section.
5. Pools located entirely within the side and/or rear yard and set back at least 3 feet from side
and rear property lines.
6. Uncovered outdoor kitchens located entirely within the side and/or rear yard and setback at
least 3 feet from side and rear property lines.
7. Pergolas provided that the pergola is:
a. located entirely within the side and/or rear yard, including structural supports and
overhangs;
b. set back at least 3 feet from side and rear property lines;
c. maintained with at least 50% open roof elements;
d. not enclosed with ground to roof walls other than that of the primary structure, except
that a shading system with at least 50% transparency is permitted on up to two sides;
and
e. no more than 8 feet in height.
8. Minor utilities.
9. Mechanical equipment such as air conditioning units, pool pumps, and similar equipment,
but such equipment is not allowed in the front setback and is allowed in the side and rear
setbacks only if such equipment cannot be reasonably located behind the structure.
10. Sills, belt courses, cornices, buttresses, chimneys, flues, eaves and other architectural features
provided that such features do not extend further than 18 inches into any required setback.
11. Stormwater ponds, pursuant to the design criteria and limitations in Section 11.04 of this
Code.
11. Parking areas that cover up to 50% of the required front setback provided that:
a. Landscape buffers eight feet wide are provided between the property line and the
nearest side of the parking pad, and also between the structure and the nearest side of
the parking pad. These buffers must be landscaped and each shall contain a 3 foot high
screen consisting of a continuous berm, hedge or wall;
b. The parking is on a paved surface, as that term is defined in this Code; and
c. The impervious coverage requirements in Section 11.02 are met.
12112. None of the features above (except plant material and public sidewalks) shall
extend into a public easement without approval of a License to Encroach.
6.0504.030 Building Height
A. Measurement
Building height refers to the vertical distance between lowest finished grade at the edge of the
building or the base flood elevation where applicable, and:
Page 70 of 131
Page 25 of 32
1. The average height level between the eaves and ridge line of a gable, shed, hip, or gambrel
roof;
2. The highest point of a mansard roof;
3. The highest point of the coping of a flat roof; and
4. Roof parapets, as described in Section 7.04.040.D, may exceed the height limitations of this
Code by no more than 10 feet.
B. Exceptions to Height Limits
Except within the Courthouse View Protection Overlay District or as otherwise expressly stated
in this Code, the height limitations of this Code shall not apply to any of the following:
1. Electrical power transmission and distribution lines;
2. Belfries, cupolas, spires, domes, monuments, chimneys, radio/television receiving antennas,
or chimney flues; or
3. Bulkhead, elevator, water tank or any other similar structure or necessary mechanical
appurtenance extending above the roof of any building where such structure does not
occupy more than 33% of the area of the roof.
Section 6.0605 Accessory Structures, Garages and Amenity
AreasCarports
6.0605.010 Accessory Structures, Garages and Carports
The requirements of this Section apply to the AG, Agriculture District and all Residential Districts,
except as specified.
A. Accessory structures and buildings shall meet the dimensional standards of the base zoning
district, except as specified in this Section. However, properties in the Old Town Overlay District
may request a Certificate of Appropriateness for setback exception in accordance with Section
3.13 of this Code.
B. The accessory structure shall only be located on a lot with a principal structure, unless two
adjacent lots have common ownership, in which case the structures may be located on different
lots. In such instance, the accessory structure shall be located in the rear yard as determined by
the lot with the principal structure on it.
C. The square footage of an accessory structure shall not exceed 25% of the square footage of the
principal structure. However, the maximum accessory structure square footage may exceed 25%
of the principal structure to allow for the construction of a detached two-car garage, not to exceed
600 square feet. For the purposes of this calculation, the square footage of an attached garage
shall not be considered part of the principal structure.
D. Accessory structures measuring 8 feet or less in height are allowed in the setbacks in the rear
yard up to 3 feet from the property line, but may not extend into any P.U.E.
E. Garages and carports, whether attached or detached from the principal structure, shall be set
back a minimum of 20 feet from the public street from which the associated driveway takes
access or a minimum of 10 feet when taking access from a public alley.
Page 71 of 131
Page 25 of 32
FE. No more than 30% of the rear yard may be covered with accessory buildings or structures.
However, the maximum coverage may be extended to 50% of the rear yard to allow for the
construction of a detached two-car garage, not to exceed 600 square feet. All impervious cover
requirements in Section 11.02 shall be met.
GF. Accessory dwelling units located in accessory structures in the AG, RE, RL, and RS Districts are
allowed subject to the limitations provided for in Section 5.02.020.B or within a Housing
Diversity Development without limitations (as detailed in Section 6.07.020).
Section 6.06 Common Amenity Area
6.06.020 010 Common Amenity Area
A. Applicability
The provisions of this Section apply to:
1A. Townhouses;
2B. Attached or detached multifamily development;
3C. Manufactured housing parks; and
4D. Any development type where more than two (2) dwelling units are located on the same parcel.
6.06.020 B. Common Recreation Amenity Area Requirements
1A. Common amenity area shall be provided by the developer. This amenity area is in addition to
any required parkland dedication or private open space requirement.
2B. The amenity area shall be privately constructed, maintained, and operated by the developer,
residents of the subdivision through an incorporated homeowners association or property
owners association, or the owner of the manufactured home lease community, and the person or
entity responsible for ownership and maintenance. Operational responsibilities shall be noted on
the plat and/or on a separate instrument recorded in the Official Records of Williamson County.
3C. Common amenity area(s), accessible to all residents, shall be provided at the following rate:
Number of Dwelling Units Minimum Number of Amenities
0-12 0
13-49 1
50-99 2
100-149 3
150-199 4
200 or more 5
4D. The required amenity area(s) shall be selected from those listed below. Director approval shall be
required for any amenity types not listed. When more than one amenity is required, they shall
differ from one another.
a1. Playground equipment - manufacturer must certify that it meets all commercial recreational
safety standards
Page 72 of 131
Page 28 of 32
b2. Picnic areas – minimum of two (2) tables and two (2) cooking grills per 100 dwelling units
c3. Trails (walkways or bike trails) - at least the distance of the perimeter of the property
d4. Landscaped sitting areas – minimum of one (1) bench per building either in an organized
grouping or dispersed throughout development
e5. Fenced dog park - minimum size of 2,500 square feet with 25-foot minimum depth
f6. Private fitness facility
g7. Business center
h8. Sport courts
i9. Clubhouse – to include kitchen and social room for resident use
j10. Swimming Pool
k11. Laundry facility
l12. After school center for children
m13. Community garden – minimum 200 square feet
5E. The common amenity area shall be designed to adequately serve the number of dwellings within
the development, according to accepted City standards set by the Parks and Recreation
Department. All equipment and other improvements must be of commercial quality and
approved by the Director of Parks and Recreation.
Section 6.07 Special Development Types
6.07.010 Conservation Subdivision Development
To encourage Conservation Subdivision development, this Code allows flexibility to development
standards in all Zoning Districts for residential developments that use conservation development
practices in order to: protect natural resources, conserve valuable open space, reduce erosion and
sedimentation, preserve riparian corridors, provide for walking trails, protect the community water
supplies, reduce infrastructure, preserve prime agricultural land, provide smaller streets with less
environmental disturbance, and plan for overall watershed protection. Attempting to achieve these
objectives using the process established in Section 11.06 of this Code qualifies a development as a
conservation subdivision eligible for the incentives and alternative development standards.
Conservation Subdivision lot and dimensional standards can be found in Section 11.06.
6.07.020 Housing Diversity Development
A. Purpose
To encourage housing diversity, this Code allows flexibility to the development standards and
allowable housing types for projects that foster housing diversity.
B. Housing Types
The following Table shows the types of housing permitted in a Housing Diversity Development.
At least three of the following housing types in any of the following Districts shall be included to
qualify for the alternative dimensional standards in Table 6.07.020.B.
Page 73 of 131
Page 29 of 32
Table 6.07.020.B: Permitted Housing Types by Residential District
Housing Type Minimum Lot Size RL RS TF TH MF-1 MF-2
Single Family, Detached 7,500 SF lot X X X X X X
Single Family, Detached 4,500 SF lot X X X X X X
Single Family, Attached 3,500 SF lot X X X X X X
Two-family 6,000 SF lot X X X X X X
Townhouse 7,000 SF lot X X X X X X
Apartment 12,000 SF lot -- -- -- -- X --
Apartment 2 acre lot -- -- -- -- -- X
C. Dimensional Standards
The following Table provides the dimensional standards for each residential building type that
can be used in lieu of the dimensional standards otherwise applicable.
Table 6.07.020.C: Housing Diversity Dimensional Standards ¹
Standard Single Family,
Detached
Single
Family,
Attached
Two- family Townhouse
Lot Size, minimum 7,500 4,500 7,000 6,000 1,750
Dwelling Size, minimum - - 3,500 3,000 --
Dwellings per structure, max. - - 3 2 7
Lot Width, minimum feet 60 35 ² 35 ² 60 20
Corner Lot Width, minimum feet 65 40 40 65 25
Front Setback, minimum feet 15 15 15 15 5 ³
Side Setback, minimum feet 10 6 6 6 10
Rear Setback, minimum feet 10 10 10 10 15
Side/Rear Street Setback,
minimum feet 15 15 15 15 15
Garage Setback 20 20 20 20 20
Unloaded Street Setback 20 20 20 20 20
Building Height, max. feet 35 40 40 40 45
Impervious Coverage, max % See Section 11.02 “Impervious Cover”
Perimeter Buffer, min.
feetLandscaping and
Bufferyards
See Chapter 8 “Tree Preservation, Landscaping and
Fencing”
1. All Standards in Table 6.07.020.C shall meet any specific requirements of the allowed housing
type, as detailed elsewhere in this Chapter. When a conflict occurs between such requirements
and the standards of this Table, the Table shall apply.
2. Lots less than 40 feet in width must be alley loaded lots, with the exception of townhouse lots.
Page 74 of 131
Page 30 of 32
3. See Section 6.0302.070.C.1.a for clarification.
D. Interpretations and Exceptions
All dimensional standards in Paragraph (C), above, are subject to the interpretations and
exceptions in Section 6.0504.
E. Perimeter Buffer
The perimeter buffer applies to the subdivision edge or contiguous area of a Housing Diversity
Development, and not to specific Zoning Districts within the Development. The perimeter buffer
may be counted towards required landscaping if it is within the lot.
F. Alternative Sidewalk Design
Refer to Section 12.02.040 Alternative Design and Financing for sidewalk options in Housing Diversity
Developments.
6.07.030 Workforce Housing Development
A. Purpose
To encourage affordable housing for the workforce, this Code allows flexibility to the
development standards and allowable housing types for projects that foster housing
affordability.
B. Dimensional Standards
The following Table provides the dimensional standards for each residential district that can be
used in lieu of the dimensional standards otherwise applicable.
Table 6.07.030 Workforce Housing Dimensional Standards
Standard RS TF TH MF-1 MF-2
Lot Size, Minimum 4,500 6,000 1,750 12,000 2 acres
Dwelling Units per acre, max -- -- -- 14 24
Dwelling Size, Minimum -- 3,000 1750 --
Dwellings per structure, Max -- 2 8 20 50
Lot Width, minimum feet 35 2 60 20 50 50
Corner Lot Width, minimum feet 40 65 25 - -
Front Setback, minimum feet 10 10 10 15 15
Side Setback, minimum feet 5.5 5.5 7.5 10 10
Side Setback to Residential District,
minimum feet -- -- -- 20 30
Rear Setback, minimum feet 7.5 7.5 10 10 15
Rear Setback to Residential District,
minimum feet -- -- -- 20 30
Side/Rear Street Setback, minimum feet 10 10 10 15 15
Garage Setback 20 20 20 -- --
Unloaded Street Setback 15 15 15 20 20
Building Height, max feet 40 40 45 35 45
Impervious Coverage, max % See Section 11.02 "Impervious Cover"
Page 75 of 131
Page 31 of 32
1. All Standards in Table 6.07.030 shall meet any specific requirements of the allowed housing type, as
detailed elsewhere in this Chapter. When a conflict occurs between such requirements and the
standards of this Table, the Table shall apply.
2. Lots less than 40 feet in width must be alley loaded lots, with the exception of townhouse lots.
C. Interpretations and Exceptions
All dimensional standards in Paragraph (C)Table 6.07.030, above, are subject to the
interpretations and exceptions in Section 6.0504.
D. Alternative Sidewalk Design
Refer to Section 12.02040 Alternative Design and Financing for sidewalk options in Workforce
Housing Developments.
E. Workforce Housing
1. Workforce Housing Developments in Single-Family Residential, Two-Family and
Townhouse Districts that include 20% of the housing units available for those whose
incomes are less than or equal to 80% of the area median family income (as set by the
Department of Housing and Urban Development) are eligible to use the standards in Table
6.070.030 for all lots within the subdivision. The deed restrictions, approved by the City
Attorney, must include language that requires all workforce housing lots be restricted for ten
years from the date of the original home sale to the qualifying buyer any resale shall be to a
party whose income is less than or equal to 80% of the area median family income or, absent
that, shall require a payment to the City of their proportionate and prorated share of fees
that were waived for their lot.
2. Workforce Housing Developments in Low-Density Multifamily (MF-1) and High-Density
Multifamily (MF-2) Districts are eligible to use the dimensional standards in Table 6.07.030
with the provision of the following workforce housing units.
a. Dwelling units per structure maximum can be reached by providing 5% of the total
development as workforce units.
b. Front Setback can be reduced by 5 feet for every 10% of total development set as
workforce units, to the minimum.
c. Impervious cover can be increase by 10% for every 10% of the total development set as
workforce units, to the maximum of 70%, with required water quality improvements as
required in Section 11.02.
F. Fee Waivers
Workforce Housing Developments are eligible for administrative fee waivers, as adopted and
published by the City of Georgetown.
6.07.040 Multi-Lot Unified Development
A. Multi-Lot Unified developments may be located in any residential zoning district, save and
except Residential Estate (RE), Residential Low Density (RL), Residential Single-Family (RS), and
Two-Family (TF) zoning districts.
Page 76 of 131
Page 32 of 32
B. Abutting properties with similar residential zoning districts and that are part of a Multi-Lot
Unified Development pursuant to Section 4.05.030 of this Code may be developed in accordance
with the development standards in Section 7.0302.030.D of this Code.
Page 77 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 7, No n-residential Development Standards. Valerie
Kreger
ITEM SUMMARY:
Since the last d is c us s io n o n Chap ter 7, staff has ad d ed provis io ns fo r a Subdivis io n Variance fo r minimum
lo t width and frontage.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 7 Cover Memo
Page 78 of 131
Page 1 of 7
Chapter 7 Non-Residential Zoning Districts: Lot, Dimensional,
and DesignDevelopment Standards
Section 7.01 General
7.01.010 Authority
The provisions of this Chapter are adopted pursuant to the Texas Local Government Code
Chapters 211 and 212 and the City Charter.
7.01.020 Purpose and Intent
The Non-Residential Lot, Dimensional, and Design StandardsThis Chapter establishes lot sizes and
development standards for non-residential properties within the city limits and ETJ of the City of
Georgetown and minimum requirements for development within the City’s Extraterritorial
Jurisdiction (ETJ). The provisions of this Chapter apply, unless otherwise specified, to development
in the zoning districts classified as Non- Residential, Special Purpose (excluding AG, Agriculture),
and Mixed-Use (see Table 4.01.010 for the list of Zoning Districts) and development in any other
zoning districts as required elsewhere in this Code. For the purposes of this Chapter, all of the
above Districts shall be referred to as Non-Residential.
The provisions of this Chapter allow for a variety of development while maintaining the overall
character of neighborhoods and commercial areas of Georgetown. The standards are established to
regulate the manner in which land is developed, minimize adverse effects on surrounding
properties and the general public, and ensure that high quality development is maintained
throughout the community.
The approach to development standards has several public benefits:
1. It allows for development that is more sensitive to the environment.
2. It allows for the preservation of open and natural areas.
3. It promotes better site layout and opportunities for recreational areas.
4. It promotes energy-efficient development.
7.01.030 Applicability
A. Within the Extraterritorial Jurisdiction (ETJ)
All non-residential development within the City’s ETJ is subject to the following sections:
1. provisions of Section 7.02.010.
2. Section 7.02.020, if fire services are provided by the City of Georgetown.
B. Within the City Limits
1. All non-residential development within the City Limits isa Non-Residential Zoning
District shall be subject to all the provisions of this Chapter.
2. All non-residential development within a Residential Zoning District shall be subject to
the Building Design Standards set forth in Section 7.04 and the Lighting Standards set
forth in Section 7.05 in addition to the development standards of the zoning district in
which it is located.
Page 79 of 131
Page 1 of 7
3. All residential development within a Non-residential Zoning District shall be subject to
shall be subject to the provisions of Sections 6.05 and 6.06 in addition to the development
standards of the zoning district in which it is located.
Section 7.02 Uniform Development Standards
7.02.010 General Lot Requirements
No building permits or other development approvals shall be issued for development that does not
meet the following minimum requirements:
A. All new development shall be located on a legal lot or tract meeting the requirements of
Section 3.08 of this code.
B. All development new lots or tracts within the city limits(with the exception of open space or
drainage lots) shall have a minimum lot width or streetdirect access and frontage on one of
the following:
1. Aalong a public street in accordance with the zoning district in which it is located. All new
lots or tracts in the ETJ shall have a minimum lot width or street frontage along a public
street; or
2. A public street via a public alley.
C. All lots created after October 27, 2009, shall meet the provisions of Paragraph (B), above, at a
minimum width of 25 feet. Private streets may be utilized to meet the minimum requirements
when partproviding frontage of to a non-residential Multi-lot Unified Development meeting
the requirements of Section 7.02.030.E. A Subdivision Variance varying or waiving these
requirements may be requested pursuant to Section 3.22 of this Code.
DC. All structures must be situated on a lot so as to provide safe and convenient access for
servicing, fire protection, on-site parking, landscaping, utility easements, and right-of-way.
E. Intersection visibility shall comply with the provisions set forth in Section 12.03.050.
F. Side lot lines shall intersect rights-of-way at an angle between 60 and 90 degrees on a straight
street or from the tangent of a curved street.
G. All lots must be numbered consecutively within each block, phase or section.
H. No building or structure shall be constructed across lot lines.
7.02.020 Fire Code Compliance
D. All development within the city limits and areas of the ETJ where the City provides fire
protection services shall comply with the applicable standards contained in the International
Fire Code, as adopted in the City of Georgetown Code of Ordinances, Chapter 8.04. When
such standards conflict with any lot, dimensional, and design standards of this Code, the
International Fire Code standards shall apply.
7.02.030 Lot Standards
A. Principle Structures Per Lot
More than one principal structure may be erected on a single lot or parcel, provided each
structure and its development site meet all building and site requirements of this Code.
Page 80 of 131
Page 3 of 7
B. Existing Structures on a Lot
The subdivision or re-subdivision of a tract or lot shall not cause an existing permanent
structure to violate the standards of this Code.
C. Structures Crossing Lot Lines
Lots with an existing building or other permanent structure built across a shared lot line shall
be treated as a single lot, with the shared lot line not considered for measurement of all
dimensional standards. All required dimensional standards, including required setbacks and
lot coverage standards shall be applied as if the two individual lots were a single lot. No
portion of the two lots may be replatted if such replatting would cause the combined lots to
become noncompliant with any provisions of this Code or the City Code of Ordinances or any
other City requirement. The provisions of this Section apply only to buildings or permanent
structures that were in existence on or before March 11, 2003, and no new building or
structure shall be constructed across lot lines.
7.02.040 Block Width
Blocks shall have sufficient width to provide for two tiers of lots except where a single tier may:
1. Separate lots from an incompatible use;
2. Accommodate a requirement for single loaded streets;
3. Allow for unusual topographical conditions; or
4. When located adjacent to the outer perimeter of a subdivision.
Section 7.03 Development Standards
7.03.010 General
A. In addition to the lot, dimensional, and design standards in this Chapter, all Non- Residential
development in a Non-Residential, Special Purpose and Mixed-Use Zoning District shall
comply with any applicable requirements contained in other Chapters of this Code.
B. All residential development in a Non-Residential Zoning District shall comply with the lot,
dimensional, and design standards of this Chapter. Additionally, townhouse development
shall be required to meet the standards of Sections 6.03.070.C and 6.02.020. See Section
5.02.020.E related to Special Use Permits for multi-family uses in a C-1, C-3, BP, or MUDT
district.
C. In the case of any conflict between the lot, dimensional or design standards in this Chapter
and in any other provision of this Code, the City Code of Ordinances or any national or
international code as adopted by the City of Georgetown (e.g., Fire Code, Building Code), the
more restrictive or stringent provision shall apply.
7.0302.020 Non-Residential Lot and Dimensional Standards
The lot and dimensional standards provided in Table 7.0302.020 are in addition to the
interpretations and exceptions in Section 7.0302.030. Table 7.0302.020 contains cross-references and
notes to specific sections or chapters of this Code when additional requirements or explanations
may apply.
Page 81 of 131
Page 4 of 7
Table 7.0302.020: Non-Residential Lot and Dimensional Standards
Non-Residential Zoning Districts
Dimension CN C-1 C-3 OF BP IN PF MU-DT MU
District Size, min. acreage -- -- 5 -- 20 -- -- -- 5
Lot Width, minimum feet 50 50 50 50 50 50 50 25
Fo
r
M
U
L
o
t
a
n
d
D
i
m
e
n
s
i
o
n
a
l
S
t
a
n
d
a
r
d
s
,
S
e
e
S
e
c
t
i
o
n
4
.1
1
Front/Street Setback, min.
feet 20 25 25 25 25 25 25 0
Front Setback, Build-to
Option
0 0 -- 0 -- -- 0 --
Refer to Section 7.0302.030.B for the Build-to Option
Front Setback, Downtown
Gateway Overlay
0 0 0 0 0 0 0 --
Refer to Section 4.13.040 for Downtown Gateway Setbacks
Side Setback, min. feet 5 10 10 10 10 10 5 0
Side Setback to Residential
District, min. feet 10 15 15 15 20 25 15 0
Rear Setback, min. feet 0 0 10 10 10 10 0 0
Rear Setback to Residential
District, min. feet 20 25 25 25 25 35 25 0
Building Height, max. feet 30 35 45 45 60 60 45 40
Bufferyards Refer to Section 8.04 for Bufferyard Requirements
Landscaping Refer to Chapter 8 for Minimum Landscape Requirements
Impervious Coverage Refer to Section 11.02 for Impervious Coverage
Requirements
A. For properties located in an Overlay Zoning District, additional or alternative provisions may
apply. See Chapter 4 for all applicable Overlay Districts.
B. For Non-Residential development in a Conservation Subdivision, see Section 11.06 for
alternative development standards.
C. Additional design limitations may be required for specific uses in Chapter 5 of this Code.
When in conflict, the stricter provision shall apply.
7.0302.030 Dimensional Interpretations and Exceptions
A. Minimum Lot Size and Width Exceptions
No building permit or development approval shall be issued for a lot that does not meet the
minimum lot size or width requirements of this Code except in the following cases:
1. Nonconforming lots shall be used in accordance with the provisions set forth in Chapter
14.
2. Utilities using land or an unmanned building covering less than 1,000 square feet of site
area shall be exempt from minimum lot size standards.
Page 82 of 131
Page 5 of 7
3. The following types of lots, as defined in Section 16.02, are exempt from the minimum lot
size and width standards of this Chapter:
a. Open Space Lots;
b. Landscape Lots;
c. Drainage Lots;
d. Median Lots; and
e. Access Lots.
B. Setbacks General
1. No building, structure, or other development feature shall be located within a required
setback or yard unless otherwise specified in this Section.
2. When determining the setbacks for corner lots, the front lot line shall be adjacent to the
shortest street dimension of the lot. In instances where the lot is relatively square or
otherwise unusually shaped, a request may be made to the Director for a determination
of the front lot line.
3. When determining the setback for lots with more than one street frontage, other than
corner lots, the Planning Director shall determine the front lot line on the basis of street
classification, lot dimensions, building orientation, access, traffic flow, proximity of
building to the street, and other best planning practices.
4. Any setback to a public street shall be considered a street setback and meet the required
front setback for lot lines adjacent to the street. The Planning Director may reduce the
street setback to be consistent with the side setback of the district on a case by case basis
based on lot configuration, building orientation, access, proximity of buildings to the
street on lots on the same block and on either side of the street, and existing character of
the district.
C. Setback Reductions and Exceptions
1. Front Setback, Build-to Option
a. For properties in the CN, C-1, OF and PF Districts, the front setback may be reduced
to zero feet from the right-of-way line or any applicable public easement, if at least
25% of the street-facing building wall of the principal structure is built within 5 feet of
the right-of-way line or applicable public or landscape easement on the primary
street.
b. Notwithstanding the foregoing provision in subsection (a), parking shall be set back
10 feet from the right-of-way line and shall not be located in a public or landscape
easement.
2. Front Setback, Downtown Gateway Overlay District
All non-residential uses located in the Downtown Gateway Overlay District, regardless
of the underlying Zoning District, have special setback requirements. For these
properties, the front setback of the underlying Zoning District is reduced to zero feet
from the right-of-way line or any applicable public or landscape easement. Additional
Page 83 of 131
Page 6 of 7
requirements for properties in the Downtown Gateway Overlay District can be found in
Section 4.13.040.
3. Side Setback, MU-DT District
Development in the MU-DT District may have no side setback if access to the rear of the
building is provided on the site or by a dedicated public alley.
4. Features Allowed Within Required Setbacks
a. The following features may be located within a required setback:
i. Landscape features (as defined in Chapter 16).
ii. Fences and walls.
iii. Driveways.
iv. Sidewalks.
v. Minor utilities.
vi. Mechanical equipment such as air conditioning units, pool pumps and similar
equipment, but such equipment is not allowed in the front setback and is
allowed in the side and rear setbacks only if such equipment cannot be
reasonably located behind the structure.
vii. Sills, belt courses, cornices, buttresses, chimneys, flues, eaves and other
architectural features that extend less than 18 inches into the setback.
viii. On-site parking may be located within a side or rear setback if:
• Such parking is located no closer than five feet from the lot line; and
• The lot complies with the applicable bufferyard requirements in Section 8.04
of this Code.
ix. Stormwater ponds, pursuant to the design criteria and limitations in Section
11.04 of this Code.
b. None of the features above (except plant material and public sidewalks) shall extend
into a public easement without approval of a License to Encroach.
5. Adjacent lots with a building or other permanent structure built across the shared lot line
on or before March 11, 2003, shall be treated as a single lot, with the shared lot line not
considered for measurement of all dimensional standards.
D. Building Height
1. Measurement
Building height refers to the vertical distance between the lowest finished grade at the
edge of the building or the base flood elevation, where applicable, and:
a. The average height level between the eaves and ridge line of a gable, shed, hip, or
gambrel roof;
b. The highest point of a mansard roof; or
Page 84 of 131
Page 7 of 7
c. The highest point of the coping of a flat roof.
2. Exceptions to Height Limits
Except within the Courthouse View Protection Overlay District or as otherwise expressly
stated in this Code, building height limitations shall not apply to any of the following:
a. Electrical power transmission and distribution lines;
b. Belfries, cupolas, spires, domes, monuments, chimneys, radio/television receiving
antennas, or chimney flues;
c. Bulkhead, elevator, water tank or any other similar structure extending above the
roof of any building where such structure does not occupy more than 33% of the area
of the roof; and
d. Roof parapets, as described in Section 7.04.040.D, may exceed the height limitations of
this Code by no more than ten feet.
E. Multi-Lot Unified Development
1. Abutting properties with similar zoning districts and that are part of a Multi-Lot Unified
Development pursuant to Section 4.05.030 of this Code may be developed in accordance
with the following standards:
a. Landscape and hardscape improvements may be located within the required setback
of an interior lot line and cross interior lot lines of a Multi-Lot Unified Development.
b. Buildings and structures may be located within the required setback along an interior
lot line of a Multi-Lot Unified Development. However, in no case shall a building or
structure be constructed across an interior lot line in accordance with Section 7.02.010
of this Code.
c. The exceptions allowing development within a required setback or across lot lines
shall only apply to the interior lot lines of a Multi-Lot Unified Development, and shall
only be permitted when no bufferyard is required per Table 8.04.060 of this Code. All
setback and bufferyard requirements shall apply along the outer perimeter lot lines of
the Multi-Lot Unified Development.
2. This subsection does not waive specific setbacks required per any applicable Planned
Unit Development District (PUD) or overlay zoning districts as identified in Chapter 4 of
this Code, or specific setbacks and/or spacing requirements for specific uses as identified
in Chapter 5 of this Code.
Page 85 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 9, Off-S treet Parking. Jordan Maddox
ITEM SUMMARY:
Since the last d is c us s io n o n Chap ter 9, staff mad e c hanges to the apartment gate s tacking to measure from
Key Co d e Bo x ins tead of gate and add turnaro und s pac e as well.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 9 Cover Memo
Page 86 of 131
Chapter 9 Off-Street Parking and Loading
Section 9.02 Parking Requirements
9.02.020 Parking Exceeding Minimum Requirements
All off-street parking spaces shall be constructed of a Paved Surface, as defined in this Code,
whether meeting or exceeding the minimum requirements. Pursuant to Section 8.04.040.B.2,
each parking stall in excess of the required shall be calculated as 1.5 stalls for purposes of the
required shade trees.
9.02.050 Alternative Parking Plans (moved to new Section 9.06)
Section 9.03 Parking Space and Parking Lot Design
9.03.010 Location, Setbacks and Buffering of Required Parking
Except as expressly stated in this Section or in an approved Alternative Parking Plan, all
required off-street parking spaces must be located on the same lot as the principal use. In ,
except for Housing Diversity Developments, where two spaces or more are required per unit,;
one space shall be located on the same lot, and the remaining spaces within 200 feet of the lot.
9.03.020 Parking Space and Parking Lot Design
A. Parking Space Dimensions
1. Required off-street pParking spaces shall have minimum dimensions of 9 feet in
width by 18 feet in length, unless otherwise indicated within this Section. When
located adjacent to a public sidewalk, off-street or on-street head-in or angled
parking shall require curb stops so as not to impede the pedestrian
walkway.Parking space length may be reduced to 16 feet provided there is a 2-foot
overhang from the curb or back of the wheel stop in accordance with Figure
9.03.020.A below:
Figure 9.03.020.A
Page 87 of 131
(Graphic Deleted)
2. Subject to approval by the Director, parking areas with 20 or more parking spaces,
may allocate up to 10 % of the minimum number of required parking spaces to
reduced size vehicles, including compact cars and motorcycles, if designed to the
following standards:
a. A compact car space shall not be less than 8 feet in width and 16 feet in length;
b. A motorcycle space shall not be less than 4.5 feet in width and 8 feet in length;
c. Reduced size spaces shall be laid out in a group and appropriately identified as
intended for exclusive use by the specified vehicle;
d. Other parking space designs may be considered and shall be submitted to the
Director for review.
3. Parallel parking spaces shall not be less than 8.5 feet in width and 22 feet in length.
4. Tandem parking spaces may be utilized only for multi-family, not to exceed 15% of
the required total off-street parking spaces and only within an enclosed garage
structure. Tandem spaces shall not count towards the required off-street parking
spaces for single- and two-family dwellings. In the Downtown Overlay, tandem
spaces for any use may considered with an Alternative Parking Plan, per Section
9.02.060.
Page 88 of 131
5. Parking spaces designated as Handicapped shall comply with the design and
location requirements of the American National Standards Institute (A117.1) and
the Texas Department of Licensing and Regulation.
6. Parking spaces internal to the
site may be reduced to 16 feet in
length with a two-foot overhang
onto grass or other flat surface.
This reduction shall not apply to
a bufferyard, screening area or
sidewalk.
B. Aisle Widths
The minimum two-way drive aisle width shall be 24 feet. One-way and two-way drive
aisle widths adjoining off-street parking spaces must comply with the following
standards:
Table 9.03.020B Minimum Aisle Width for Specified Parking
Parking Angle Stall Width (ft)
Aisle Width
One Way Two Way
30° or 45° 9 13 26
30° or 45° 10 12 24
60° 9 16 --
60° 10 15 --
75° 9 23 --
75° 10 22 --
90° 9 -- 26
90° 10 -- 24
C. Markings
1. Each required off-street parking space and off-street parking area shall be identified
by surface markings at least 4 inches in width. Markings shall be visible at all times.
Such markings shall be arranged to provide for orderly and safe loading,
unloading, parking, and storage of vehicles.
2. One-way and two-way accesses into required parking facilities shall be identified
by directional arrows on the pavement.
D. Surfacing and Maintenance
1. All required parking, driveways, drive aisles, and entrances driveway approaches
shall be constructed and maintained withhave a Paved Surface, as defined in this
Code., as approved by the Development Engineer. . Exceptions to the Paved Surface
Page 89 of 131
material requirements may be considered administratively by the Urban Forester and
Development Engineer in order to protect critical root zone for Heritage Trees.
2. All designated fire lanes shall be paved according to the typical street cross sections
for local street design in the City of Georgetown Construction Specifications and
Details, and kept in a dust-free condition at all times.
3. In a Residential Estate subdivision or rural lot, residential driveways may be
constructed of a non-Paved Surface material if outside of the right-of-way and not in
an area designated for required off-street parking.
E. Access
Required off-street parking spaces shall not have direct access to a public street, with or
highway. Access to required parking spaces shall be providedaccess provided by on-site
driveways. Off-street parking spaces shall be accessible without backing into or
otherwise reentering a public right-of-way. In unique circumstances on local streets, the
Director may consider, through an Alternative Parking Plan, parking spaces with direct
access from the street if there is determined to be little or no negative impact on
surrounding properties or the function of the public street.
Parking
All required parking shall be constructed of a Paved Surface. No parking shall be
allowed on any surface other than a paved surface.
Section 9.04 Vehicle Stacking Areas
9.04.010 Minimum Number of Spaces
Off-street stacking spaces shall be provided as indicated in the following Table. Off-street
stacking spaces shall be in addition to any required parking and loading spaces.
Page 90 of 131
Table 9.04.010 Minimum Off-Street Stacking Spaces
Activity Type Minimum
Spaces Measured From
Bank teller lane 4 Teller or Window
Automated teller machine 3 Teller
Restaurant drive through 6 Order Box
Restaurant drive through 4 Order Box to Pick-Up Window
Car lubrication stall 2 Entrance to stall
Car wash stall, automatic 4 Entrance to wash bay
Car wash stall, self-service 3 Entrance to wash bay
Day Care drop off 3 Facility passenger loading area
Gasoline pump island 2 Pump Island
Parking lot, controlled entrance 4 Key Code Box
Apartment gated entrance 4 Key Code Box
School (Public and Private) Determined by Director
Other Determined by Director
9.04.020 Design and Layout
Required stacking spaces are subject to the following design and layout standards.
A. Size
Stacking spaces must be a minimum of 10 feet by 20 feet in size.
B. Location
Stacking spaces may not impede on- or off-site traffic movements or movements into or
out of off-street parking spaces.
C. Design
Stacking spaces must be separated from other internal driveways by raised medians if
deemed necessary by the Director for traffic movement and safety. Turnaround space
shall be provided between the Key Code Box and gate for any gate-restricted entrance to
safely allow a vehicle to exit the entrance queue.
Section 9.05 Off-Street Loading
A. No Use of Public Right-of-Way
At no time shall goods be loaded or unloaded from the right-of-way of a collector or
arterial street. No part of any vehicle shall be allowed to extend into the right-of-way of
a collector or arterial street while being loaded or unloaded.
B. Location
Plans for location, design, and layout of all loading spaces shall be indicated on required
Site Plans.
Page 91 of 131
C. Space Size
Off-street loading spaces, excluding maneuvering areas, shall be at least 12 feet wide
and 20 feet long unless off-street loading will involve the use of semi-tractor trailer
combinations or other vehicles in excess of 25 feet in length, in which case the minimum
size of a space shall be 12 feet by 54 feet.
Section 9.06 Alternative Parking Plans (moved from Section 9.02.050)
See Section 3.16 for the process of an Administrative Exception for an alternative parking plan.
Section 9.06.010 Alternative Plans
An Alternative Parking Plan, processed through an Administrative Exception in accordance
with Section 3.16 of this Code, may be considered by the Director for alternatives to the
parking, stacking, or loading standards of this Chapter. An alternative plan also may be
approved by the Director for specific developments or uses that are deemed to require a
different amount of parking than the standards shown in the Off-Street Parking Requirements
Table. The Director shall establish conditions necessary to assure the adequacy of future on-
site parking when approving an alternate parking standard. Potential alternative parking plan
approaches and specific regulations are described below. See Section 3.16 for the process of an
Administrative Exception for an alternative parking plan.
9.02.060 Alternative Parking Plans in a Historic Overlay District
A. General. Within any Historic Overlay District the Historic Preservation Officer, or
designee, shall be authorized to approve alternatives to providing the number of off-
street parking spaces required in accordance with this Section.
B. Procedure. Alternative Parking Plans shall be reviewed and approved by the Historic
Preservation Officer, or designee following the procedures of the Administrative
Exception process established in Section 3.16 of this Code.
C. Recording of Approved Plans. Where an Alternative Parking Plan requires use of
property other than the subject property, an attested copy of an approved Alternative
Parking Plan must be recorded with the County Clerk on forms made available in the
Planning and Development Department. An Alternative Parking Plan may be amended
by following the same procedure required for the original approval. The applicant shall
provide proof of recording prior to approval of the Certificate of Occupancy.
D. On-Street Parking. The Historic Preservation Officer, or designee, may approve counting
on-street parking spaces to satisfy the requirements for off-street parking. Such on-street
parking shall be located on public right-of-way immediately abutting the subject
property and shall be reviewed by the Development Engineer for compliance with
City’s standards for use of rights-of-way.
Page 92 of 131
E. Off-Site Parking. Historic Preservation Officer, or designee, may approve the location of
required off-street parking spaces on a separate lot from the lot on which the principal
use is located if the off-site parking complies with all of the following standards.
1. Ineligible Activities. Off-site parking may not be used to satisfy the off-street
parking standards for residential uses (except for guest parking), restaurants
(except in the Downtown Overlay District), convenience stores, or other
convenience-oriented uses. Required parking spaces reserved for persons with
disabilities may not be located off-site.
1. Location. No off-site parking space may be located more than 900 feet from the
primary entrance of the use served (measured along the shortest legal pedestrian
route) unless remote parking shuttle service is provided. Off-site parking spaces
may not be separated from the use served by a street right-of-way with a width of
more than 80 feet, unless a grade-separated pedestrian walkway is provided or
other traffic control or remote parking shuttle service is provided.
2. Zoning Classification. Off-site parking areas require the same or a more intensive
zoning classification than required for the use served.
3. Agreement for Off-Site Parking. In the event that an off-site parking area is not
under the same ownership as the principal use served, a written agreement between
the record owners will be required. The agreement must be for a specified time, and
guarantee the use of the off-site parking area for a minimum of five years. An
attested copy of the agreement between the owners of record must be submitted to
the Historic Preservation Officer, or designee, for recording in form established by
the City Attorney. Recording of the agreement must take place before issuance of a
Building Permit or Certificate of Occupancy for any use to be served by the off-site
parking area. An off-site parking agreement may be terminated only if all required
off-street parking spaces will be provided. No use shall be continued if the parking
is removed unless substitute parking facilities are provided, and the Historic
Preservation Officer, or designee, shall be notified at least 60 days prior to the
termination of a lease for off- site parking.
Page 93 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 11, Enviro nmental P ro tec tion. Jordan Maddox
ITEM SUMMARY:
Chap ter 11 is the Enviro nmental chap ter o f the c o d e and the Committee has no t yet s een amend ments this
cycle. Pro p os ed amendments inc lude an impervio us credit for p ublic trails and s id ewalks (disc ussed as
p art o f Chapter 12); a rewrite o f the p ro visio ns o n s tormwater p o nd d es ign fo r c larity, includ ing where
p o nds can be loc ated, ho w they are c o nstruc ted , and ad d ing the Sub d ivisio n Variance to the sec tion;
finally, remove the alternative s treet design tab le from the Co nservation Sub d ivis ion s ec tion –an alternative
lo cal s treet is pres erved in Chapter 12.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 11 Cover Memo
Page 94 of 131
Page 1 of 3
Chapter 11 Environmental Protection
Section 11.02 Impervious Cover
11.02.010 Impervious Cover Limitation
D. Impervious Cover Credits
5. Credit for Public Trails and Sidewalks
Public trails and sidewalks do not count against the maximum impervious cover percentage
but shall be accounted for in stormwater calculations.
Section 11.04 Stormwater Management System Requirements
11.04.030 General Design Requirements
F. Design of all drainage facilities, including detention and water quality ponds, streets, inlets,
storm sewers, outfall, drainage berms, culverts, and ditches, and other associated improvements
shall conform to the City’s Drainage Criteria Manual, the City’s Construction Specifications and
Standards Manual, and the following general design standards.
1. Drainage facilities Detention and water quality ponds are not allowed within any Gateway
landscape buffer. Detention and water quality ponds located within the front any setback
shall be designed with a vegetated slope not to exceed 3:1 and shall not include structural
walls. All ponds shall be set back at least 20 feet from a platted residential lot except those
that are necessary to convey drainage in the shortest possible route to or from the street
right‐ of‐way, as determined by the Development Engineer. Drainage facilities include all
detention ponds, water quality ponds, outlet structures, drainage berms, improved channels,
or other improvements associated with the drainage improvements..
2. All dDetention ponds and water quality ponds within the front setback shall be designed to
the greatest extent possible to conform to the natural terrain of the land and, if possible, inas
curvilinear, non‐rectangular shapes. When visible from a street or adjacent to a residential
lot, the structural walls of Ddetention ponds and water quality ponds within the front street
setback shall not contain concrete walls (or similar material)shall be either constructed or
faced with stone, brick or similar masonry product. Outlet structures may be concrete. For
detention and water quality ponds located behind the Gateway landscape buffer, native
stone ‐ if mortared in place or dry stacked, or sloped grass walls are required if visible from
the right‐of‐way.
3. Fencing is allowed around detention ponds only if the fencing is constructed of wrought
iron or tubular steel or other similar product. Chain link fencing is not allowed. . TThe fence
pond shall be buffered from a publicthe street with Shade Trees. Shade Trees shall be spaced
a minimum of 30 feet apart, installed with at least 5 feet of pervious area in all directions,
shall be irrigated, and depicted on the Construction Plans.
view by planting 5‐gallon evergreen shrubs and vines that shall, at maturity, screen at least 40%
of the view of the detention pond and fence.
4. Separate ponds for each lot may be utilized if they are designed with a curvilinear contoured
shape, do not require fencing, utilize vegetatedive slope stabilization with a slope not to
exceeding 3:1, and do not use structural retaining walls.
Page 95 of 131
Page 2 of 3
5. A Subdivision Variance to these requirements may be requested pursuant to Section 3.22 of
this Code.
11.04.040 Building Permits and Utility Connections
B. Plans and design calculations for all drainage facilities shall be submitted to the Drainage
Development Engineer prior to issuance of any permit within the development or subdivision.
11.04.050 Drainage Easements
B. Design Requirements
1. Where topography or other conditions are such as to make impractical the inclusion of
drainage facilities within the road right‐of‐way, as determined by the Drainage Development
Engineer, perpetual unobstructed easements at least 15 feet in width for such drainage
facilities shall be provided across property outside the road lines and with satisfactory access
to the road. Easements shall be recorded by separate instrument and indicated on the plat.
Drainage easements shall be carried from the road to a natural watercourse or to other
drainage facilities.
Section 11.06 Conservation Subdivisions
11.06.060 Geometric and Pavement Standards
Local Sstreets within conservation subdivisions may be constructed to an alternativee cross‐section, as
described in Section 12.04.030. standards than those required in Chapter 12. The neighborhood street
network shall form an organized, connected pattern that defines the community both functionally and
visibly. Streets shall take the form of two‐way streets, two one‐way streets separated by a landscaped
median or a residential lane and shall be designed to respect and follow the existing terrain and
natural contours. Streets should, when possible, parallel existing tree lines, minimize construction and
grading costs, promote pedestrian movement and minimize crossing of primary conservation areas.
Maximum grading can be increased to 12% on local streets, where applicable. In addition, streets
should be shorter and narrower than traditional streets to lessen impervious cover and combine gentle
curves and grade changes with traffic calming measures for safety purposes. See the Table of standards
below.
Page 96 of 131
Page 3 of 3
Table 11.06.060: Conservation Street Geometric Standards
Criteria Alley Residential
Lane/Loop Local Res.
Collector*
Major
Collector
Minor
Arterial
Major
Arterial
Expected ADT -- <800 <800 >800 >2,500 >12,500 >24,000
Right-of-Way
(minimum feet) 20 50 50 70 112 136 160
Pavement Widths
(minimum feet) 15 20 26 33** 44 48 48-72
Traffic Lanes 1 2 1 shared
lane 2 2-4 2-4 4-6
Lane Width
(minimum width) 15 10 10 10 11 12 12
Parking Lanes None None Both sides Both sides Both
sides*** None None
Design Speed
(mph) -- 20-25 20-25 20-25 30-35 35-40 35-40
Median Width****
(minimum feet) -- -- -- 10 16 24 24
Edge Landscaping
(both sides (in
row))
-- -- -- -- 6 12 12
Sidewalk/Trail None Both Sides Both Sides Both Sides Both Sides Both Sides Both Sides
Sidewalk Width
(minimum feet) -- 5 5 5 8 ft trail*****8 ft trail 8 ft trail
Landscape
Easement (min 10
foot width)
None Both Sides Both Sides Both Sides Both Sides Both Sides Both Sides
* Residential Collectors are required to have a 15x6 foot bulb-out in the parking lanes every 250 feet.
** Pavement widths for Residential Collectors shall only be required at a minimum of 26 feet without parking
lanes if homes do not front onto it. R.O.W. for these streets would remain at 76 feet.
*** Parking required for 2-lane roadways only
**** Edge landscaping and 8’ trails can be interchangeable and meandering according to topography, existing
vegetation, slope or desired path.
***** 8 foot trails will be built to hike/bike standards in place of 5 foot sidewalk standards and can carry both
bicycle and pedestrian traffic.
Page 97 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 12, Pedestrian and Vehic le Circulation. Jordan
Mad d o x
ITEM SUMMARY:
Since the last d is c us s io n o n Chap ter 12, s taff has made changes adding a Sub d ivis ion Varianc e sec tion
clarifying that the entire chap ter is eligib le exc ep t fo r Des ign and Technic al Standards and Traffic Impac t
Analysis req uirements ; clarifying develo p er res p o ns ibilities on boundary brid ge s tructures; added
p ro visions that s id ewalks in rural/estate s ubd ivis ions are req uired o n b o th s id es of collec tors and o ne s ide
o f loc als ; clarified s ome language on fire cod e ac c es s req uirements; c ul-de-s ac s and lo t acc umulation;
ad d ed provis ion that s treet s tub s c anno t b e us ed as basis fo r lot frontage/ac c es s ; lo ng street b lo cks mus t
have a p ed es trian p as s -thro ugh; set minimum s pac ing requirements for right-in, right-o ut driveways
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 12 Cover Memo
Page 98 of 131
Page 1 of 17
Chapter 12 Pedestrian and Vehicle Circulation
Section 12.01 General
12.01.010 Purpose
An integrated vehicle, pedestrian, and bicycle transportation network is essential for the efficient,
effective and reliable movement of people and goods. The standards in this Chapter ensure that public
roads, sidewalks and trails within the city limits and the extraterritorial jurisdiction are of a sufficient
quality to ensure public health, safety, and welfare. Additionally, these standards ensure that the
comprehensive transportation network has sufficient connectivity and access from residential areas to
commercial and employment centers to promote the safe, orderly, and healthful development of the
city. The City’s Comprehensive Plan shall serve as a guide for the location and functionality of a
cohesive and integrated transportation network.
An interconnected street system is necessary to ensure that streets function in an interdependent
manner, provide adequate access for emergency and service vehicles, enhance walkability, and
provide continuous and comprehensible traffic routes. Adequate streets shall be provided such that the
arrangement, character, extent, width, and grade of each shall be considered in their relation to existing
and planned streets, topographical conditions, public safety and convenience, and an appropriate
relationship with the built environment.
12.01.020 Authority
The provisions of this Chapter are adopted pursuant to Texas Local Government Code Chapters 211
and 212, and the City Charter.
12.01.030 Applicability
A. The standards of this Chapter apply to development within the corporate limits and
Extraterritorial Jurisdiction (ETJ) of the City of Georgetown.
B. No subdivision, Site Development Plan or Stormwater Permit shall be approved until
conformance to these standards is demonstrated, unless otherwise provided for in this Chapter.
C. All required transportation improvements shall be designed in accordance with this Chapter and
as detailed in the adopted Construction Specifications and Standards Manual (“Construction
Manual”), as amended, or any specially-developed construction standards provided by the
Development Engineer. When the standards of this Code and the Construction Manual conflict,
the more stringent provision shall apply.
12.01.040 Subdivision Variance
A Subdivision Variance, pursuant to Section 3.22 of this Code, may be requested for all sections of this
chapter except for Section 12.06, Design and Technical Standards, and 12.09 Traffic Impact Analysis.
Section 12.02 Comprehensive Plan Thoroughfares
Regional thoroughfares provide linkages within the community and throughout the region, primarily
through vehicular traffic movement. The City’s Comprehensive Plan includes elements for an Overall
Transportation Plan that is developed in conjunction with the Capital Area Metropolitan Planning
Organization’s (CAMPO) long-range plan. Goals from the Overall Transportation Plan include:
A. Improve the local roadway system, including new thoroughfare linkages to enhance connectivity,
Page 99 of 131
Page 2 of 17
improved and coordinated traffic signalization, and access management standards.
B. A functional, well-integrated, multi-modal transportation system providing a variety of choices.
C. Reduce reliance on single-occupant automobile traffic and enhance bicycle and pedestrian
mobility and accessibility by encouraging compact land use development.
D. Provide for a high degree of safety for motorists, transit users, pedestrians and bicyclists.
E. Discourage primary traffic routing through local streets.
F. Preserve right-of-way for future roadway development and expansion.
12.02.010 General
It is necessary and desirable to obtain right-of-way for abutting and internal streets at the time of
platting or development to support the needs of the community. Developers share the responsibility of
providing adequate roadways through compliance with the minimum standards governing internal
and perimeter streets. Perimeter streets shall include thoroughfares directly abutting the proposed
subdivision, whether located within the boundaries of the subdivision or within adjacent public right-
of-way. Each development shall provide for the continuation of all streets depicted on the Overall
Transportation Plan, approved Concept Plan, plat, or other City-approved document depicting a
planned street connection.
The precise alignment of thoroughfares included in the Overall Transportation Plan may be varied to
allow for locational adjustments that would increase the compatibility of the right-of-way with natural
or man-made features such as steep slopes, waterways, wildlife habitats, historic structures, existing
development, or existing roadways.
12.02.020 Developer Responsibilities
The developer/subdivider shall be responsible for the dedication of internal and adjacent
comprehensive plan thoroughfares in accordance with the standards of the street classifications
described in the following section. There must be a rough proportionality between the traffic impacts
created by a new development and the associated impact requirements placed on the property owner.
The developer is responsible for all costs of materials and installation of the public improvements
required by this Chapter, unless otherwise specified. Utility assignments within street rights-of-way
can be found in the Construction Manual.
A. Minimum right-of-way requirements shall be in accordance with Table 12.03.030. If the
thoroughfare is an adjacent boundary street, the subdivider shall dedicate one-half of the balance
between the existing right-of-way and the ultimate right-of-way of the street and intersection
right-of way required per Table 12.02.030. Where the thoroughfare is internal to the property, the
developer shall dedicate the full section of ultimate right-of-way.
A.B. In addition to the minimum right-of-way standards, the City may require a right-of-way
reservation for individual thoroughfares expressly stated in the comprehensive plan, and right-
of-way for County and State highway projects that exceed the minimum right-of-way. The
Development Engineer may require additional right-of-way and/or easements for drainage,
utilities, slopes, etc. necessary to facilitate construction of the roadway.
C. In special circumstances, and at the discretion of the Director, the minimum right-of-way width
may be reduced to accommodate existing conditions. Special circumstances may include, but are
not limited to, adjustments to accommodate the compatibility of the roadway with natural or
Page 100 of 131
Page 3 of 17
man-made features such as steep slopes, waterways, wildlife habitats, historic structures, existing
development, or existing roadways.
D. Improvement to such roadways, in accordance with Section 12.09.030 (F), shall be the
responsibility of the developer unless otherwise provided. Developers are not responsible for
construction of any bridge structure at the boundary of subdivision if the bridging of such a
roadway does need to immediately connect to the network. A pro-rata contribution towards the
future construction of the bridge may be required, as determined by a Traffic Impact Analysis.
12.02.030 Comprehensive Plan Roadway Classifications
The following table provides general details for Comprehensive Plan regional transportation facilities.
Average Daily Trips (ADT) are utilized as a planning tool for projected development, while Level of
Service (LOS) is used as a measurement of functioning roadway adequacy once the facility is in
operation. All right-of-way widths listed in the table are minimum dimensions. Addition of facilities
beyond the minimums in the table, unusual natural site conditions, etc. may precipitate a larger right-
of-way section. All paved width dimensions are minimum and measured from back-of-curb to back-
of-curb and include travel lanes, bicycle lanes, the street gutter and the curb. Public Utility Easements
shall be required adjacent to every street right-of-way per Section 13.03 of this Code.
Table 12.02.030 Comprehensive Plan Street and Trail Standards
Regional Trail Major Collector Minor Arterial Major Arterial
Average Daily Trip (ADT)
Projected Range --- 2,501-12,500 12,501-24,000 24,001+
Design Speed (mph) ---
35 40 45
Right-of-way
(min. feet) 20 92 110 135
Right-of-way at
intersections (feet) --- 92 134 159
Travel Lanes (number of) --- 4 4 6
Travel Lane Width (feet) --- 11 11 12
Bicycle Lanes (feet) --- 4 4 4
Paved Width total (feet) 10 60 66 90
Median Width (min. feet) --- 10 16 16
Parking --- Prohibited Prohibited Prohibited
Sidewalks (min. feet) 10 6 6 6
Sidewalk Clear Zone
(min. feet) 6 6 6 6
Table Notes
Page 101 of 131
Page 4 of 17
1. Bike lanes may be combined with sidewalks into a Shared-use Path at a minimum width of 10 feet
with Clear Zone separation to satisfy the requirements of both. Regional Trail right-of-way is intended
for trails not adjacent to roadways.
2. Arterial roadway rights-of-way at intersections are increased according to the table for a distance of
200 feet from the right-of-way of the intersecting roadway.
3. Major Arterials may be designed intermittently at 40 mph at the discretion of the Development
Engineer.
4. Major Arterials shall not be expanded or re-striped beyond a 5-lane section without a median.
5. Landscape lots and commercial signage are prohibited within any part of the right-of-way of a
comprehensive plan roadway or trail.
Section 12.03 Local and Neighborhood Streets
The neighborhood street network shall form an organized, connected pattern that defines the
community both functionally and visibly. Streets should be planned and modeled so that future urban
expansion will not require the conversion of minor streets to major streets. When possible, streets
should be designed to respect and follow existing contours and natural features, minimize construction
and grading costs, promote pedestrian movement and minimize crossing of open space. In addition,
streets should generally be short in length and include cross-street access and traffic calming design
elements to promote safety and discourage speeding.
12.03.010 Developer Responsibilities
The developer/subdivider shall be responsible for the dedication and improvement of all local and
neighborhood streets in accordance with the standards of the street classifications described in the
following section. Where existing right-of-way does not meet the minimum standards, the developer
shall dedicate the remaining land in order to achieve roadway adequacy. The developer is responsible
for all costs of materials, design and construction of the public improvements required by this Chapter,
unless otherwise specified.
12.03.020 Neighborhood Streets
The following table provides general details for neighborhood streets. Average Daily Trips (ADT) are
utilized as a planning tool for a projected development, while Level of Service (LOS) is used as a
measurement of functioning roadway adequacy once the facility is in operation. All streets shall be
public streets, except for alleys and local private streets serving non-residential Multi-lot
developments, described in Section 7.02.030. Private streets in such situations shall be constructed to
local street standards and include a street maintenance agreement tied to the approved final plat.
All rights-of-way listed in the table are minimum dimensions and additional right-of-way and/or
easements may be required by the Development Engineer due to drainage, utilities, or construction
necessity. All paved width dimensions are measured from back-of-curb to back-of-curb and include
travel lanes, parking lanes, street gutter and curb. Public Utility Easements shall be required along
every street right-of-way per Section 13.03 of this Code. Utility assignments within street rights-of-way
can be found within the Construction Manual.
Page 102 of 131
Page 5 of 17
Table 12.03.010 Neighborhood Street Classification Standards
Alley Residential
Lane
Local
Street
Local Street –
Tree (alt.)
Local Street
- Downtown
Residential
Collector
Neighbor-
hood
Collector
Average Daily Trip
(ADT) Projected
Range
--- 1-800 1-800 1-800 N/A 801-1,400 801-2,500
Design Speed (mph) --- 30 30 30 30 30 30-35
Right-of-way
(min. feet)
20
(private) 40 50 50-62 60 60 60
Paved Width (feet) 15 22 30-32 30-32 38 36 28
Parking Prohibited Cut-out
parking only 2 Sides 2 Sides 2 Sides 2 Sides Prohibited
Sidewalks (min. feet) --- 5 5 5 6 5 5
Sidewalk Clear Zone
(min. feet) --- Optional Optional Varies Varies 5 10
Driveways Permitted Yes No Yes Yes Yes Limited No
Intersection Spacing
(max. feet) 1,500 1,320 1,320 1,320 N/A 1,320 2,000
Table Notes
1. All streets, with the exception of Alleys, are two-way streets. A Residential Lane may be signed for
one-way with parking on one side of the street. A one-way Lane shall not exceed 300 feet in length.
2. Alleys shall have at least two direct access points to public streets. Alleys shall either be platted in a
private lot or easement with full public access rights including public safety and utilities.
3. Residential Lanes require companion alleys to provide access to the lots fronting on the lane. Cut-out
parallel parking for temporary loading and visitor parking is allowed with additional right-of-way.
4. Local Streets vary in width depending on curb type, in accordance with Section 12.06.E.
5. Local Street - Tree alternative shall be designed according to the provisions in Section 12.06.G.
6. Residential Collectors are subject to the driveway separation requirements pursuant to Section 12.08.
7. Residential Collectors shall have curbed bulb-outs measuring 15x6 feet in the parking lanes located at
300 feet intervals and at all intersections.
8. Neighborhood Collectors shall not have residential lots fronting on the roadway, nor permitted access
to residential lots. Access to parkland, amenity centers, or common areas is permitted. Neighborhood
Collectors shall be designed in accordance with the street tree planting provisions in Section 12.06.G.
9. Local Streets in the ETJ may be designed at 25 mph.
Section 12.04 Alternative Streets
Street designs and configurations may often require a contextual approach to both transportation need
and design of certain facilities beyond the standard details. Alternative street designs may be
Page 103 of 131
Page 6 of 17
warranted when streets are located in areas that require situational solutions based on density, land
use, and pedestrian environment.
12.04.010 Downtown Overlay District Streets
All streets, rights-of-ways, sidewalks, and associated design features located within the Downtown
Overlay District shall comply with the Downtown Master Plan, as amended. For development
occurring within the Downtown Overlay District, the developer shall be responsible for the dedication
of half of the remaining right-of-way and full construction of landscaping, sidewalks, lighting and
other features of the Downtown Master Plan, where non-existent or in need of re-construction, up to
but not beyond the curb. If a development is approved for parking to be located within the right-of-
way, the developer shall be responsible for any necessary paving and/or intersection improvements to
conform to the standards of subsection (A) below.
The Director may consider a lesser right-of-way and/or street design when existing structures, trees, or
other objects preclude the expansion to the minimum right-of-way. In such instance, the Director
consider reduced lanes, alternative on-street parking configurations, or other alternative design
A. Street Standards
1. All streets located within the Downtown Overlay District shall meet the minimum right-of-
way and pavement widths in Table 12.03.010. Downtown Local Streets shall be designed with
parallel parking inset by intersection bulb-outs on each side of the street and one travel lane
in each direction.
2. Streets uniquely identified within the Downtown Master Plan shall be dedicated and
constructed according to the cross-section in the Downtown Master Plan.
3. Intersection crosswalks shall be constructed, at a minimum as Type B crosswalks, as depicted
in the master plan. Street lighting shall be in accordance with Section 12.06 of this Code.
B. Sidewalks and Trees
1. Sidewalks located within the Downtown Overlay District shall be at least six (6) feet wide and
constructed according to the design standards of a Level III Sidewalk, as described in the
Downtown Master Plan, unless the associated street/sidewalk is classified therein as a Level I
or II sidewalk, which shall be constructed accordingly. Level III sidewalks shall include a four
(4) foot vegetated strip between the curb and sidewalk when not adjacent to head-in or
angled street parking.
2. Street Trees shall be required in the Downtown Overlay at a spacing of 40 feet for Shade Trees
and 20 feet for Ornamental Trees. Shade Trees shall be placed in a tree wells sized and
equipped with underground root barrier treatments in accordance with Section 12.06.
Approved Ornamental Trees shall not require root barrier treatments.
12.04.020 Local Street - Street Tree Alternative
Street trees are permitted in the right-of-way only through the local street alternative cross-section
designed specifically for street trees. All other trees planted along streets shall be located in the front
yard of the lot. Shade Trees shall be spaced 40 feet apart within a parkway strip sized and equipped
with designated root barrier treatments in accordance with Section 12.06.
Page 104 of 131
Page 7 of 17
12.04.030 Conservation Subdivision Streets
Local Streets within a designated Conservation Subdivision (per Section 11.06 of this Code) may be
constructed to a 26-foot pavement width with parking restricted to one designated side of the street in
accordance with the provisions of the adopted fire code. The parking lane shall be inset from the travel
lanes using bulb-out curb design measuring 15x6 feet at each intersection and at 300-foot intervals.
12.04.040 Residential Rural Estate Streets
Local Streets within a Residential Rural/Estate Subdivision (per Section 13.01) may be constructed to a
26-foot pavement width, measured from outside of curb to outside of curb. Within the City’s
designated fire service area, on-street parking is restricted in accordance with the adopted fire code.
Rural/Estate streets located in the ETJ may be designed to 25 mph speeds and utilize a ribbon curb to
allow for sheet flow or open-ditch stormwater drainage. Rural/Estate Streets within the ETJ shall
conform to the street length provisions in the Williamson County Subdivision Regulations, as
amended. Sidewalks in Rural/Estate subdivisions are required on both sides of all collector-level and
higher streets, including perimeter streets, and one side along local streets.
12.04.050 Context Sensitive Street Alternatives
The City’s Overall Transportation Plan allows for design flexibility for comprehensive plan roadways
to accommodate the existing or desired built environment. Context Sensitive Street (CSS) alternative
cross-sections are provided within the Overall Transportation Plan to account for settings that contain
a mixture of uses, densities, and building types that may affect pedestrian and bicycle patterns, speeds
of roadway and on-site parking options. As an alternative to the standard street types for
comprehensive plan roads and neighborhood streets, the cross-sections approved in the plan may be
considered as options for development with this Code.
Additionally, a development in a Mixed-Use (MU) Zoning District may utilize the urban street cross-
sections identified in Section 4.09 of this Code.
Section 12.05 Subdivision and Street Design
To further the goal of the Overall Transportation Plan of an interconnected street network, new streets
shall be designed to integrate into the existing and planned street network. New subdivisions shall
account for primary and secondary entry points into a subdivision, connect to streets stubbed from
adjacent properties, and provide for a neighborhood street layout focused on the safety of vehicles,
bicycles, and pedestrians.
12.05.010 Street Network Connections
Street network connections shall be made based on the number of proposed residential lots/units, the
size and configuration of the land, and the type of roadways constructed. Connection locations shall be
depicted on the Preliminary Plat, Concept Plan and any associated phasing plans, and shall conform to
the standards detailed below.
A. Street Connections Required
Each subdivision or lot accumulation shall contain a minimum number of total street connections to
the public street network, depending on the number of lots/units. In addition to these minimum
connections, intersection spacing and connectivity provisions may alter the number of connections
Page 105 of 131
Page 8 of 17
required. For the purposes of this Section, lots/multi-family units and subdivision/Site Development
Plan for multifamily are interchangeable. In addition to the following public street connection
requirements, development shall also comply with the emergency access requirements in the
adopted Fire Code.
1. Minimum Number of Total Street Connections
The total number street connections to the ultimate street network includes connections to
existing public streets and future stubs to adjacent properties.
a. A subdivision or lot accumulation of five (5) lots or greater shall contain a minimum of
two (2) total street connections. Residential cul-de-sacs within a subdivision that has a
minimum of two (2) street connections are allowed pursuant to Section 12.05.020.B.
b. 100 lots or greater shall contain a minimum of three (3) total street connections.
c. 150 lots or greater shall contain a minimum of four (4) total street connections.
d. 200 lots or greater shall contain a minimum of five (5) total street connections.
e. 300 lots or greater shall contain a minimum of six (6) total street connections.
f. 500 lots to 999 lots shall contain a minimum of seven (7) total street connections and every
additional 500 lots thereafter shall require one (1) additional street connection.
2. Existing Street Connections
Existing Street Connections are public street connections to an existing public street that
ultimately connects in two or more locations to a Major Street.
Of the required Street Connections described above:
a. A subdivision or lot accumulation of 80 lots or greater shall contain two (2) Existing Street
Connections.
b. A subdivision or lot accumulation of 500 lots or greater shall contain three (3) Existing
Street Connections.
3. Future Street Connections
Future Street Connections are public street stubs to an adjacent unplatted property that will not
immediately connect to a public street, and the ultimate connection is dependent upon the
development of the adjacent property. To meet the total number of street connections, street stubs
would be in addition to any required connections to existing streets.
Credits towards the total number of street connections include:
a. A street connection that is a collector-level or higher classification roadway counts as two
(2) local street connections.
b. A street connection that is a Major Collector or higher classification roadway counts as
three (3) local street connections.
B. Additional Requirements
1. All existing streets in adjoining areas shall be connected and continued into the new
subdivision in alignment therewith. Practical downsizing or upsizing of street widths, speeds,
and design will be reviewed and permitted at the discretion of the Development Engineer.
Page 106 of 131
Page 9 of 17
2. Whenever existing or future street connections are required, the right-of-way shall be
extended and all public improvements constructed to the property line boundary.
3. The Director can require that a proposed Future Street Connection be shifted to a more
suitable location in order to minimize block length, discourage cut-through traffic, align
compatible uses, preserve trees, prevent reserve strips, and increase the likelihood of eventual
connection.
4. All Major Collector-designated streets and higher classifications shall connect or stub on both
ends to an existing or planned collector or higher-level street. All other collectors should
generally connect to another collector although, on a case-by-case basis, exceptions can be
considered an Administrative Exception. Collectors shall not turn in a perpendicular manner
after a stop or 90 degree bend, nor shall a collector end in a cul-de-sac or other permanent
turn-around.
5. Streets in a Residential Rural/Estate Subdivision that connect to an adjacent stub street shall
be constructed to the width and standards of the connecting roadway.
6. A street stub cannot be used as the basis of frontage and/or access for an adjoining lot. Street
stubs are intended only to continue through such property.
6.7. An existing platted residential lot or portion thereof may not be utilized as a means to connect
a proposed street to an existing public street or cul-de-sac in order to meet the requirements
of this Section.
12.05.020 Streets and Blocks
A. Intersection Spacing
Intersection spacing for Neighborhood Streets shall not exceed the lengths specified in Table
12.03.020. Intersection spacing shall be measured from the center line of three-way or four-way
intersections of through-streets. Cul-de-sac and other non through-streets do not apply as an
intersection when measuring length of spacing. Intersection spacing shall apply beyond each
individual subdivision and measurements shall be continued into the adjacent subdivision.
Intersection spacing requirements do not apply to Comprehensive Plan roadways.
B. Mid-Block Connection
Any street block that is 1,000 feet or greater in length shall have a minimum 15-foot wide pass-
through lot near the mid-point of the block. The pass-through lot shall connect on both ends to a
public street and extend the depth of the block and shall be owned and maintained by a property
owner’s association. Within the lot, a minimum 6-foot wide sidewalk shall be constructed and
connect on either end to public sidewalks.
C. Cul-de-sacs
A residential Cul-de-sac Street (or streets) shall not exceed 20 total lots or 500 feet in length,
whichever is less. A Cul-de-sac Street (or streets) exceeding 15 lots shall include a pedestrian or trail
access from the end of the cul-de-sac through to the nearest public street, public school, sidewalk or
trail, provided that such connection is located within the same subdivision. A residential cul-de-sac is
permitted only within a subdivision that has more than one public street connection and shall not
take access off of an arterial roadway.
D. Temporary Dead-end Streets
Page 107 of 131
Page 10 of 17
Dead-end streets shall be prohibited except for street stubs and approved cul-de-sacs. For streets that
are planned to extend in the future, temporary turn-arounds shall be required where the street stub
exceeds 150 feet in length and shall be depicted on the plat as a temporary easement. The following
note should be placed on the plat: “Crosshatched area is temporary easement for turn-around until
street is extended.” No temporary dead-end street in excess of 500 feet shall be allowed. Reserve
strips at the end of streets are prohibited.
E. Street Connectivity
The street network for any subdivision with internal roads or access to any public road shall achieve
a connectivity ratio of not less than 1.20. A Connectivity Ratio is achieved by taking the number of
street links divided by the number of nodes or end links, including cul-de-sac heads. A node is the
terminus of a street or the intersection of two or more streets.
A link is any portion of a street defined by a node at each end
or at one end. Streets intersecting to an external collector or
arterial street are not considered nodes, but are considered
links. Street stubs to an adjacent property are considered
links, but alley intersections are not.
The adjacent graphics and sample calculation shows how the
street connectivity ratio for a subdivision shall be calculated.
12.05.030 Inter-Parcel Connectivity
All new and amended commercial and multi-family Site Development Plans and Stormwater Permits
that require off-street parking and driveways shall provide driveway connection to adjacent properties
parallel to the fronting roadway, whether such property is developed or undeveloped. Access
Easements shall be provided where necessary to achieve such a connection. The Director may consider
alternative connections to the rear or adjust connection locations where practical.
12.05.040 Exceptions
Exceptions to the requirements of Section 12.05 may be considered by the Director, through a
Subdivision Variance, or by the abandonment of a right-of-way, in compliance with this Code and the
City’s Municipal Code.
A. Administrative Exception
The Director may consider an Administrative Exception during subdivision plat review if a natural
or man-made barrier such as a highway, railroad, floodplain, or severe topography would prevent a
road connection from taking place.
B. Subdivision Variance
Numbers (#) indicate Links = Nodes
13 links/11 nodes = 1.18 ratio
(Does not meet required 1.20 ratio)
Page 108 of 131
Page 11 of 17
A Subdivision Variance pursuant to Section 3.22 can be considered for proposed and required Street
Connections. The developer shall demonstrate that all other administrative options have been
exhausted. The following are eligible for Subdivisions Variance consideration:
1. Number of required connections, type of street connection, land use compatibility, or location.
2. A local street that would connect a commercial/industrial development and a residential
development. In such instance, the developer who proposes or is required to make such a
connection may apply for the subdivision variance and must ensure that removal of such a
connection does not cause detrimental effects to the street network of the adjacent subdivision.
C. Street Abandonment
If not otherwise eligible for a Subdivision Variance or exception provided for in this Section, a City-
approved public street or street stub that is proposed by any party to be closed, disconnected or
never connected to another public street shall be submitted to the City Council for abandonment.
Street Abandonment shall follow the procedures in the City’s Municipal Code. No public street,
right-of-way, or street approved by a plat shall be abandoned by the City or County if not in
accordance with this Code. The City and County will collectively determine whether to close or
abandon the portion of a public street that is or is planned to be in both jurisdictions.
Section 12.06 Design and Technical Standards
Streets shall be designed in accordance with the design speed standards established in this Chapter
in conjunction with the American Association of State Highway and Transportation Officials
(AASHTO) Manual, as amended. When AASHTO standards and the City’s conflict, the more
stringent standard shall apply.
A. Street Curves and Geometry
1. Vertical curves shall be designed in accordance with AASHTO standards.
2. Horizontal curves shall be separated by a minimum tangent of 100 feet for Comprehensive
Plan Roadways and 50 feet for all other roadways.
3. Reverse curves shall be separated by a minimum tangent of 100 feet. Super-elevated curves
shall not be allowed.
4. Horizontal tangents approaching an intersection shall be a minimum of 50 feet in depth.
5. Street landings shall be a minimum of 30 feet in depth with a grade of less than 2%
approaching an intersection.
6. Grade breaks shall not exceed 1% without a vertical curve.
7. Longitudinal grade shall be a minimum of 0.5% for streets using a curb and gutter drainage
system. Maximum grade shall conform to AASHTO criteria for all Comprehensive Plan
Roadways and shall not exceed 15% for all other roadways.
8. Exceptions to these standards, in addition to the design speeds for streets not classified as
Comprehensive Plan Roadways may be considered by the Development Engineer on a case-
by-case basis. Approved design speeds differing from the statutory prima facie speed limits
shall require signage in accordance with the Texas Manual on Uniform Control Devices.
Page 109 of 131
Page 12 of 17
B. Turning Radius
1. Local street intersections with local streets shall have a minimum curb radii of 15 feet. All
collector-level roadway intersections with local streets and collectors shall have a minimum
curb radii of 25 feet. All arterial roadway intersections with any type of street shall have a
minimum curb radii of 30 feet.
2. Cul-de-sac streets shall have a minimum 60-foot right-of-way and of 50-foot paved radius for
single- and two-family uses, and 70-foot right-of-way and 60-foot paved radius for all other
uses. Cul-de-sacs shall include a 25-foot inside, 50-foot outside turning radius for fire
apparatus.
3. Street intersections containing one or more Neighborhood Collector and higher classification
streets shall include 25-foot right-of-way flares. The 25 feet is measured along the tangents
from the point of intersection of the two right-of-way lines.
C. Intersection Alignment
1. All streets shall intersect at a 90-degree angle, except where existing conditions will not
permit. A deviation of up to 15 degrees may be considered by the Development Engineer on a
case-by-case basis.
2. New streets intersecting with an existing street shall be tied to the existing street on center
line with dimensions and bearings to show relationship. Where the Development Engineer
determines that precise alignment of local streets or Residential Collectors is impossible due
to natural features or other unique elements of the land, such off-sets may be included
provided the distance between center lines is not less than 125 feet.
D. Intersection Visibility and Sight Triangle
1. A sight triangle shall be established at all street intersections to
ensure street visibility, measuring 25 feet along the right-of-way in
each direction from the projected intersection. At the intersection
of two local streets, however, the sight triangle can be measured
from the back of the curb or, where no curbs are in existence, the
edge of the pavement. Where the right-of-way/curb curves at the
intersection, the tangents at the points of beginning for the corner
curve shall be projected to determine the origination of the sides
of the sight triangle.
2. Within the sight triangle, no construction, planting, grading or other natural or manmade
object, including signs and human advertising, that interferes with street visibility shall be
permitted between the heights of three (3) and eight (8) feet, measured from the crown of the
street, except as approved by the Development Engineer.
3. The Development Engineer has the authority to extend the sight triangle based on speeds,
pedestrian facilities, and location of the painted stop bar at the intersecting roadway.
Furthermore, the Development Engineer may make a determination that objects interfering
with street visibility shall be removed or otherwise altered to restore visibility.
E. Street Curbs
1. Approved street curb types are vertical, mountable, and ribbon curbs. Each curb type shall be
appropriate for the street classification, speed, drainage collection and meet the requirements
Page 110 of 131
Page 13 of 17
of this Chapter. All curbs, gutters, and inlets shall be designed and constructed in accordance
with the Construction Manual.
2. Comprehensive Plan Roadways, Neighborhood Collectors and streets within a Residential
Rural/Estate Subdivision may include ribbon curbs with approved drainage plans. All other
streets shall be constructed with mountable or stand-up curbs unless approved by the
Development Engineer.
3. Mountable and ribbon curbs require a clear zone safety separation between sidewalks, in
accordance with Section 12.07.
4. Curb Basis for all streets shall be a minimum of nine (9) feet, measured from the back of curb
to the right-of-way to ensure that utilities can be adequately provided. The adjacent property
owner is responsible for maintenance of all pervious surfaces within this area, including
vegetative materials, trees, etc. per City Code Section 8.20.100. Encroachments into the right-
of-way such as trees, landscaping, signage, and irrigation shall require a License to Encroach
unless specified by a plat or maintenance agreement.
F. Street Lights
1. Street lights shall be provided by the developer on all public and private streets located at
intervals not exceeding 300 feet, at all street intersections, and at the terminus of a cul-de-sac,
except as otherwise specified herein. The lighting type, size of luminaire, mounting poles,
location, and installation procedures shall be determined by the City’s Electrical Engineer or
designee, in accordance with the standards in the Construction Manual.
2. In a Residential Rural/Estate Subdivision, installation of street lights shall only be required at
the entrances to the subdivision. The subdivider shall be responsible for the installation and
capping of electrical conduits at all street intersections and cul-de-sacs within the subdivision
so as to allow for future installation of street lights.
3. In the Downtown Overlay District, street lights shall be constructed using either the antique
lighting or standard light poles painted “Dark Green” in accordance with the Downtown
Master Plan and the Construction Manual.
G. Street Trees
Trees are an important part of the streetscape and should be planted according to the context of a
street. Shade trees shall typically be planted outside of the right-of-way in the front yard except
where otherwise restricted in this Code. Shade trees planted within the right-of-way between the
curb and sidewalk shall be planted in accordance with the following criteria:
1. 4-foot minimum separation with a modular suspended pavement framing system;
2. 8-foot minimum separation with plastic root barriers; or
3. 10-foot minimum separation between back of curb and sidewalk with no root barrier.
4. Tree species and spacing requirements, unless otherwise specified, shall be approved by the
Urban Forester on the Construction Plans.
5. All street trees shall be irrigated and maintained by the adjacent property owner, property
owner association, or special district. A maintenance agreement and plat note shall be
established prior to recordation of the final plat for the subdivision.
Page 111 of 131
Page 14 of 17
H. Street Naming
1. Streets shall be named according to the City’s Addressing and Naming Policy.
2. Streets shall be named so as to provide continuity of name with existing streets and so as to
prevent conflict with identical or similar names within the county.
3. Driveways or approved private streets serving more than one internal lot that connect to an
Arterial roadway shall be named and signed according to the City’s Addressing and Street
Naming Policy.
Section 12.07 Pedestrian and Bicycle Mobility
12.07.010 General
The developer shall be responsible for all sidewalks and trails that are identified in this Code, the
City’s Sidewalk Master Plan, Overall Transportation Plan, Parks Recreation and Open Space Master
Plan, Trails Master Plan, Downtown Master Plan, and other relevant plan. Public sidewalks and trails
do not count against the maximum impervious cover percentage required in Section 11.02 of this Code.
A. Sidewalks
1. Sidewalks shall be constructed on both sides of all streets, including frontage roads, at the
minimum widths described in Tables 12.03.030 and 12.04.020 of this Code, except as provided
in Section 12.04.040. Sidewalks shall be constructed consistent with the Construction Manual
and in conformance with the requirements of the Americans with Disabilities Act (ADA).
2. Sidewalks shall be separated a minimum of six (6) feet from the back of a ribbon curb and
four (4) feet from the back of a mountable curb on streets with speeds of 30 mph and greater,
in addition to the Sidewalk Clear Zone minimums provided in Tables 12.02.030 and 12.03.010.
3. Sidewalks constructed with new Site Development Plans shall be located within the street’s
public utility easement and shall be maintained in perpetuity by the property owner and their
successors. A public access easement shall be granted by either the recording of a plat or
separate instrument, and shall be depicted on any subsequent plans.
4. Pedestrian accessways shall be provided from the public sidewalk to the main entrance of
each building or to a sidewalk leading to the main entrance.
5. Construction of public sidewalks on single-family and two-family lots may be deferred to the
building permit, built to the standards and specifications at the time of the permit. Sidewalks
located in common areas, parks and along Neighborhood Collectors shall be constructed at
the time of street improvements.
6. Sidewalks located within the Downtown Overlay District shall comply with the design
standards in Section 12.04 of this Code and the Downtown Master Plan, as amended.
7. Sidewalks constructed as infill, retrofitted, or rehabilitation projects should follow the
standards of this Chapter where practical to do so, but consideration shall be given to the
existing conditions of the built and natural environment when locating such sidewalks.
B. Trails
Page 112 of 131
Page 15 of 17
Regional Trails depicted on the Trails Master Plan shall be dedicated and constructed at the time of
development as a public improvement in the general locations and alignments depicted therein.
1. If the trail is not located on public property, a minimum of 20 feet of right-of-way or public
access easement, shall be dedicated as approved by the Director of Parks and Recreation.
2. The trail shall be a minimum of 10 feet in width, constructed to the standards depicted in the
Trails Master Plan, or otherwise approved by the Director of Parks and Recreation.
3. A trail may substitute for a street sidewalk if located along the same roadway.
C. On-Street Bicycle Facilities
On-street bicycle facilities are required on Major Collectors and Arterials at the minimum widths
specified in Table 12.02.030. Design and construction of all bicycle facilities shall meet or exceed
standards set forth in the City’s Overall Transportation Plan.
D. Sidewalk Fund
A separate fund to be deposited at the highest interest rate permitted by law to be entitled
“Sidewalk Fund” shall hold any financial contributions paid by owners, developers, etc., as
applicable to this Chapter. Funds shall be held in trust to be used exclusively for the purpose of
purchasing and/or equipping public streets for sidewalks.
E. Alternative Pedestrian Improvements
1. Alternative locations or design variation(s) of sidewalks, pedestrian access facilities, or hike
and bike trails to a standard that deviates from the Construction Manual can be requested to
the Development Engineer. If approved, ownership and maintenance shall be transferred to
the property owner or property/homeowner association and recorded by separate
instrument, along with a public access agreement.
2. When an administrative alternative cannot be achieved for a sidewalk, pedestrian accessway
or trail, a Subdivision Variance pursuant to Section 3.22 may be requested for either fees-in-
lieu of construction, delay of construction, or waiver at such time the improvement is
required. Justification for the variance include, but are not limited to, the location of the
facility in relation to the existing or planned pedestrian network, the need for the facility,
and/or difficult topographical and other natural features on site. Prior to approval of the plat,
Site Development Plan, or other applicable process, payment of fees shall be provided for
deposit into the Sidewalk Fund at a cost not to exceed 125% of the estimated construction
plan costs, as approved by the Development Engineer. A request may be made to City
Council for City participation in any pedestrian improvements required by this Chapter.
Section 12.08 Driveway Standards
All driveways accessing a street shall require a permit through either a Site Development Plan,
Building Permit, Stormwater Permit, or Driveway Access Permit, in accordance with the terms of this
Code. The Development Engineer may use discretion on exact spacing distance and location, where
warranted. A lot approved in accordance with this Code has the right to at least one (1) driveway
access point, which may or may not be full-access depending on conditions. Driveways may provide
access to no more than four (4) lots before requiring a public street, or where permitted, a private
street.
Page 113 of 131
Page 16 of 17
A. Residential Driveways
1. Single-family and two-family lots shall take access only from an alley, local street, residential
lane, or residential collector.
2. Residential driveways on a Local Street serving single-family or two-family lots shall be
separated from a street intersection by a minimum of 50 feet, measured from the right-of-way
to the center of the driveway. Residential lots with frontage on more than one non-
intersecting street shall take access from the street with the lower classification.
3. Residential driveways on a Residential Collector serving single-family or two-family lots shall
be spaced a minimum of 70 feet on center and shared driveways are not permitted.
Exceptions to this provisions include:
a. Does not apply to alley-loaded lots fronting on Residential Collectors.
b. Does not apply if less than 25% of the linear street frontage contains front-loaded lots.
c. Distance separation may be reduced to 55 feet if only one side of the street is front-loaded
or if the street is divided by a median.
d. A platted lot that is 90 feet or greater in width located on a collector-level or higher
roadway may be allowed a second driveway access point irrespective of the 70-foot
separation provision, in full accordance with all setback provisions.
B. Non-Residential Driveways
1. Non-Residential driveways shall be no wider than 30 feet, except where a median is present
within the driveway. When a median is desired or required, the driveway width shall not
exceed 45 feet and the median shall be constructed with a mountable curb. On roadways
operated by the Texas Department of Transportation (TxDOT), the Development Engineer
may defer to TxDOT in circumstances where these standards are not practical.
2. Non-Residential full-access driveways shall be separated from a street intersection in
accordance with Table 12.08, measured from the right-of-way to the center of the driveway.
Minimum separation for right-in, right-out-only driveways shall be determined by the
Development Engineer on a case-by-case basis, but in no case be spaced less than 200 feet
from a street or driveway.
3. Non-Residential driveways on double-frontage lots located in a Residential Zoning District
shall have offsetting access points from opposing streets to inhibit cut-through traffic.
4. The Development Engineer shall have the authority to require the closure or relocation of
existing driveway access points where multiple access points to the site are available.
5. A Driveway Access Permit may require an engineering study or a Traffic Impact Analysis in
accordance with Section 3.19 of this Code.
Page 114 of 131
Page 17 of 17
Table 12.08 Driveway Spacing
Non-Residential Driveway Spacing
Posted Speed (MPH) Driveway Spacing (Feet)
≤30 200
35 250
40 305
45 360
50 425
Minimum Connection Spacing Criteria for Highway Frontage Roads
Minimum Connection Spacing (feet)
Posted Speed (MPH) One-Way Frontage Roads Two-Way Frontage Roads
≤30 200 200
35 250 300
40 305 360
45 360 435
>50 425 510
Desirable Spacing between Highway Exit Ramps and Driveways
Total Volume
(Frontage Road + Ramp)
(vph)
Driveway or Side Street Volume
(vph)
Spacing
(feet)
Number of Weaving Lanes
2 3 4
< 2500 < 250 460 460 560
> 250 520 460 560
> 750 790 460 560
> 1000 1000 460 560
>2500 < 250 920 460 560
> 250 950 460 560
> 750 1000 600 690
> 1000 1000 1000 1000
* The standards in this table are derived from the City of Georgetown Driveway Spacing Study, adopted July
2001 and based on AASHTO sight distance standards; and the City of Georgetown Access Management
Policy, adopted December 2003.
Section 12.09 Traffic Impact Analysis (unchanged)
Page 115 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 13, Infrastruc ture and Pub lic Imp ro vements.
Jordan Maddo x
ITEM SUMMARY:
Since the last d is c us s io n o n Chap ter 13, s taff has made changes c larifying exc eptio ns to Fire Flow
p ro visions in the F ire Co d e; remo ved the Mo numentation sec tion from the c hap ter; removed S ubdivis io n
Variances from the C hapter alto gether and replac ed with Development Engineer exc ep tions and alternatives ;
mo ved s o me language regard ing fisc al surety into the Develo p ment Manual; mo ved d efinitio ns fro m
Sec tion 13.10 into C hapter 16 and mad e minor ed its .
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 13 Cover Memo
Page 116 of 131
Page 1 of 8
Chapter 13 Infrastructure and Public Improvements
Section 13.01 General
The purpose of this Chapter is to ensure the orderly continuation of public improvements for
development in Georgetown, including the planning, design, and construction thereof. The intent of
this Chapter is to ensure that development provides for the construction of adequate public
improvements in a safe, equitable, and efficient manner.
13.01.010 Applicability
The provisions of this Chapter are adopted pursuant to Texas Local Government Code Chapters 211
and 212, and the City Charter.
13.01.020 Public Improvements
Land proposed for development in the City’s corporate limits and extra‐territorial jurisdiction (ETJ)
shall be adequately served by essential public facilities and services, including but not limited to water
distribution, wastewater collection and treatment, roadways, pedestrian circulation, storm drainage
conveyance, and park and recreational facilities. Development seeking or requiring connection to a
public utility system shall design and install public improvements in accordance with the
Comprehensive Plan, and shall meet the minimum requirements established by this Code, the City’s
Construction Standards and Specification Manual (“Construction Manual”) and any other adopted
City design or technical criteria.
Public improvements required for development under the provisions of this Code include, but are not
limited to:
A. Stormwater drainage system, including but not limited to drainage easements, channels, storm
sewer lines and inlets, in accordance with the provisions of Chapter 11 of this Code.
B. Streets, including but not limited to sidewalks, alleys, bridges, and street lighting, in accordance
with the provisions of Chapter 12 of this Code.
C. Utility system, including but not limited to water, wastewater, and electric infrastructure, in
accordance with the provisions of this Chapter.
D. Utility services for communications, gas, other electric providers, or other approved service shall
be installed in accordance with the approved utility assignment locations and associated
franchise agreements.
13.01.030 Public Improvement Exemptions
A. 80 Percent Rule
Residential subdivisions processed as either a Minor Plat or a Resubdivision of four (4) or fewer
lots may provide certain public improvements to the same or similar level, as determined by the
Development Engineer, as the existing improvements serving 80% of adjacent properties that
contain a residential or agricultural use. For purposes of this section, “adjacent properties”
include properties directly across a street right‐of‐way from the subject property.
The 80% Rule exemption applies to the public improvements required in this Code, except as
follows:
1. Chapter 11, Stormwater.
Page 117 of 131
Page 2 of 8
2. Section 12.02, Comprehensive Plan roadway right‐of‐way dedication.
3. Section 12.08, Sidewalks, in the city limits only. Sidewalks in the ETJ are exempt.
4. Section 13.03, Public Utility Easements.
5. Section 13.04, Fire Flow, unless granted an exception as authorized by Sections B103 and
B105 of the International Fire Code, considering density, on‐site storage, sprinkler system,
and any other authorized modifications. by the Fire Chief.
6. Section 13.07. Monumentation and Control Point Markers.
7.6. Section 13.07, Utility Master Plan lines infrastructure.
B. Residential Rural/Estate Subdivisions
Single‐family development within the Agriculture (AG) and Residential Estate (RE) Districts, or
in the City’s extraterritorial jurisdiction (“Residential Rural/Estate Subdivisions”) qualify for
certain modified standards throughout this Chapter and other chapters of this Code, where
specified. It is the intent that these modified standards be used to create a rural‐type atmosphere
for a development without sacrificing the integrity of current or future infrastructure systems.
The resubdivision of a Residential Rural/Estate Subdivision to a density which does not meet the
rural exemption shall be upgraded in conformance with this Code.
C. Subdivision Variances
The requirements in the following sections of this Chapter are eligible to be considered for a
Subdivision Variance, per Section 3.22 of this Code:
1. Section 13.04, Public Water Standards
2. Section 13.05, Public Wastewater Standards
3. Section 13.06, Electric Standards
Section 13.02 Public Improvement Requirements
13.02.010 Developer Responsibilities
The developer is responsible for payment of all costs of materials and installation of all infrastructure
and public improvements required by this Code, unless otherwise specified.
13.02.020 Continuity of Improvements
All public improvements shall be designed and installed to provide for a logical system of utilities,
drainage and streets, and to create continuity of improvements for the development of adjacent
properties. All required public improvements shall be extended along the boundary and/or through
the subject property to the perimeter of the subject property. Utility assignments are depicted in the
Construction Manual.
13.02.030 Inspection of Improvements
A. During the course of installation and construction of the required improvements, the
Development Engineer or designee shall make periodic inspections of the construction to ensure
that all improvements comply with the provisions of this Code. Construction that fails to comply
with the standards and specifications contained or referred to herein shall not be accepted.
Page 118 of 131
Page 3 of 8
B. The City will charge engineering inspection fees during construction and for final inspection. The
City will not provide layout work or daily inspection.
C. Compaction tests on embankments and flexible bases, depth tests on flexible bases and
pavements, and pressure tests on piping systems are required prior to final approval.
13.02.050 Acceptance and Maintenance of Improvements
A. Upon completion of installation and construction of all required public improvements, the
developer shall seek acceptance of all public improvements by the City. The City will may
consider aacceptance of the constructed public improvements only after the developer has
submitted record as‐built drawings including a statement signed by a registered Professional
Engineer that all improvements have been installed and constructed in accordance with this
Code and the submitted as‐built drawings.
B. The developer shall furnish to the City a written guarantee that all workmanship and materials
associated with public improvements shall be free of defects for a period of two (2) years from the
date of acceptance by the Development Engineer. A two (2) year maintenance bond in the
amount of 10% of the total construction cost of all workmanship and materials shall be submitted
to the City per the approved City form.
C. The developer shall make available all necessary materials to make the final tap or connection.
D. The City shall not repair, maintain, install, or provide any streets, public utilities or services in
any subdivision for which a Final Plat has not been approved and recorded, nor in which the
standards contained herein or referred to herein have not been complied with in full.
E. Public improvements constructed to a standard varying from City specifications but approved by
the City shall be accompanied by a maintenance agreement with a Property Owner’s Association
(or similar organization) for the proper and continuous operation, maintenance, and supervision
of such facilities. A copy of the agreement(s) providing for such shall be presented to the
Development Engineer and approved as to form by the City Attorney prior to recordation of a
Final Plat and shall be filed of record with the plat thereof.
13.02.060 Provision of Utilities
A. The City shall not supply water, wastewater, or electricity according to the standards of this
Chapter for any tract of land unless a plat has been approved and recorded for said tract of
landthat is not a legal lot, nor shall the City have any obligation to extend utility service to any
parcel created in violation of the requirements of this Code.
B. A connection to or tap into the City water system, electric system, or wastewater system shall not
be made without a permit or express prior written approval. The developer shall make available
all necessary materials to make the final tap or connection.
C. Temporary utility service may be provided according to the standards and procedures of the
utility provider and are not subject to the requirements of this Chapter.
Section 13.03 Utility Easements
A. Uniform and continuous public utility easements (P.U.E.) shall be provided along all street lot
lines at a minimum of 10 feet. If not dedicated by plat, the easement shall be granted at the time
Page 119 of 131
Page 4 of 8
of Site Development Plan or by separate instrument, at the discretion of the Development
Engineer. The City may consider approval of an alternative easement location other than along
the street lot line.
B. Alongside major collectors, arterials, and highways, the P.U.E. shall be a minimum of 15 feet.
Shade Trees shall not be planted within these easements, unless approved by the
DirectorDevelopment Engineer. In any P.U.E. with existing overhead electric lines, Shade Trees
are prohibited. Ornamental Trees are allowed within all P.U.E.s.
C. Utility easements may be required across parts of lots other than as described above, at the
discretion of the Development Engineer. If situated between lots, easements for water,
wastewater and storm sewer lines shall be at least 20 feet in width. Where the proposed
development adjoins an unplatted area, up to a 20‐foot easement may be required along the rear
of lots adjoining the unplatted area.
D. Where utility easements are not straight due to curved streets, a larger easement shall be
provided where needed for overhead electric, at the discretion of the Development Engineer.
E. Utility easements may be fenced if unlocked gates are provided to allow free movement of
excavating machines, maintenance equipment, and personnel throughout the full length of the
easement.
Section 13.04 Public Water Standards
All development shall be served with an adequate water supply and distribution systems for fire
protection and domestic use, unless otherwise specified. The developer shall be responsible for
providing an approved public water supply system, including but not limited to, water distribution
lines, fire hydrants, valves, water meter repeater pole and water towers, consistent with the City’s
Comprehensive Plan. All improvements shall be designed and constructed according to the City’s
Construction Standards and Specifications.
A. Where an approved public water collection main or outfall line is less than one‐half (1/2) mile
from the property boundary, connection to the public water system shall be required and public
water shall be installed throughout the development.
B. Extension of water utilities shall conform to the City’s adopted Utility Extension and
Improvement Policy, as amended.
C. The developer shall be responsible for the cost of extension and connection to the existing public
water system.
D. The water main pipe size for water distribution system improvements and extensions shall be a
minimum diameter of eight (8) inches. Water infrastructure shall be of sufficient size to furnish
adequate domestic water supply for fire protection in conformance with the City’s adopted Fire
Code, as amended. Fire hydrants shall be provided in accordance with the Construction Manual.
Properties in the ETJ that desire or require fire flow service from the City of Georgetown shall
first submit a petition for voluntary annexation, in accordance with Section 3.25 of this Code.
E. The design and construction of the components of the public water system shall comply with
regulations covering extension of public water systems adopted by the Texas Commission on
Environmental Quality (TCEQ). For development that is not served by a public water supply, the
developer shall provide to the Development Engineer proof of a safe and adequate water supply.
Page 120 of 131
Page 5 of 8
F. Where an approved public water collection main or outfall line is more than one‐half (1/2) mile
away from the property boundary, on‐site wells may be utilized; however, if the City’s Capital
Improvement Plan has scheduled the extension of a water collection main or outfall line to be
completed to a location point within one‐half mile away from the property boundary within five
(5) years from the date of the Preliminary Plat submittal, connection to the public water system is
required. In such instance, the subdivider shall be required to install a public water system and
shall bear the cost of connecting the subdivision to such existing water system.
G. Improvements required through the Water Services Master Plan shall be designed and installed
in accordance with Section 13.08 of this Code.
H. Subdivision variancesExceptions or alternatives to the requirements of this Section may be
considered in accordance with Section 3.22 of this Code.by the Development Engineer or their
designee.
Section 13.05 Public Wastewater Standards
All development, where desired or required, shall be served with an approved public wastewater
system, including but not limited to, wastewater lines, manholes, force mains, and lift stations,
consistent with the Comprehensive Plan. Properties in the ETJ that desire or require wastewater
service from the City of Georgetown shall first submit a petition for voluntary annexation, in
accordance with Section 3.25 of this Code. All improvements shall be designed and constructed
according to the City’s Construction Standards and Specifications.
A. Where an approved public wastewater collection main or outfall line is less than one‐half (1/2)
mile from the property boundary, connection to the public wastewater system shall be required
and a public wastewater collection system shall be installed throughout the development.
B. Extension of wastewater utilities shall conform to the City’s adopted Utility Extension and
Improvement Policy, as amended.
C. The developer shall be responsible for cost of extension and connection to the existing
wastewater collection system.
D. The wastewater gravity main pipe size for wastewater improvements shall be a minimum
diameter of eight (8) inches.
E. The design and construction of all wastewater systems shall comply with regulations covering
extension of public sanitary wastewater systems adopted by the Texas Commission on
Environmental Quality.
F. All wastewater systems shall be designed and constructed to operate on a gravity flow basis. In
extraordinary circumstances and with the approval of the Development Engineer, lots one (1)
acre and greater may design a low‐pressure, vacuum, or gravity flow system to minimize the
need for lift stations.
G. Where an approved wastewater collection main or outfall line is more than one‐half (1/2) mile
away from the property boundary, on‐site septic system(s) may be utilized; however, if the City’s
Capital Improvement Plan has scheduled the extension of a wastewater collection main or outfall
line to be completed to a location point within one‐half mile away from the property boundary
within five (5) years from the date of the Preliminary Plat submittal, connection to the public
water system is required. In such instance, the subdivider shall be required to install a public
Page 121 of 131
Page 6 of 8
wastewater collection system and shall bear the cost of connecting to such existing wastewater
collection system.
H. Improvements required through the Water Services Master Plan shall be designed and installed
in accordance with Section 13.08 of this Code.
I. Subdivision variancesExceptions or alternatives to the requirements of this Section may be
considered in accordance with Section 3.22 of this Code.by the Development Engineer or their
designee.
Section 13.06 Electric and Communication Standards
The City’s Electrical Engineer shall design the electrical system for all development, unless otherwise
authorized. Where permanent electric service is desired and/or improvements required, the electric
improvements shall be installed and maintained in accordance with the following standards:
A. For residential subdivisions, all electric distribution lines and individual service lines shall be
installed underground unless located within an alley or otherwise approved. If overhead lines
existed prior to underground installation, such poles, guy wires, and related structures shall be
removed following construction of the underground infrastructure.
B. For non‐residential and multi‐family development where no existing overhead infrastructure
exists, underground electric utility lines shall be required along the street and within the site.
Where existing overhead infrastructure is to be relocated, it shall be re‐installed underground
and the existing facilities shall be removed at the discretion of the Development Engineer..
C. Underground electric and communication service lines shall be located and installed according to
the Construction Manual.
D. Electric transformers and related equipment shall be mounted on pads at ground level. For non‐
residential development, such equipment shall be located outside of the street yard where
practical and preferably located behind the front façade of the primary building structure. Such
equipment shall be reasonably separated from pedestrian or vehicular access ways, shall have
approved driveway or all‐weather vehicular accessibility, shall not conflict with roadway sight
visibility, and shall be located outside of future right‐of‐way.
E. Screening of pad‐mounted transformers for non‐residential development shall consist of barrier
fencing or shrub plantings located no closer than three (3) feet from the transformer, except for
the entry side of the transformer, which shall have a minimum of 10 feet of unobstructed
clearance. The entry side of the transformer shall not face a public street unless located behind the
front façade of the primary building structure. The transformer pad shall be located with
adequate room for the required landscape screening to be installed consistent with these
provisions. Transformers in the Downtown Overlay are exempt from these requirements.
F. Once utility service lines have been installed underground, the installation of new above‐ground
lines in that location is prohibited, except in rare occasions approved by the Electrical Engineer..
G. The installation of public street lights, and connection of electric service thereto, shall be the
responsibility of the subdivider/developer as provided in Chapter 12 of this Code.
H. Installed overhead and underground electric service shall take into account Heritage and
Protected Trees when locating new service lines.
Page 122 of 131
Page 7 of 8
G.I. Exceptions or alternatives to the requirements of this Section may be considered by the
Development Engineer or their designee.
Section 13.07 Master Plan Infrastructure
The City’s Comprehensive Plan includes utility master plans for the water distribution, wastewater
collection and electric utility. Each master plan identifies future system improvements that are
necessary to meet or exceed treatment and transport requirements for the specific utility. The planning
horizon for the plan is up to 20 years in the future.
A. Construction of Master Plan Infrastructure
When a master plan requires the installation of regional infrastructure on a property, the developer
shall extend and construct such facilities at their own expense. When these facilities exceed the utility
needs for the specific development beyond the utility minimum size, the facility shall be considered
oversized. All necessary easements and/or rights‐of‐way for such infrastructure shall be dedicated at
no cost to the City.
B. Oversizing Cost Participation
1. The City may, at its sole discretion, participate with the subdivider in the cost of oversized
facilities based upon, but not limited to the following factors:
a) The approved utility budget for the current year;
b) The ability of the specific utility to fund any future costs;
c) The degree to which the project conforms to and accomplishes the 5‐year CIP priorities;
d) The degree to which the project accomplishes the utility Master Plan; and
e) The impact to system operations. Any cost participation contract shall be approved by the
City Council prior to approval of the Final Plat.
2. Cost participation shall be based upon the cost differential between the master plan line size
and the minimum line size required to serve the development, for eligible construction costs.
3. When the subdivider constructs line extensions included in the current 5‐year CIP, the
approved cost participation contract shall provide for the payment to be scheduled during the
same fiscal year as the CIP project that would have accomplished the line extension, and after
the date of notice of acceptance by the City.
4. The fees shall be calculated by the City based on information from the developer’s engineer,
using a methodology that apportions the developer’s planned usage (based upon the
minimum pipe size) to the available usage due to oversizing. The developer’s engineer shall
use the City’s approved water or wastewater master plan as a basis for calculating residential
flow per dwelling unit. Calculations for non‐residential units shall be calculated using the
latest edition of the “Design Criteria for Sewage Systems,” as produced by the Texas
Commission on Environmental Quality.
5. The calculation of cost participation shall be based on construction costs in effect at the time
the connection to the system (the “tap”) is made. All calculations shall be submitted to the
City for appropriate review, verification, and approval.
Page 123 of 131
Page 8 of 8
6. A cost participation contract is not a guarantee of capacity. Guarantee of capacity is achieved
through payment of impact fees.
C. Impact Fee Credits
When the subdivider constructs line extensions included in the 10‐year Capital Improvement Plan
(CIP), the subdivider may be eligible for an Impact Fee credit on the fee assessment for each lot in the
subdivision. Impact Fee credit shall be calculated based upon the number and size of service
connections and the allocation of costs in the most recent Impact Fee calculation, as amended.
Section 13.09 Subdivision Improvement Guarantee
In lieu of full construction of all public improvements prior to Final Plat recordation, a plat may be
recorded without acceptance of the required public improvements through the posting of financial
security. Financial Security shall be provided in an amount of at least 125 percent of the cost of the
required public improvements, as estimated by a licensed engineer and approved by the
Development Engineer. The Development Engineer has the discretion to reduce the percentage of the
financial security instrument based on the amount of the construction completed.
The financial instrument shall state the name of the development or subdivision, and shall list the
required improvements and estimate costs thereof. A plat shall not be recorded unless the subdivider
has provided the financial security in a form provided by the City and approved as to form and
legality by the City Attorney. No release of any security shall occur until the City has formally
accepted the improvement that is the subject of such security. The guarantee shall not expire. The
following methods are acceptable forms of financial security.
1. Performance Bond
A bond executed by a surety company licensed in the State of Texas and acceptable to the City of
Georgetown.
2. Letter of Credit
A letter of credit, in a form approved by the City, signed by a principal officer of a local bank, local
savings and loan association, or other financial institution, acceptable to the City, agreeing to pay to
the City of Georgetown on demand.
3. Trust Agreement
A deposit in a bank or trust company in the name of the City, and approved by the City, in a trust
account. Selection of the trustee shall be subject to approval by the City.
Section 13.10 Creation of Special Districts (unchanged)
13.10.020 Definitions
(moved to Chapter 16, Definitions)
Page 124 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding p ro p o s ed amend ments to Chap ter 16, Definitions . Jord an Mad d o x
ITEM SUMMARY:
Chap ter 16 is definitions and this is the firs t round o f definition review b y the Committee. There are 20-25
ad d itional terms that s taff is reviewing and will bring b ack at the Octo b er meeting. Nearly all of thes e
d efinitio ns p ertain to trans p o rtatio n-related terms s uc h as streets, c urbs, and d riveways. Although there are
s o me edits to exis ting terms , mo s t d efinitio ns pres ented here are new to the c ode.
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
ATTACHMENTS:
Description Type
UDC Chapter 16 Cover Memo
Page 125 of 131
Alley. See Street, Alley.
Alternative Parking Plan. A plan approved by the Director that allows for alternatives to the vehicular
parking, stacking, and loading requirements in Chapter 9 of this Code.
AASHTO. American Association of State Highway and Transportation Officials.
Average Daily Trip (ADT). The projected or counted amount of traffic traversing a street. Used often as a
modeled or calculated measurement of expected traffic generation for a development or neighborhood in
order to determine roadway adequacy.
Back-of-curb. The outside edge of an approved curb type not adjacent to a travel way. The basis of
measurement for paved width and curb basis within this Code.
Bicycle Lane. An on‐street defined travel lane for the exclusive use of bicycles.
Block Length. The length of a street between the intersection of said street and another street, unless
otherwise dictated by this Code, measured from the center point of two streets.
Bond. Instrument, including a bond, note, certificate of participation or other instrument evidencing a
proportionate interest in payments due to be paid by an issuer or other type of obligation that: (1) is issued
or incurred by an issuer under the issuer’s borrowing power; without regard to whether it is subject to
annual appropriation; and (2) is represented by an instrument issued in bearer or registered form or is not
represented by an instrument but the transfer of which is registered on books maintained for that purpose
by or on behalf of the issuer.
Bond. Any form of security including a cash deposit, surety bond, property, or instrument of credit in an
amount and form satisfactory to the City Attorney.
Comprehensive Plan Roadway or Thoroughfare. A street or trail identified in the City’s Overall
Transportation Plan as an existing or future roadway needed to accommodate the current and future
transportation needs of the community. Includes Major Collector, Minor Arterial, Major Arterial, and any
identified public trail or railway.
Connectivity Ratio. A numerical calculation determined by the number and linkage characteristics of
streets within a subdivision.
Consent resolution. A resolution approved by the City Council setting forth terms of its consent to
creation of a district.
Construction Specifications and Standards Manual. Referred to often in this Code as the
“Construction Manual,” this City of Georgetown document includes standard details and specifications for
the construction of public improvements.
Cul-de-sac. See Street Cul‐de‐sac.
Curb. A defined concrete edge of a street, which may or may not include a stormwater gutter.
Curb, Mountable. Also described as a rollover or roll‐up curb, a Mountable Curb is a street border that has
sloping faces that allow vehicles to easily encroach upon on them and is not considered a vehicular barrier
curb. Mountable Curbs are considered a combined curb type that is the primary component of a stormwater
conveyance system that carries alongside a roadway.
Curb, Ribbon. Also described as a lay‐down curb, a Ribbon Curb is a street border that is generally flat and
is not considered a vehicular barrier curb. Typically associated with sheet‐flow or open ditch stormwater
Page 126 of 131
conveyance and does not carry stormwater laterally alongside a roadway.
Curb, Vertical. Also described as a stand‐up curb or barrier curb, a Vertical Curb is a street border that is
generally accepted as a safety barrier separating vehicular traffic from a building, sidewalk, or other area
where vehicles are not desired. Typically paired with a defined stormwater conveyance gutter that carries
stormwater laterally alongside a roadway.
Curb Basis. The dimensional area between the back of a street curb and the outside of the right‐of‐way.
Curb Stop. A concrete barrier secured to a parking stall to stop the tire of a moving vehicle.
Cut-Out Parking. A designated street parking lane with defining characteristics separating it from the
primary travel way of the street. Cut‐out areas are typically seen in residential neighborhoods and in the
downtown area. Graphical design of cut‐out parking can be found in the Chapter 12 Technical Appendix.
Certificate of convenience and necessity (CCN). A permit issued by the Texas Commission on
Environmental Quality (“TCEQ”) authorizing a specified utility to be the retail water or sewer service
provider in a specified area.
City Council. City Council of the City of Georgetown.
Consent agreement. An agreement between the City and owners and developers of land in a proposed
district which, if agreed to, shall be attached to the consent resolution adopted by the City Council.
Driveway, Non-Residential. A driveway serving typically non‐residential development, including multi‐
family and townhouse uses.
Driveway, Residential. A driveway serving single‐ and two‐family uses.
Driveway. A private roadway vehicular travel way providing access for vehicles to a parking space,
garage, dwelling, or other structure. Does not include Private Street and a site’s utilities and street lights do
not conform to the standard street assignments and locations
Electrical Engineer. The person designated by the City’s electric utility to make decisions regarding
placement, design, procedures, and other authorized determinations regarding electrical public
improvements.
Existing Street Connection. A public street connection to an existing public street that ultimately
connects in two or more locations to a Major Street.
Extraterritorial jurisdiction (ETJ). UThe unincorporated area, not part of any other municipality, which
is outside of and contiguous to the corporate limits of the City of Georgetown generally extending two miles
from the City limit, excluding other incorporated municipalities and their ETJ, in which the City has the
authority to annex property, as definedetermined and established in accordance with Chapter 42 of the Local
Government Code.
Future Street Connection. A public street stub to an adjacent property that will not immediately connect
to a public street, and the ultimate connection is dependent upon the development of the adjacent property
Impact Fee. A user fee charged for connection to the public utility system.
Internal Roadway. A street that is entirely within a subdivision but not located along the boundary. Does
not constitute or equal a Perimeter Street.
Level of Service (LOS). A qualitative assessment of a roadʹs operating conditions, indicating capacity per
unit of demand a street based on and related to the operational characteristics of the facility.
Median. A raised or depressed curbed division of travel lanes. Does not include a “flush” median, which
Page 127 of 131
acts only as a painted division of travel lanes. May be of a pervious or impervious surface but is typically
covered with grass, landscaping, trees and may contain pedestrian facilities.
Multi-Modal. The availability of multiple modes of transportation within a system or corridor, which may
include but not be limited to, vehicles, pedestrians, cyclists, transit
Numbered County Road. A public roadway within the jurisdiction of a county which contains a
numbered designation. For example: CR 140.
Oversized Utility Line. A utility facility that is described in the City’s water or electric master plan,
necessary to accommodate current and future users. May be constructed by various parties with potential
cost‐sharing partnership opportunities.
Paved Surface. An area surfaced with single or multiple‐course surface treatment, asphalt, concrete,
pervious concrete, or grasscrete pavement constructed on a base course or similar all‐ weather surface,. Does
not includinge gravel, grass, stones, decomposed granite, or similar unpaved materials.
Paved Width. The dimensional width between the back of a street curb to the back of a curb across travel
lanes. Does not include a median.
Plat Waiver. An exception to specifically‐defined regulations of this Code to address difficulties in
developing a property for subdivision. A Plat Waiver does not constitute a Variance, as that term is defined
in this Code, and only applies to certain provisions relating to subdividing a lot or parcel.
Property Owner’s Association. An entity established to represent the interests of property owners within
a defined area and may include maintenance and enforcement responsibilities.
Reserve Strip. A narrow strip of property usually separating a parcel of land from a roadway or utility line
easement, that is characterized by limited depth, which will not support development and is intended to
may prevents access to the a roadway or utility easement from adjacent property. and which is prohibited by
these regulations unless their control is given to the City.
Right-of-Way Flare. A diagonal cut‐back between two public street rights‐of‐way specified in Chapter 12.
Residential Rural/Estate Subdivision. A subdivision that is zoned either AG (Agriculture) or RE
(Residential Estate) if within the City Limits or a subdivision in the extraterritorial jurisdiction (ETJ) that is
platted for single‐family residential development with lots of at least one acre in size.
Shared-Use Path. A paved pathway accommodating pedestrians and bicyclists, meeting accessibility
standards. Differentiated from a “hike‐and‐bike trail” which may be a pervious material and not accessible.
Sidewalk Clear Zone. The dimensional area between the curb or edge of pavement (where no curb exists)
and a pedestrian facility such as a sidewalk, trail or pedestrian accessway. The clear zone is established to
protect pedestrians from vehicular movements, as determined by speed and street classification.
Sidewalk Fund. A fund established to accept and distribute revenue in accordance with the provisions of
this Code for the purpose of constructing public sidewalks and/or trails.
Sight Triangle. The triangular area formed by an invisible diagonal line at the corner of either two
intersecting street right‐of‐way lines, the edge of street lines, the edge of a driveway or combination of two
thereof, as specified in Chapter 12. The Sight Triangle exists to prevent sight obstruction for motor vehicles,
pedestrians, etc. May also be referred to as “street visibility triangle” or “sight distance triangle”
Site Development Plan. A detailed site layout plan containing sufficient information to evaluate the land
use, construction plans, and architectural harmony of the proposed development including compatibility of
Page 128 of 131
the development with nearby areas. A Site Plan shall follow the requirements and approval procedures of
Section 3.09 of this Code and the Development Manual.
Special District. A municipal utility district (“MUD”), water control and improvement district (“WCID”),
frlesh water supply district (“FWSD”), or similar political subdivision created to provide water, sewer or
drainage utility services, roads, or other services allowed by law to a specified area, pursuant to Article III,
Section 52, and/or Article XVI, Section 59, of the Texas Constitution.
Strategic Partnership Agreement. An agreement between the City and a special district addressing the
relationship between the City and the district, including limited purpose annexation of commercial areas
and other matters pursuant to Section 43.0751 of the Local Government Code.
Street Centerline. A line bisecting a street that is parallel to the edge of pavement.
Street Cul-de-Sac. A street or series of connected streets that has a single approved vehicular access point.
having one end open to vehicular traffic and having one end terminated by an approved turnabout.
Street Landing. The area of an intersection where the grades of the respective streets need to be sufficiently
flat to accommodate either an accessible crosswalk.
Street Tree. See Tree, Street
Street, Alley. An alley is a passageway designed primarily to provide access to or from the rear or side of
property otherwise abutting on a public street.
Street, Arterial. A street designed to carry large volumes of local and regional traffic into or out of the city
which provide for efficient vehicular movement between distant locations, decreasing. traffic on local and
collector‐level streets. Separated in this Code by Minor and Major classifications, the specific characteristics
and average daily trip ranges of which each can be found in Section 12.03 Chapter 12 of this Code.
Street, Collector. A street that connects and distributes traffic between Arterial Streets and Local Streets
providing access and movement between neighborhoods, parks, schools, retail areas and the arterial street
system.. A collector street maycan serve both residential and commercial development, depending on the
type of collector and average daily traffic volume. Separated in this Code by Residential, Neighborhood and
Major classifications, the specific characteristics and average daily trip ranges of which each can be found in
Section 12.03 of Chapter 12 of this Code. See also “Street”, “Residential Collector”, and “Street, Major
Collector”
Street, Context Sensitive. A street constructed to the alternative cross‐sections depicted in the Overall
Transportation Plan to allow for design characteristics compatible with adjacent development.
Street, FreeHighway. A controlled‐access divided street or highway that is intended to move high traffic
volumes over long distances and serve as primary routes throughout the region. Includes the term
“highwayfreeway” and “expressway.”.
Street, Half. Streets with half the width of the required right‐of‐way on the bounding edge of a tract being
subdivided.
Street, Loaded. A street that allows for vehicular access driveways.
Street, Residential or Residential Local. A street that serves a limited number of residential dwelling
units and is expected to carry less than 800 vehicles per day. Alleys are permitted in conjunction with
Residential Streets. On‐street parking is provided on both sides within the standard pavement width of the
street.
Street, Local – Downtown. A street located within the Downtown Overlay District that carries a Local
Page 129 of 131
Street cross‐section design. The characteristics of this street can be found in Chapter 12 of this Code and in
the Downtown Master Plan, May be designated as a collector or arterial in functionality.
Street, Local (tree alternative). A Local Street designed to the alternative cross‐section identified in this
Code that accommodates Street Trees within the right‐of‐way.
Street, Neighborhood. A street that primarily serves the local traffic needs a subdivision, neighborhood or
development, with relatively low traffic counts and lower speeds. Street types include Residential Lanes,
Local Streets, Residential Collectors and Neighborhood Collectors.
Street, Perimeter. A street directly abutting a development or subdivision, whether the street is external
to, partially or wholly within the boundary.
Street, Rural Residential Rural/Estate. A street serving Rural Residential Rural/Estate Subdivisions
that may include roadside ditches in lieu of curb and gutter and other generally rural roadway features.
Rural streets include residential and collector classifications, as specified in Section 13.04.
Street, Stub. A non‐permanent, dead‐end street intended to be extended in conjunction with the
subdivision and development of adjacent land.
Street. An improved surface used for the transport of automobiles and other motor vehicles from one
location to another. Includes the term “road” and “roadway”
Subdivision Variance. See Variance, Subdivision.
Tandem Parking Space. A paired parking space accommodating two or more vehicles that are parked
directly behind each other that is only accessed by passing through another parking space from a street,
lane, drive aisle or driveway.
Total Street Connections. The total number of street connections to the ultimate street network, including
connections to existing public streets and future stubs to adjacent properties.
Transportation Improvement Program (TIP). Staged, multi‐year program of transportation projects
consistent with the Overall Transportation Plan.
Tree, Street. An approved Shade Tree planted within the right‐of‐way in accordance with this Code.
TxDOT. Texas Department of Transportation
Unloaded Street. A street where vehicular access driveways are outright prohibited or provisionally
allowed. Includes Neighborhood Collectors, Major Collectors, Arterials and Highways.
Variance, Zoning. A grant of relief to a person from the Zoning requirements of this Code when specific
application thereof would result in unnecessary hardship, as determined by the Zoning Board of
Adjustment. A Zoning Vvariance, therefore, permits construction or development in a manner otherwise
prohibited by this Code ordinance. Does not constitute nor equal a Waiver of any kind Subdivision Variance.
Variance, Subdivision. A grant of relief from the Subdivision requirements of this Code, as determined by
the Planning and Zoning Commission. Subdivision Variances may be considered to the provisions only as
specified within this Cpde. A Subdivision Variance permits construction or development in a matter
otherwise prohibited by this Code. Does not constitute nor equal a Zoning Variance.
Waiver. See “Plat Waiver”
WalkwayPedestrian Accessway. Walkways Pedestrian Accessways are strips or sections of concrete or
stone not typically located adjacent to vehicle roadways, which provide pedestrian access to or through
property. This area must be kept free of obstructions, both temporary and permanent.
Page 130 of 131
City of Georgetown, Texas
Unified Development Code Advisory Committee
September 14, 2016
SUBJECT:
Disc ussion regarding next s teps in the proc es s . S o fia Nels o n
ITEM SUMMARY:
Staff will disc us s the next s teps in the proc es s regarding p ublic no tic e, committee vo te, Co uncil and
Planning and Zo ning Commission, etc .
FINANCIAL IMPACT:
.
SUBMITTED BY:
Jordan Maddo x
Page 131 of 131