Browse
Search
Minutes 05-27-2014
OrangeCountyNC
>
Board of County Commissioners
>
Minutes - Approved
>
2010's
>
2014
>
Minutes 05-27-2014
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/24/2015 11:28:11 AM
Creation date
9/5/2014 8:34:00 AM
Metadata
Fields
Template:
BOCC
Date
5/27/2014
Meeting Type
Public Hearing
Document Type
Minutes
Document Relationships
Agenda - 05-27-2014 - Agenda
(Attachment)
Path:
\Board of County Commissioners\BOCC Agendas\2010's\2014\Agenda - 05-27-2014 - Quarterly Public Hearing
Agenda - 05-27-2014 - C1
(Attachment)
Path:
\Board of County Commissioners\BOCC Agendas\2010's\2014\Agenda - 05-27-2014 - Quarterly Public Hearing
Agenda - 05-27-2014 - C2
(Attachment)
Path:
\Board of County Commissioners\BOCC Agendas\2010's\2014\Agenda - 05-27-2014 - Quarterly Public Hearing
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
77
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
locations are not scattered across the field as shown here, but rather are concentrated in 3 <br /> locations. So, this is the inverter transformer nearest to Cascade Drive, and there are 2 others <br /> located here and here. I want to note that this is not a single inverter. This is a station <br /> consisting —excuse me a 15 kilowatt station —wait let me think about that— 1500 kilowatt <br /> station rather than a 500 kilowatt station. So it's 3 of these 68 decibel producing units together. <br /> In addition, there is apparently a transformer associated with this, and transformers in <br /> themselves produce noise. So it's really very difficult to determine the total noise that's going to <br /> be produced from this unit, since we don't exactly know what the unit is comprised of. However, <br /> I attempted to calculate the noise from 3 separate 68 decibel sources, which is apparently what <br /> this includes without considering the additional noise that could be produced by a transformer. <br /> So I found the formula to do this on the web, and there is actually a place where you can plug in <br /> the numbers. I double checked the numbers by hand to make sure that they were correct, and <br /> instead of 68 decibels for this unit, it produces 77.54 decibels. That does not include any <br /> transformer noise. How much louder is 77.54 decibels? Well it's not a linear scale, so it's <br /> roughly 10 times, a little less than 10 times the sound pressure and twice the perceived <br /> loudness of 68 decibels. I then used the same methodology that the applicants used in their <br /> proposal here, in which they estimated the noise at different distances from the source. And <br /> you can see if you do it in meters it's a little bit easier because it's whole numbers, but a meter <br /> is about 3.3 feet. That with each doubling of distance from the source, the sound level drops by <br /> 6 decibels, and you can see this goes down by 6 decibels with every doubling of distance from <br /> the source. I then measured the distance from the inverter on Cascade Drive to my property <br /> line and got a different figure from Mr. Wallace. Using the scale on the site plan, I determined <br /> that the distance from the inverter on Cascade Drive to my property line was 104 feet <br /> approximately, as best as I could determine using that method. At that distance the sound level <br /> at my property line would be 47.54 decibels. So how loud is 47.54 decibels compared to the <br /> ambient sound on my property? I didn't have time to get a calibrated sound meter, but I did <br /> download an app that most people agree, at least online, is a fairly good and fairly accurate tool. <br /> We went out to our side yard at the property line near the development. The development <br /> would be on this side. This is Cascade Drive here. This is Falls coming in. That's my wife <br /> holding the meter, and that's the sign for the hearing. And this is what I saw. I did this a couple <br /> of times at different times of the day. We have about a 32 decibel background. I just want to <br /> point out that these little blips that you see is birdsong. So how much difference is 32 decibels <br /> from 47 decibels? Well it's 15 decibels and the perceived difference in sound levels is different <br /> from the decibel number, but for every 10 decibels there is roughly a doubling in perceived <br /> sound —the psycho acoustic sort of thing. So this means that the sound in my property <br /> boundary will apparently go up by about 3 fold at the property line. So, what I submit to you <br /> then is that the applicant's noise level data incorrectly states the locations and the types and the <br /> combined noise levels of the inverter transformers at the Binks site. It also emits the contribution <br /> of the step up transformer on the Cascade side; so we don't really know how much noise this <br /> thing is going to produce. <br /> At our property boundary there will be a continuous 47.5 decibel or greater inverter <br /> drone during the sunny days that will be perceived as being at least 3 times louder than the <br /> current ambient rural sounds. And since the applicants didn't base their laboratory noise <br /> analysis on triple inverter units and apparently did not factor in transformer noise, the noise <br /> levels could be even higher. I submit to you that the applicants' noise impact assessment is <br /> faulty as a result of using false assumptions about the types, configurations and locations of the <br /> inverter/transformer units; and that the applicants should be required to submit sound level <br /> testing data for the actual that they are going to install at the site and have proposed to use and <br /> then estimate the noise impacts from their true locations as depicted in the site plan. Thank <br /> you. <br />
The URL can be used to link to this page
Your browser does not support the video tag.