Submission guidelinesΒΆ

Repository structureΒΆ

The public GitHub repository has the following structure:

| The Environmental Data Science Book
| β”œβ”€β”€ **/.github**
| β”‚   β”œβ”€β”€ ISSUE_template
| β”‚   β”œβ”€β”€ workflows
| β”‚   └── ...
| β”œβ”€β”€ **/book**
| β”‚   β”œβ”€β”€ _toc.yml
| β”‚   β”œβ”€β”€ _config.yml
| β”‚   └── ...
| β”œβ”€β”€ CODE_OF_CONDUCT.md
| β”œβ”€β”€ CONTRIBUTING.md
| └── ...

The .github folder refers to GitHub related deployment files and templates of issues/pull requests usually curated by the repository maintainers or developers. The book folder holds the website content and other relevant files (table of content and configuration files).

For the book content, the following contributions are accepted: Narrative content: include plain text, citations, equations, figures, special content blocks and more. Executable content: consists of computational material in a given programming language e.g. python along a narrative.

See also

Please visit the corresponding Jupyter Book guidelines for narrative and executable content.

The _toc.yml file sets the main sections of the Environmental DS book. It is a simple configuration file specifying a table of content from all the executable and narrative content found in the book folder (and in subfolders). The current version of the book consists of four key sections:

Preamble: contains narrative content i.e. plain markdown files describing the aims of the book, the target audience, how to use and attribution. Environments: provides narrative and executable content by environmental system e.g. Forest. We set different themes: sensors, modelling, etc to differentiate the type of analysis or procedure. Community: compiles community-related resources such as notes of co-working meetings, templates for new executable content i.e. demonstrators and interesting readings.
Afterword: describe miscellaneous material such as glossary, bibliography and execution statistics.

Contribution of executable notebooksΒΆ

The contribution process has three main steps: exploration, preparation and submission.

ExplorationΒΆ

We encourage you to explore existing templates of proposed topics or themes which are available in the community section. The proposed themes are described below. Sensor: highlights a particular environmental sensor with visualisation and interpretation of the corresponding layers of information. Preprocessing: refers to all procedures to clean and prepare environmental data for analysis. The notebook should highlight differences between the raw and preprocessed data. Modelling: comprises models to analyse a given environmental system. Post-processing: refers to post-process routines to fine tune and/or adjust modelling outputs.

In addition to defining the target environmental system and theme, we suggest inspecting existing published notebooks to have some notions about the expected content. For instance, a common component of the notebooks is their interactive plotting. For python, we provide a recent webinar about open-source packages for handling and visualising geospatial data. Some of these packages have been successfully used in the existing notebooks of the Environmental DS book, including intake for data cataloguing and hvplotfor interactive plotting.

PreparationΒΆ

The following procedures will allow you preparing the submission:

  • Make a branch or fork the repo

  • Copy the chosen notebook template to a new folder with the name of the target theme inside the directory of the target environmental system.

  • Rename the filename of the template to the pattern (XXX-YYY-ZZZ, where XXX refers to the environmental system, YYY to the theme and ZZZ to a preferred identifier of the model, sensor or pre/post-processing pipeline)

  • Fill the information header according to your use case. Be free to guide from previous modelling notebooks, see for instance the IceNet notebook.

  • Change the structure of the remaining sections of the notebook according to your preference.

  • Test the notebook is working according to your virtual or conda environment.

  • Note, the Binder does not provide GPU support, so we would suggest testing the notebook works with cpu when predicting from the pretrained models.

SubmissionΒΆ

Once you have tested a draft version of the notebook containing the information in the heading and remaining sections, you make a pull request. You will have to fill a form with a series of questions related to the contribution. Please complete them. If you have any questions, please send a direct message to environmental.ds.book@gmail.com.

AttributionΒΆ

Some material in this section has been adapted from Neurolibre submission guidelines, released under CC BY 3.0.