Please download the Copernicus Publications LaTeX Package to prepare your manuscript. The package contains the LaTeX2e class file, the configuration file, all needed style files, as well as a template serving as the framework for your manuscript. Please download the Copernicus Publications LaTeX Package, version 6.2, 15 January 2020.

Authors are kindly requested to make use of the template.tex file embedded in the LaTeX Package since most of the definitions for the structure of manuscript elements are described there. Since we convert all typeset TeX files into XML, the expressions and markups have to be highly standardized. Therefore, please keep the following in mind:

• Please provide only one figure file for figures with several panels, and please do not use \subfloat or similar commands.
• Please use only commands in which words, numbers, etc. are within braces (e.g. \textrm{TEXT} instead of {\rm TEXT}).
• For algorithms, please use the syntax given in template.tex or provide your algorithm as a figure.
• Please do not define new commands.
• The most commonly used packages (\usepackage{}) are integrated in the copernicus.cls. Some other packages often used by the community are defined in template.tex. Please do not insert additional ones in your *.tex file.
• Spaces in labels (\label{}) are not allowed; please make sure that no label name is assigned more than once.
• Please do not use \paragraph{}; only \subsubsection{} is allowed.
• It is not possible to add tables in colour.

If you are familiar with BibTeX, you can use copernicus.bst from the package. It will sort your bibliography entries alphabetically and produce the proper layout of the reference list.

To prepare your manuscript in a format compatible with MS Word (*.doc, *.docx, or *.rtf), please use the Copernicus Publications Word template (docx). Please use the Microsoft equation editor and not the graphic mode when compiling your equations.

For the review process a *.pdf file of the complete manuscript is required following the standards for sectioning and structure (see below). Tables and figures as well as their captions should be included in the text. All pages must be numbered consecutively and line numbers must be included. Please note that only manuscripts submitted in portrait format will be considered for review. Single pages in landscape format are not acceptable.

