My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD04031
CWCB
>
Floodplain Documents
>
Backfile
>
3001-4000
>
FLOOD04031
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2010 6:45:04 PM
Creation date
10/5/2006 12:17:26 AM
Metadata
Fields
Template:
Floodplain Documents
County
Statewide
Community
State of Colorado
Stream Name
All
Basin
Statewide
Title
Subdivision Design in Flood Hazard Areas
Date
9/1/1997
Prepared For
State of Colorado
Prepared By
FEMA
Floodplain - Doc Type
Educational/Technical/Reference Information
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
62
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).
Show annotations
View images
View plain text
<br /> <br /> <br />Figure 4-1. Subdivision Design Hierarchy <br /> <br />LEVEL <br /> <br />1 <br /> <br />su~g~~~~~~TI~tAN RECOMMENDED APPROACH <br />NO LOTS IN FLOODPLAIN <br /> <br />2 <br /> <br /> <br />PORTION OF SOME LOTS IN FLOODPLAIN; <br />EACH LOT HAS BUILDABLE APEA ON <br />NATURAL HIGH GROUND <br /> <br />FOR USE IN CASE,S <br />WHERE FLOODPLAIN <br />DEVElOPMENl <br />IS UNAVOIDABLE <br /> <br />3 <br /> <br />SOME LOTS ENTIRELY IN FLOODPLAIN' <br />FILL ONLY TO PROVIDE BUILDING SITES AND ROAD ACCESS <br /> <br />'-f <br /> <br /> <br />MOST LOTS PARTIALLY OR ENTIRELY IN FLOODPLAI N; <br />CLUSTERING RECOMMENDED ON AREA OF SHALLOWEST FLOODING <br /> <br />adequate lot sizes and configurations, roads, s€\vers, <br />and drainage. Most communities have developed a <br />detailed checklist of requirements for what a developer <br />must provide \vhen submitting a subdivision proposal. <br />The subdivision approval process is typically done in <br />two or three stages: 1) a concept plan approval; <br />2) preliminary plat approval; and 3) final plat approval. <br />Often certain information is required at a preliminary <br />stage, and more detailed information is required in a <br />later stage of revie\'\'. Subdivision approvals by local <br />government are the official means by \vhich the size, <br />location, and configuration of lots, public spaces, and <br />streets are publicly recorded. <br />Increasingly, local governments are adopting site <br />plan revievv ordinances that establish a higher level of <br />scrutiny in the revie\v process for certain classes of <br />development (e.g., all residential subdivisions over a <br />certain acreage or lot quantity, or all proposed <br />development that is not listed as permitted in the <br />zoning ordinance). Also, most communities that have <br />adopted special purpose zoning districts, such as <br />planned unit development or cluster development <br />districts, have established site plan revielvv standards to <br />guide these processes. <br />The assumption of this report is that a community <br />should have a detailed site plan revie\.\' process for <br />subdivisions that have the potential to affect the <br />floodplain or to be at risk from flooding. If this is not <br />possible, the requirements and recommendations <br />described in this chapter would have to be applied <br />through the community's conventional subdivision and <br />floodplain ordinances. <br />The site plan reviev,! procedure for a subdivision <br />usually begins ,,,rith a preapplication conference <br />behveen the applicant and the planning staff. This <br />meeting gives both parties the chance to informally <br />discuss the contents of the proposed development <br /> <br />28 <br /> <br />before the official review process gets undenvay and a <br />large amount of time and money is spent. Planning staff <br />should provide the developer with a checklist of items <br />that must be included on the site plan to be submitted <br />for revie\v. (An example of the site plan review checklist <br />appears in Appendix DJ Following the preapplication <br />conference, the developer submits a site plan that <br />should include all required information and that reflects <br />the comments and suggestions offered in the meeting. <br />There are a couple of vvays that communities <br />accomplish site plan revie\v. Some establish a <br />committee of staff from the pfanning, building, public <br />\vorks, and zoning departments. This committee meets <br />\-...'eekly to review and discuss site plans. A member of <br />the committee then summarizes the results of that <br />meeting and mails a copy to the applicant and submits <br />another to the appropriate review board. Other <br />communities forego the committee structure and simply <br />distribute the site plan to the various departments, <br />where it is assigned to a staff member, \,vho then is <br />given a deadline for commenting on the plan and <br />returning it to the planning department. In either <br />arrangement, a planner \-'\'ill summarize all of the <br />comments and present the case to the planning or <br />zoning board \-'\'ith the list of conditions that should be <br />met for the development to be approved. <br />The site plan revie\'\' process is an implementing <br />mechanism for the zoning ordinance, subdivision <br />regulations, and the comprehensive plan. For the site <br />plan review process to work in favor of flood protection <br />and water-quality protection, floodplain protection <br />goals have to be made a part of those documents and <br />processes. Better yet, a floodplain management plan <br />should be prepared, and the site plan review procedure <br />would be identified as one method of implementation. <br />Another simple task would be to add floodplain <br />considerations to the site plan review checklist. At a <br />
The URL can be used to link to this page
Your browser does not support the video tag.