My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSA - SUNSHINE ORDINANCE
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2012
>
09/17/2012
>
WSA - SUNSHINE ORDINANCE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/1/2012 1:25:41 PM
Creation date
9/13/2012 5:31:10 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
City Manager's Office
Item #
WSA
Date
9/17/2012
Destruction Year
2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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
(b) Number and timing of community meeting: For those development <br />projects that meet the criteria listed in Sec. 2-153(a) the applicant shall hold one <br />community meeting no later than 20 days after submittal of an application for <br />administrative site plan review. Should the applicant fail to hold the community <br />meeting within this time, the completion of administrative site plan review shall be <br />delayed until such time as the community meeting is held. <br />(c) Noticing: Notice of the community meeting shall be provided to all <br />property owners, and occupants having a valid United States Postal Service <br />address within a 500 foot radius of the subject property. Said notice shall be <br />mailed no less than 10 days prior to the community meeting. The notice shall <br />also be posted on the development project site and published in a newspaper of <br />general circulation no less than 10 days prior to the community meeting. The City <br />shall then post the notice on the City's website. It shall be the sole responsibility <br />of the applicant to prepare and distribute this notice. <br />(d) Notice content: The notice shall include the time, place and date of <br />the 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 notice <br />shall be written in English and Spanish and include instructions as to how to <br />request language interpretation services for those wishing to have interpretation <br />during the community meeting in languages other than English. <br />(e) Community meeting time and place: The community meeting <br />should be held either on a weeknight during the early evening hours or on a <br />Saturday. If there are special circumstances under which it is more convenient <br />for the meeting attendees to attend the meeting at a different time, the applicant <br />may adjust the meeting time accordingly. The meeting shall be held in any facility <br />that is accessible to the public and that is no more than 1 mile from the project <br />site. Should there not be any such facilities available in the required area, the <br />applicant may arrange, at their own expense and subject to availabijity, to use <br />the next closest City facility. <br />(f) Community meeting language interpretation: Should the applicant <br />receive a request for language interpretation services prior to the meeting, it shall <br />be the applicant's responsibility to arrange for such services to be available at the <br />community meeting. <br />(g) Community meeting format and content: During the community <br />meeting the applicant should give a presentation detailing the components of the <br />proposed development project and a description of any impacts or benefits to the <br />community, and provide contact information so that members of the public can <br />contact them for further information. The applicant should allow enough time for <br />the attendees to ask questions and provide input. The applicant shall prepare <br />Ordinance No. NS-XXX <br />Page 4 of 10 <br />WSA-10
The URL can be used to link to this page
Your browser does not support the video tag.