• Sectioning and structure:
1. Title page
2. Abstract
3. Copyright statement (will be included by Copernicus)
4. Introduction
5. Sections
6. Conclusions
7. Appendices
8. Code availability
9. Data availability
10. Sample availability
11. Video supplement
12. Supplement link (will be included by Copernicus)
13. Team list
14. Author contribution
15. Competing interests
16. Disclaimer
17. Special issue statement (will be included by Copernicus)
18. Acknowledgements
19. References
the title page must include the title (concise but informative), author first and last names, full institutional addresses of all authors, and correspondence email for proofs. Deceased co-authors should be marked accordingly.
• Abstract: The abstract should be intelligible to the general reader without reference to the text. After a brief introduction of the topic, the summary recapitulates the key points of the article and mentions possible directions for prospective research. Reference citations should not be included in this section, unless urgently required, and abbreviations should not be included without explanations.
• Sections: The headings of all sections, including introduction, results, discussions or summary must be numbered. Three levels of sectioning are allowed, e.g. 3, 3.1, and 3.1.1. The abbreviation "Sect." should be used when it appears in running text and should be followed by a number unless it comes at the beginning of a sentence.
• Footnotes: These should be avoided, as they tend to disrupt the flow of the text. If absolutely necessary, they should be numbered consecutively. Footnotes to tables should be marked by lowercase letters.
• Equations: They should be referred to by the abbreviation "Eq." and the respective number in parentheses, e.g. "Eq. (14)". However, when the reference comes at the beginning of a sentence, the unabbreviated word "Equation" should be used, e.g.: "Equation (14) is very important for the results; however, Eq. (15) makes it clear that..."
• Reproduction and reuse of figures, maps, and tables: authors must secure the right to reproduce any material that has already been published or copyrighted elsewhere, and corresponding citations must be included in the text as well as in the captions. If distribution licences other than CC BY are applied, corresponding statements must be included in the captions. If applicable, maps from map providers such as Google Maps or OpenStreetMap used in manuscripts must include the required copyright and distribution licence statements of the map provider. Authors must adhere to the individual redistribution permissions. The copyright and distribution licences of such maps must be visible in the maps themselves.
• Figure composition: It is important for the production process that separate figures are submitted. Composite figures containing multiple panels should be collected into one file before submission. The figures should be labelled correctly with Arabic numerals (e.g. fig01, fig02). They can be submitted in *.pdf, *.ps, *.eps, *.jpg, *.png, or *.tif format and should have a resolution of 300 dpi. The width should not be less than 8 cm. A legend should clarify all symbols used and should appear in the figure itself, rather than verbal explanations in the captions (e.g. "dashed line" or "open green circles"). The produced paper file will contain all figures in *.jpg or *.png format. However, if authors use vector graphics, readers can download such files labelled "high-resolution" from the full-text HTML version online. Tips for producing high-quality line graphics:
1. The first choice should be vector graphics in *.eps or *.pdf format. Fonts must be embedded. Please make sure that the *.pdf files do not contain hidden objects. If you want to adjust fonts in your original figure file before converting into *.pdf, please make sure that you change the actual font of the original figure rather than adding text boxes or other additional layers.
2. Please use only one font family in your figures (e.g. Arial or Helvetica) and consider using sans-serif fonts. Keep in mind that the usage of regular, italic, bold, and bold-italic of one font family already leads to four different fonts that must be embedded or adjusted by our image processors in case of text corrections within figures.
3. If the processing of your vector figures requires an exceptional amount of time due to multiple fonts or hidden objects, we reserve the right to convert your *.eps or *.pdf figures into *.png files for the further production process.
4. If the usage of vector graphics is not possible, a bitmap image should be saved in a "non-lossy" format (e.g. *.png). A high quality is recommended. It is always possible to reduce the size of the figure later.
5. The *.jpg format should only be used for photos. It is not suitable for sharp edges. Note that it is not advisable to convert a *.jpg file back to *.png. If *.jpg files must be used please save them with high quality.
6. If you are not able to fulfil the above-mentioned criteria, it is also possible to submit figures produced with Excel, PowerPoint, Word, Photoshop, Illustrator, or InDesign in the original file format. Our image processors will then produce the figures from these source files.
7. For maps and charts, please keep colour blindness in mind and avoid the parallel usage of green and red. For a list of colour scales that are illegible to a significant number of readers, please visit ColorBrewer 2.0.

The abbreviation "Fig." should be used when it appears in running text and should be followed by a number unless it comes at the beginning of a sentence, e.g.: "The results are depicted in Fig. 5. Figure 9 reveals that...".

