Browse
Search
Agenda - 10-15-2024; 8-a - Minutes
OrangeCountyNC
>
BOCC Archives
>
Agendas
>
Agendas
>
2024
>
Agenda - 10-15-2024 Business Meeting
>
Agenda - 10-15-2024; 8-a - Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/10/2024 1:32:23 PM
Creation date
10/10/2024 11:42:38 AM
Metadata
Fields
Template:
BOCC
Date
10/15/2024
Meeting Type
Business
Document Type
Agenda
Agenda Item
8-a
Document Relationships
Agenda for October 15, 2024 BOCC Meeting
(Message)
Path:
\BOCC Archives\Agendas\Agendas\2024\Agenda - 10-15-2024 Business Meeting
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
127
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
3 <br /> 1 b. The current land use designation of the subject property consistent with the <br /> 2 Orange County Comprehensive Plan and Future Land Use Map (FLUM), which <br /> 3 can be accessed utilizing the embedded links; <br /> 4 c. The alleged error in the Zoning Atlas (if any) that will be corrected by the <br /> 5 proposed request; <br /> 6 d. The changed, or changing, conditions (if any) that makes the proposed <br /> 7 amendment reasonable and necessary to promote the public health, safety, and <br /> 8 general welfare; and <br /> 9 e. How the proposed amendment is consistent with, or carries out the intent and <br /> 10 purpose of, the Orange County Comprehensive Plan. <br /> 11 4. Plan review fee(s) consistent with the adopted Orange County Fee Schedule. <br /> 12 <br /> 13 Basic Review Process: A conventional district rezoning application requires submission of a <br /> 14 detailed area map and other documents, in accordance with Section 2.8.3 of the Unified <br /> 15 Development Ordinance (UDO). A site-specific plan is not required for conventional rezoning <br /> 16 applications and conditions cannot be applied to an approval action. The typical cadence for the <br /> 17 review is as follows: <br /> 18 • FIRST ACTION — Submission of an application with required supporting documents <br /> 19 by the property owner. <br /> 20 STAFF COMMENT. The applicant submitted an application and documents on <br /> 21 April 19, 2024, Attachment 1. <br /> 22 • SECOND ACTION — Staff holds a Development Advisory Committee (DAC) Meeting. <br /> 23 STAFF COMMENT. The Development Advisory Committee Meeting was held on <br /> 24 May 16, 2024, at 9:30 a.m., via Microsoft Teams. Comments received from this <br /> 25 review are available in Attachment 4. <br /> 26 • THIRD ACTION — The Planning Board reviews the application at a regular meeting <br /> 27 and makes a recommendation to the BOCC. <br /> 28 STAFF COMMENT. The Planning Board reviewed this application at its regular <br /> 29 meeting on August 7, 2024. <br /> 30 • FOURTH ACTION — The BOCC receives the Planning Board and staff <br /> 31 recommendations at an advertised public hearing and makes a decision on the <br /> 32 application. <br /> 33 STAFF COMMENT: The public hearing is scheduled for September 5, 2024. <br /> 34 <br /> 35 Public Notification: In accordance with Section 2.8.7 of the UDO, notices of the Public Hearing <br /> 36 were mailed via first class mail to property owners within 1,000 feet of the subject parcel. These <br /> 37 notices were mailed on August 22, 2024, 14 days before the meeting. Staff also posted the <br /> 38 subject parcel with signs on August 22, 2024, 14 days before the meeting. See Attachment 3 for <br /> 39 the notification materials. <br /> 40 Planning Board Recommendation: The Planning Board reviewed the proposed amendments at <br /> 41 its August 7, 2024 regular meeting. At this meeting the Board voted unanimously to recommend <br /> 42 approval of the Statement of Consistency (Attachment 6) and the proposed Ordinance <br /> 43 (Attachment 7). <br />
The URL can be used to link to this page
Your browser does not support the video tag.