My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Parks and Recreation Commission - 01/08/2015
Ramsey
>
Public
>
Agendas
>
Parks and Recreation Commission
>
2015
>
Agenda - Parks and Recreation Commission - 01/08/2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/25/2025 12:56:16 PM
Creation date
1/15/2015 12:26:06 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Parks and Recreation Commission
Document Date
01/08/2015
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
118
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
Park and Recreation Commission <br />Meeting Date: 01/08/2015 <br />By: Mark Riverblood, Engineering /Public <br />Works <br />Information <br />Title: <br />Begin Process of Public Engagement for the Proposed Municipal Plaza <br />Purpose /Background: <br />5.2. <br />As the case title introduces, the purpose of this agenda item is to invite public engagement for the proposed <br />Municipal Plaza, and also to discuss concepts and configurations. The park has been envisioned to be on the north <br />side of Sunwood Drive with its position being in many ways, the center of the Center of Ramsey or The COR. <br />As the Commission will recall, a similar invitation for ideas and public comment was issued for the lake feature in <br />The COR, and the Commission held an open house explicitly for this purpose. Much planning and visioning for the <br />park space called Lake Ramsey on the city's development plan remains. <br />There is a strong beneficial value to commercial and residential properties that abut quantity parks. For this reason, <br />expressing what either of these two proposed parks ('Lake Ramsey' and Municipal Plaza) may look like is useful in <br />attracting developers. Additionally, there can be cross - easements and shared uses for certain amenities and <br />infrastructure, E.g. a park may accommodate stormwater from an adjacent residential property, or a restaurant site <br />may have public /private paths that lead customers to the business, or an adjoining park may provide seating or <br />programming beneficial to a particular business. <br />Another reason that exploring concepts for the two proposed park together is timely, is that given their close <br />geographic relationship (and eventual connection in some manner), the public spaces should be complimentary in <br />opportunities for residents and visitors, and should have minimum redundancies in what they offer patrons in terms <br />of programming and experience. <br />Notification: <br />Observations /Alternatives: <br />Attached are three alternatives for the proposed Municipal Plaza. As indicated, Staff is seeking any and all feedback <br />from the Commission, residents and the business community. This invitation shall be extended via the city's web <br />site, and each commission, board and City Council will be asked to engage as well. In the end, the park space may <br />look and function like one of the concepts presented, a hybrid of the three - or something quite different. <br />It should be pointed out that there is no timeline per se, however ideally, a buyer may be found for the land adjacent <br />to the park(s) and a park development plan may be crafted that is synergistic with the new residential or commercial <br />land use. <br />Funding Source: <br />None required at this time. <br />Recommendation: <br />As indicated, Staff will continue to assimilate all comments on parks and public spaces within The COR - and so <br />Staffs recommendation is for Commissioners to have discussions with residents, friends and neighbors on these <br />planning endeavors, and share the feedback with Staff, within or aside from the regular Commission meeting. <br />
The URL can be used to link to this page
Your browser does not support the video tag.