• Figure content guidelines: In order to facilitate consistency with our language and typesetting guidelines applied to the text of the manuscript, please keep the following in mind when producing your figures:
1. Labels of panels must be included with brackets around letters being lower case (e.g. (a), (b), etc.).
2. Ranges need an en dash and no spaces between start and end (e.g. 1–10, Jan–Feb).
3. Coordinates need a degree sign and a space when naming the direction (e.g. 30° N, 25° E).
4. Spaces must be included between number and unit (e.g. 1 %, 1 m).
5. Units must be written exponentially (e.g. W m^–2).
6. Common abbreviations to be applied: hour as h (not hr), kilometre as km, metre as m.
7. Capitalization: only the first word is capitalized in headers (in addition to proper nouns). More guidelines are provided in section English guidelines and house standards.
8. Maps: please adhere to United Nations naming conventions for maps used in your manuscript. In order to depoliticize scientific articles, authors should avoid the drawing of borders or use of contested topographical names. The editors reserve the right to insert the label "under dispute" if contested borders are presented. If disputed territories are relevant for your map, please make sure that the figure caption stays neutral as well as the legend and labelling within your map.
• Figure captions: Each illustration should have a concise but descriptive caption. The abbreviations used in the figure must be defined, unless they are common abbreviations or have already been defined in the text. Figure captions should be included in the text file and not in the figure files.
• File size: Authors are kindly asked to find the best balance between the quality of figures and submitted material on the one hand, and a manageable file size on the other hand. Individual figures in the *.pdf format should not exceed 2 MB, file types other than *.pdf should not exceed 5 MB per figure, and the overall size of all submitted files, excluding supplements, should not exceed 30 MB.
• Plot data: Authors are encouraged to publicize the data needed to create the plots, which are included in the manuscript, in order to enable reviewers and readers to reproduce the plots. Ideally, such plot data is treated like any other research data and should be deposited in FAIR-aligned data repositories that assign persistent identifiers (see section data sets).
• Tables: They should be numbered sequentially with Arabic numerals. For the production of the accepted manuscript, they should be submitted as MS WORD or included in the LaTeX file. Tables submitted as a PDF or an image file cannot be processed. Tables should be self-explanatory and include a concise, yet sufficiently descriptive caption. Horizontal lines should normally only appear above and below the table, and as a separator between the head and the main body of the table. Please note that the word "Table" is never abbreviated and should be capitalized when followed by a number (e.g. Table 4).
• Appendices: All material required to understand the essential aspects of the paper such as experimental methods, data, and interpretation should preferably be included in the main text. Additional figures, tables, as well as technical and theoretical developments which are not critical to support the conclusion of the paper, but which provide extra detail and/or support useful for experts in the field and whose inclusion in the main text would disrupt the flow of descriptions or demonstrations may be presented as appendices. These should be labelled with capital letters: Appendix A, Appendix B etc. Equations, figures and tables should be numbered as (A1), Fig. B5 or Table C6, respectively. Please keep in mind that appendices are part of the manuscript whereas supplements (see below) are published along with the manuscript.
• Software and model code: authors are encouraged to deposit software, algorithms, and model code in FAIR-aligned repositories/archives whenever possible. These research outputs are then cited in the manuscript using the received DOI and included in the reference list. The manuscript must then include a section entitled "Code availability" or, in the case of data and code, "Code and data availability".
• Data sets: Authors are requested to follow our data policy including
• the deposit of research data (i.e. the material necessary to validate the research findings) that correspond to journal articles in reliable FAIR-aligned data repositories that assign persistent identifiers (preferably digital object identifiers (DOIs)). Suitable repositories can be found at https://www.re3data.org/;
• the proper citation of data sets in the text and the reference list (see section references) including the persistent identifier. For data sets hosted on GitHub, authors are kindly asked to issue a DOI through Zenodo and include this DOI in the reference list;
• the inclusion of a statement on how their underlying research data can be accessed. This must be placed in the section "Data availability" at the end of the manuscript before the acknowledgements. If the data are not publicly accessible, a detailed explanation of why this is the case is required (e.g. applicable laws, university and research institution policies, funder terms, privacy, intellectual property and licensing agreements, and the ethical context of the research);
• the provision of unrestricted access to all data and materials underlying reported findings for which ethical or legal constraints do not apply.
• Sample availability: if geoscientific samples which are registered as International Geo Sample Number (IGSN) have been used for the manuscript, authors are required to include the IGSN in the reference list, cite it in the article, and provide a statement on how to access the sample by adding a section "Sample availability" to the manuscript.
• Video supplements and video abstracts: authors are encouraged to upload videos associated with their manuscript to the TIB AV-Portal for archiving and DOI registration, facilitating proper citation of the videos in their manuscript. Please find more information in the dedicated section below.
• Supplement: Supplementary material is reserved for items that cannot reasonably be included in the main text or as appendices. These may include short videos, very large images, maps, CIF files, as well as short computer codes such as matlab or python script. In no case can supplementary material contain scientific interpretations or findings that would go beyond the contents of the manuscript. In general, supplementary material that can be hosted in alternative sites such as FAIR-aligned data repositories should be placed there. These include data sets, movies, animations, or computer programme codes, for which a persistent identifier, ideally a DOI, should be mentioned in the "data availability" section of the manuscript. Normal size figures, tables, as well as technical or theoretical developments that do not need to be included in the main text should be included as appendices. Moderate-size data sets may be presented as supplements, but this should be cleared with the editor. When supplements are justified, the following will apply:
1. Supplements will receive their own DOI (digital object identifier) and will be published online along with the article as *.zip archive or single *.pdf file.
2. Supplements will receive a title page added during the publication process including title ("Supplement of"), authors, and the correspondence email. Therefore, please avoid providing this information in the supplement.
3. Equations, figures and tables in supplements should be numbered as (S1), Fig. S5 or Table S6. Sections are numbered as S3, S3.1, and S3.1.1.
4. The overall file size of a supplement is limited to 50 MB. Authors of larger supplements are kindly asked to submit their files to a reliable FAIR-aligned data repository and to insert a persistent identifier, ideally a DOI, in the manuscript.
• Author contribution: Authors are required to add a section "Author contribution" before the acknowledgements in which the contributions of all co-authors are briefly described. Example: "AA and BB designed the experiments and CC carried them out. DD developed the model code and performed the simulations. AA prepared the manuscript with contributions from all co-authors." We recommend using the taxonomy of CASRAI's CRediT definitions of contributor roles.
• Competing interests: Declaration of all potential conflicts of interest is required by Copernicus Publications as this is an integral aspect of a transparent record of scientific work. Please see our competing interests policy.
1. If there are no competing interests in their submitted manuscripts, authors should state: "The authors declare that they have no conflict of interest."
2. If there are possible conflicts of interest, authors must state what competing interests are relevant to the submitted work: "Author A is a member of the editorial board of the journal. Author B has received research funding from Company Y. Author C is a member of committee Z."

