Browse
Search
ORC agenda 080515
OrangeCountyNC
>
Advisory Boards and Commissions - Active
>
Orange County Planning Board
>
Ordinance Review Committee
>
Agendas
>
2015
>
ORC agenda 080515
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/29/2018 11:53:18 AM
Creation date
8/29/2018 11:29:59 AM
Metadata
Fields
Template:
BOCC
Date
8/5/2015
Meeting Type
Regular Meeting
Document Type
Agenda
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
67
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
Article 2: Procedures <br /> Section 2.8: Zoning Atlas and Unified Development Ordinance Amendments <br /> <br /> <br />Orange County, North Carolina – Unified Development Ordinance Page 2-27 <br /> <br />SECTION 2.8: ZONING ATLAS AND UNIFIED <br />DEVELOPMENT ORDINANCE AMENDMENTS <br />2.8.1 Review and Approval Flow Chart <br />The review and approval process for a Zoning Atlas and Unified <br />Development Ordinance Amendment is shown in the <br />procedure’s flowchart. <br />2.8.2 Amendment Initiation <br />(A) An amendment to this Ordinance or the Zoning Atlas <br />may be initiated by: <br />(1) The Board of County Commissioners on its own <br />motion; <br />(2) The Planning Board; <br />(3) Application, by any person or agency, or <br />(4) The Planning Director. <br />(B) If a request for consideration of an amendment proposal <br />is submitted directly to the Board of County <br />Commissioners, said Board may decline to consider the <br />request or may refer the amendment proposal to the <br />Planning Director for preparation of an amendment <br />application. <br />(C) Once initiated, all amendments shall be referred to the <br />Planning Board.32 <br />2.8.3 Contents of Application <br />Applications shall contain the following: <br />(A) For amendments to the Zoning Atlas: <br />(1) A map at a legible scale showing the land which would be covered by the <br />proposed amendment, and <br />(2) A legal description of the land. <br />(B) For amendments to the Unified Development Ordinance text: <br />(1) A copy of the existing text provision(s) which the applicant proposes for <br />amendment, and <br />(2) A written statement which describes in detail the changes the applicant proposes <br />to make. <br />(C) The alleged error in the Zoning Atlas and/or Unified Development Ordinance text that <br />would be corrected by the proposed amendment with a detailed explanation of such error <br /> <br />32 These proposed revisions here and on subsequent pages incorporate the discussion the Planning Board had in <br />October, November, and December 2014 and which the BOCC discussed on May 12, 2015. The cadence of the <br />review process would be revised to have the Planning Board make its recommendation prior to the public hearing <br />for legislative items. Notices would be mailed to nearby property owners and a sign(s) would be posted; this <br />revision will notify nearby property owners of potential changes much earlier in the process. Although the <br />Planning Board meeting would not be an official public hearing, the public could address the Planning Board (the <br />existing requirement for written comments only is not proposed to continue in this revised process) and the <br />Planning Board can take all public comments into consideration when making its recommendation. <br />Decision by the BOCC <br />Staff Assessment <br />and Analysis <br />Planning Board Review <br />and Recommendation <br />Schedule/Advertise <br />Public Hearing and <br />Mail Required <br />Notifications <br />Hold Public Hearing <br />and Receive Public <br />Comments <br />Zoning Atlas and <br />UDO Amendments <br />Application <br />Submittal <br />See proposed revised <br />flow chart on next page <br />25
The URL can be used to link to this page
Your browser does not support the video tag.