My WebLink
|
Help
|
About
|
Sign Out
SR 05:069
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2005
>
SR 05:069
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2005 1:59:43 PM
Creation date
3/10/2005 12:50:28 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT DATE
3/15/2005
DESTRUCT DATE
15 Y
DOCUMENT NO
SR 05:069
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
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
by staff and was discussed by the Planning Commission and City Council at their public bear- <br />ings. Copies of the neighbors' petitions in favor of the sidewalk connection and in opposition to <br />the sidewalk connection are attached. The Bozorgzads believe that Condition No. 8 provides the <br />ability to revisit the sidewalk's location even though there is an existing easement for the side- <br />walk's location. <br /> <br />Present Proposal and Issues <br /> <br />Hoss and Mojgan Bozorgzad have stated their opposition to the sidewalk connection because of <br />potential impacts to the privacy of their home and requested that it be deleted from the proposed <br />project. In an effort to resolve the issues on the sidewalk, there have been substantial discus- <br />sions involving Mr. Bozorgzad, the applicants, and staff, including an on-site meeting. The ap- <br />plicants agreed to several continuances of the public hearing in order to work out the sidewalk <br />issues and other neighbor issues. <br /> <br />To address the Bozorgzads privacy concerns, staff committed its support to Mr. Bozorgzad re- <br />placing the existing open fence with a six-foot tall solid wall/fence. In staff's opinion, the solid <br />wall/fence would effectively screen his property from the view of pedestrians on the sidewalk. <br />However, prior to the Planning Commission's public hearing, there remained unresolved issues <br />including: <br /> <br />· The location of the public sidewalk with respect to the Bozorgzads' property - the Bo- <br /> zorgzads wanted the sidewalk moved farther into the subject property. <br />· The location of the previously mentioned solid wall/fence in relation to the Bo- <br /> zorgzads' existing driveway - the Bozorgzads wanted a minimum three-foot separa- <br /> tion between the relocated wall/fence and their driveway to accommodate landscaping <br /> that would screen the wall from the view of their home. <br />· Relocating the existing eight-inch water line - the water line must be relocated to ac- <br /> commodate the relocated wall/fence. Otherwise, the relocated wall/fence would be sit- <br /> uated directly over the water line. <br />· Payment of the costs for the construction of wall and the relocated water line. <br />· Reimbursement of the applicants' portion of the costs borne by the Bozorgzads to con- <br /> struct Sycamore Terrace. Staff notes that there is a current reimbursement agreement <br /> providing civil means to resolve this issue. <br /> <br />From a design/construction standpoint, the above-mentioned items can be done. The stumbling <br />point has been who would pay the costs of their implementation, e.g., the applicants totally or <br />shared between the applicants and the Bozorgzads. Staff understands that the applicants would <br />not be receptive towards paying the total costs but would be receptive to sharing the costs with <br />the Bozorgzads. Staff would not support the Bozorgzards' request that the City require the appli- <br />cants pay the costs to relocate the sidewalk, pay for the construction of the wall, and relocate the <br />waterline because the required nexus for such a requirement would be absent. The issue regard- <br /> <br />SR 05.'069 <br />Page 6 of ! 5 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.