Papers should make proper and sufficient reference to the relevant formal literature. Informal or so-called "grey" literature may only be referred to if there is no alternative from the formal literature. Works cited in a manuscript should be accepted for publication or published already. In addition to literature, data and software used should be referenced (citations should appear in the body of the article with a corresponding reference in the reference list). These references have to be listed alphabetically at the end of the manuscript under the first author's name. Works "submitted to", "in preparation", "in review", or only available as preprint should also be included in the reference list. Please do not use bold or italic writing for in-text citations or in the reference list.

Please supply the full author list with last name followed by initials. After the list of authors, the complete reference title needs to be named. Journal names are abbreviated according to the Journal Title Abbreviations by Caltech Library, followed by the volume number, the complete page numbers (first and last page), the digital object identifier (DOI), and the publication year. If the abbreviation of a journal name is not known, please use the full title. In addition to journal articles, all reference types are summarized together with examples below.

If there is more than one work by the same first author, their papers are listed in the following order: (1) single author papers (first author), followed by (2) co-author papers (first author and second author), and finally (3) team papers (first author et al.). Within these three categories the respective papers are then listed as follows:

• Single author papers: chronologically, beginning with the oldest. If there is more than one paper in the same year, a letter (a, b, c) is added to the year, both in the in-text citation as well as in the reference list.
• Co-author papers: first alphabetically according to the second author's last name, and then chronologically within each set of co-authors. If there is more than one paper in the same year per set of co-authors, a letter (a, b, c) is added to the year both in the in-text citation as well as in the reference list.
• Team papers: first chronologically (beginning with the oldest), independent of the team author names, then alphabetically within each year according to the second (third, etc.) author. If there is more than one paper in the same year for a first author (independent of the team), a letter (a, b, c) is added to the year both in the in-text citation as well as in the reference list.

In-text citations

