My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
City Council Agenda and Packet 1984 05 15
PORTAL
>
CITY COUNCIL RECORDS
>
AGENDAS & PACKETS (45.010)
>
1973-1989 City Council Agendas and Packets
>
1984 City Council Agendas and Packets
>
City Council Agenda and Packet 1984 05 15
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2021 1:46:53 PM
Creation date
12/29/2009 1:23:38 PM
Metadata
Fields
Template:
City Council Records
Doc Type
City Council Packet
Signed Date
5/15/1984
Supplemental fields
Test
CCAGPKT 1984 05 15
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
119
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
ILO Exhibit B <br /> 4111" <br /> MTH= Tali ma upon <br /> This report via compiled by en appointed Citizen's Task Force io response to <br /> a public appeal by Louisville Mayor Norbert Mier. On November 17, 15$3, Mayor <br /> Maier isetrreted the Task torte to make rscommmndatioae to the City Couonil <br /> wed Planning Cammissios. these recommendations were to be based on review sad <br /> brraetigaaoa of the seven charges contained within this revert. <br /> The Task force conducted an expansive review of available data end input <br /> information obtained !eon a variety of sources. The informatioa base is <br /> summarised at the end of this report. <br /> CLdGS No. 1 -- Is method of developrent in compliance with goals end general <br /> 1444reheaa ve Plan objectives? <br /> A. Apparently the method of development in Louisville is in compliance with <br /> the existing Comprehensive Plan's goats and objectives. However, it is <br /> the consensus of this Task Force that Louisville's Comprehensive Plan is <br /> lacking by definition and/or application in the following four erase: <br /> 1) The Comprehensive Plan does not provide clear guidelines for everyone <br /> concerned; city councils, citizens, and developers; <br /> 2) The Compreheasive Ilan does not establish goals for the City; <br /> 1) The Comprehensive Plan fails to tie together Louisville's general <br /> management policies, sod; <br /> 4) The Comprehensive Plan is not clearly a general policy document. <br /> 1. The current method of development appears to be in compliance because past <br /> City Councils wanted to be flexible regarding development policy. They <br /> did not clearly specify where given growth would occur. They winced to <br /> meet the changing views of the citiseary and take advantage of growth <br /> ' opportunities. This resulted in addressing growth on a piece-seal basis. <br /> The Comprehensive Plan was not used as a tool to project growth, but rather <br /> it was adjusted to suit the needs of growth. <br /> C. The current Comprehensive Plan doss not provide clear guidelines for <br /> everyone concerned regarding annexation; development phasing, open space <br /> ecquiattion and tnduacriel and commercial recruitment. Policies governing <br /> drnlopsest is Louisville are not cataloged and written in such a sinner <br /> that all interested parties can obtain and study those policies in order <br /> to readily understand their iaplicatioaa. <br /> The Teak Force recommends that Louisville's Comprehensive Plan be <br /> ' sapplaweated by genera po icy plow which address the dasaads of growth, <br /> davelopmsat and wishes of the citizens is the community. Phase policy <br /> plans must be readily accessible sad understandable to ail incarnated <br /> parties. <br /> D. The current Comprehensive Plan does not establish goal, as a general basis <br /> for action within the City. Iiatoricatly, the course of action has been <br /> to serge City goals with the end result of negotiations is the Planned <br /> Unit Development (PIUD) process. <br />
The URL can be used to link to this page
Your browser does not support the video tag.