How is the HITRAN project structured?
The HITRAN database is a curated compilation of validated molecular spectroscopic parameters, established in the early 1970s. It is used by various computer codes to interpret and model the transmission and emission of light in terrestrial and planetary atmospheres. The HITRAN compilation consists of six major components. These components include the line-by-line spectroscopic parameters required for high-resolution radiative-transfer codes, experimentally derived absorption cross-sections (for molecules where it is not yet feasible for representation in a line-by-line form), collision-induced absorption data, a water-vapor continuum model, aerosol indices of refraction, and general tables (including partition sums) that apply globally to the data. The database is updated quadrennially, and the corresponding papers are among the most cited in Geoscience.
With the rapid advances in instrumentation and computational resources, the applications require more and more critical updates and enhancements from HITRAN. Following a PACT (Practicality, Accuracy, Completeness, and Traceability) philosophy, these updates include, but are not limited to, adding more molecules and isotopologues, extending spectral and dynamic coverage, appreciable improvement of the accuracy of the existing parameters, adding new line shape representations and associated parameters, and parametrizations of ``new'' (to HITRAN) phenomena, such as water-vapor continuum, that are required to reduce the residuals of atmospheric retrievals. The flow diagram below summarizes how the data is typically collected and curated by HITRAN, including the validation process. The priorities are set by NASA's needs and recommendations from the HITRAN committee. The data is then being sourced and once obtained, is gone through validation by cross-comparisons of alternative sources, if they exist, and comparisons against laboratory and field data when available. At the end, the best values for the parameters are selected and compiled into the current version.
The database is then released. The user feedback is an integral part of the process, as it enables us to update the deficient parameters or seek funding for future improvements.