My WebLink
|
Help
|
About
|
Sign Out
12
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2011
>
021511
>
12
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/11/2011 4:54:04 PM
Creation date
2/10/2011 2:13:42 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
2/10/2011
DESTRUCT DATE
15Y
DOCUMENT NO
12
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
192
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
• Non -core standards, retail and live /work requirements, and permitted uses <br /> • Development standards and design guidelines related to street design, site planning, <br /> building types and architectural features. <br /> • Illustrations and descriptions of six residential building types varying in density from 14 <br /> units per acre to 80 units per acre, various retail buildings, and live /work prototypes. <br /> The document includes three types of guidance to developers: Core PUD regulations, non - <br /> core standards, and guidelines. Although development project on sites 1,2 and 3 will be <br /> required to meet all the Core Standards, the City Council may exercise discretion in the <br /> application of the other development standards, if such proposals meet the intent and purpose <br /> of the standards. Some flexibility is warranted in order to comply with the guidelines where <br /> specific site circumstances would make application of the guideline infeasible, produce an <br /> undesirable outcome that is counter to the Vision, or where a creative alternative clearly <br /> promotes the intent expressed in this document. <br /> JOINT PLANNING COMMISSION /CITY COUNCIL WORKSHOP <br /> On December 16, 2010, the Hacienda Task Force met in a Joint Workshop with the Planning <br /> Commission and City Council to discuss the draft document (minutes attached as Exhibit D). <br /> Issues raised fell broadly into three areas: items that need clarification in the draft Hacienda <br /> TOD Standards and Design Guidelines; policy issues yet to be resolved; and "bigger picture" <br /> items that need further discussion (mostly by the City Council or other entities) but that cannot <br /> be resolved by the Task Force or within the Hacienda document. <br /> • Issues addressed by chanqes /clarifications to the Draft Hacienda TOD Standards and <br /> Design Guidelines. The following amendments /clarifications were discussed with the <br /> Hacienda Task Force at a follow -up meeting on January 6, 2011. There was general <br /> agreement with the changes noted below; any additional comments from the Task <br /> Force are included. <br /> Issue Resolved by: <br /> Owens Drive — desire to see an option Page 18 now includes an Owens Drive option <br /> which does not significantly change the showing the existing curb lines and median, <br /> existing curb line of Owens Drive and therefore requiring minimal change to the <br /> configuration of Owens Drive. <br /> Minimum height of retail buildings Page 12 now shows a 25 -foot minimum <br /> height for principal structures. <br /> Permitted uses: should be specific or At the January 6, 2011 Task Force meeting <br /> generalized? there was conflicting input regarding making <br /> the list of uses more general or specific, and <br /> what uses should be prohibited or made <br /> subject to a Conditional Use Permit (CUP). <br /> Staff has made revisions (reflected in the <br /> draft, attached) and has clearly indicated <br /> uses requiring a CUP (including permitted <br /> uses operating between 10 p.m. and 6 a.m.) <br /> and prohibited uses. The current list does not <br /> •rohibit liquor stores (as some Task Force <br /> Case No. PRZ -57, City of Pleasanton Planning Commission <br /> Page 3 of 8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.