My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-26-26 Planning Commission Meeting
LakeElmo
>
Commissions and Committees
>
6 - Planning Commission
>
02 - Packets
>
2020's
>
2026
>
01-26-26 Planning Commission Meeting
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/6/2026 3:11:06 PM
Creation date
2/6/2026 3:10:06 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
32 <br />LA515\1\1066805.v2 <br />development of such stages or units shall be submitted stating the <br />approximate beginning and completion date for each such stage or unit and <br />the proportion of the total PUD public or common open space and dwelling <br />units to be provided or constructed during each such state and overall <br />chronology of development to be followed from stage to stage. <br />11. When the proposed PUD includes provisions for public or common open <br />space or service facilities, a statement describing the provision that is to be <br />made for the care and maintenance of such open space or service facilities. <br />12. Any restrictive covenants that are to be recorded with respect to property <br />included in the proposed PUD. <br />13. Schematic utilities plans indicating placement of water, sanitary and storm <br />sewers infrastructure and systems. <br />14. Applicable plans must meet or exceed the requirements of the City’s <br />Engineering Design and Construction Manual. <br />15. Any additional information deemed necessary and required by the Planning <br />Director. The Planning Director may waive for good cause certain <br />information requirements not pertinent to the particular request. <br />16. The City may excuse an applicant from submitting any specific item of <br />information or document required in this stage which it finds to be <br />unnecessary to the consideration of the specific proposal. <br />17. The City may require the submission of any additional information or <br />documentation which it may find necessary or appropriate to full <br />consideration of the proposed PUD. <br />3. PUD preliminary plan review. <br />1. As part of the review process for a PUD preliminary plan, the Planning <br />Director shall review the PUD, and shall prepare a report and make a <br />recommendation about the proposed preliminary PUD plan for Planning <br />Commission and City Council consideration. <br />2. The Planning Director shall prepare a draft ordinance to establish the <br />potential PUD overlay zoning district to be established as a component of <br />the PUD final plan. <br />3. The Planning Commission shall hold a public hearing and report its findings <br />and make recommendations to the City Council on the merit, needed <br />changes and suggested conditions the City should impose on the PUD. <br />4. The City Council shall review and finalize the ordinance. Adoption and <br />publication of an overlay district ordinance shall occur upon approval of the <br />preliminary PUD. The effective date of the ordinance shall be upon <br />approval of the final PUD. <br />4. Effect of a PUD preliminary plan review. The approved PUD preliminary plan and <br />ordinance governs the preparation of the PUD final plan. The applicant or developer <br />shall submit the proposed PUD final plan to the City for final approval in <br />accordance with the requirements of this title. <br />5. Limitation of approval. The City Council’s approval of a PUD preliminary plan <br />shall remain valid for a period of 180 days, unless a request for time extension of <br />up to one (1) year is submitted in writing to the City and approved by the City <br />Council. (See subsection (c)(4) of this section about PUD time limits.)
The URL can be used to link to this page
Your browser does not support the video tag.