My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
31C - CUP - 2800 N MAIN STREET UNIT 3100
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2014
>
09/16/2014
>
31C - CUP - 2800 N MAIN STREET UNIT 3100
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/11/2014 4:54:24 PM
Creation date
9/11/2014 4:49:29 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Planning & Building
Item #
31C
Date
9/16/2014
Destruction Year
2019
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
Mr. Gregg Berwin <br />June 9, 2014 <br />Page 4 <br />Previous Variance <br />The City has previously approved a parking variance for MPM resulting in a reduction to the <br />Code requirement. Variance 96 -01 (approved April 1996) established an overall parking supply <br />ratio requirement of 4.1 spaces per 1,000 sf at MPM. As detailed in Table 2, the variance <br />requires a total parking supply of 4,635 spaces based upon the 1,130,523 sf available upon <br />completion of the Project. The total future parking supply of 4,940 spaces maintains consistency <br />with the previous parking variance by providing an overall ratio of 4.4 spaces per 1,000 sf. <br />Parkins Summary <br />Based on the future on -site parking supply of 4,940 spaces, the Project would not be able to <br />satisfy the Code parking requirements; a deficit of approximately 2,137 parking spaces is <br />anticipated. <br />Conversely, the proposed future parking supply of 4,940 spaces is able to adequately satisfy the <br />requirements of Variance 96 -01; a surplus of approximately 305 spaces is anticipated. Although <br />the parking supply is consistent with the requirements of the approved variance, a shared <br />parking analysis was prepared to determine the adequacy of the parking supply during periods <br />of peak demand and with the introduction of new uses to MPM. <br />SHARED PARKING <br />The shared parking analysis is based upon Shared Parking, 2nd Edition (Urban Land Institute <br />[ULI] and the International Council of Shopping Centers [ICSC], 2005). As part of their national <br />research on shared parking, ULI and ICSC developed a database that identifies the peak <br />parking demand for every land use typically found within a mixed -use development. This <br />national research database forms the basis for the assumptions in the shared parking model. <br />Shared Parking, 2 "d Edition describes shared parking as follows: <br />"Shared parking is defined as parking space that can be used to serve two or more <br />individual land uses without conflict or encroachment. The opportunity to implement shared <br />parking is the result of two conditions: <br />• Variations in the peak accumulation of parked vehicles as the result of different activity <br />patterns of adjacent or nearby land uses (by hour, by day, by season) <br />Relationships among land use activities that result in people's attraction to two or more <br />land uses on a single auto trip to a given area or development" <br />Most zoning codes provide peak parking ratios for individual land uses. While this appropriately <br />recognizes that separate land uses generate different parking demands on an individual basis, it <br />does not reflect the fact that the combined peak parking demand, when a mixture of land uses <br />shares the same parking supply, can be substantially less than the sum of the individual <br />demands, as is common of shopping centers like MPM. For example, retail uses peak in the early <br />to mid - afternoon while restaurant uses peak in the lunchtime and/or evening hours (depending on <br />the type of restaurant). <br />31 C -21 <br />
The URL can be used to link to this page
Your browser does not support the video tag.