Who is this article for?

Noise analysts who want to understand how ANOMS separates airport, overflight and community noise.

Access to the ANOMS Noise Analyst Workbench is required.

ANOMS keeps noise from local airport operations, overflights, and community sources separate throughout its calculations, so each contribution can be analysed and compared independently.

Separating local airport and overflight noise

ANOMS separates the hourly and daily Leq values calculated for each classification, so that community noise, local airport noise, and other airport-related DNL or Leq values can be compared.

You can edit errors in the automatic event classification. Only classifications that are allowable for the action being performed can be selected. For example, if a noise event is matched to an aircraft, it cannot be classified as a community noise event until it is first unlinked from the correlated track. See the article Unlinking or reclassifying a noise event.

The summary noise values of hourly and daily Leqs and DNLs are automatically recalculated every time a noise event classification is changed. This recalculation keeps the summary noise values up to date and accurate. The summary noise database includes values for total noise, aircraft noise, local aircraft noise, and community noise.

Understanding noise climates

ANOMS calculates and stores hourly noise levels. Hourly values are included for local aircraft, community noise, noise from other airports' aircraft, and six values of Ln. Daily DNL and WECPNL values for local aircraft, community noise, and overflights are stored in the Daily Data table.