Browse
Search
5-1-24 PB Agenda Packet
OrangeCountyNC
>
Advisory Boards and Commissions - Active
>
Orange County Planning Board
>
Agendas
>
2024
>
5-1-24 PB Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/25/2024 7:51:28 PM
Creation date
4/25/2024 7:49:45 PM
Metadata
Fields
Template:
BOCC
Date
5/1/2024
Meeting Type
Regular Meeting
Document Type
Agenda
Document Relationships
5_1_24 Planning Board Minutes
(Message)
Path:
\Advisory Boards and Commissions - Active\Orange County Planning Board\Minutes\2024
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
131
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
(2) Stormwater Management Plans (SMPs) as necessary to be approved by the <br />Erosion Control Officer prior to the issuance of a Zoning Compliance Permit, and <br />(3) Building construction plans to be approved by the Building Official prior to <br />issuance of a building permit. <br />2.5.3 Plan Specifications <br />Each site plan shall be drawn at a scale adequate to show required detail and shall contain the <br />following information: <br />(A) The boundary of the lot(s) to be developed labeled with bearings and distances; <br />(B) The name, address, and phone number of the applicant and the property owner; <br />(C) Name of project, vicinity map, north arrow, scale, tax map reference number, date of plan <br />preparation, and subsequent revision dates; <br />(D) Zoning of the property to be developed and all adjacent zoning and existing adjacent land <br />uses; <br />(E) Adjacent right-of-way widths with road names and numbers; <br />(F) A development summary including total acres, proposed use(s), total building square <br />footage, required and proposed parking spaces. <br />(G) Demonstrated compliance with all applicable performance standards contained in Articles <br />3, 4, 5, and 6 of this Ordinance; <br />(H) Maximum and proposed impervious surface and required stream buffers as detailed in <br />Sections 4.2 and 6.12 of this Ordinance; <br />(I) Estimated traffic generated by the proposed development in trips per day. If the estimate <br />exceeds 800 trips per day, a traffic impact study must be submitted in accordance with <br />Section 6.17; <br />(J) Front, side, and rear building setbacks as required by Articles 3 and 5 of this Ordinance; <br />(K) Location of all proposed buildings and structures labeled with floor area, building height <br />and function, and proposed finished floor elevation; <br />(L) Vehicular use areas including existing and proposed streets and access drives, off street <br />parking and loading to comply with Section 6.9 of this Ordinance, and entry/exit points of <br />adjacent parcels; <br />(M) Overhead and underground utilities with accompanying easements and storm drainage <br />facilities/easements (including septic tanks and wastewater disposal fields, wells, fire <br />hydrants, irrigation, and security lights); <br />(N) Solid waste disposal facilities; <br />(O) All proposed free-standing and wall-mounted signs. Signs must comply with Section 6.12 <br />of this Ordinance; <br />(P) A landscape plan demonstrating compliance with Section 6.8 of this Ordinance; <br />(Q) For all developments other than those regulated by the NC Residential Code single- <br />family residential, and duplexes, existing contour lines (dashed) and proposed contours <br />(solid) at 5-foot intervals with 10-foot contours bold. Where site conditions warrant, 2-foot <br />contours may be required; <br />(R) Retaining walls, tree wells, or rip rap as part of the grading plan; <br />(S) Streams, ponds, drainage ditches, swamps, floodway and floodplain boundaries; <br />(T) Phase lines and numbers if the development is to be phased; <br />109
The URL can be used to link to this page
Your browser does not support the video tag.