![](https://davisvanguard.org/wp-content/uploads/2021/05/noise-ordinance-765x510.jpg)
Because the City of Davis is considering a revised sound ordinance, I thought it would be helpful to hear from Robert Lawson, a sound professional, who recently posted the following informative piece on Nextdoor.com.
By David L. Johnson, Davis
I am a Certified Industrial Hygienist and Certified Safety Professional with over 35 years experience taking sound level measurements and commenting on noise issues as a part of the CEQA process.
1. It is unusual, and in my opinion a bad idea, to base the City of Davis noise ordinance in large part on sound levels averaged over a 1 hour period (l eq – 60 minutes).
Unusual?
Color coded noise ordinances from several other communities with University of California campuses (Berkeley, Los Angeles, Riverside, San Diego, San Francisco, Santa Barbara) as well as from Sacramento are available at https://nonoise.org/regulation/stateregs.htm .
Unless I’m mistaken, only San Diego uses l eq – 60 minutes. Although several use a sliding scale for averaged sound levels (30 minutes to 5 minutes, based on sound levels) most of these have specific mention or provisions for impulsive noise (noise of very short duration with a sharp onset), which is the type of noise that has had much discussion lately in town in regards to recreational equipment.
The nonoise.org site also includes a summary review of hundreds of ordinances across the country, indicating that 60 minute averaging (l eq 60 mins) is not common in community noise ordinances.
2. It could be costly and difficult to enforce a noise ordinance largely based on average noise levels over a 60 minute period.
Costly/difficult to enforce?
An employee of the city or a contractor would be required to personally perform the one hour measurement in order to have an enforceable result. At an hourly employee wage, this would be costly. Unless the noise equipment is attended at all times (or somehow installed in a remote protected place), the equipment is easily subject to tampering (to either raise or lower the number) making the result indefensible.
3. Sound levels averaged over a 1 hour period (l eq – 60 minutes) are particularly ill-suited for evaluating short, sharp noises – often called “impulsive” noise (such as metal pieces clanging together, a fire cracker, a gunshot, a roofing nail gun). The two biggest problems are the effect of averaging, and the slow-response setting that is typically used for the measurement.
Sound averaging bad for occasional loud noises?
The longer the averaging period, the easier it is for truly high numbers to disappear. Imagine a 1-hour drive. You average 100 mph for 5 minutes and 60 mph for 55 minutes. Your average speed for the one hour trip is 63 mph. A similar thing happens when you average sound over a 1 hour period (though, because sound is on a logarithmic scale the calculation is not intuitive).
Typical 1-hour average sound measurement settings (slow-response setting on the meter) bad for short/sharp noises?
A typical long-term average sound level measurement uses either the A scale/slow response or C scale/slow response setting. The effect of the slow response setting is to grossly under-report the actual highest level the sound reaches. In the worst case (such as high caliber rifles) the slow response setting will under-report the actual peak sound level by 10’s of decibels, but this effect will be seen for any short/sharp noise.
That is the reason most of referenced noise ordinances include a special definition for “impulsive noise.” If I recall, however, only the Los Angeles and San Francisco ordinances say that impulsive noise should not be measured on the slow scale, reflecting a low level of technical sophistication in the other ordinances. (Sacramento includes a provision for adjusting allowable levels for impulsive noise, but does not clarify how impulsive noise should be measured.)
A note on 1 hour/slow response averaging. This type of measurement is typical for relatively steady background sound, such as from highways and factories (often sources that have some economic benefit and are hard and expensive to do anything about).
Robert Lawson
Would have been great to have gotten this article say YESTERDAY, when some people could have read it before the meeting. But not blaming the DV, blaming the CITY, for putting this out there with zero notice before a holiday weekend we all just returned from. Booooooooo! Bad City!
Gee… someone broached the same issues… May 30, ~3:30…
Still, as that somebody already said, notice was poor… folk can just ask a CC member to move to defer hearing/action for a couple/3 weeks… simple solution…
Or, one could just say,
Real constructive… “good choice”… much easier than contacting CC members…
Seems Item 8 was tabled.
“Yaaaaaaaay! Good City!”
If a noise ordinance falls at the City Council does it make a sound?
🙂 😉 🙂
Fits… there was no one there, too few CC members, who wanted ‘to hear it’…
Seriously… there needs to be several standards… is the noise continual? is it frequent, but sporadic… should it be based on a ‘sensitive receptor?… is it due to an emergency (sirens, emergency repairs on a waterline break, for examples)? time of day? In an emergency, should the City be exempt?
Mr Krovosa appears to believe there should be no distinctions… whatever…
The proposed revisions were not “ready for prime time”… would be interesting why the CC recognized that… I’m not judging the revisions… as I have before, questioning the ‘timing’… as have others…
There are times that incident related noises need to be sanctioned… other times when on-going noises are…
Sound levels vs. noise, can be in the ear of the beholder… sound levels can cause temporary/permanent hearing loss (not just ‘annoyance’)… pitch can be a factor [Alan M rightfully pointed that out, previously… if bass sounds are ones I can ‘feel’ (not just hearing), there is a problem]… sound volumes and ‘noise’ are multi-variable… the current ordinance somewhat addresses that… could we do better? Probably, yes…
The enforcement issue also looms large… costs… who does… when, how?
The changes proposed were not ready for ‘prime-time’, to be sure (factually, and ‘process’)… but the “answer” has complex variables… borders on “rocket science”…