My WebLink
|
Help
|
About
|
Sign Out
AGENDA REPORT
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2011
>
020811 Workshop
>
AGENDA REPORT
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/4/2011 1:23:18 PM
Creation date
2/4/2011 1:23:17 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
2/8/2011
DESTRUCT DATE
15Y
DOCUMENT NO
AGENDA REPORT
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
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
PLANNING COMMISSION ACTION <br /> At its meeting on January 26, 2011, the Planning Commission reviewed the Draft <br /> Hacienda TOD Standards and Design Guidelines (see Attachment 4: Planning <br /> Commission draft minutes). Speakers at the public hearing included several members of <br /> the Hacienda Task Force as well as participants in the Advisory/Stakeholder Group. <br /> John Wayland of BRE Properties, Inc. discussed several concerns with the draft <br /> document that he believed would work against developing an economically viable project. <br /> These are described in the Planning Commission draft minutes as well as in a letter <br /> provided to the Planning Commission (Attachment 6). <br /> After considering public input and deliberating on several topics, the Planning <br /> Commission recommended the Draft Hacienda TOD Standards and Design Guidelines to <br /> the City Council with several amendments. The proposed amendments, followed by <br /> staff's recommendations (in italics) are as follows: <br /> • Public Park: Provide additional incentives (such as relief of in -lieu fees, or <br /> reduction of the amount of private open space required) to encourage the <br /> development of a public park on Parcels 2 or 3. Staff concurs with this <br /> recommendation but believes these incentives should also be extended to Parcel <br /> 1. <br /> • Curvilinear Connecting Trail: Include a "sunset clause" in the design guidelines <br /> that would eliminate the trail from the requirements, if agreement is not reached <br /> with Kaiser to jointly implement the trail by the fourth quarter of 2011. If the trail <br /> remains in the document, the setbacks on Sites 1 and 2 should be reduced as <br /> follows: Willow Road: 20 feet, not 22 feet; Hacienda Drive: 25 feet, not 35 feet; <br /> Gibraltar Drive: 20 feet, not 25 feet. Staff believes the connecting trail is an <br /> essential piece of the pedestrian and bicycle circulation plan and recommends <br /> some flexibility in applying the sunset clause. Staff recommends that the trail <br /> requirement not be eliminated from the plan if Kaiser has indicated its willingness <br /> to work with the City by the December 31 date. <br /> • Density: Retain as in draft: minimum of 30 units per acre and a maximum of 55 <br /> units per acre. Staff concurs with this recommendation. <br /> • Retail: Require 5,000 square feet, not 10,000 square feet of dedicated retail <br /> space overall, with the 5,000 square feet located on Owens Drive. Retail space <br /> may be located on Parcels 2 and 3 as a builder's option. Staff supports 5,000 <br /> square feet of retail at Owens as well as the live/work space as described below. <br /> In regards to the retail space at Gibraltar Drive, staff seeks direction from the City <br /> Council. <br /> • Live/Work Space: Retain the live /work requirement on Owens Drive (Parcel 1); <br /> allow live /work space on Parcels 2 and 3 as a builder's option, but not required in <br /> this location. Staff believes that requiring Live/Work space (designed with the <br /> higher ceiling requirement included in the Standards and Design Guidelines) <br /> along Owens Drive is crucial to providing an option for additional retail <br /> Page 3 of 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.