My WebLink
|
Help
|
About
|
Sign Out
Home
pf_03350
Roseville
>
Planning Files
>
Old Numbering System (pre-2007)
>
PF3000 - PF3801
>
3300
>
pf_03350
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/17/2007 1:53:01 PM
Creation date
4/26/2005 11:47:03 AM
Metadata
Fields
Template:
Planning Files
Planning Files - Planning File #
3350
Planning Files - Type
Comprehensive Plan Amendment
Address
City of Roseville
Project Name
Comprehensive Plan Update
Applicant
City of Roseville
Status
Approved
Date Final City Council Action
1/28/2002
Date Final Planning Commission Action
12/12/2001
Additional Information
Approval of Annual (2001) Comp Plan Revisions
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
212
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
<br />The Capital Improvement Program (CIP) is required by State Statute 462.356 to be part <br />of the Comprehensive Plan review process in this sense: Annually, the Planning <br />Commission is to review the list of implementation projects (for 2002) and advise/affirm <br />whether they are consistent with land use provisions and policies of the Comprehensive <br />Plan. The Commission is also to review the remainder of the five-year CIP as a "guide" <br />and advise on consistency with the Plan or recommend changes in the Plan to create more <br />consistency. The Commission is not charged with the task of reviewing and advising on <br />financial feasibility or budgetary issues. <br /> <br />2.12 Section 12 - Appendices: Comprehensive Plan Appendices, Book 2 continues to be <br />updated to retain implementation programs and other works and "white papers" for each <br />Section. It also contains a summary of the five-year capital improvement program <br />consistent with the Comprehensive Plan. <br /> <br />3.0 STAFF RECOMMENDATION <br /> <br />3.1 The Community Development Department recommends opening the hearing, taking <br />comments and questions, then continue the hearing to the January 2, 2002 Planning <br />Commission meeting when the Plan as updated will be available for review. <br /> <br />4.0 PLANNING COMMISSION RECOMMENDATION PROCEDURE <br /> <br />4.1 On January 2,2002, the Planning Commission will re-open the required public hearing. <br />After accepting and discussing public comment, the Commission closes the hearing. By <br />a resolution the Planning Commission reaffirms the changes (and any <br />additions/deletions) made to the Plan during 2001, adopts the outline for placement in the <br />Plan and recommends that the changes be placed within the Comprehensive Plan, and <br />advises that the CIP is (is not) consistent with the Plan. The Plan is then sent to the <br />Council for its action. <br /> <br />4.2 Assuming that the City Council concurs with the Planning Commission, copies of the <br />Plan are distributed via the Internet and compact disk. Copies are also sent to the <br />Metropolitan Council to update the City's file, and notice of availability of the <br />Comprehensive Plan is distributed to surrounding cities. <br /> <br />5.0 SUGGESTED PLANNING COMMISSION ACTION <br /> <br />5.1 Open the public hearing on the Comprehensive Plan and 2001 Capital Improvement <br />Program (CIP) affirmation, request public comments on both and on the inclusion ofthe <br />updates/changes within the Comprehensive Plan. <br /> <br />5.2 Continue hearing to January 2,2002. <br /> <br />Report by: Thomas Paschke (490-2236) <br /> <br />Attachments: Outline of Text Revisions; Citizens Guide to Comp Plan, Executive Summary, Trend Report, Comp <br />Plan Amendment Process, Comp Plan Amendment Spreadsheet. <br />60-Day Time Limit: Not applicable. <br /> <br />PF 3350 - RPCA (12/12/01) - Page 4 of 4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.