Air Quality & Environment

Understanding AERMET, AERMAP and BPIP-PRIME

Understanding AERMET, AERMAP and BPIP-PRIME

Overview

Any air dispersion modelling study built around AERMOD depends on three preprocessors that prepare the data the model needs before it can run. These are AERMET, AERMAP and BPIP-PRIME. AERMOD is the regulatory dispersion model recommended by the US Environmental Protection Agency and widely used in India for Environmental Impact Assessment (EIA) and Environmental Clearance studies. It cannot function on raw inputs alone. It needs meteorology described in a specific format, terrain elevations resolved for every source and receptor, and building dimensions translated into downwash parameters. The three preprocessors produce exactly these inputs.

This article explains what each preprocessor does, why it exists, and how the three fit together in a typical Indian modelling workflow.

Direct answer: what do AERMET, AERMAP and BPIP do?

In one line each:

  • AERMET is the meteorological preprocessor. It converts raw weather observations and upper-air soundings into the boundary-layer parameters AERMOD requires.
  • AERMAP is the terrain preprocessor. It reads digital elevation data and assigns elevations and hill-height scales to sources and receptors.
  • BPIP-PRIME is the building preprocessor. It calculates building downwash parameters so the model can account for how nearby structures disturb a plume.

AERMOD then reads the outputs of all three, combines them with source emission data, and produces predicted ground-level concentrations that can be compared against the National Ambient Air Quality Standards (NAAQS) notified by the Central Pollution Control Board (CPCB).

Why does AERMOD need preprocessors at all?

AERMOD is a steady-state Gaussian plume model with modern boundary-layer physics. To calculate dispersion it needs a physically consistent description of the atmosphere, the ground surface and the obstacles around a stack. Field data does not arrive in that form. Weather stations report wind speed, temperature and cloud cover. Terrain arrives as a grid of elevations. Buildings are drawn as plans and elevations. Each preprocessor performs the translation from measured reality into model-ready parameters, and each was designed so that the science is applied consistently rather than being left to the individual analyst.

Separating these steps also keeps the workflow auditable. Regulators reviewing an EIA report under the EIA Notification 2006 can trace each input back to its source dataset, which matters when the State Pollution Control Board (SPCB) or the Ministry of Environment, Forest and Climate Change (MoEFCC) scrutinises a Consent to Establish or Environmental Clearance application.

AERMET: the meteorological preprocessor

AERMET is usually the most demanding of the three to run well, because meteorology drives dispersion more than any other single input.

AERMET processes data in stages. It reads surface observations, upper-air (radiosonde) soundings and, where available, on-site tower measurements. It quality-checks the data, merges the sources, and then computes the boundary-layer parameters that AERMOD uses to characterise turbulence and mixing.

Key outputs from AERMET include:

  • Surface friction velocity, which describes mechanical turbulence near the ground.
  • Monin-Obukhov length, which indicates atmospheric stability.
  • Convective velocity scale, relevant to daytime buoyant mixing.
  • Surface heat flux.
  • Mixing height, both mechanical and convective.
  • Wind speed, wind direction and temperature profiles.

AERMET requires three surface characteristics to be defined for the area around the meteorological station: albedo (reflectivity), Bowen ratio (a measure of surface moisture) and surface roughness length. These vary by land use and by season, so the analyst typically defines them for wind-direction sectors and for each season. In the Indian context this matters a great deal, because the same site can shift from irrigated cropland in one season to dry fallow land in another, and the monsoon strongly alters surface moisture.

AERMET produces two output files for AERMOD: a surface file and a profile file. Together they give the model an hour-by-hour description of the atmosphere for the modelling period, which is normally a full year of data, or the season-specific period required by the terms of reference for a particular study.

Good meteorological data handling is the single biggest determinant of a defensible AERMOD result. Poorly screened or unrepresentative met data will undermine an otherwise careful study.

AERMAP: the terrain preprocessor

AERMAP handles elevation. Real terrain influences plume behaviour because a plume travelling toward rising ground behaves differently from one over flat land, and because elevated terrain can bring a plume closer to the ground.

AERMAP reads digital elevation model (DEM) data and performs two main tasks:

  1. 1It assigns a ground elevation to every source and every receptor in the modelling domain.
  2. 2It calculates a hill-height scale for each receptor, which represents the height of terrain that could influence the plume at that location.

The hill-height scale is the parameter that lets AERMOD apply its critical dividing streamline concept, deciding whether air at a given point tends to travel over a hill or around it. Without AERMAP, the modeller would have to assign these values manually for potentially thousands of receptors, which would be impractical and inconsistent.

