What is ODMAP?
Species distribution models (SDMs) constitute the most common class of biodiversity models. The advent of ready-to-use software packages and increasing availability of digital geo-information have considerably assisted the application of SDMs in recent years enabling their use in informing conservation and management, and quantifying impacts from global change.
However, models must be fit for purpose, with all important aspects of their development and applications properly considered. Despite the widespread use of SDMs, the standardisation and documentation of model protocols remains limited. To address these issues, we propose a standard protocol for reporting SDMs. We call this the ODMAP (Overview, Data, Model, Assessment and Prediction) protocol as each of its components reflects the main steps involved in building SDMs and other empirically-based biodiversity models ( Zurell et al. 2020 ).
The ODMAP protocol serves two main purposes. First, it provides a checklist for authors detailing key steps for model building and analyses. Second, it introduces a standard approach to documentation that ensures transparency and reproducibility, facilitating peer review and expert evaluation of model quality as well as meta-analyses.
This Shiny web application helps to implement the ODMAP approach and produces well formatted protocols that can be exported for further usage. For further explanation please refer to the original publication (Zurell et al. 2020).
Please cite as follows:
Zurell D, Franklin J, König C, Bouchet PJ, Serra-Diaz JM, Dormann CF, Elith J, Fandos Guzman G, Feng X, Guillera-Arroita G, Guisan A, Leitão PJ, Lahoz-Monfort JJ, Park DS, Peterson AT, Rapacciuolo G, Schmatz DR, Schröder B, Thuiller W, Yates KL, Zimmermann NE, Merow C (2020) A standard protocol for describing species distribution models. Ecography 43: 1261-1277. DOI: 10.1111/ecog.04960
How to create an ODMAP protocol
Enter all relevant information into the fields provided under 'Create a protocol'. Your progress in individual ODMAP sections is displayed in the side bar at the left. The 'Hide optional fields' switch on the left allows you to only display mandatory fields, which depend on the model objective chosen. A preview of your current protocol is available in the 'Protocol Viewer'.
You can always save your progress by clicking the download button on the left. We recommend always downloading the csv file as this will allow you to resume your work later. After downloading your protocol as csv, it is safe to close the Shiny app. For a better layout, you can also download the ODMAP protocol as word document. Please note that word documents cannot be uploaded again to the Shiny app.
You will be able to resume working on your protocol by choosing the Upload tab above and uploading your previously saved ODMAP csv file. In addition, you can import objects generated with the rangeModelsMetaData R-package to autofill your ODMAP protocol.
Should you have any conceptual questions or feedback regarding the ODMAP protocol, or any technical questions and feedback regarding the Shiny app, please do not hesitate to visit our Github repository or contact us directly at email@example.com .
Give a brief overview of all important parts of your study.
Describe your your data in detail.
Describe your modeling approach in detail.
Describe how you assessed your model results.
Describe your model predictions in detail.
There are two options for importing data into your ODMAP protocol
(1) Upload an ODMAP protocol (.csv)
This option is convenient if you want to edit or resume working on a previously saved ODMAP protocol.
(2) Upload an RMM file (.RDS or .csv)
The rangeModelMetaData package of Merow et al. (2019) allows exporting standardized metadata for SDMs directly from R. Note that the objectives of ODMAP and RMM differ and not all fields can be mapped between both approaches. This option is therefore not a replacement for filling out ODMAP, but may be helpful for e.g. documenting model settings or references. If RMM values have been imported, the corresponding field and entity is indicated in parentheses as Field1($Field2)($Field3)-Entity)