Browse
Search
Agenda - 12-15-2020; 5-b - Zoning Atlas Amendment - Master Plan Development Conditional Zoning District (MPD-CZ) for Efland Station (formerly Beaver Crossing)
OrangeCountyNC
>
BOCC Archives
>
Agendas
>
Agendas
>
2020
>
Agenda - 12-15-20 Virtual Business Meeting
>
Agenda - 12-15-2020; 5-b - Zoning Atlas Amendment - Master Plan Development Conditional Zoning District (MPD-CZ) for Efland Station (formerly Beaver Crossing)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/10/2020 3:19:39 PM
Creation date
12/10/2020 2:49:47 PM
Metadata
Fields
Template:
BOCC
Date
12/15/2020
Meeting Type
Business
Document Type
Agenda
Agenda Item
5-b
Document Relationships
Agenda 12-15-2020 Virtual Business Meeting
(Message)
Path:
\BOCC Archives\Agendas\Agendas\2020\Agenda - 12-15-20 Virtual Business Meeting
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
204
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
32 <br /> approximately 500,000 sq.ft. of building area/land uses (Exhibit F). <br /> The FAR either needs to be: <br /> • Modified to be consistent with the building square footage <br /> utilized in the development of the TIA, <br /> • The TIA need to be modified to document traffic impacts <br /> anticipated for the square footage of proposed building <br /> area based on a FAR of .65, or <br /> • A condition needs to be recommended that floor area <br /> exceeding that studied as part of the TIA will require <br /> modification to the MPD-CZ consistent with Section 2.9.2 <br /> of the UDO. <br /> The FAR for the Project should also be listed on the Master <br /> Concept Plan, specifically sheet(s) C 2.0 and/or 2.1. <br /> iii. Open Space: the Narrative indicates there will be a minimum of <br /> 30% open space for the project, translating to approximately 32 <br /> acres of land area. Please correct the narrative to reflect 30% of <br /> the proposed 104 acre development site. <br /> iv. Proposed building height for the Project is listed at a maximum of <br /> 60 ft. Existing language indicates `accessory structures' may <br /> exceed 60 ft. in overall height. Typically there are additional <br /> setback requirements for structures exceeding 40 ft. in height per <br /> Section 3.7 of the UDO. Staff recommends references in the <br /> narrative to a '60 ft. height limit' be replaced with the following: <br /> Buildings within the development shall abide by the <br /> height limitations and allowances established within <br /> Section 3.4 Office/Research and Manufacturinq of the <br /> UDO. Building height shall be limited to 35 ft. 2 feet of <br /> additional height shall be allowed for one foot increase in <br /> require setback from an external road/property line with a <br /> maximum cap of 60 ft. <br /> Additional information is required on the anticipated accessory land <br /> uses exceeding the 60 ft. height limit. Put simply: the applicant will <br /> need to provide a detailed list of land uses, other than signs, <br /> exceeding the height limit and the rationale for same. <br /> Height limit(s) will also need to be listed on the Master Concept <br /> Plan, specifically sheet(s) C 2.0 and/or 2.1. <br /> v. A total impervious surface limit should be established for the <br /> project. Under current regulations, development with this area of <br /> the County could be a maximum of 70% with compliance <br /> development of stormwater control measures. <br /> After conferring with the Director, it has been recommended the <br /> narrative contain language discussing the cumulative/shared nature <br /> of the development (i.e. shared access roads, shared parking, <br /> common stormwater control measures, open space preservation, <br /> 10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.