My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 05/05/1992
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
1992
>
Agenda - Planning Commission - 05/05/1992
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/20/2025 4:03:28 PM
Creation date
11/13/2017 11:31:24 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
05/05/1992
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
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
CASE # 7 <br /> <br />CONSIDER PROPOSED ORDINANCE TO AMEND RAMSEY CITY CODE <br />CHAP.~EI~ 9 (ZONING AND SUBDIVISION OF LAND), SECTION 9.22 <br />(FLOOD:~L~INS) AND SECTION 9.50.38 (FLOOD PLAIN REQUIREMENTS) <br />By: Zoning Administrator <br /> <br />Background: <br /> <br />As a result Of~ chlmges to Federal regulations in 1986, communities participating in the National <br />Flood Insuraa~ ce Program are required to amend their floodplain zoning ordinances. The Federal <br />Emergency ~l~anhgement Agency (FEMA) and the Minnesota DNR have developed a model <br />ordinance to ~e. fl~t the changes in federal regulations. That model ordinance has been retrofitted <br />for incorpo~'ltio~ into Ramsey's City Code as a replacement for Section 9.22. The required <br />amendment8 ~lso~affected Section 9.50.38 of the City Code and an ordinance amendment has been <br />drafted accor~ngly. Both of the proposed ordinances are enclosed for your information. <br />Observatiol~s: <br /> <br />Federal law allows communities 90 days from the time DNR contact to amend their ordinance. <br />Ramsey was ¢off~cted on February 6, 1992. Therefore, the ordinance should have been adopted <br />by May 6, 19~2. [The schedule we are proceeding on is Council introduction of the ordinance on <br />May 26 and atloption on June 9. <br /> <br />Below is a summary of the changes to the current regulations resulting from the required <br />amendments: r <br /> <br />Section 9.22.01 (Statutory Authorization, Findings of Fact and Purpose) - No changes. <br /> <br />Section 9.22.02 {General Provisions) - Definitions were added for Basement, Conditional Use, <br />Principal U'S~ of Structure, Reach, Regulatory Flood Protection Elevation, and Variance. <br />Compliance!ang~lage was moved to Section 9.22.03. <br /> <br />Section 9.22;03 ~stablishment of Zoning Districts) - The Compliance language was expanded and <br />moved fromg~.22;02 to this section. <br /> <br />Section 9.22.04 (Floodway District) - The format was revised to more clearly state which uses are <br />permitted or Conditionally permitted. Other revisions include: provisions for regulating travel <br />trailers and travel vehicles consistent with FEMA's new standards; recommendation for a <br />maximum I0 Ye~flood height for agricultural levees that protected crops only; requiring long-term <br />site and ultim~te development plan for uses requiring storage for significant volumes of materials in <br />the floodway;., clarification of which accessory structures can be wet-flood, in lieu of dry food <br />proofing. <br /> <br />Section 9.22.05 (.Flood Fringe District) - Language was added to specifically cite "construction" <br />and "use of 8pa~e" standards for elevated buildings not in fill' and are required when this <br />construction :~ch~flique is allowed. Language was included as a warning for those who may be <br />requesting al LOMR once construction is complete that FEMA has specific fill compaction <br />standards for f~suance of LOMR's. <br />Section 9.22.06 The floodway/flood fringe determination procedure was moved up to this <br />section. It was al~ revised to have the City Council approve the final floodway alignment. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.