My WebLink
|
Help
|
About
|
Sign Out
PC 052108 Special Mtg
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
MINUTES
>
2000-2009
>
2008
>
PC 052108 Special Mtg
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/5/2017 4:37:21 PM
Creation date
11/26/2008 11:57:12 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
MINUTES
DOCUMENT DATE
5/21/2008
DESTRUCT DATE
15 Y
DOCUMENT NAME
PC 052108
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).
Show annotations
View images
View plain text
Commissioner O'Connor was more disturbed by events after the City got involved and laid out <br />the rules for the applicant. He noted that the licensed contractor did not seem to follow anything <br />the City asked. He believed that as a minimum, the water should be removed from the pond until <br />the problems are further identified. He noted that there was a safety issue, as well as leakage. <br />Commissioner Fox agreed with Commissioner O'Connor's comments and noted that the leakage <br />and the slope may not be stable enough for a retrofit to be performed successfully. <br />Chair Blank noted that there was a fault near that area and that even a small temblor on that fault <br />could cause damage in this area. <br />Commissioner Narum agreed that the project should meet the engineering requirements as <br />spelled out in the report. She noted that she struggled with the setback and noted that a <br />swimming pool had just been allowed across the street with a 10-foot setback, even though the <br />pool could have fit within the 20-foot setback. <br />Chair Blank noted that in that case, the conditions were different and that there was no leakage at <br />that location and that this was not up against the hazard boundary. <br />Commissioner Narum noted that the Planning Commission had been striving for consistency and <br />that she believed that with the correct engineering, it could be accomplished and the reduction of <br />the rear yard setback from the required 20 feet to 10 feet could be allowed. <br />Ms. Decker noted that the Spencers had requested that the rear yard setback be reduced from the <br />required 20 feet to 5 feet. She stated that the Planning Commission agreed with staff s <br />recommendation to at least have 10 feet because they wanted some distance from the downslope <br />property as a rear yard setback. She added that the Planning Commission did agree with staff <br />that the side yard setback could be reduced from ten feet to five feet, but there was no elevation <br />difference as great as that to the rear yard neighbor, nor in this particular instance, either. <br />Commissioner Narum understood staff s rationale for the side yard setback, but with respect to <br />the 20-foot setback, she believed the City should be consistent with its determinations. She <br />noted that in effect, aten-foot variance had been given across the street from this applicant. <br />Chair Blank suggested that if Option 2 were to be chosen, the applicant could remove the pond <br />and then return to request a variance fora 10-foot setback once the pond was properly removed <br />and engineered. <br />Commissioner Fox noted that even if the applicant were to retrofit this prof ect, she was <br />concerned about the overall slope stability. She agreed with Chair Blank that this was a different <br />situation because of the safety issue. <br />Commissioner Olson agreed with that assessment. He added that given what the Commission <br />knew, he believed it would be irresponsible to choose Option 1. He stated that he believed the <br />applicant should properly construct this pool, which would require tearing it out and starting <br />over. <br />PLANNING COMMISSION MINUTES, May 21, 2008 Page 21 of 26 <br />
The URL can be used to link to this page
Your browser does not support the video tag.