Comparing optimized CO emission estimates using MOPITT or NOAA surface network observations

Abstract

This paper compares two global inversions to estimate carbon monoxide (CO) emissions for 2004. Either surface flask observations from the National Oceanic and Atmospheric Administration Earth System Research Laboratory (NOAA/ESRL) Global Monitoring Division (GMD) or CO total columns from the Measurement of Pollution in the Troposphere (MOPITT) instrument are assimilated in a 4D-Var framework. Inferred emission estimates from the two inversions are consistent over the Northern Hemisphere (NH). For example, both inversions increase anthropogenic CO emissions over Europe (from 46 to 94 Tg CO/yr) and Asia (from 222 to 420 Tg CO/yr). In the Southern Hemisphere (SH), three important findings are reported. First, due to their different vertical sensitivity, the stations-only inversion increases SH biomass burning emissions by 108 Tg CO/yr more than the MOPITT-only inversion. Conversely, the MOPITT-only inversion results in SH natural emissions (mainly CO from oxidation of NMVOCs) that are 185 Tg CO/yr higher compared to the stations-only inversion. Second, MOPITT-only derived biomass burning emissions are reduced with respect to the prior which is in contrast to previous (inverse) modeling studies. Finally, MOPITT derived total emissions are significantly higher for South America and Africa compared to the stations-only inversion. This is likely due to a positive bias in the MOPITT V4 product. This bias is also apparent from validation with surface stations and ground-truth FTIR columns. Our results show that a combined inversion is promising in the NH. However, implementation of a satellite bias correction scheme is essential to combine both observational data sets in the SH

Similar works

Full text

thumbnail-image

Utrecht University Repository

redirect
Last time updated on 14/06/2016

This paper was published in Utrecht University Repository.

Having an issue?

Is data on this page outdated, violates copyrights or anything else? Report the problem now and we will take corresponding actions after reviewing your request.