The Development and possible recovery of the Antarctic Ozone Hole.

Since its prediction and discovery, ozone depletion in the stratosphere
\nover Polar Regions has been a topic of widespread interest and debate.
\nStarting in the late 1970s, when the Antarctic ozone observations began,
\nthere has been a dramatic decrease in ozone during the polar spring each
\nyear (WMO, 2003). The total amount of column ozone regularly goes below
\n220 DU1
\n in the atmosphere above Antarctica, at which point it is defined as an
\nozone hole (Newman et al., 2004). Whilst the influences on the mechanisms
\nthat cause this dramatic ozone loss each year are many, the essential
\nprerequisites for ozone destruction are stratospheric chlorine and bromine
\n(WMO, 2003).
\nIn the few years after 1979, the depletion of ozone rapidly increased
\nfrom year to year due to the increased emission of chlorofluorocarbons
\n(CFCs) through anthropogenic industrial activities. The tropospherestratosphere2
\n exchange at low latitudes allows compounds such as CFCs to
\nenter the stratosphere. Once there, these compounds are transported to the
\npoles via Brewer-Dobson3
\n circulation (Reid, 2000). Here they have very long
\nlifetimes and they can continuously destroy ozone for several decades.
\nThis one part of the reason, why the effective ban on the emission of
\nCFCs agreed to in “The Montreal Protocol on Substances that Deplete the
\nOzone Layer” in 1989 (Solomon, 1999) has not yet resulted in a significant
\nreduction of the size of the Antarctic ozone hole. Furthermore, the actual
\nextent of ozone destruction is also influenced by other factors such as the
\npolar vortex, polar stratospheric clouds, temperature, water vapour, aerosols
\nand planetary wave activity, which are highly interdependent. How they
\ncontribute to severe ozone depletion over Antarctica and why the recovery of
\nstratospheric ozone is believed to be in progress, although still undetected,
\nwill be discussed in this paper.

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.