My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CC MINUTES 06262001
StAnthony
>
City Council
>
City Council Minutes
>
2001
>
CC MINUTES 06262001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/19/2016 5:35:52 PM
Creation date
4/19/2016 5:35:51 PM
Metadata
Fields
SP Box #
36
SP Folder Name
CC MINUTES AND AGENDAS 2001
SP Name
CC MINUTES 06262001
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
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
City Council Regular Meeting Minutes <br /> June 26, 2001 <br /> Page 5 <br /> they not tie the hands of the development community, by getting too specific. Mr. Rapp added that if <br /> 2 the City is too specific, they limit their choices as well as the quality and responsiveness of the <br /> 3 development community. Instead, he urged the Council to focus on a general framework, that is <br /> 4 flexible and allows for input by the developer. <br /> s Mr. Rapp continued by stating that it is a partnership between the City and the developer. He indicated <br /> 6 that they would clearly document everything that the community has said, and that it would be included <br /> 7 in their recommendations in the Concept Plans. Yet, he added, they had to allow the development <br /> s community to have a stake in the project with them. Mr. Rapp identified other communities (Burnsville <br /> 9 and St. Louis Park) that have gone through large-scale re-development projects, who learned that <br /> 10 being too specific on the front-end cost them time, money, and choices in the end. <br /> 11 Mr. Rapp stated that their role is to get them to the point of having Concept Plans to examine, but <br /> 12 stated they will not make a recommendation to them as to which Plan they believe they should choose. <br /> 13 Then, he added, Ehlers and Associates, will represent them through the process of selecting a <br /> 14 developer, and learning the financial implications associated with the project. <br /> Councilmember Horst asked what, specifically, would be provided them. Mr. Rapp responded that <br /> they will receive the cost of the project, the implications for the city, and the feasibility in the <br /> 17 marketplace. <br /> 18 Councilmember Horst added that, looking at some of the criteria, it seems ambitious. Mr. Rapp stated <br /> 19 that the people working on the project have a tremendous amount of experience, and that some of the <br /> 20 information to be distributed at the next meeting is already prepared. <br /> 21 Mr. Rapp stated that, collaboratively, they will work with a developer on details like color of brick, <br /> 22 and placement of architectural features. Councilmember Horst added that the details have bogged <br /> 23 down this process in the past, and asked what the skeleton was going to look like. Mr. Rapp indicated <br /> 24 that there would be two Concept Plans to examine. <br /> 25 Mr. Rapp continued that there would exist criteria associated with each particular Plan, such as <br /> 26 estimated cost per square foot used in anticipating the level of development they would want to see <br /> 27 there. Mr. Rapp stated that they would need to decide on the removal of the building. He added that <br /> 28 was an implication that would be identified within the report. <br /> 29 Mr. Rapp stated that the City always has the option to do nothing, and that it was important that they <br /> 30 be aware of that. <br /> R1 Mayor Cavanaugh stated that, when they started this process, it was implied that they retained DSU in <br /> 2 order to give them a recommendation. Mr. Rapp responded that they would be giving them two <br /> 33 Concept Plans, each with pros and cons attached to them, and an indication that the market would <br /> 34 respond to both of them, but in different ways. <br />
The URL can be used to link to this page
Your browser does not support the video tag.