Traffic Noise Abatement: A Rural State Faces Challenges and Opportunities
Bibliographic record
Abstract
This paper describes how the Montana Department of Transportation (MDT) is being pressured by increased residential complaints because of highway traffic noise. Many of these complaints come from neighborhoods where the road was constructed long before traffic noise was an issue. The traditional approach to traffic noise control throughout the country has been the installation of traffic noise barriers along the highway edge of pavement or along the right-of-way adjacent to noise-sensitive areas. However, noise barriers are not always feasible, nor are they always desirable or reasonable in cost. As a non-barrier state, MDT has struggled with its traffic noise policy to allow for noise barriers and to involve local governments in the decision-making process. There is an overwhelming need to educate planners and developers regarding MDT’s noise abatement responsibilities. This research was proposed to: (1) examine abatement solutions that are alternatives to MDT-built barriers, and (2) generate awareness at MDT and throughout the planning community regarding residents’ and planners’ perceptions of traffic noise problems and solutions. Reviews of the literature addressed pavement-related noise, noise-compatible land use planning and development, sound insulation, and traffic management techniques for noise reduction1. In addition to a review of published literature, this research involved extensive correspondence and discussions with the staff of numerous state DOT and local agencies across the United States and in Canada. Also researched were Montana’s land use programs and responses to growth concerns. Finally, two surveys were developed and administered in the summer of 2003 to assess people’s perceptions of noise and noise mitigation: one survey was for residents near busy roads in four Montana urban areas, and the other was for local planners throughout the state. This paper addresses the idea of noise-compatible planning and development in Montana, with emphasis on an analysis of the survey data.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.006 | 0.002 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".