About

Intended audience

This manual was written for NCC-CNC GIS staff to provide explanations for the basic functionalities of the Where to Work tool (advanced version), to allow testing and recommendations for improvement during the development phase. As such, it is subject to change.

Purpose of tool

NCC is adopting a systematic and standardized approach to land prioritization via the introduction of a spatial prioritization tool Where to Work to NCC’s conservation planning framework. Doing so enables NCC to establish quantitative, organization-wide conservation goals and positions NCC to report on its collective impact in a way that resonates with donors, partners and funders.

Where to Work is a web-based, graphical user interface that uses an algorithm to build and solve complex conservation planning problems. The spatial prioritization tool that Where to Work interfaces, or interacts, with is prioritzr, which uses integer linear programming techniques to solve problems. The exact algorithms used are guaranteed to find the optimal result (Groves & Game, 2016; Hanson et al., 2023) and can analyze large, complex datasets efficiently, providing near real-time analysis for stakeholder meetings and discussions (Hanson et al., 2023). However, it is important to note that what is optimal mathematically may not be optimal from a practicality standpoint, and the results are dependent on the input data. Thus, the tool is intended for decision support, but is not meant to dictate final decisions.

Software dependencies

The tool is available as an online web application. For the best experience, it is recommended to use the latest version of the Google Chrome web browser (https://www.google.com/chrome/). Efforts have been made to support other web browsers, such as Mozzillla Firefox, Microsoft Edge, and Apple Safari.

Code availability

All code for the Where to Work tool is publicly available on GitHub here: https://github.com/NCC-CNC/wheretowork

If you find problems with the Where to Work tool you can submit a ticket, or Issue as GitHub calls it here: https://github.com/NCC-CNC/wheretowork/issues

If you are not a GitHub user, you can get in touch via email.

Terminology and concepts

Systematic conservation planning

A commonly used decision-support framework that seeks to optimize where to act and what to do in a systematic and repeatable way – two key outputs of a conservation planning process.

Spatial prioritization tool

A problem-solving tool that uses an algorithm to inform the spatial allocation of conservation actions (e.g., prioritzr, Marxan, Zonation).

Theme

Themes describe facets of biodiversity that are important for conservation (e.g., species, habitats, ecosystems). To help safeguard Themes, you can set Goals to ensure a minimum level of coverage by solutions (e.g., setting a Goal of 20% ensures that 20% of the overall spatial extent of the Theme is covered by the solution). Some Themes can contain multiple components that are termed Features. For example, a Theme pertaining to Threatened Species may contain Features, wherein each Feature corresponds to a different species.

Note that “Goals” are similar to Marxan’s “targets”

Weight

A Weight describes properties of places that can impede or improve conservation efforts. Set the Weight factor between -100 and 100 to indicate how important it is to avoid or cover (respectively) a given Weight in the solution. To completely avoid a Weight (e.g., to avoid areas with high human footprint), use a value of -100 (i.e. ensure that planning units with the lowest possible values in the Weight dataset are selected). To include as much of the Weight as possible (e.g., to include areas climate refugia), use a value of 100 (i.e. ensure that planning units with the highest possible values in the Weight dataset are selected). Setting a value of zero (deselecting the Weight using the toggle) means that it is not considered at all in the prioritization.

Includes

This term refers to areas that are already managed for conservation; to build on the current reserve network, these areas should be automatically included. However, solutions can be constructed that do not automatically include the current reserves. These are also useful to explore counterfactuals and management plans generated using other processes (e.g., what if we built a new system from scratch?).

Note that “Includes” are similar to Marxan’s “locked-in” areas.

Excludes

This is the opposite of an Include. Areas defined as Excludes are removed from the analysis and cannot be selected to contribute to Goals (i.e. they are locked-out).

Planning unit

A spatial locality (or area) that can be managed independently from other localities. In many cases, planning units are defined using property boundaries. In other cases, especially in large-scale planning exercises, landscapes are often divided into equal-area (e.g., 1 km2) grid cells that are used to serve as different planning units.

Reserve

A contiguous set of planning unit selected for prioritization.

Algorithm

An optimization technique that aims maximize performance according to certain criteria. Specifically, the Where to Work tool uses exact algorithms implemented with the CBC (Coin-or branch and cut) or Gurobi mixed integer programming solver.

Launching Where to Work

Accessing the Where to Work tool

The tool can be accessed with the following link: Where to Work.

This User Manual is written for the “advanced” user.

Select import method

To begin, select the method for importing data into the application. To use a previously prepared publicly available project, select “built-in project.”

To upload a project dataset that was previously prepared for you personally, select “upload project data.” This is the recommended approach and is explained in detail in wtw-data-prep.

To upload a spatial dataset that has not been prepared specifically for the tool, select “spatial dataset.” We don’t recommend this method for reasons explained in wtw-data-prep.

Built-in project

Sample projects are pre-loaded into the app. Select the project you wish to view, then click “Import.” Several of these projects are sample projects (e.g., those with the name “simulated”) and others have been prepared by GIS technicians.

Upload project data

A project dataset comprises four files. These files include configuration file, spatial data, attribute data, and boundary data files. These files are created using custom R scripts or the ArcGIS plugin currently under development. In most cases, a GIS technician would prepare these files specifically for your project. Please note that all four files need to be uploaded to the application.

Instructions and example scripts for creating these files can be found in the wtw-data-prep github repo.

Select configuration file

A configuration file contains the specification for the project. It specifies the Themes, Includes, Excludes and Weights that are part of the project, along with default settings and colors for visualization. This file is encoded using YAML (e.g, project.yml) file format (https://yaml.org/).

Select spatial data

A spatial data file contains the geographic information used to display the data on a map. Spatial data files can either be in the GeoTIFF format (e.g., spatial_data.tif) or the ESRI Shapefile format. Note that the ESRI Shapefile format is a file format that spans multiple files with the same prefix and different file extensions. For example, when uploading the “spatial_data” ESRI Shapefile, one must upload all four of the following files: spatial_data.shp, spatial_data.prj, spatial_data.shx, and spatial_data.dbf.

Select attribute data

An attribute data file details the expected amount of each Theme, Weight, or Include within each planning unit. The attribute data files can be supplied in the Comma Separated Values format (e.g., “attribute_data.csv”), or a compressed version of this format (e.g., “attribute_data.csv.gz”). Here, each column pertains to a different Theme, Weight, Include or Exclude, and each row corresponds to a different planning unit. The last column in this file should be called “_index” and indicates the spatial index associated with each planning unit (e.g., the index of the grid cell or geometry each planning unit is associated with in the spatial data file).

Select boundary data

A boundary data file contains information on the spatial boundaries of the planning unit. The boundary data file can be supplied in the Comma Separated Values format (e.g., “boundary_data.csv”), or a compressed version of this format (e.g., “boundary_data.csv.gz”). Specifically, it can be provided using the Marxan boundary data file format, wherein it contains the following three columns: “id1”, “id2”, and “boundary”. The “id1” and “id2” columns indicate the shared boundary between different planning units based on their spatial indices, and the “boundary” column indicates the length of these shared boundaries (e.g., 100m). To encode the length of boundaries along the outer edge of the study area, the “id1” and “id2” columns can contain the same spatial index value. This data is used when the spatial clustering options are enabled (see below).

Spatial dataset

An ESRI Shapefile can be uploaded to the application to automatically create a new project. Please note that this approach is not generally recommended for beginner users, because users need to ensure that the spatial dataset contains all relevant Themes, Weights, Includes and Excludes. Additionally, because the spatial dataset upload option involves creating a new project, this means that none of the Themes, Weights, or Includes/Excludes will have sensible default options (e.g., Goals or factors) and the provenance of the underlying data is unknown. Note that the ESRI Shapefile format is a file format that spans multiple files with the same prefix and different file extensions. For example, when uploading the “spatial_data” ESRI Shapefile, one must upload all four of the following files: spatial_data.shp, spatial_data.prj, spatial_data.shx, and spatial_data.dbf.

References

Ball, I. R., Possingham, H., & Watts, M. E. (2009). Marxan and relatives: Software for spatial conservation prioritisation. In A. Moilanen, K. A. Wilson, & H. Possingham (Eds.), Spatial Conservation Prioritisation: Quantitative Methods & Computational Tools (pp. 185–189). Oxford University Press.
Groves, C. R., & Game, E. T. (2016). Conservation Planning: Informed Decisions for a Healthier Planet (p. 580). Roberts; Company Publishers, Inc.
Hanson, J. O., Schuster, R., Morrell, N., Strimas-Mackay, M., Watts, M. E., Arcese, P., Bennett, J., & Possingham, H. P. (2023). Systematic conservation prioritization in r (Version 8.0.2.5). https://prioritizr.net/