My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 30 - Sunshine Ordinance Amendments
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2023
>
05/16/2023 Special and Regular & Special HA
>
Item 30 - Sunshine Ordinance Amendments
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/10/2023 11:37:09 AM
Creation date
8/10/2023 11:37:06 AM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
30
Date
5/16/2023
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).
View images
View plain text
Ordinance No. NS-XXX Page 3 of 6 3 <br />153(a) shall be provided to all property owners and at least one (1) <br />occupant per tenant space having a valid United States Postal <br />Service address within: <br />a. A 2,000-foot radius of the subject property within the city <br />boundary; and <br />b. A 300-foot radius of the subject property where the notification <br />radius extends over the city boundary into another jurisdiction. <br /> <br />(2) Notice of any public hearings for projects that do not meet the criteria <br />listed in subsection 2-153(a) shall be provided to all property owners, <br />and at least one (1) occupant per tenant space having a valid United <br />States Postal Service address within: <br />a. A 1,000-foot radius of the subject property within the city <br />boundary; and <br />b. A 300-foot radius of the subject property where the notification <br />radius extends over the city boundary into another jurisdiction. <br /> <br />(3) Said notices shall be mailed no less than ten (10) days prior to the <br />community meeting or public hearing. The notice shall also be posted <br />on the development project website if the project meets the criteria <br />listed in subsection 2-153(a), and published in a newspaper of general <br />circulation no less than ten (10) days prior to the community meeting <br />or public hearing. The city shall then post the notice on the city's <br />website. It shall be the sole responsibility of the applicant to prepare <br />and distribute notices for any required community meeting. <br /> <br />(d) Notice content. The notice shall include the time, place and date of the <br />community meeting; a map depicting the location of the subject property, <br />including the properties contained within the notification boundary; a brief <br />description of the project; and the applicant's contact information. The <br />notice shall be written in English and Spanish and include instructions as <br />to how to request language interpretation services for those wishing to <br />have interpretation during the community meeting in languages other than <br />English and Spanish. <br /> <br />(e) Community meeting time and place. Community meetings shall be held <br />either on a weeknight during the early evening hours or on a Saturday. The <br />meetings shall be held in any facility that is accessible to the public and <br />that is no more than one (1) mile from the project site. Should there not be <br />any such facilities available in the required area, the applicant may <br />arrange, at their own expense and subject to availability, to use the next <br />closest city facility. <br /> <br />(f) Community meeting language interpretation. The applicant shall provide <br />language interpretation services for in-person attendees in Spanish during <br />all required meetings. Should the applicant receive a written request for <br />language interpretation services for languages other than Spanish no later <br />than forty-eight (48) hours prior to the meeting, the applicant shall provide <br />interpretation services for in-person attendees in the language requested.
The URL can be used to link to this page
Your browser does not support the video tag.