My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
20-1536 Amending ULDR Chapters I, II and IV
Laserfiche
>
City Clerk's Public Records
>
Ordinances
>
Ordinance Archives
>
2020's Ordinance Directory
>
2020 Ordinances
>
20-1536 Amending ULDR Chapters I, II and IV
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/17/2020 5:31:28 PM
Creation date
9/17/2020 5:31:19 PM
Metadata
Fields
Template:
City Clerk
City Clerk - Doc Type
Ordinances
City Clerk - Date
8/24/2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
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
e. Whether the proposed project renuires a traffic impact analysis. <br />f. Whether the property requires annexation. <br />g. The desired duration of the PUD agreement. <br />h. Any overlay districts that apply to the property. <br />i. A list of all federal, state, regional, county, or City -permit requirements. <br />j. Any additional information regarding the project and/or site design. <br />2. Supporting documentation required with application. <br />a. A legal description of the land comprising the PUD and identification of any <br />lands or outparcels to be exempt from the PUD agreement. <br />b. Proof of ownership. Legal instruments acceptableto the Citv Attorney which <br />clearly indicate persons having a legal and equitable ownership interest in the <br />subject property. Where ownership resides with a publicly held corporation whose <br />stock is traded on a nationally recognized stock exchange, the name and address of <br />the corporation and all of its principal executive officers will be sufficient. The <br />documentation shall also include an affirmation that no other persons have claims <br />or interests (known to the applicant, developer, or owners) which might affect their <br />right to develop the entire planned unit development as proposed. In the event that <br />any partnerships, joint ventures or other entities, other than individuals, own -a legal <br />or equitable interest in the subject property, all principals and other persons with <br />interest in such partnerships or joint ventures shall be revealed. In the event that <br />any corporation owns a legal or equitable interest in the subject property <br />officers and directors and any shareholder owning more than ten percent of the <br />interest in the corporation shall be revealed. <br />c. Mailing labels for all property owners within 500 ft. of the subject property. <br />d. Concept plan. The required components of the concept plan are provided in <br />Section 4-20.3(C). <br />e. Survey of the property.. A registered Florida surveyor's certified property <br />boundary survey depjctjng all pertinent title encumbrances and existing conditions <br />of the property and prepared no more than 12 months prior to the application <br />submittal. <br />f. Development schedule. A proposed development schedule indicating the <br />approximate starting and completion dates for the entire project and any phases <br />thereof, together with appropriate identification and conceptual description of such <br />hases. <br />g. Concurrency management. A preliminary assessment of the proposed <br />development's impact on available concurrency facilities capacity shall be <br />submitted. Article IX addresses concurrency management. The preliminary <br />assessment is intended to jdentifv whether any major potential problems exist <br />which constitute grounds for project denial or reassessment. The assessment should <br />review the project's proposed demands on public facilities and services, existing or <br />programmed, including transportation, water and wastewater services, solid waste <br />Ordinance 20-1536 <br />Page 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.