(A) Authority to file applications. Unless otherwise specified in this code, development review applications may be initiated by:
(1) The owner of the property that is the subject of the application; or
(2) The owner’s authorized agent; or
(3) The City of Springdale.
(B) Public notification for public hearings.
(1) Content. Notices for public hearings, whether by publication or written notice, shall at a minimum:
a) Identify the location and size of the subject property by its address or by legal description and the nearest cross street;
b) Indicate the date, time, and location of the public hearing;
c) Describe the nature, scope, and purpose of the application;
d) Identify the location where the public may view the application and related documents;
e) Include a statement that the public may appear at the public hearing, be heard, and submit written comments with respect to the application; and
f) Include a statement describing where written comments should be submitted prior to the public hearing.
(2) Notice requirements. Notification requirements for public hearings shall be provided as defined in Table 201-1: Public Notice Requirements.
Procedure | Section Reference | Notification on the Subject Property | Published Notice | Mailed Notice |
Procedure | Section Reference | Notification on the Subject Property | Published Notice | Mailed Notice |
Zoning Text or Map Amendments | Sign shall be placed by a representative of the city in the front yards of the subject property at least 15 days prior to the date of the public hearing | Must be published at least 15 days prior to the date of the public hearing | 15 days prior to the date of the public hearing | |
Conditional Use Permits | Sign shall be placed by a representative of the city in the front yards of the subject property at least 15 days prior to the date of the public hearing | Must be published at least 15 days prior to the date of the public hearing | 15 days prior to the date of the public hearing | |
Variances | Sign shall be placed by a representative of the city in the front yards of the subject property at least 15 days prior to the date of the public hearing | Must be published at least 15 days prior to the date of the public hearing | 15 days prior to the date of the public hearing | |
Appeals | Must be published at least 15 days prior to the date of the public hearing | 15 days prior to the date of the public hearing | ||
Planned Unit Development-Zone Map Amendment and Preliminary Redevelopment Plan | 153.255(F)(1) | Sign shall be placed by a representative of the city in the front yards of the subject property at least 15 days prior to the date of the public hearing | Must be published at least 15 days prior to the date of the public hearing | 15 days prior to the date of the public hearing |
T-District Zone Map Amendment and Preliminary Redevelopment Plan | 153.256(F)(1) | Sign shall be placed by a representative of the city in the front yards of the subject property at least 15 days prior to the date of the public hearing | Must be published at least 15 days prior to the date of the public hearing | 15 days prior to the date of the public hearing |
(3) Published notice. When provisions of this code require that notice be published, a representative of the city shall prepare the content of the notice and publish the notice in a newspaper of general circulation in the city. The content of the notification shall be consistent with § 153.201(B)(1): Content.
(4) Written notice. When provisions of this code require that written notice be sent, a representative of the city shall prepare the content of the notice and send the notice out as described below. The content of the notification shall be consistent with § 153.201(B)(1): Content.
a) Property owners of record, per the Hamilton County Auditor, within 300 feet of the subject parcel shall be notified by regular mail and shall include the information set forth in § 153.201(B)(1): Content.
b) Written notices shall be postmarked no later than the minimum number of days required in Table 201-1: Public Notice Requirements.
(Ord. 4-2016, passed 3-2-16)