My WebLink
|
Help
|
About
|
Sign Out
Home
pf_03722
Roseville
>
Planning Files
>
Old Numbering System (pre-2007)
>
PF3000 - PF3801
>
3700
>
pf_03722
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/28/2014 11:30:17 AM
Creation date
7/3/2013 10:52:19 AM
Metadata
Fields
Template:
Planning Files
Planning Files - Planning File #
3722
Planning Files - Type
Planning-Other
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
27
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
boundaries of the AUAR and any subdistricts used in the AUAR analysis; (2) land use <br />and planning and zoning maps as required in conjunction with items 9 and 27; and (3) a <br />cover type map as required for item 10. Additional maps may be included throughout <br />the document wherever maps are useful for displaying relevant information. <br />6. Description. Instead of the information called for on the form, the description section of <br />an AUAR should include the following elements for each major development scenario <br />included: <br />-anticipated types and intensity (density) of residential and commercial/warehouse/light <br />industrial development throughout the AUAR area; <br />-infrastructure planned to serve development (roads, sewers, water, stormwater system, <br />etc.) Roadways intended primarily to serve as adjoining land uses within an AUAR area <br />are normally expected to be reviewed as part of an AUAR. More "arterial" types of <br />roadways that would cross an AUAR area are an optional inclusion in the AUAR <br />analysis; if they are included, a more intensive level of review, generally including an <br />analysis of alternative routes, is necessary; <br />-information about the anticipated staging of various developments, to the extent known, <br />and of the infrastructure, and how the infrastructure staging will influence the <br />development schedule. <br />Important Note: Every AUAR document MUST review one or more development scenarios <br />based on and consistent with the RGU's Comprehensive Plan in effect when the AUAR is <br />officially ordered. (This is equivalent to reviewing the "no-build" alternative in an EIS.) If an <br />RGU expects to amend its existing Comprehensive Plan, it has the options of deferring the start <br />of the AUAR until after adopting the amended plan or reviewing developments based on both <br />the existing and amended comprehensive plans; however, it cannot review only a development <br />based on an expected amendment to the existing plan. Also, the rules require that one or more <br />development scenarios analyzed must be consistent with known development plans of property <br />owners within the AUAR area. <br />7. Project magnitude data. No changes from the EAW form, except that the information <br />should be given for each major development scenario. <br />8. Permits and approvals required. A listing of major approvals (including any <br />comprehensive plan amendments and zoning amendments) and public financial <br />assistance and infrastructure likely to be required by the anticipated types of <br />development projects should be given for each major development scenario . This list <br />will help orient reviewers to framework that will protect environmental resources. The <br />list can also serve as a starting point for the development of the implementation aspects <br />of the mitigation plan to be developed as part of the AUAR. <br />9. Land use. No changes from the EAW form. <br />10. Cover types. The following information should be provided instead: <br />a. cover type map, at least at the scale of a USGS topographic map, depicting: <br />-wetlands — identified by type (Circular 39) <br />-watercourses — rivers, streams, creeks, ditches <br />� <br />
The URL can be used to link to this page
Your browser does not support the video tag.