Common elevation datasets used with AERMAP include globally available DEM products such as SRTM and ASTER data, which cover Indian project sites at usable resolution. The analyst must ensure the datum and coordinate system are consistent between the elevation data, the source locations and the receptor grid. Coordinates are typically handled in UTM, and getting the zone and datum right for the Indian region is a routine but essential check.

For sites on genuinely flat land, terrain effects are minor, but AERMAP is still normally run so that elevations are assigned consistently and the modelling file remains complete for regulatory review.

BPIP-PRIME: the building downwash preprocessor

BPIP stands for Building Profile Input Program. The PRIME suffix refers to the Plume Rise Model Enhancements algorithm, which is the modern treatment of building downwash embedded in current versions of the program and in AERMOD.

Building downwash occurs when wind flowing over and around a structure creates zones of turbulence and low pressure in the lee of the building. If a stack is short relative to nearby buildings, its plume can be caught in this disturbed flow and pulled toward the ground much sooner than it otherwise would, producing higher local concentrations. This is a common and important effect at industrial sites where stacks sit among process buildings, boiler houses and storage structures.

BPIP-PRIME takes as input:

  • The footprint corners and heights of buildings and structures near each stack.
  • The location and height of each stack.

From these it calculates, for 36 wind-direction sectors (every 10 degrees), the building dimensions that matter for downwash. These are:

  • Building height for each sector.
  • Projected building width for each sector.
  • Projected building length.
  • Distances describing the position of the stack relative to the building.

The concept of a Good Engineering Practice (GEP) stack height is central here. GEP height is the stack height above which downwash effects are considered negligible. BPIP also reports whether each stack is above or below its GEP height, which informs both the modelling and, in some cases, the stack design itself. AERMOD reads the BPIP-PRIME output and applies downwash only where the geometry warrants it.

How the three fit together

The workflow is sequential in preparation but converges at the model run. A simplified view:

PreprocessorPrimary inputPrimary outputWhat it answers
AERMETSurface and upper-air met data, site characteristicsSurface and profile met filesWhat is the atmosphere doing each hour?
AERMAPDigital elevation data, source and receptor coordinatesElevations and hill-height scalesHow does terrain shape the domain?
BPIP-PRIMEBuilding footprints and heights, stack locationsDirection-specific downwash parametersHow do nearby buildings disturb the plume?

Once all three have produced their outputs, the analyst assembles the AERMOD control file, adds source parameters such as stack height, diameter, exit velocity, exit temperature and emission rate, defines the receptor grid, and runs the model. AERMOD then predicts concentrations that can be evaluated against the NAAQS limits for pollutants such as particulate matter, sulphur dioxide and oxides of nitrogen.

Common questions

Do all three preprocessors always need to be run?

AERMET is effectively always required, because AERMOD cannot run without processed meteorology. AERMAP is run for almost all studies, and is essential wherever terrain is not flat. BPIP-PRIME is required whenever buildings or structures near a stack could cause downwash, which covers most industrial facilities. For an isolated tall stack on flat, open ground with no nearby structures, downwash processing may be unnecessary, but this should be a documented judgement rather than an omission.

Are these tools accepted by Indian regulators?

AERMOD and its preprocessors are the standard regulatory package internationally and are routinely used in Indian EIA and consent studies. Indian regulators, including SPCBs and MoEFCC expert appraisal committees, expect ambient results to be compared against CPCB NAAQS and expect the modelling inputs to be traceable and defensible.

What most often goes wrong?

The most frequent issues are unrepresentative or poorly screened meteorological data, mismatched coordinate systems or datums between terrain, sources and receptors, and incomplete building inventories that miss structures relevant to downwash. Each of these can materially change predicted concentrations.

Conclusion

AERMET, AERMAP and BPIP-PRIME each solve a distinct problem: the state of the atmosphere, the shape of the ground, and the influence of buildings. Understanding what each does, and treating their inputs with care, is what separates a credible dispersion study from a box-ticking exercise. DSTechnoverse provides air dispersion modelling services built on this preprocessor workflow for EIA, Environmental Clearance and consent applications in India.

Further Reading

Frequently Asked Questions

What data does AERMET need? Hourly surface observations (wind speed and direction, temperature, cloud cover), upper-air soundings or a validated substitute, and the surface characteristics of the site: albedo, Bowen ratio and surface roughness.

What elevation data is used in AERMAP? A digital elevation model covering the whole modelling domain. Freely available global datasets such as SRTM are commonly used, at a resolution suited to how complex the terrain is.

When is building downwash analysis needed? When a stack is close to buildings that can pull its plume down into their wake. Under the US EPA good engineering practice approach, a stack lower than the building height plus 1.5 times the lesser of the building height or projected width is likely to be affected, so BPIP-PRIME is run.

Sources and Further Reading

Official and primary sources for the standards, rules and data discussed on this page.