Laserfiche WebLink
Commissioner Balch: ... yes, for this application. <br />Beaudin: ... for this particular application, and I think that's where I said we'll apply some <br />discretion. I think that if it's a small site and somebody's proposing a two -story structure <br />that's consistent with or maybe equal to or close to what's around it, maybe those story <br />poles become less relevant to the decision - making process. And then where people are <br />proposing larger buildings or things where we have some concerns about, maybe at the <br />staff level we can bring that to the workshop discussion and make sure that we flesh <br />that out a little bit more. <br />Chair Ritter: I agree. I don't think it should be a requirement for every project. I think if <br />it's going to have an impact. If the neighbor's view is going to get blocked or if it's going <br />to be a mass when you turn around the corner and you can't see around it from a .... <br />just want to make sure there's an intent that's needed; a purpose and not just to have <br />story poles on every project. If they are all below the height restrictions and all of that <br />you can't "not" approve a project if they're all within the codes that we have set up just <br />because it's purple and doesn't look good. Then the quality of the story poles could be <br />different on everybody. On some of those projects they're tipping over, so I don't know if <br />we have a certified story pole maker, but I'd just be careful in making a requirement of it <br />unless there's a purpose. <br />Commissioner Balch: And if I may, I apologize —this is jumping real fast. I'm also in the <br />position that the difficulty in knowing when they are required is almost impossible based <br />on what I think the process is. If an application comes in and it's a workshop, we can't <br />say we wanted story poles for the workshop or not at that point. You know, that's the <br />first time I think we're seeing it, right, unless we saw it in the future and then when it's <br />the next hearing item. So it's complicated. <br />Beaudin: Well, what I was going to add to that is I think there are cases where I think <br />staff recognizes that something may be out of character and I think for a workshop we <br />may make that request of the developer and we'll be very clear that this conversation <br />has been had and that's where we think there may be an opportunity to get way out in <br />front of and make sure that information is available to you for the workshop. There may <br />be other instances where that's not a staff position but it may come from the Planning <br />Commission and there will be ample opportunity between the workshop and the first <br />hearing on the project if that is the will of the Planning Commission. So there are <br />multiple opportunities. I don't want to make it "one size fits all it shall be done" because I <br />just think we see a variety of project types in the Downtown. <br />Commissioner Balch: Well, if I may, the motion that I made was more of a "one size fit <br />all" and I think I'll say that I'm probably backing off of that in light of Council's <br />conversation that I did observe. My position is that I noticed that the people who stood <br />up at Council —it wasn't the same group that comes here necessarily but it is a different <br />group that comes here and they do talk about their views a lot more and they may not <br />make it to Council, right? So they vet it here, so maybe it isn't necessary at the Council <br />level but it might be here. <br />Commissioner Nagler: Which I think is a point that's important for us to recognize; that <br />whether the Council, individual Council members took into consideration or wanted to <br />PLANNING COMMISSION MINUTES, September 14, 2016 Page 5 of 22 <br />