Browse
Search
Agenda - 03-08-2018 8-g - Comprehensive Plan and Unified Development Ordinance (UDO) Amendment Outline and Schedule – Four UDO Text Amendments
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2010's
>
2018
>
Agenda - 03-08-2018 Regular Meeting
>
Agenda - 03-08-2018 8-g - Comprehensive Plan and Unified Development Ordinance (UDO) Amendment Outline and Schedule – Four UDO Text Amendments
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/2/2018 2:44:00 PM
Creation date
3/2/2018 3:06:55 PM
Metadata
Fields
Template:
BOCC
Date
3/8/2018
Meeting Type
Regular Meeting
Document Type
Agenda
Agenda Item
8-g
Document Relationships
Agenda - 03-08-2018 Regular Board Meeting
(Message)
Path:
\Board of County Commissioners\BOCC Agendas\2010's\2018\Agenda - 03-08-2018 Regular Meeting
Minutes 03-08-2018
(Message)
Path:
\Board of County Commissioners\Minutes - Approved\2010's\2018
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
19
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Form Revised 09-29-16 <br /> <br />B. RATIONALE <br />1. Purpose/Mission <br />In accordance with the provisions of Section 2.8 Zoning Atlas and Unified <br />Development Ordinance Amendments of the UDO, the Planning Director has <br />initiated text amendments to the UDO to amend the timeframe for holding of <br />neighborhood information meetings. The purpose of the amendment is to eliminate <br />confusion on the required time frame for holding neighborhood information meetings <br />and ensure uniformity within the UDO. <br /> <br />2. Analysis <br />As required under Section 2.8.5 of the UDO, the Planning Director is required to: <br />‘cause an analysis to be made of the application and, based upon that analysis, <br />prepare a recommendation for consideration by the Planning Board and the Board of <br />County Commissioners’. <br />Neighborhood Information Meetings (NIM) are typically required for several types of <br />projects (i.e. special use permits, conditional use districts/conditional zoning <br />applications, major subdivision concept plan, governmental land uses, etc.) and are <br />typically required to occur before formal review commences (i.e. staff, Planning <br />Board, or BOCC) <br />A synopsis of these requirements is as follows: <br />1. Section 2.7.5 Special Use Permits (Class A or B not including <br />telecommunication facilities): NIM held a minimum of 45 days prior to public <br />hearing. <br />2. Section 5.10.8 (B) (2) Telecommunication Facilities: <br />a. For Class A permit applications (i.e. 200 ft. and taller) a balloon test is <br />held a minimum of 11 weeks (77 days) prior to the public hearing. Staff <br />attends the balloon test and conducts the NIM on-site. <br />b. For Class B permit applications (i.e. 76ft to 199.9 ft.) a balloon test is <br />held a minimum of 6 weeks (42 days) prior to the public hearing. Staff <br />attends the balloon test and conducts the NIM on-site. <br />3. Section 2.9.1 (D) Conditional Use District (CUD): NIM held a minimum of 45 <br />days prior to the public hearing. <br />4. Section 2.9.2 (D) Conditional Zoning District (CZD): NIM held a minimum of <br />14 days prior to the public hearing. <br />5. Section 2.14.2 (B) Minor Subdivisions. For a minor subdivision utilizing the <br />flexible development option with more than 5 lots, a NIM is required once the <br />concept application is accepted for review (i.e. after determined to be <br />complete) by staff. <br />The UDO does not establish a specific timeline as to when this meeting is <br />held. Standard practice has been the NIM is held before staff takes formal <br />action on the application. <br />6. Section 2.15.2 (D) Major subdivision: NIM held a minimum of 14 days prior to <br />8
The URL can be used to link to this page
Your browser does not support the video tag.