My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 10/23/2012
Ramsey
>
Public
>
Agendas
>
Council
>
2012
>
Agenda - Council - 10/23/2012
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/18/2025 12:24:58 PM
Creation date
10/19/2012 1:33:34 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
10/23/2012
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
560
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
in parking facing Peridot Street NW. Since a building addition is planned it seems onerous to require an <br />architectural wall if it will eventually be removed for the building addition. Staff recommends installation of <br />landscape screening that meets the 3 feet height minimum along the entire west property line extending from the <br />northerly building line to the northerly property line to provide parking lot screening and a consistent "street <br />presence" of the site along this western edge. This suggested alternative is consistent with past practices and <br />approvals of other phased developments in the COR. At their meeting on October 4th, the Planning Commission <br />supported this condition as an alternative to a screen wall. <br />Required sidewalk and streetscaping is installed along the entire portion of Sunwood Drive. The applicant will be <br />responsible for a similar pattern of sidewalk and streetscaping consisting of landscaping, street furniture and <br />lighting along Peridot Street NW. <br />The COR Design Framework establishes parameters for parking in all subdistricts and sets a minimum parking <br />space standard of one space per five seats for places of assembly (with a maximum of one per three seats). The <br />guidelines also support the use a wide range of parking options to fulfill required parking including use of on -street <br />parking and encouraging shared parking solutions. Based on the total of 504 seats at 1 space per 5 seats a total of <br />101 parking stalls are required. The applicant is proposing 43 on -site parking stalls, 40 proof of parking stalls <br />(on -site) and 25 on street parking stalls (along Peridot Street NW and 145th Avenue NW) to fulfill its required <br />parking. <br />While this shared method of parking is different than other "typical" sites in Ramsey, it is the intent in the COR that <br />sites minimize surface parking and create strategies for shared parking between adjacent users particularly when <br />taking advantage of peak and off peak parking cycles. This proposal is an excellent candidate for alternative <br />parking arrangements due to their primary use on Sunday mornings and evenings, opposite of other users <br />immediately adjacent to the site. The applicant has provided a summary of information regarding their proposed use <br />and its intent to install only the parking it needs while relying on shared and joint parking and facility use with <br />PACT, NAU, Allina, the City, and other community groups. The Design Framework states that the City may <br />approve joint parking for one or more businesses where the total number of parking stalls provided for joint use is <br />less than the sum of the total required for each business should they be provide them separately. A written report, as <br />detailed on Page 21 of the Design Framework, is required. Staff is generally supportive of the use of on -street <br />parking for the proposed use, as no parking structures (vertical) are planned in this area. <br />It is important to note that the first phase construction could meet required parking if the City required the <br />construction of 40 additional stalls, accepted the proposed proof of parking alternative. The applicant is proposing <br />proof of parking as a method to save initial site development and construction costs. The applicant intends to utilize <br />shared parking through cross -parking agreements with PACT, Allina and NAU. Again, the COR Design Framework <br />encourages shared parking as a method to provide required off-street parking. However, any shared parking shall be <br />approved only when it's in close proximity, no conflict in hours and a legally binding instrument for joint use of <br />off-street parking is approved by the City and recorded at the County. While the Northgate intends to share parking <br />through "cross -parking agreements", and has an effective history of doing so, no recordable document has been <br />provided to the City therefore the site is not meeting minimum requirements for off-street parking. This leaves the <br />City in the position of needing to make a decision on whether to support the proposed proof of parking or require <br />installation of the 40 stalls during Phase 1. Options to consider include: <br />• Require full parking to be installed with Phase 1 due to lack of legally recordable shared parking agreements to <br />meet requirements of the COR Design Framework. <br />• Provide City with legally recordable shared cross -parking agreement. <br />• Accept proof of parking plan with a condition that at such time that parking demand is beyond what is provided <br />on -site and the 25 accepted on -street parking stalls, and extending into additional on -street parking areas beyond <br />300' radius of the site, such proof of parking shall be installed at the applicants expense. <br />The Planning Commission discussed the proposed parking plan and agreed that a combination of on -street, on -site <br />and use of proof of parking is acceptable for this use for the Phase one construction. The Planning <br />Commission supported the condition that proof of parking may be utilized as written in the Conditional Use Permit <br />resolution. <br />
The URL can be used to link to this page
Your browser does not support the video tag.