My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
75C - PH - THE BOWERY
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2020
>
08/18/2020
>
75C - PH - THE BOWERY
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/13/2020 5:10:27 PM
Creation date
8/13/2020 4:53:25 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Planning & Building
Item #
75C
Date
8/18/2020
Destruction Year
2025
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.
/
1021
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
by the Project, in a currently non-residential area. The comment further states that California law requires <br />a project -specific application and analysis, and the Project fails to provide a project -specific analysis of <br />how code compliance translates to sufficient mitigation. <br />Response 16: The Draft EIR describes on page 5.1-19 that nighttime lighting associated with the existing <br />urban development is present both onsite and within the surrounding area, and includes streetlights along <br />Red Hill Avenue and Warner Avenue, parking lot and building fagade lighting, interior illumination passing <br />through windows, and illumination from vehicle headlights. Also, page 5.1-33 describes that all of the <br />Project's outdoor lighting would be hooded, appropriately angled away from adjacent land uses. It also <br />describes that the Project would be required to comply with the City's lighting regulations that would be <br />verified by the City's Planning and Building Agency during the permitting process. Because lighting exists <br />on the Project site area, the increase in light that would be generated by the Project would not be <br />substantial. As the lighting standards are part of the City's development standards and would be imposed <br />in the same manner as the rest of the development standards related to the Project, pursuant to the <br />municipal code. The City's standard development review and permitting process involves verification that <br />all of the development standards applicable to the Project, including lighting, are implemented, which <br />would ensure that impacts related to lighting would be less than significant. <br />Comment 17: The comment asserts that the air quality analysis is flawed because the input parameters <br />used with CaIEEMod were not consistent with information disclosed in the Draft EIR and that vehicle <br />emissions factors used to estimate the proposed Project's operational emissions were changed from the <br />CaIEEMod default values without proper justification. The comment further contends that as a result, the <br />Project's construction and operational emissions are underestimated and a new EIR should be prepared. <br />Response 17: The comment asserts that unsubstantiated changes were made to the CaIEEMod default <br />values for operational emissions. The California Air Resources Board (CARE) released EMFAC2017 as its <br />latest emissions inventory model. It should be noted that the air districts recommended California Emissions <br />Estimator Model (CaIEEMod) v 2016.3.2 does not yet incorporate EMFAC2017 when calculating emissions. <br />As such, post -processing of EMFAC2017 emissions data for import into CaIEEMod was completed in the <br />modeling, as noted in the model output data sheets that are included in the Draft EIR for review. <br />Comment 18: The comment asserts that the pass -by trip percentages utilized in the air quality model are <br />inconsistent with the Traffic Impact Analysis and as a result the model may underestimate the Project's <br />mobile -related operational emissions. <br />Response 18: The default pass -by and vehicle percentages were adjusted to reflect the internal capture <br />identified in the trip generation data provided to Urban Crossroads, Inc. at the time the AQIA was <br />prepared. It should be noted that CaIEEMod does not include an option to account for internal capture — <br />and in fact, use of the pass -by model option is likely a conservative representation since the pass -by <br />category assigns a trip length of 0.1 miles to every trip, per CaIEEMod guidance. Notwithstanding, as <br />noted in the Draft EIR and as summarized by the commenter in subsequent comments, the total trips <br />identified in the final traffic study include 12,872 daily vehicle trips after accounting for pass -by and <br />internal capture. As the commenter summarizes in their comments and as presented in the Draft EIR, the <br />AQIA and underlying associated technical analysis is based on 16,400 daily trips which is higher than the <br />final trip generation in the traffic study. As such, the AQIA likely overstates rather than understates any <br />potential impacts from vehicular activity. <br />Comment 19: The comment asserts that the Saturday and Sunday trip rates are incorrect and that the <br />number of vehicle trips is higher than the input parameter figures used in CaIEEMod and thus the trip <br />estimates are incorrect and cannot be relied upon. <br />75C-200 <br />
The URL can be used to link to this page
Your browser does not support the video tag.