The AERMOD modeling system has a variety of settings and options which can be employed in many ways. This includes options which have been pre-approved for use in regulatory applications and those which are meant for testing or may require additional approval in a regulatory context. This tip will review the differences between these options and include examples of each one.
Last month, our tip described how AERMET reads custom meteorological data via its Onsite Pathway. AERMET’s Onsite Pathway gives users full control over how the model will read the data provided by the modeler, but there are some general conventions that must still be followed. Let’s take a closer look at some of the rules and guidelines for how the Onsite data file should be written.
AERMET – the meteorological pre-processor for the AERMOD modeling system – allows users to input their own custom meteorological data via its Onsite Pathway. This produces a highly representative dataset when using observations recorded at the site that will be modeled in AERMOD. One of the biggest challenges to this approach is that the modeler is responsible for identifying the variables and input format to AERMET. AERMET has two separate format specifications which can be utilized.