In terms of in-text citations, the order can be based on relevance, as well as chronological or alphabetical listing, depending on the author's preference. In-text citations can be displayed as "[…] Smith (2009) […]", or "[…] (Smith, 2009) […]". If the author's name is part of the sentence structure only the year is put in parentheses ("As we can see in the work of Smith (2009) the precipitation has increased"). If the author's name is not part of the sentence, name and year are put in parentheses ("Precipitation increase was observed (Smith, 2009)"). If you refer to multiple references at the same position all references are put in parentheses separated by semicolons ("Precipitation increase was observed (Smith, 2009; Mueller et al., 2010)").

Copernicus style files

• EndNote® Output Style File and example library
• CSL style (for Zotero, Mendeley, Papers, etc.) and example library
• Bibtex Bibliographic Style File

Examples for reference sorting

Examples for reference types

• Journal article
• Author(s) (initials always after last name)
• Article title
• Journal title abbreviation
• Volume
• Page numbers or article number
• DOI
• Year

Porter, J. G., De Bruyn, W., and Saltzman, E. S.: Eddy flux measurements of sulfur dioxide deposition to the sea surface, Atmos. Chem. Phys., 18, 15291–15305, https://doi.org/10.5194/acp-18-15291-2018, 2018.

• Preprint
• Author(s) (initials always after last name)
• Preprint title
• Preprint server name [preprint]
• Persistent identifier as link
• Published date

Jung, M., Koirala, S., Weber, U., Ichii, K., Gans, F., Gustau-Camps-Valls, Papale, D., Schwalm, C., Tramontana, G., and Reichstein, M.: The FLUXCOM ensemble of global land-atmosphere energy fluxes, arXiv [preprint], arXiv:1812.04951, 11 December 2018.

• Book
• Author(s), editor(s) (initials always after last name)
• Book title
• Edition
• Series title and volume (if any)
• Editors (if not authors)
• Publisher
• Location
• Total pages (optional) pp.
• Persistent identifier (DOI preferred)
• Year

Singh, O. N. and Fabian, P. (Eds.): Atmospheric Ozone: a Millennium Issue, Copernicus Publications, Katlenburg-Lindau, Germany, 2003.

• Book chapter
• Author(s) (initials always after last name)
• Article title
• Book title
• Edition (if any)
• Editors (if any)
• Publisher
• Location
• Page numbers of article in book
• Persistent identifier (DOI preferred)
• Year

van Edig, X., Schwarze, S., and Zeller, M.: The robustness of indicator based poverty assessment tools in changing environments – empirical evidence from Indonesia, in: Tropical Rainforests and Agroforests under Global Change, Environmental Science and Engineering (Environmental Engineering), edited by: Tscharntke, T., Leuschner, C., Veldkamp, E., Faust, H., Guhardja, E., and Bidin, A., Springer, Berlin, Heidelberg, Germany, 191–211, https://doi.org/10.1007/978-3-642-00493-3_9, 2010.

• Presented paper
• Author(s) (initials always after last name)
• Paper title
• Name of meeting/conference
• Location of meeting/conference
• Date of meeting/conference
• Abstract number
• Persistent identifier (DOI preferred)
• Year

Buiter, S.: How syn-rift sedimentation promotes the formation of hyper-extended margins, EGU General Assembly 2020, Online, 4–8 May 2020, EGU2020-18622, https://doi.org/10.5194/egusphere-egu2020-18622, 2020.

• Presented paper published in conference proceedings
• Author(s) (initials always after last name)
• Paper title
• Proceedings title
• Name of meeting/conference
• Location of meeting/conference
• Date of meeting/conference
• Abstract number or page numbers
• Persistent identifier (DOI preferred)
• Year

Iwata, M., Matsumoto, H., and Kojima, H.: Computer experiments on the plasma wave generation in the vicinity of Earths bow shock, in: Proceedings of the 6th International School, Symposium on Space Plasma Simulation Overview, Garching, Germany, 3–8 September 2001, 4–6, 2001.

• Data set
• Creators
• Title
• Publisher/repository [data set]
• Persistent identifier (DOI preferred)
• Publication year

