How to use this tutorial effectively?
Last updated: 2025-02-28
Checks: 2 0
Knit directory: nbs-workflow/
This reproducible R Markdown analysis was created with workflowr (version 1.7.1). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
The results in this page were generated with repository version 7226f26. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
Note that you need to be careful to ensure that all relevant files for
the analysis have been committed to Git prior to generating the results
(you can use wflow_publish or
wflow_git_commit). workflowr only checks the R Markdown
file, but you know if there are other scripts or data files that it
depends on. Below is the status of the Git repository when the results
were generated:
Ignored files:
Ignored: .Rhistory
Ignored: .Rproj.user/
Unstaged changes:
Modified: analysis/index.Rmd
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
These are the previous versions of the repository in which changes were
made to the R Markdown (analysis/How_To.Rmd) and HTML
(docs/How_To.html) files. If you’ve configured a remote Git
repository (see ?wflow_git_remote), click on the hyperlinks
in the table below to view the files as they were in that past version.
| File | Version | Author | Date | Message |
|---|---|---|---|---|
| Rmd | 7226f26 | Desmond Lartey | 2025-02-28 | wflow_publish("analysis/How_To.Rmd") |
| html | 76f52ce | Desmond Lartey | 2025-02-28 | Build site. |
| Rmd | 0ce17c3 | Desmond Lartey | 2025-02-28 | wflow_publish("analysis/How_To.Rmd") |
How to Use This Guide
Welcome to the step-by-step guide on Impact Chain Assessment. The main purpose of this guide is to help you implement the baseline characterisation of various landscapes. We provide a structured approach to processing geospatial datasets, for further analysis. Follow these steps to ensure a smooth workflow.
1. Follow the Learning Path
This guide is structured sequentially, with each section building upon the previous one. Start with dataset preparation, then move on to classification, visualization, and exporting results. If you're new to Earth Engine or geospatial analysis, proceed step by step.
2. Download the Required Data
To follow along, ensure you have access to the required geospatial datasets. For your covenience, we also attached the link to the full code which you caan also run on the web. There are also already both raw and processed datasets which you can also jumpstart to work on. These are available in shpfiles/geopakage (vector) and GeoTIFF (raster) formats:
- Biophysical Data - Land cover, elevation models, and protected areas.
- Social Data - Population density, demographic distributions.
- Governance Data - Administrative boundaries, policy zones.
- Hazard Data - Flood zones, fire risk, environmental stressors.
- Supplementary Data - Additional supporting datasets.
3. Understand the Code Structure
Each section of this guide contains well-documented JavaScript code snippets and Python notebook designed for Google Earth Engine (GEE) and or Earth Engine API to work in jupyter notebook. These scripts allow for land use classification, reclassification to EUNIS habitat types, processing and anlaysis on governance and social indicators and and visualization their imapcts.
4. Experiment with the Code
Modify the code to understand how it works. Adjust parameters such as land cover classifications, visualization styles, and region filters to customize the workflow to your specific needs.
5. Export Your Results
The guide includes methods for exporting results in raster (GeoTIFF) and vector (shapefiles) formats for further analysis in QGIS, ArcGIS, WebGIS or other geospatial tools.
6. Refer to Additional Resources
For further details on EUNIS classifications and data sources, refer to these links:
- EUNIS Habitat Classification - Official documentation and habitat descriptions.
- EU Project Page - Details on the research project supporting this work.
By following these steps, you will gain a structured understanding of habitat classification and spatial data processing in Earth Engine.