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
for b. For c, potential locations of storage tanks associated with commercial uses in the <br />AUAR should be identified (e.g., gasoline tanks at service stations). <br />21. Traffic. For most AUAR reviews a relatively detailed traffic analysis will be needed, <br />especially if there is to be much commercial development in the AUAR area or if there <br />are major congested roadways in the vicinity. The results of the traffic analysis must be <br />used in the response to item 22 and to the noise aspect of item 24. <br />Instead of responding to the information called for in item 21, the following information <br />should be provided: <br />--a description and map of the existing and proposed roadway system, including state, <br />regional, and local roads to be affected by the development of the AUAR area. This <br />information should include existing and proposed roadway capacities and existing and <br />projected background (i.e., without the AUAR development) traffic volumes; <br />—trip generation data —trip generation rates and trip totals—for teach major <br />development scenario broken down by land use zones and/or other relevant subdivisions <br />of the area. The projected distributions onto the roadway system must be included; <br />—analysis of impacts of the traffic generated by the AUAR area on the roadway system, <br />including: comparison of peak period total flows to capacities and analysis of Levels of <br />Service and delay times at critical points (if any); <br />—a discussion of structural and non-structural improvements and traffic management <br />measures that are proposed to mitigate problems; <br />Note: in the above analyses the geographical scope must extend outward as far as the <br />traffic to be generated would have a significant effect on the roadway system and traffic <br />measurements and projections should include peak days and peak hours, or other <br />appropriate measures related to identifying congestion problems, as well as ADTs. <br />22. Vehicle-related air emissions. The guidance provided in "EAW Guidelines: should <br />also be followed for an AUAR. Mitigation proposed to eliminate any potential problems <br />may be presented under item 21 and merely referenced here. <br />23. Stationary source air emissions. This item is not applicable to an AUAR. Any <br />stationary air emissions source large enough to merit environmental review requires <br />individual review. <br />24. Dust, odors, noise. Dust, odors, and construction noise need not be addressed in an <br />AUAR, unless there is some unusual reason to do so. The RGU might want to discuss as <br />part of the mitigation plan, however, any dust control or construction noise ordinances in <br />effect. <br />If the area will include or adjoin major noise sources a noise analysis is needed to <br />determine if any noise levels in excess of standards would occur, and if so, to identify <br />appropriate mitigation measures. With respect to traffic-generated noise, the noise <br />analysis should be based on the traffic analysis of item 21. <br />25. Sensitive resources: <br />Archeological, historic, and architectural resources. For an AUAR, contact with the <br />State Histaric Preservation Office is required to determine whether there are areas of <br />7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.