Getting started
Your SoilFER Learn lab: JupyterLab, RStudio and QGIS in your browser
1. Sign in
Your trainer gives you a username and password for the training. Sign in here and you land on My lab, your start page: continue the notebook you were working on, open a tool, see your progress in each module and the handouts from your trainer. The first time you open a tool, your personal lab starts in about 20–60 seconds.
To change your password, click your name at the top right of My lab, then Change password.
You only need a web browser: no installation, no other account and no powerful computer. Your lab is private: other participants cannot see your files or reach your lab. Training accounts stop working after the end date of the training; download anything you want to keep before then.
2. Open a workspace
| Workspace | What for | Open |
|---|---|---|
| JupyterLab | Ready-to-run notebooks for every session (R and Python) | |
| RStudio | The original R scripts of the manual, in the SoilFER-Training-Resources project |
|
| QGIS desktop | Look at and edit your maps |
Your trainer tells you which one to use. All of them see the same project, data and your own files.
3. Where things are in your lab
~/notebooks/ ready-to-run notebooks (module0 … module4)
~/SoilFER-Training-Resources/ training project: 01_data, 02_scripts, 03_outputs, 04_assignments
01_data/module1/training_data/ course rasters + MIR spectra (already in place, read-only)
~/mydata/ your own data (also on the QGIS desktop as "My data")
~/R/library/ R packages you install yourself
Broke the training project? Open a Terminal and run soilfer-reset-project: you get a fresh copy, and your old one is kept as a backup.
Notebooks start with a Setup cell. Run it first; in the Lab it takes only a few seconds.
4. Your own data
- JupyterLab: drag files from your computer onto the file browser (or click ⬆ Upload). To unpack a zip, open a Terminal and run
unzip myfile.zip. - RStudio: Files pane → Upload → choose a file or a
.zip(unpacked automatically). - Put your data in a folder of your own, for example
~/mydata/, and read it with the same code as the course data (terra::rast(),sf::st_read(),readxl::read_excel()…). - Large files: uploads up to 2 GB per file. RStudio’s text editor opens files up to 50 MB; for bigger tables read them in R (
df <- readr::read_csv("~/mydata/big.csv"); View(df)), or open them in QGIS. JupyterLab opens CSV files in a table viewer (right-click → Open With → CSVViewer). - Open everything (course data, your uploads, your results) in QGIS: QGIS desktop. QGIS opens by itself; the desktop has shortcuts to Training data, My data, Results and Notebooks, and the same folders are under Favorites in the QGIS Browser panel: drag a file onto the map.
5. Install any extra package
| How | Notes | |
|---|---|---|
| R (RStudio or R notebook) | install.packages("ggridges") |
Ready-made binaries: most packages install in seconds. They go into ~/R/library and stay installed. |
| R from GitHub | pak::pak("owner/repo") or remotes::install_github("owner/repo") |
Compilers and the common system libraries are already installed. |
| Bioconductor | BiocManager::install("name") |
|
| Python (Python notebook) | %pip install name |
Then restart the kernel (⟳). Stays installed while your lab exists. |
| System library (rare) | Ask your trainer | Labs run without administrator rights, for safety. The common system libraries are already installed. |
Copy the error message and send it to your trainer. Most problems are a package that needs a system library or a newer R version; your trainer can add it to the lab for everyone.
6. Help, handouts and feedback
- Ask a trainer for help: click Help at the top of My lab, or Ask a trainer for help on the page itself. In JupyterLab use the SoilFER menu → Ask a trainer for help; in RStudio run
soilfer_help(). You can allow the trainer to join your lab and fix the problem with you in your notebook; without your permission they come to your desk. - Handouts: files your trainer sends during the training appear in
~/handouts(also on the QGIS desktop). They are your own copies; edit them freely. - Something unclear? Select the sentence on any page of the course or the manual and press Something unclear?. Your message goes to the authors, without your name.
Google Earth Engine (Module 2)
- Register at https://earthengine.google.com/register for non-commercial use and create or select a Google Cloud project.
- Run the export script of the module in the Earth Engine Code Editor.
- The Kansas example rasters are already in your lab. For your own country, upload your exports to
01_data/module2/rasters.