My WebLink
|
Help
|
About
|
Sign Out
18 ATTACH 05-06
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2015
>
121515
>
18 ATTACH 05-06
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/3/2017 11:01:40 AM
Creation date
12/9/2015 12:44:26 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
12/15/2015
DESTRUCT DATE
15Y
DOCUMENT NO
18 ATTACH 05-06
Document Relationships
18
(Message)
Path:
\CITY CLERK\AGENDA PACKETS\2015\121515
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
31
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
DRAFT <br /> Chair Allen stated that she would like to itemize the following issues for discussion by <br /> the Commission: commercial versus residential in relation to the front house; parking; <br /> building height; and the garage in front. <br /> Parking <br /> Chair Allen stated that she thinks there are five spaces, at a minimum, for which she <br /> would like to require in-lieu parking fees, and she could even argue for seven: the <br /> applicant is actually proposing to demolish two spaces; there are two existing on-site, <br /> the existing garage and the space associated with the little white house; and the net of <br /> three on-street parking spaces that are being lost. She stated that the project needs a <br /> PUD and the project needs five spaces. She asked staff to confirm what the parking <br /> demand need for the commercial space is, just using the standard methodology for <br /> saying the commercial is "X" amount of square feet and it would expect to have four <br /> cars. <br /> Mr. Luchini replied that it would be four spaces for the approximately 1,200 square feet, <br /> based on the standard of one parking space for every 300 square feet. <br /> Chair Allen stated that one question asked when considering any commercial building is <br /> how many people are going to visit, and based on the square footage of that property, <br /> how many spots would be expected to be required; staff indicated that would be four <br /> parking spots, and added to the three on-street parking spots lost to making space for <br /> the driveways, would make seven parking spaces. <br /> Commissioner Nagler inquired how many parking spaces currently exist on the street, <br /> contiguous to this lot, that are unaffected by this construction and could be used for <br /> commercial purpose. <br /> Commissioner Ritter stated that this is getting too complicated and asked what currently <br /> exists and what is being proposed. He requested confirmation that the applicants are <br /> asking to reduce two spaces less than what they currently have and, therefore, are <br /> paying in-lieu parking fee for the two spaces they are giving up on their lot space. <br /> Mr. Weinstein replied that the applicants initially were not proposing any payment of <br /> in-lieu fees, and what they are doing is getting rid of two on-site spaces and three <br /> on-street spaces. He reiterated that the Code requirements for payment of in-lieu fees <br /> for on-site spaces are unclear, but that is an interpretation that could be made; and <br /> there are no Code requirements for the payment of in-lieu fees for the removal of <br /> on-street parking spaces. He indicated that what staff is proposing as part of the <br /> Conditions of Approval is payment of in-lieu parking fees just for the three spaces on the <br /> street. He added, however, that it would be a valid and reasonable interpretation of the <br /> policy should the Commission decide that in-lieu parking fees should also be paid for <br /> the two on-site spaces as well. <br /> Commissioner Ritter inquired how many more spaces are being lost because of this <br /> development. <br /> DRAFT EXCERPT: PLANNING COMMISSION MINUTES, 11/182015 Page 11 of 22 <br />
The URL can be used to link to this page
Your browser does not support the video tag.