My WebLink
|
Help
|
About
|
Sign Out
23
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2007
>
011607
>
REGULAR MEETING
>
23
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/25/2007 12:07:47 PM
Creation date
1/11/2007 3:15:10 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT DATE
1/16/2007
DESTRUCT DATE
15 Y
DOCUMENT NO
23
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
157
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
<br />reduce the size of the building or construct a two-story structure. Furthermore, demolishing the <br />existing driveway and installing a new driveway at Stoneridge Drive would be undesirable from <br />a traffic flow perspective as parishioners wanting to travel westbound on Stoneridge Drive from <br />the church would first have to turn right (eastbound) onto Stoneridge Drive and then make a U- <br />turn in front of the church's existing Stoneridge Drive driveway where there is a median break. <br />This would also lead to internal queuing and congestion issues at the church's eastern parking <br />lot as parishioners wanting to turn left from the existing Stoneridge Drive driveway would have <br />to compete with the eastbound U-turn traffic from the church's western Stoneridge Drive <br />driveway. Based on the above discussion, staff feels that the existing Rheem Drive driveway <br />remain as currently constructed. <br /> <br />Parking <br /> <br />Users of the proposed parish center building would utilize the existing parking lots, which <br />currently have a total of 311 spaces. The proposal would eliminate 20 spaces to create a drop- <br />off area in front (east side) of the parish center and to create a pedestrian pathway through the <br />existing parking lots. The applicants have proposed to replace all 20 of these spaces by <br />restriping some of the existing standard-sized spaces to compact-sized spaces and by creating <br />seven new parking spaces within or adjacent to the existing parking lots, resulting in a total of <br />311 parking spaces. <br /> <br />Staff notes that the five proposed parallel spaces along the northern end of the western parking <br />lot would not meet the Municipal Code and fire truck access requirements as they would reduce <br />the width of the adjacent drive aisle from 26 feet 9 inches to 18 feet 3 inches, where a 20-foot <br />minimum is required, and would not provide adequate fire truck turning radii. Therefore, a <br />condition requires that these five spaces be removed from the plan. As a result, a total of 306 <br />on-site parking spaces would be available to accommodate the existing and proposed church- <br />related activities. <br /> <br />The Municipal Code requires that auditoriums, churches, private clubs and lodge halls, <br />community centers, mortuaries, sports arenas and stadiums, theaters, auction establishments and <br />other places of public assembly, including church, school, and college auditoriums provide one <br />parking space for every six fixed seats or one space for each sixty square feet of floor area <br />usable for seating if seats are not fixed in all facilities in which simultaneous use is probable as <br />determined by the Zoning Administrator. In this instance, one space for each six seats would <br />apply to the 835-fixed-seat sanctuary and one space for each 60 square feet of floor area would <br />apply to the 13,502 square feet of usable seating area in the proposed parish center without fixed <br />seating. <br /> <br />As shown in the table on the following page, the church's 306 parking spaces would not meet <br />the Municipal Code parking requirements for the 835-fixed-seat sanctuary (139 spaces) and the <br /> <br />Planning Commission <br /> <br />PDR-561/PV-158 <br /> <br />Page 15 <br />
The URL can be used to link to this page
Your browser does not support the video tag.