My WebLink
|
Help
|
About
|
Sign Out
Home
Reso 2016-117
CityHall
>
City Clerk
>
City Council
>
Resolutions
>
2016
>
Reso 2016-117
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/24/2017 4:51:30 PM
Creation date
10/7/2016 4:40:40 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Resolution
Document Date (6)
9/19/2016
Retention
PERM
Document Relationships
_CC Agenda 2016 0919 CS + RG
(Reference)
Path:
\City Clerk\City Council\Agenda Packets\2016\Packet 2016 0919
4B1 Public Hearing 2016 0919
(Reference)
Path:
\City Clerk\City Council\Agenda Packets\2016\Packet 2016 0919
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.
/
258
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
SAN LEANDRO GENERAL PLAN UPDATE DRAFT FEIR <br />CITY OF SAN LEANDRO <br />REVISIONS TO THE DRAFT EIR <br />As discussed above, the ongoing 1-880 Integrated Corridor Management effort led by the MTC that <br />aims to optimize freeway, arterial signal, rail, and bus systems and incorporate Intelligent <br />Transportation System would also help enhance efficiency on the freeway. However, for the reasons <br />listed above this impact would remain significant and unavoidable. <br />3.7 REVISIONS TO CHAPTER 5, SIGNIFICANT UNAVOIDABLE <br />IMPACTS <br />The bulleted list on page 5-2 of the Draft EIR is hereby amended as follows: <br />■ As shown in Table 4.13-114.14 the addition of proposed Plan traffic would result in significant <br />impacts to 125 intersections during at least one of the peak hours. <br />■ As shown in Table 4.13-12 4-4R 16; and Table 4.13-13 4.14 !:�, the addition of proposed Plan traffic <br />would result in significant impacts to=agven-&44 freeway segments during at least one of the peak <br />hours. <br />3.8 REVISIONS TO CHAPTER 6, ALTERNATIVES TO THE <br />PROPOSED PROJECT <br />The first bulleted paragraph on page 6-2 of the Draft EIR is hereby amended as follows: <br />No Project Alternative. Consistent with Section 15126.6(e)(2) of the CEQA Guidelines, under the No <br />Project Alternative, ek4e--the proposed General Plan Update 4eF7and the proposed Zoning Code <br />amendments would not be adopted, and future development in the city would continue to be subject <br />to existing policies, regulations, development standards, and land use designations under the existing <br />San Leandro General Plan and Zoning Code. The General Plan land use map for the No Project <br />Alternative would be the same as the City's current General Plan land use map. Total acreages of <br />various land use designations would not differ drastically between the proposed project and the No <br />Project Alternative. However, the No Project Alternative would not include the new higher density <br />residential land use or transit -oriented development designations of the proposed project, nor would <br />it include the increases in allowable residential densities associated with proposed Zoning Code <br />amendments. Therefore, the No Project Alternative would result in less residential development than <br />the proposed project. In terms of job growth, the No Project Alternative would not include the <br />proposed Industrial Transition designation or the proposed Economic Development Element, with its <br />job -generating focus on innovation, and local manufacturing and technology sector growth. <br />Therefore, while the No Project Alternative might result in a similar amount of non-residential square <br />footage by 2035, that square footage would amore likely te-be warehousing or traditional <br />manufacturing; containing a lower proportion of employees per square foot and therefore fewer jobs. <br />PLACFWORKS 3-9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.