My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Planning Commission Agenda and Packet 2025 01 09
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
PLANNING COMMISSION
>
2025 Planning Commission Agendas Packets Minutes
>
Planning Commission Agenda and Packet 2025 01 09
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/19/2025 12:00:53 PM
Creation date
2/19/2025 11:41:23 AM
Metadata
Fields
Template:
City Council Records
Meeting Date
1/9/2025
Doc Type
Boards Commissions Committees Records
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
109
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).
Show annotations
View images
View plain text
Planning Commission <br />Meeting Minutes <br />September 12, 2024 <br />Page 7 of 12 <br />improvement planning process, but Post indicated that it was unlikely the 5-foot reduction <br />would be supported there either. <br />Choi asked about the traffic impacts on the broader area, particularly given the lack of a <br />left -out onto South Boulder Road. He wondered if any consideration had been given to <br />that issue. <br />Fowlkes said they hadn't explored that specific subject yet. He mentioned that Canon <br />Circle did have a left -out, and that future traffic restrictions would be considered as the <br />development progressed. <br />Choi asked for clarification regarding the inclusionary housing issue, noting that the <br />applicant wanted to pursue the Voluntary Alternative Agreement. He pointed out that the <br />staff presentation recommended that "the applicant can choose between the Voluntary <br />Alternative Agreement or the Inclusionary Housing Agreement." <br />Post explained that the exact arrangement was still to be determined but had been <br />brought up in the meeting due to how long the matter had been under review by staff. <br />Bangs asked whether the decision on which agreement to follow would affect the fiscal <br />analysis. <br />Post confirmed that it would, but that the fiscal analysis would need to be re -run based <br />on whichever agreement was selected. <br />Brauneis asked about the language in the city ordinance regarding the 12% of units <br />required for inclusionary housing, noting that the language seemed somewhat broad. <br />Post explained that the ordinance provided multiple options for satisfying the inclusionary <br />housing requirements, and the language was intended to allow flexibility in meeting the <br />goals. <br />Brauneis asked if the ordinance could be satisfied by including micro -units. <br />Post responded that if the applicant were proposing to include 12% of units for <br />inclusionary housing, those units would likely need to be similar in size and design to the <br />other units on the site. Staff would not accept micro -town homes as part of the 12%, since <br />they would not be considered comparable to the other units in the development. <br />Bangs asked about the setbacks, specifically about the request for setbacks to be <br />anywhere from 6 to 20 feet in relation to fire mitigation, and whether a 6-foot setback <br />would be acceptable. <br />Post responded that, from a fire mitigation perspective, Planning wouldn't review or <br />approve setbacks until the building permit stage. However, Louisville Fire Protection had <br />reviewed the proposal for emergency access and had no additional comments at this <br />point. <br />Moline asked about the rezoning to MU -Residential, specifically how it was required to <br />have two distinct uses, which he believed would be residential and commercial. <br />Post agreed with Moline's statement. <br />Applicant Presentation: <br />City of Louisville <br />Community Development 749 Main Street Louisville CO 80027 <br />303.335.4592 www.LouisvilleCO.gov <br />
The URL can be used to link to this page
Your browser does not support the video tag.