Browse
Search
Agenda - 05-17-2005-9c
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2000's
>
2005
>
Agenda - 05-17-2005
>
Agenda - 05-17-2005-9c
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/29/2008 9:29:41 PM
Creation date
8/29/2008 10:25:27 AM
Metadata
Fields
Template:
BOCC
Date
5/17/2005
Document Type
Agenda
Agenda Item
9c
Document Relationships
Minutes - 20050517
(Linked To)
Path:
\Board of County Commissioners\Minutes - Approved\2000's\2005
ORD-2005-023 - Proposed County Noise Control Ordinance Revisions
(Linked From)
Path:
\Board of County Commissioners\Ordinances\Ordinance 2000-2009\2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
25
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
decibels. Up to 60 d6(A) is the standard between 8:00 a.m. and 11:00 p.m; up to 50 dB(A) <br />from 11:00 p.m. to 8:00 a.m. The chart illustrates a range of decibel noise levels and general <br />activities. <br />There are three options. The first is to change the time or shorten the daytime periods when <br />louder noise is permissible. The second is to lower the permissible noise levels, and the third <br />may be a combination of the two. Staff are looking for input regarding what different time <br />periods are acceptable which would reflect when typical construction noise happens. Other <br />aspects include how and when noise readings are taken. The measurements are taken from <br />the adjacent property. People should be able to enjoy any noise on their property so long as it <br />does not intrude onto neighboring lands. A list of exceptions to the noise standards, with <br />suggested clarifications is incltaded along with additional language regarding registered vehicles <br />with mufflers. Violation and penalty increases are suggested as are nuisance noises (utilitarian <br />verses recreational noise). <br />The zoning ordinance has performance standards on noise and vibration and hopefully the two <br />noise standards will eventually match. <br />Commissioner Comments: <br />This discussion and public hearing is the result of on-going concerns from County citizens and <br />not a specific event. <br />How would noise be measured? At the adjacent property line, four feet above the ground, ten <br />feet from wall, barriers, or obstn~ctions. <br />Usually we have an ordinance available at the public hearing. Why isn't the proposed <br />ordinance presented? We did not want to lock in at this time specific revisions. Rather, we are <br />looking for input and guidance to shape the actual recommendations and bring back the <br />recommendations to the Commissioners at another meeting. <br />Do we have problems with the public hearing and the specifics of the proposed revisions? <br />Revisions to the Noise Control Ordinance do not require a public, hearing. The Commissioners <br />have free reign to proceed on this matter. <br />There are some problems with the definitions of noise. We should take the best of both <br />suggested noise definitions, but start with the second definition. We should address the <br />confusion and the different standards in the zoning ordinance. The higher standard would <br />prevail and there would be consistency. <br />We need a common sense definition, one that the normal person would know. What kind of <br />enforcement history with a definition, for instance the one used in Durham County, have other <br />communities experienced? <br />The proposed methodology of taking 100 noise readings, each ten seconds apart would require <br />nearly seventeen minutes, a significant amount of time. How would someone know? We need <br />a general definition, which the common person would know, and we should not increase the <br />penalties. <br />
The URL can be used to link to this page
Your browser does not support the video tag.