My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Planning Commission Minutes 2006 08 10
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
PLANNING COMMISSION
>
2000-2019 Planning Commission
>
2006 Planning Commission Agendas and Minutes
>
Planning Commission Minutes 2006 08 10
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2021 9:55:16 AM
Creation date
9/19/2006 11:53:00 AM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
PCMIN 2006 08 10
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
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 />AUGUST 10, 2006 <br />Page 7 of 10 <br /> <br />McCartney stated that is a valid point and suggested that a condition regarding that could be <br />added to the resolution of approval. <br />Lipton discussed the compliance to the Comprehensive Plan, density, the possibility of an <br />additional access point. <br />Dalton inquired about condition #9 and what is the objective of the condition. <br />McCartney stated that it came as a request from the Public Works department. <br />Sheets had questions for the applicant regarding landscaping and density. <br />Rozier explained the proposed fencing and the difference of yard and bulk requirements between <br />the current zoning and the proposed zoning. <br />Dalton asked for an accident count at South Boulder Road and McCaslin Blvd. and a comparison <br />to similar intersections. <br />Public Hearing Closed / Commission Comments: <br />Hartman stated that she agreed with the majority of the public comments and that the discussion <br />should start with the current entitlements. <br />Lipton stated that he understands the desire of the community to have more open space and he <br />appreciates the current owners willingness to dedicate Lots 1 and 2 on the west side of McCaslin <br />to the City as Open Space. <br />Deborski stated that the number of lots needs to be closer to the number of lots proposed during <br />the Comprehensive Plan which was 14. He agrees with the traffic issues that have been discussed <br />by the public. He also stated that the proposal is not what he wants for the “gateway” to <br />Louisville. <br />Pritchard sited the following: traffic access and safety; concerns with the fiscal analysis; <br />development should be 14 not 25 lots; and the development is not the “gateway” he expected for <br />Louisville. <br />Lipton discussed how this development can serve as the “gateway” to Louisville and as proposed <br />it is the nicest “gateway”. He requested that the Commissioner specifically discuss what they <br />want to see as the “gateway”. He continued with the following topics: traffic is not about volume <br />but safety; additional landscaping and not using prairie grass. <br />Loo reviewed her concerns with traffic and access to McCaslin. She also suggested that if seven <br />homes are built they would most likely have a value of $2M each, where this proposal is for a <br />home value of $400 - $500 thousand. <br />Sheets stated that she agreed with comments made by Loo and Lipton. She discussed her <br />concerns with traffic safety and the need for the City staff to complete a fiscal study. She also <br />appreciates the proposed land dedication to open space. <br />Dalton questioned if a lower speed on McCaslin would address some of the traffic safety <br />concerns. He stated that any development, no matter what size, would affect the view corridor. <br />He supports the development of the site but seven is not a sensible plan. He also requested that <br />the City complete a fiscal analysis. <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.