Last updated: 2022-02-11
Checks: 6 1
Knit directory: mapme.protectedareas/
This reproducible R Markdown analysis was created with workflowr (version 1.6.2). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
The R Markdown is untracked by Git. To know which version of the R Markdown file created these results, you’ll want to first commit it to the Git repo. If you’re still working on the analysis, you can ignore this warning. When you’re finished, you can run wflow_publish to commit the R Markdown file and build the HTML.
Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
The command set.seed(20210305) was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.
Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.
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 153d847. 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: .RData
Ignored: .Rhistory
Ignored: .Rproj.user/
Ignored: data-raw/addons/docs/rest/
Ignored: data-raw/addons/etc/
Ignored: data-raw/addons/scripts/
Ignored: ~/
Untracked files:
Untracked: Recursos_en_Espanol/
Untracked: Resources_in_English/
Untracked: Ressources_en_Francais/
Untracked: Shapefile_splitting_README.txt
Untracked: analysis/projects_map_giz.Rmd
Untracked: analysis/threat_assessment.Rmd
Untracked: code/development/pa_polygon_simplifcation.R
Untracked: code/wdpa-giz.R
Untracked: Ресурсы_на_русском_языке/
Untracked: الموارد_باللغة_العربية/
Unstaged changes:
Modified: analysis/rapid-assessment_centralamerica.rmd
Modified: code/development/threat_assessment.R
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.
There are no past versions. Publish this analysis with wflow_publish() to start tracking its development.
The following map shows a match of the GIZ portfolio with the World Database on Protected Areas - WDPA. 1. The displayed database currently comprises 218 PAs which are situated in 44 different countries. Those areas can be broadly categorized into 189 terrestrial, 23 marine, and 6 partly marine/terrestrial protected areas. The georeferenced data covers a total surface of 0.658 Mio. km2 which corresponds to about 1.8 times the size of Germany.
Feel free to play around with the map and activate different layers.