Browse
Search
Agenda 5-a - Unified Development Ordinance (UDO) and Zoning Atlas Amendments – Modification of Neighborhood Information Meeting (NIM) Requirements
OrangeCountyNC
>
BOCC Archives
>
Agendas
>
Agendas
>
2018
>
Agenda - 06-05-2018
>
Agenda 5-a - Unified Development Ordinance (UDO) and Zoning Atlas Amendments – Modification of Neighborhood Information Meeting (NIM) Requirements
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/31/2018 4:36:48 PM
Creation date
5/31/2018 4:28:26 PM
Metadata
Fields
Template:
BOCC
Date
6/5/2018
Meeting Type
Regular Meeting
Document Type
Agenda
Agenda Item
5-a
Document Relationships
Agenda - 06-05-2018 Regular Board Meeting
(Message)
Path:
\BOCC Archives\Agendas\Agendas\2018\Agenda - 06-05-2018
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
25
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
a. For Class A permit applications (i.e. 200 ft. and taller) a balloon test is held a <br />minimum of 11 weeks (77 days) prior to the public hearing. Staff attends the <br />balloon test and conducts the NIM on-site. <br />STAFF COMMENT: This request would be reviewed by the BOCC during a <br />previously advertised public hearing with a recommendation made by the <br />Planning Board. The Planning Board typically reviews the item anywhere <br />from 30 to 40 days prior to the anticipated public hearing. <br />b. For Class B permit applications (i.e. 76ft to 199.9 ft.) a balloon test is held a <br />minimum of 6 weeks (42 days) prior to the public hearing. Staff attends the <br />balloon test and conducts the NIM on-site. <br />STAFF COMMENT: This request would be reviewed by the Board of <br />Adjustment during a previously advertised public hearing with no <br />recommendation/review required by the Planning Board. <br />3. Section 2.9.1 (D) Conditional Use District (CUD): NIM held a minimum of 45 days prior to <br />the public hearing. <br />4. Section 2.9.2 (D) Conditional Zoning District (CZD): NIM held a minimum of 14 days <br />prior to the public hearing. <br />5. 2.14.2 (B) Minor Subdivisions. For a minor subdivision utilizing the flexible development <br />option with more than 5 lots, a NIM is required once the concept application is accepted <br />for review (i.e. after determined to be complete) by staff. <br />STAFF COMMENT: Minor subdivisions utilizing the flexible development <br />option are acted upon by staff with no review made by either the Planning <br />Board or BOCC. <br />The UDO does not establish a specific timeline as to when this meeting is held. Standard <br />practice has been the NIM is held after the application is accepted but before staff takes <br />formal action on the application. <br />6. 2.15.2 (D) Major subdivision: NIM held a minimum of 14 days prior to the review of the <br />Concept Plan by the Planning Board. <br />7. Section 2.24.2 (A) Government Uses: Has to occur prior to the formal submittal of the <br />Zoning Compliance Permit/Site Plan application to the Planning Department for <br />processing. <br />Current regulations typically require a NIM to be held 45 days before a public hearing. For <br />those projects requiring review/recommendation by the Planning Board, this translates to a NIM <br />being held within a few days/a week before the Planning Board meeting where the project is <br />slated for review. Staff has heard from some members of the public, Planning Board members, <br />and elected officials that NIMs are typically occurring too close to the Planning Board meeting to <br />be of any real benefit. <br /> <br />To address these issues staff is recommending the following: <br />a. NIMS for: <br />• Non-telecommunication facility Class A Special Use Permits, <br />• CUD, and <br />• CZD applications <br />2
The URL can be used to link to this page
Your browser does not support the video tag.