My WebLink
|
Help
|
About
|
Sign Out
Home
Search
05-23-2016 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2016
>
05-23-2016 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2018 3:23:09 PM
Creation date
9/7/2016 1:32:06 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
05/23/2016
Council Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
89
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 WORK SESSION May 2, 2016 <br />DRAFT <br /> 5 <br /> 179 <br />4. Watermark Development Update – City Planner Larsen updated the council on 180 <br />the Watermark Project. A public hearing was held at the Planning and Zoning Board and 181 <br />three comments were received (none from Lino Lakes’ residents). The comments heard 182 <br />were about drainage, traffic, signals, buffers or noise walls. The Planning and Zoning 183 <br />Board discussed the lack of commercial development that was planned and one member 184 <br />still has concerns with the development being called mixed use under those terms. There 185 <br />were some minor changes proposed to the development based on P&Z discussion on 186 <br />traffic and those changes will be brought back to them. The design standards are still 187 <br />under review for the townhomes (they are mostly hammered out for the single family 188 <br />element). 189 <br /> 190 <br />Council Member Maher asked about the small parcel in the southwest corner of the map 191 <br />that isn’t included. Ms. Larsen said the property owners apparently are not interested in 192 <br />selling that land. 193 <br /> 194 <br />Mayor Reinert noted that this would be the largest development in the history of the city 195 <br />so it is a big consideration. He also noted that if this development wasn’t master 196 <br />planned, it would be split into many individual projects each looking for different things 197 <br />and probably higher density and different standards and quality. As a whole he feels this 198 <br />development looks good in its fit within the city. This being right against 35E and to get 199 <br />good quality in that location, he sees as a win for the city. The gross and actual density 200 <br />was noted and is fairly low. 201 <br /> 202 <br />Council Member Manthey noted that the project also ties into the city’s future plans in the 203 <br />area of drainage and improvements that are much needed. 204 <br /> 205 <br />Council Member Rafferty asked if this will be reviewed by the Public Safety Department 206 <br />and Ms. Larsen said they’ve been involved in the design review process from the 207 <br />beginning. 208 <br /> 209 <br />The mayor asked about remaining issues and Ms. Larsen noted design standards which 210 <br />will be a topic at the next Planning and Zoning Board meeting. Other than that, minor 211 <br />things like storm main location and impact on property lines, a trail connection and minor 212 <br />tweaks in the plat. The mayor asked about park dedication budget and Ms. Larsen said 213 <br />that isn’t finally determined as yet but she explained the areas that will be credited to the 214 <br />developer within the development (trails, private park land, etc). Mayor Reinert noted 215 <br />that he really likes the front end build out of the park and those inclusions for residents to 216 <br />use right away but he does understand that will have an impact on the park dedication 217 <br />fees. 218 <br /> 219 <br />Mayor Reinert discussed a communication plan, including proactively working with the 220 <br />newspaper to get information out about the development so that people can bring forward 221 <br />their questions. 222 <br /> 223
The URL can be used to link to this page
Your browser does not support the video tag.