z-logo
open-access-imgOpen Access
Ten years of CO emissions as seen from Measurements of Pollution in the Troposphere (MOPITT)
Author(s) -
FortemsCheiney A.,
Chevallier F.,
Pison I.,
Bousquet P.,
Szopa S.,
Deeter M. N.,
Clerbaux C.
Publication year - 2011
Publication title -
journal of geophysical research: atmospheres
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.67
H-Index - 298
eISSN - 2156-2202
pISSN - 0148-0227
DOI - 10.1029/2010jd014416
Subject(s) - troposphere , environmental science , northern hemisphere , longitude , latitude , atmospheric sciences , southern hemisphere , climatology , seasonality , biomass burning , pollution , sciamachy , meteorology , satellite , geography , aerosol , geology , statistics , ecology , mathematics , geodesy , aerospace engineering , engineering , biology
The Measurements of Pollution in the Troposphere (MOPITT) retrievals are used as top‐down constraints in an inversion for global CO emissions, for the past 10 years (from March 2000 to December 2009), at 8 day and 3.75° × 2.75° (longitude, latitude) resolution. The method updates a standard prior inventory and yields large increments in terms of annual regional budgets and seasonality. Our validation strategy consists in comparing our posterior‐modeled concentrations with several sets of independent measurements: surface measurements, aircraft, and satellite. The posterior emissions, with a global 10 year average of 1430 TgCO/yr, are 37% higher than the prior ones, built from the EDGAR 3.2 and the GFEDv2 inventories (1038 TgCO/yr on average). In addition, they present some significant seasonal variations in the Northern Hemisphere that are not present in our prior nor in others' major inventories. Our results also exhibit some large interannual variability due to biomass burning emissions, climate, and socioeconomic factors; CO emissions range from 1504 TgCO (in 2007) to 1318 TgCO (in 2009).

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here