Loew, A., Bennartz, R., Fell, F., Lattanzio, A., Doutriaux-Boucher, M., and Schulz, J.: Surface Albedo Validation Sites, EUMETSAT [data set], https://doi.org/10.15770/EUM_SEC_CLM_1001, 2015.

• Software and model code
• Creator
• Title
• Publisher/repository [code]
• Persistent identifier (DOI preferred)
• Publication year

Randall, D., Dazlich, D., Heikes, R., and Konor, C.: CSU model for DCMIP 2016, Zenodo [code], https://doi.org/10.5281/zenodo.5800992018, 2017.

• Report, map, thesis, and dissertation
• Author(s) (Initials always after last name!)
• Title
• Report designator (M.S., Ph.D., etc.)
• Issuing organization/university
• Location
• Total pages (optional) pp.
• Persistent identifier (DOI preferred)
• Year

Monger, J. W. H. and Journeay, J. M.: Guide to the geology and tectonic evolution of the southern Coast Mountains, Geol. Surv. of Can., Ottawa, Ont., Open File Rep. 2490, 77 pp., 1994.

Brown, R. J. E.: Permafrost in Canada, Geol. Surv. of Can., Ottawa, Ont., Map 1246A, 1967.

Kronberg, E. A.: Dynamics of the Jovian Magnetotail, Ph.D. thesis, International Max Planck Research School, Universities of Braunschweig and Göttingen, Germany, 133 pp., 2006.

• Webpages
• Title
• URL
• Access date
• Year (if not the same as access date)

Copernicus Publications: https://publications.copernicus.org/, last access: 25 October 2018.

• Mathematical symbols and formulae: In general, mathematical symbols are typeset in italics. The most notable exceptions are function names (e.g. sin, cos), chemical formulas, and physical units, which are all typeset in roman (upright) font. Matrices are printed in boldface, and vectors in boldface italics. A range of numbers should be specified as "a to b" or "a...b". The expression "a–b" is only acceptable in cases where no confusion with "a minus b" is possible.
• Equations should be numbered sequentially with Arabic numerals in parentheses on the right-hand side, e.g. (1), (2). If too long, split them accordingly. If there are chemical formulae included, e.g. reactions, please number them (R1), (R2), etc. When using Word, the equation editor and not the graphic mode should be used under all circumstances.
• Units: For units of physical quantities, the metric system is mandatory and, wherever possible, SI units should be used. Hereby, we differentiate between SI base units, SI-accepted units, and SI-derived units. Regarding the abbreviation of such units, SI base units and SI-accepted units must be abbreviated in conjunction with numbers (e.g. the velocity is 10 km h^-1) and must be written out without numbers (e.g. the velocity is given in kilometres per hour). SI-derived units must also be written out when they do not contain a number. If they contain numbers, the abbreviation is preferred where possible (e.g. the average atmospheric pressure is 1013 hPa), but authors can decide not to abbreviate them if no abbreviation is commonly used (e.g. the distance is 237 nautical miles). Regarding the notation, if units of physical quantities are in the denominator, contain numbers, and are abbreviated, they must be formatted with negative exponents (e.g. 10 km h^-1 instead of 10 km/h). Commonly used examples for units without abbreviation are week, month, or decade. These should be written out and not be formatted with negative exponent if placed in the denominator (e.g. 10 kg per week). Units of non-physical quantities must not be abbreviated and if they are in a denominator, they must also not be exponentially notated (e.g. two cars per household).
• Date and time: 25 July 2007 (dd month yyyy), 15:17:02 (hh:mm:ss). Often it is necessary to specify the time if referring to local time or universal time coordinated. This can be done by adding "LT" or "UTC", respectively. If needed when referring to years, CE (common era) and BCE (before the common era) should be used instead of AD and BC since CE and BCE are more appropriate in interfaith dialogue and science.
• In addition, the SI and IUPAC recommendations should be followed:
1. SI brochure
2. IUPAC Green Book, 3rd edition
3. IUPAC Gold Book