My WebLink
|
Help
|
About
|
Sign Out
PC 071316
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
2010-2019
>
2016
>
PC 071316
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/11/2017 2:45:49 PM
Creation date
8/11/2017 2:35:32 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
7/13/2016
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
38
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
Amos: I believe its five feet. <br />Commissioner Balch: And we talked about the communication. <br />Commissioner Nagler: I don't have questions. I have comments. <br />Chair Ritter: Okay, let's start with comments. <br />Commissioner Allen: I have one more question for Mike. Mike, and I apologize I didn't <br />ask you earlier, if we were to preserve all three trees, there are three heritage trees and <br />one is being removed. What would it take to keep all three? <br />Amos: I'm just going to point out where this tree is. It's right here, so the third tree is <br />right here. <br />Commissioner Allen: Okay, so that answers my question. <br />Chair Ritter: Okay, let's move on with comments. <br />Commissioner Nagler: Let me just go through the issues. First of all just to repeat <br />something I said at the workshop, I appreciate the creativity of this project and the fact <br />that it is a bit out of the ordinary, but in a way that is of high quality and helps us move <br />the architecture in downtown Pleasanton along so that we don't end up without the <br />interest that evolving architecture often brings, particularly the City core, and that this <br />project asks us to be more creative in the type of architecture that fits our design <br />criteria, I appreciate that, and I think that's important. Therefore, specifically on the use <br />of various materials, I appreciate the point that Commissioner Allen made about the <br />siding. I would want the design guidelines to be different in some ways but they are not. <br />And so I would support asking that the applicant change or remove the metal siding. I'm <br />okay with the metal roof because the guidelines as you point out are not as stringent on <br />the point, but also I think it adds to the interest of the architecture. There's nothing <br />unattractive or cheap about it, and I think that the channel metal roofing is very much an <br />important element to the overall look and architecture of the structures and that we <br />shouldn't start changing it. So I'm fine with the metal roof. <br />On the setbacks, I appreciate that the setback particularly on the mixed use building is <br />much less than what we typically require and we've talked about that previously and I've <br />certainly thought about it. I think I'm fine with it mostly because we want to communicate <br />that this is a mixed use building and that there is a commercial element to it. Given the <br />size of the lot and the fact that the applicant is attempting to get the number of buildings <br />onto it that they are, and in conjunction with that, that we want the mixed use building to <br />clearly have a commercial component to it, I'm fine with the less than standard setback <br />on that building, and that the setbacks on the rest of the project are within striking <br />distance. <br />On the parking, it's a tough one and I harp back to the fact that nothing has really <br />changed on this question since our workshop and that our workshop fully discussed and <br />vetted this issue. The one thing that maybe has changed is the mixed use on <br />Residence 1, so one could reasonably argue that there is a requirement for one <br />PLANNING COMMISSION MINUTES, July 13, 2016 Page 21 of 38 <br />
The URL can be used to link to this page
Your browser does not support the video tag.