My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
AgdaPkt 2013-11-18 Special
RedwoodCity
>
City Clerk
>
Agenda Packets
>
2010-2019
>
2013
>
AgdaPkt 2013-11-18 Special
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/19/2013 10:11:16 AM
Creation date
11/15/2013 3:48:02 PM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Agenda Packet
Meeting Type
Special
Agency Type
City Council
Date
11/18/2013
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.
/
402
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
8.A. - Page 20 :aff also identified eight intersections having the potential to be impacted <br /> by the Project and warranting further evaluation. This report was evaluated as part of <br /> the IS checklist and staff review, and staff concluded that In summary, the proposed <br /> Project forecasted traffic falls within the magnitude of the traffic increase accounted for <br /> in the DTPP EIR. <br /> 7. There is no need for additional CEQA analvsis reqardinq "relational <br /> heiqht considerations" or "tower wall stepbacks" since the Proiect is not <br /> adlacent to a four-story heiqht zone. <br /> The Appellant incorrectly states the need for an analysis of"relational heighY' and "tower <br /> wall stepback" considerations in the DTPP EIR (Appeal, Items II.0 and II.D). Again, this <br /> objection relates to the analysis in the DTPP EIR, and it is too late for Appellant to raise <br /> objections to that certified, approved EIR (see Master Response, IV.A.1 above). <br /> Nevertheless, Staff assumes that the Appellant is referring to Figure 6.3 in the EIR, not <br /> "Figure 7.3" as the Appellant refers to. The Project site is not adjacent to a four-story <br /> height zone (see DTPP Height Regulations Map, p. 86, Figure 6.3 in the DTPP EIR, as <br /> well as Master Response 1 in this document). The Appellant assumes that references to <br /> "tower wall stepbacks", "relational heighY' provisions, and other DTPP descriptive terms <br /> (DTPP EIR, Chapter 6, Aesthetics) are mandatory standards that apply to the Project. <br /> As discussed in Master Response 1 , they do not apply to the Project as a regulatory <br /> standard. <br /> V. The Project does not require additional environmental review because of <br /> the inclusion of the "unbundled" parking approach. <br /> A. The Appeal Should Not Be Granted on the Grounds that impacts from the <br /> "unbundlinq" of parkinq have not been analvzed. <br /> AppellanYs Position: Additional environmental analysis is needed because the Project <br /> proposes to "unbundle" parking (Appeal, Item II.B). <br /> City's Response: <br /> 1 . The Project meets the City's parking requirements, and as a result, <br /> there will be no significant impact due to the Project being <br /> "underparked". <br /> As discussed in Section 1 , Table 1 — Compliance with Key Standards of this staff report, <br /> the Project complies with the minimum parking requirement. In fact, the Project provides <br /> for 599 spaces, while the requirement per the DTPP is 526 spaces (for a surplus of 73 <br /> spaces). <br /> In addition, in the opinion of San Franciscans Upholding the Downtown Plan v. City and <br /> County of San Francisco (2002) 102 Cal. App. 4th 656 (1st App. Dist.) (Attachment 11) <br /> the court held that even if unbundled parking may lead to less use of on-site parking <br /> and more vehicles relying on street parking, a shortfall in the parking is not, in and of <br /> itself, a significant environmental effect under CEQA. <br /> 2. There is some evidence that unbundled parking results in reduced <br /> demand for parking as well as other general benefits. The City Is not <br /> Page 20 <br />
The URL can be used to link to this page
Your browser does not support the video tag.