My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
7.2 SR 06-01-2020
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2011 - 2020
>
2020
>
06-01-2020
>
7.2 SR 06-01-2020
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/23/2020 3:46:01 PM
Creation date
5/29/2020 9:20:50 AM
Metadata
Fields
Template:
City Government
type
SR
date
6/1/2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
69
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
Jill: What type of residential — like how many residential units could go in there right now without a <br />PUD? <br />Zack: Right now it's zoned business park, so it would have to be rezoned to a residential district. I <br />would say it would have to either be an R-3 to be townhome standards or R-4 high density <br />residential, but it would have to be rezoned. Right now it's a business park with underlying land <br />use of mixed use residential. So it could be different, it could be townhomes, it could be an <br />apartment building, it could be other options but as it stands today, without some sort of <br />change, it would only be a business park use. <br />Jill: Okay. I was just thrown where it said that it's guided for mixed use and residential uses are <br />permitted. But it isn't actually permitted right now, it would need to be rezoned? <br />Zack: Correct, it's permitted under the land use guidance, not under the current zoning. <br />Jill: The only comment I would want to add, we've had some experiences as a city where we've put <br />PUDs in industrial parks, and then when those industrial locations look to expand or change or <br />do anything different or request CUPS for themselves, it creates a significant amount of tension <br />between homeowners and business owners. As I look at this, that's what I'm concerned about, I <br />think about over by Casey's and the PUD we have over in that area and the sheer volume of <br />high-tension issues that we've had between business and homeowners. I know we don't have a <br />crystal ball to see the future but I'm a little bit concerned about this, going in there and just <br />creating problems from here on out. Because it is right in the middle of business park, an <br />industry, and those businesses have a right to expand and change and do things differently in <br />the future as well. So that's my main concern with it <br />Rob: I have to echo with Jill, that's kind of where I was headed with my question. Is the inconsistent <br />businesses on each side of this, are we creating a problem where we're making another <br />exception in an area it's not suited for? I know technically, but realistically, what's going to <br />happen if someone else wants to put something in that's incompatible with both of the other <br />two uses but we've already set a precedent for that. I just get concerned about shoving that <br />many people in to that area and then expecting everyone to be able to get in and out of there. <br />Eric: I guess to that too, both Jill and Rob bring up an interesting point, when you look at the property <br />directly to the south, if a business park were to go in there, how would that affect all these <br />residents having even something noisier closer by. <br />Nate: In effect it's almost a spot zone. If you insert residential in between two industrials like that. <br />Eric: Right. Well business park and industrial. <br />Nate: Well yea, yea, exactly. That's a great point, Jill. <br />Rob: But effectively we have done that with Xavier Circle down there already, but -- <br />Eric: But to the south of that is also residential. It's not quite as boxed in as this development would <br />be. But this is a lot more homes you're talking about, 29 verses whatever was there. <br />
The URL can be used to link to this page
Your browser does not support the video tag.