My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 01/08/2015
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2015
>
Agenda - Planning Commission - 01/08/2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:22:22 AM
Creation date
1/15/2015 12:12:59 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
01/08/2015
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.
/
344
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
May 14, 2014 Location: Fbrama>H::Drive>15153>Rndings/ port <br />In March, 2013 the City notified 250 surrounding property owners of the proposed data center <br />development. Said property owners were invited to attend a public open house in April 2013. Below is <br />a summary of input received: <br />Public comments were received from open house attendees; as well as non -attendees. In total, the Qty <br />received twenty-six (26) public comments. Of those, twenty-four (24) opposed a data center development <br />and two (2) were in favor of a data center development. <br />Gaff received an uncertified public petition in opposition of a data center development, and in support of <br />a residential development, from surrounding property owners, on April 26, 2013. Said petition included <br />sixty-nine (69) signatures. Qick hereto view. <br />General public inquiries included, but were not limited to, the use of the abject Ropertyas a school, <br />park, or renovated Rre Sation #2; and, inquiries as to whether a data center could be sited elsewhere in <br />the community. <br />Public comments in opposition of a data center included: concerns with decreased property values, <br />presence and view of data center being undesirable, compatibility with the character of surrounding <br />properties, noise, long term risk/potential re -use of the SObject R'operty, traffic and spot zoning. <br />For those in favor of a data center development, common public comments included concern with the <br />high traffic impact of a residential development; as well as, concerns that a residential development <br />would reduce the privacy of surrounding property owners (considering low impact and hours of operation <br />for a data center). <br />General FAQs See Appendix or Click Here <br />abject Property Reference Map: See Appendix or Dick Here <br />Development Cbmparison Chart: See Appendix or Oick Here <br />SECOND ROUND OF PUBU C INPUT, Simmer 2013 <br />In response to the first round of public input outlined above, the City revised and adjusted datacenter <br />site concept maps in an attempt to mitigate public concerns. In June 2013, the Ramsey ®A, PCand City <br />Council reviewed said revised data center site concept maps. <br />In July of 2013 the City Council directed Gaff to facilitate a second public input process. The purpose of <br />this second public input process was: to better understand under what circumstances would a data <br />center development be an acceptable use for the Sabject Property. <br />The key outcome of this second public input process is a proposal for Council consideration; which will <br />include (1) further documentation/ information addressing specific concerns (2) mitigation proposals <br />addressing specific concerns (3) updated site concept maps. This information was to be used by the City <br />Council before making a fi nal decision to submit a Comprehensive Ran Amendment and Zoning <br />Amendment application to allow for a potential data center development. <br />For detailed information on the OMCStudy Goup process, cee next section. <br />OMCStudy Goup, Findings Report (DR4F7) Page 6 of 42 <br />
The URL can be used to link to this page
Your browser does not support the video tag.