Introduction to traffic-noise distance estimates
This traffic-noise distance calculator estimates how a roadside sound level may change between a reference position 10 m from the source and a more distant receiver, such as a home, garden, schoolyard, office façade, or property boundary. It subtracts a logarithmic distance loss and a user-selected ground-attenuation allowance from the reference level. The result is a transparent screening estimate, not a regulatory prediction.
Distance is only one part of roadside acoustics, but it is useful during early planning. A homeowner can compare possible patio locations, while a designer can test alternative building setbacks before detailed site modelling is available. The calculator does not infer a source level from traffic counts. You provide a measured or otherwise supported starting level, so the source assumption remains separate from the propagation calculation.
Enter the reference traffic-noise level, receiver distance, and ground-loss setting to estimate the sound level at the listening point.
How to use the roadside sound inputs
Enter the representative traffic level at 10 m, the source-to-receiver distance in metres, and the additional ground attenuation in dB per 100 m. Then select Estimate Level. Distance must be greater than zero because the formula contains a logarithm. Decimal values are accepted. For comparisons, change one input at a time or record every scenario so that its assumptions remain clear.
The reference level at 10 m is the acoustic starting point. Ideally, it comes from a representative measurement of the same road, traffic condition, pavement, and time period. It can also come from a trusted study or prediction method if the reference distance and sound metric are known. A value from an unrelated road may produce correct arithmetic but a poor practical estimate.
The reference metric matters as much as the number. Traffic noise may be reported as an hourly equivalent level, a day-evening-night indicator, a maximum pass-by level, or a statistical level such as L10. This calculator does not convert between those measures. If the input is an A-weighted hourly equivalent level, the output should be read as an estimated A-weighted hourly equivalent level under comparable source conditions.
The distance to receiver is the separation used for geometric spreading. Choose a meaningful source position, such as the road centreline or a representative traffic lane, and use that convention consistently. A wide road’s nearest lane, centreline, and far lane have different distances. If source and receiver elevations differ substantially, a slant-path distance may be more representative than a horizontal map measurement.
The ground attenuation field adds a simplified linear loss. A value of 0 applies no additional ground loss. A value of 1 subtracts 0.5 dB at 50 m, 1 dB at 100 m, and 1.5 dB at 150 m. This is a scenario setting rather than an automatic classification of grass, soil, pavement, or water. Negative values describe amplification rather than attenuation and will normally be unsuitable for screening.
Formulas for traffic-noise spreading and ground loss
The calculator applies a 20 × log₁₀ distance term, followed by the selected linear ground allowance:
Here, Lr is the estimated receiver level in dB, L10 is the reference level at 10 m, d is distance in metres, and g is the ground allowance in dB per 100 m. Decibels are logarithmic, so equal distance ratios create equal geometric changes. Under this model, doubling distance adds about 6 dB of geometric reduction.
The geometric term depends on the ratio between the receiver distance and 10 m. Adding 40 m near the road can therefore have a larger effect than adding the same 40 m at an already distant receiver. The 20-log rule resembles compact-source spreading. A long, continuously occupied road may behave more like a line source, so this equation is a defined screening assumption rather than a universal roadway law.
The ground term depends on absolute distance and grows linearly. It does not model frequency-dependent interference between direct and ground-reflected sound. The implementation also applies this allowance over the full entered distance, including the first 10 m. That convention matters when comparing the result with another acoustic method.
This shorter form reads as reference level minus geometric loss minus ground loss. The same relationship can be rearranged to infer a compatible 10 m reference from a known receiver value, provided all assumptions remain unchanged:
At exactly 10 m, the geometric term is zero. The calculator still subtracts one tenth of the selected ground rate:
Set the ground field to zero if you want the output at 10 m to equal the entered reference exactly. This detail prevents an apparent discrepancy when checking the formula against the default reference position.
Worked example: estimating noise 50 m from a road
Suppose the reference level is 70 dB at 10 m, the receiver is 50 m away, and ground attenuation is 1 dB per 100 m. The geometric reduction is 20 × log₁₀(50 ÷ 10), or about 13.98 dB. Ground loss is 1 × (50 ÷ 100), or 0.5 dB. The result is 70 − 13.98 − 0.5 = 55.52 dB, displayed as 55.5 dB.
If the receiver moves to 100 m while the other inputs stay fixed, geometric loss becomes 20 dB and ground loss becomes 1 dB. The estimate is then 49 dB. Moving from 50 m to 100 m lowers the modelled level by about 6.5 dB: approximately 6 dB from doubling distance and another 0.5 dB from the extra ground allowance.
A quick directional check can reveal input mistakes. Raising the reference level should raise the result by the same amount. Increasing distance should generally lower it, and increasing a positive ground rate should also lower it. If the answer seems implausible, confirm that the source value applies at 10 m, that distance is in metres, and that the input and intended output use the same acoustic metric.
How to interpret setback and source scenarios
The displayed number is an estimated outdoor receiver level under the entered assumptions. It is most useful for relative comparisons, such as a 30 m patio versus a 60 m garden, or a current traffic scenario versus a quieter source scenario. It is not automatically a conclusion about annoyance, sleep disturbance, indoor conditions, health effects, or legal compliance.
Do not treat decibels as a linear percentage scale. A level of 60 dB is not twice the acoustic level represented by 30 dB. Small differences may also be less meaningful than the uncertainty in traffic, measurement conditions, or geometry. Results are rounded to one decimal place for comparison, but that precision does not imply that the real site is known to one tenth of a decibel.
For setback comparisons, keep the reference level and ground setting fixed while changing distance. For source-control comparisons, keep distance and ground conditions fixed while changing the reference level. In this model, a 3 dB reduction at the source creates a 3 dB reduction at the receiver. Actual benefits from quieter pavement, lower speeds, truck routing, or traffic-flow changes should come from reliable evidence rather than arbitrary adjustments.
Record each run with a receiver description and all three inputs. A label such as “east bedroom façade at 42 m” is more useful than “scenario 2.” Testing low, central, and high source assumptions can show whether a decision is robust. If a proposal works only with the quietest source assumption, it deserves closer investigation.
Limitations of this roadway-noise screening model
This traffic-noise calculator does not model vehicle count, speed, heavy-vehicle percentage, pavement, gradients, braking, horns, barriers, berms, buildings, cuttings, receiver height, reflections, wind, temperature structure, or frequency content. A barrier or building can interrupt the direct path, while hard façades can create reflections. Those effects cannot be reproduced reliably by increasing or decreasing the ground field.
The model also treats traffic through a 20-log spreading rule. A sparse road may be experienced as individual pass-bys, while a busy motorway can act more like a long, continuous source. The appropriate relationship and sound metric can differ between those situations. Intersections, bridge joints, ramps, steep grades, and engine braking may create localized sources that one uniform road level cannot describe.
Topography and elevation require care. A berm may protect a ground-floor receiver while leaving an upper storey exposed, and an elevated road may maintain a clear path over nearby fences. The calculator reports an outdoor value and does not predict indoor noise. Façade performance depends on windows, vents, walls, roofs, leakage paths, room characteristics, and whether openings are closed.
Use the result to understand trends, compare simple setbacks, and decide whether detailed analysis is warranted. Formal planning, environmental review, building design, or health-sensitive decisions may require a recognized traffic-noise method, representative measurements, future traffic assumptions, multiple receiver positions, and review by a qualified acoustical professional.
Frequently asked questions about traffic-noise distance
Does doubling distance always reduce road noise by 6 dB? Doubling distance reduces the geometric part of this calculator’s result by approximately 6 dB. The ground term may add further reduction. Real roads may follow another relationship because source length, terrain, barriers, reflections, and weather alter propagation.
Can the result be treated as dB(A)? Only when the reference input is A-weighted. The calculator preserves the acoustic metric supplied by the user. It does not convert unweighted, C-weighted, maximum, equivalent, or statistical sound levels into another metric.
What ground-attenuation value should I use? There is no universal value for every site. Zero is a transparent baseline when no extra allowance is justified. A modest positive value can be tested as a sensitivity case when supported by the chosen screening approach. Grass alone does not guarantee a particular rate because ground effects also depend on frequency, source height, receiver height, and geometry.
Can the calculator predict a noise barrier’s benefit? No. Barrier performance depends on height, length, gaps, line of sight, source and receiver positions, edge diffraction, and frequency. Use a barrier-specific method rather than disguising shielding as ground attenuation.
Is the estimate suitable for a compliance report? No. It is an early screening calculation. Applicable criteria vary by jurisdiction, land use, time period, metric, baseline condition, and project type. Compare like with like and consult the relevant standard or responsible authority.