Browse
Search
Agenda - 11-14-2017 - D.2 - Unified Development Ordinance (UDO) and Zoning Atlas Amendments – Flood
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2010's
>
2017
>
Agenda - 11-14-2017 - QPH
>
Agenda - 11-14-2017 - D.2 - Unified Development Ordinance (UDO) and Zoning Atlas Amendments – Flood
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/14/2017 2:52:30 PM
Creation date
11/14/2017 2:45:57 PM
Metadata
Fields
Template:
BOCC
Date
11/14/2017
Meeting Type
Public Hearing
Document Type
Agenda
Agenda Item
D.3
Document Relationships
2017-628 Statement of Approval and Consistency Of A Proposed Unified Development Ordinance Text Amendment With the Adopted Orange County 2030 Comprehensive Plan
(Linked From)
Path:
\Board of County Commissioners\Contracts and Agreements\General Contracts and Agreements\2010's\2017
2017-629 Statement of Approval and Consistency Of A ProposedZoning Atlas Amendment with the Adopted Orange County 2030 Comprehensive Plan
(Linked From)
Path:
\Board of County Commissioners\Contracts and Agreements\General Contracts and Agreements\2010's\2017
Minutes 11-14-2017
(Linked From)
Path:
\Board of County Commissioners\Minutes - Approved\2010's\2017
ORD-2017-024 Ordinance amending the Zoning Atlas by eliminating the Special Flood Hazard Area (SFHA) Overlay District as currently depicted on the atlas encumbering the identified parcels of property
(Linked From)
Path:
\Board of County Commissioners\Ordinances\Ordinance 2010-2019\2017
ORD-2017-026 Ordinance adopting a new Flood Insurance Study (FIS) and new Flood Insurance Rate Maps (FIRMs) as produced by the State of NC and FEMA
(Linked From)
Path:
\Board of County Commissioners\Ordinances\Ordinance 2010-2019\2017
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.
/
230
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.6: Floodplain Development APPLICATION, Permit and Certificate Requirements <br /> (F) Plans and/or details for the protection of public utilities and facilities such as sewer, gas, <br /> electrical, and water systems to be located and constructed to minimize flood damage; <br /> (G) Copy of all other Local, State and Federal permits required prior to floodplain <br /> development permit issuance (i.e. Wetlands, Erosion and Sedimentation Control, <br /> Riparian Buffers, Mining, etc.); <br /> (H) If the application is for placement of recreational vehicles and/or temporary structures, <br /> documentation to ensure compliance with Section 6.621.1(B)(5) and (7) of this <br /> Ordinance. <br /> (I) If a watercourse is proposed to be altered and/or relocated, a description of the extent of <br /> watercourse alteration or relocation, an engineering report on the effects of the proposed <br /> project on the flood-carrying capacity of the watercourse and the effects to properties <br /> located both upstream and downstream; and a map, drawn to scale, (if not shown on plot <br /> plan) showing the location of the proposed watercourse alteration or relocation. <br /> 2.6.3 Data Requirement <br /> The following information shall be provided at a minimum on the floodplain development permit to <br /> ensure compliance with this Ordinance.•(A) - - -• - " --••-. _• ---- - • --.- __ --. _ ••• • -- A <br /> complete description of all the development to be permitted under the floodplain <br /> development permit(e.g. house, garage, pool, septic, bulkhead, cabana, pier, bridge, <br /> mining, dredging, filling, grading, paving, excavation or drilling operations, or storage of <br /> equipment or materials, etc.).16 <br /> (B) The Special Flood Hazard Area (SFHA) determination for the proposed development per <br /> available data specified in Section/1.3.5. 1.1.3 of this Ordinance. <br /> (C) The regulatory flood protection elevation required for the reference level and all attendant <br /> utilities. <br /> (D) The regulatory flood protection elevation required for the protection of all public utilities. <br /> (E) All certification submittal requirements with timelines. <br /> (F) A statement that no fill material shall encroach into the floodway or non-encroachment <br /> area of any watercourse, if applicable. <br /> (G) If in an AE zone, specify the minimum foundation opening requirements. <br /> (H) State limitations of below BFE enclosure uses (if applicable) such as, parking, building <br /> access and limited storage only). <br /> (Ha_ A statement indicating that all materials below BFE and/or Regulatory Flood Protection <br /> Elevation (RFPE) must be flood resistant materials.17 <br /> 2.6.4 Certification Requirements <br /> (A) An Elevation Certificate (FEMA Form 81 31086-0-33) or Flood Proofing Certificatc <br /> (FEMA Form 81 65) is required after the reference level is completed. 18 <br /> 16 Staff is updating language to be consistent with the new model ordinance. <br /> 17 This is identified as optional language within the FEMA minimum model ordinance. Staff is recommending we <br /> include. While we restrict new development below the base flood elevation(BFE),we do have several structures <br /> located within the floodplain where portions of same are below BFE. In instances where there are improvement <br /> projects to these structures we need to require this information as part of our floodplain management program. <br /> 18 Staff is recommending existing language be modified to split out references to the Elevation Certificate and a <br /> Flood Proofing Certificate to ensure consistency with the FEMA minimum model ordinance. There are now unique <br /> provisions/standards for each certificate. Keeping them combined will create confusion and lead to compliance <br /> issues. <br /> Orange County, North Carolina—Unified Development Ordinance Page 2-15 <br />
The URL can be used to link to this page
Your browser does not support the video tag.