My WebLink
|
Help
|
About
|
Sign Out
Home
4B Public Hearing 2015 0720
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2015
>
Packet 2015 0720
>
4B Public Hearing 2015 0720
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/5/2019 9:05:15 AM
Creation date
7/30/2015 5:42:11 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Staff Report
Document Date (6)
7/20/2015
Retention
PERM
Document Relationships
_CC Agenda 2015 0720 CS+RG
(Reference)
Path:
\City Clerk\City Council\Agenda Packets\2015\Packet 2015 0720
2A Business 2015 0727
(Reference)
Path:
\City Clerk\City Council\Agenda Packets\2015\Packet 2015 0727
8G Consent 2015 0908
(Amended)
Path:
\City Clerk\City Council\Agenda Packets\2015\Packet 2015 0908
Ord 2015-008
(Reference)
Path:
\City Clerk\City Council\Ordinances\2015
Reso 2015-126
(Reference)
Path:
\City Clerk\City Council\Resolutions\2015
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
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).
Download electronic document
View images
View plain text
PALMIERI, TYLER. WIENER. WILHELM &WALDRO,�_. <br />Members of the San Leandro Planning <br />Commission <br />June 18, 2015 <br />Page 4 <br />2. The Planning Commission should not recommend the amendments to <br />the General Plan and Zoning. <br />City Staff and the developer are attempting to amend the General Plan before <br />receiving City Council certification of the EIR and approval of the project. The timing is <br />improper. Why is the City proceeding with approving a final step before approving the <br />beginning step? Any amendment to the General Plan and Zoning should be considered <br />when, or if, the EIR is approved. <br />The proposed amendment to the zoning for the Shoreline is improper. The <br />proposed amendment seeks to change the zoning of the project area from Commercial <br />Recreation to "Community Commercial, Planned Development overlay." This change is <br />in direct conflict with the General Plan goals, policies and actions for the Marina and <br />Shoreline. Policy 9.02 provides, "Enhance the San Leandro Marina areas as a <br />distinguished recreational shoreline, with complementary activities ..." In fact, the <br />proposed project seeks to eliminate the recreation and the shoreline. <br />Further, the information proffered as the justification for the Planned <br />Development zoning overlay in the Staff Report is different from that provided in the <br />proposed Planning Commission resolution. The proposed resolution provides that the <br />"overlay is intended for projects that include a mix of land uses, that can be made <br />compatible by applying careful and imaginative treatments to the interrelationships of <br />uses and activities to ensure that orderly and thorough planning will result in high- <br />quality urban design." <br />The Staff Report, however states that the overlay is to "reduce or eliminate the <br />rigidity ... that otherwise would result from application of the zoning standards and <br />procedures ..." The Staff Report goes on to say that the overlay would provide "greater <br />freedom" to the developer. The positions are doublespeak. It is a simultaneous <br />expression of contradictions. It can't be both careful, orderly, thorough and structured <br />and free from order and structure. <br />In order for the Planning Commission to recommend approval of the rezone to a <br />Planned Development Overlay District, it must first find that the Planned Development <br />Concept Plan is consistent with the adopted Land Use Element of the General Plan and <br />other applicable policies of the General Plan and is compatible with surrounding <br />development. (Zoning Code, § 3-1008B.) <br />1557190.2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.