Browse
Search
OCPB agenda 040616
OrangeCountyNC
>
Advisory Boards and Commissions - Active
>
Orange County Planning Board
>
Agendas
>
2016
>
OCPB agenda 040616
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/8/2018 11:47:52 AM
Creation date
3/8/2018 11:45:12 AM
Metadata
Fields
Template:
BOCC
Date
4/6/2016
Meeting Type
Regular Meeting
Document Type
Agenda
Document Relationships
OCPB minutes 040616
(Message)
Path:
\Advisory Boards and Commissions - Active\Orange County Planning Board\Minutes\2016
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
65
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 6: Development Standards <br /> Section 6.12: Signs <br /> <br /> <br />Orange County, North Carolina – Unified Development Ordinance Page 6-89 <br /> <br />cumulative allowable sign area limit of 64 square feet per parcel and shall abide <br />by the restrictions contained in Section 6.12.11 (B) of the Ordinance <br />(1)(2) Freestanding or Ground Monument SignsOn-Premise Signs <br />(2) These signs sShall comply with all state and county building codes and <br />the National Electric Code. Clearance of signs is required from high <br />voltage power lines and signs shall be located in such a way that they <br />will maintain horizontal and vertical clearance of all overhead electrical <br />conductors in accordance with the National Electric Code specifications, <br />provided that no sign shall be installed closer than ten feet horizontally or <br />vertically from any conductor or public utility guy wire. 32 <br />(3) On-premise commercial signs shall be permitted within the following zoning <br />districts: LC-1, NC-2, CC-3, GC-4, EC-5, OI, EI, I-1, I-2, I-3, AS, MPD-CZ, MHP- <br />CZ and all of the Economic Development zoning districts. <br />(a) Required Setbacks: <br />(i) All on-premise commercial signsSigns shall be setback ten feet <br />from the front, side, and rear propertyall property lines or the <br />edge of any existing or projected street right-of-way line <br />whichever is greater. <br />(ii) Signs greater than 32 square feet in area, as allowed herein, <br />shall be setback an additional 10 feet. <br />(4)(iii) In cases where a property abuts a residential zoned parcel of <br />property, the side or rear yard setback requirement shall be <br />doubled. <br />(5) Number of Signs Permitted <br />(b) Number of Signs Permitted: <br />(a)(i) One on-premiseOne freestanding sign commercial sign shall be <br />permitted per parcel. However, oneAn additional on-premise <br />commercial sign may be permitted for parcels with frontage on <br />more than one publicly maintained right-of-way in accordance <br />with the provisions of this Section. <br />(b)(ii) Under no circumstances shallNo more than one three- <br />dimensional sign shall be permitted on-site. <br />(c)(iii) For multi-tenant buildings and/or sites permitted as a conditional <br />use or conditional zoning district, additional on-premise <br />commercial signs or sign area may shall be permitted by the <br />Board of County Commissioners with the approval of a master <br />sign plan. <br />(6)(c) Height of Signs: <br />(a)(i) Pole signsFreestanding signs shall be limited to a height of 24 <br />feet with a mandatory ground clearance of eight feet from the <br />normal or finished grade elevation of the property at the base of <br />the sign <br />(b)(ii) Ground signsGround monument signs shall not exceed six feet <br />in height from the normal or finished grade elevation of the <br />property at the base of the sign <br />(7)(d) The allowable area for on-premise commercial signs shall be determined <br />as followsAllowable sign area: <br /> <br />32 Moved to Section 6.12.3 of the existing sign ordinance. <br /> 43
The URL can be used to link to this page
Your browser does not support the video tag.