ecmwfr::wf_set_key("<your personal access token>")Appendix A — Resources
A.1 Forum
If you are actively using the package, join the GeoPressure forum to stay informed about bugs, issues, and improvements.
A.2 Main Publications
Main paper presenting the approach to estimate a likelihood map from pressure timeseries:
Nussbaumer, R., Gravey, M., Briedis, M., & Liechti, F. (2023). Global positioning with animal-borne pressure sensors. Methods in Ecology and Evolution, 14, 1104–1117. https://doi.org/10.1111/2041-210X.14043
Paper presenting the movement model:
Nussbaumer, R., Gravey, M., Briedis, M., Liechti, F. & Sheldon, D. (2023) Reconstructing bird trajectories from pressure and wind data using a highly optimised hidden Markov model. Methods in Ecology and Evolution, 14, 1118–1129. https://doi.org/10.1111/2041-210X.14082
Paper describing the GeoLocator Data Package standard and the Master GeoLocator Data Package, which compiles all published packages:
Nussbaumer, R., Adamík, P., Bell, F., et al. (2026). Standardised multi-sensor geolocator data for bird migration ecology. Scientific Data. https://doi.org/10.1038/s41597-026-08873-x
Paper reviewing the strengths, limitations, and opportunities of geolocation by pressure from a more applied perspective:
Rhyne, G. S., Stouffer P. C., Briedis, M., Nussbaumer, R. (2024). Barometric geolocators can reveal unprecedented details about the migratory ecology of small birds. Ornithology. https://doi.org/10.1093/ornithology/ukae010
A.3 Presentations
Raphaël Nussbaumer. GeoPressureR: Introduction and case studies. August 2023. 14th European Ornithologicals’ Union Congress. PRESENTATION available as PDF.
Raphaël Nussbaumer, Colin Jackson, Lennox Kirao, Felix Liechti. The potential of multi-sensor geolocators to study short-distance Afrotropical migrants. November 2022. 15th Pan-African Ornithological Congress. PRESENTATION available as PDF.
Raphaël Nussbaumer, Mathieu Gravey, Martins Briedis, Felix Liechti. Leveraging light, pressure, activity, and wind data to improve geolocator positioning. August 2022. 28th International Ornithological Congress. PRESENTATION available at Youtube and as PDF.
Raphaël Nussbaumer, Mathieu Gravey, Felix Liechti. Improving the spatial accuracy of multi-sensor geolocators’ position using atmospheric surface pressure. October 2021. 7th International Bio-logging Science Symposium. PRESENTATION available at Youtube and as PDF.
A.4 Use with an AI assistant
An AI assistant can guide you through a GeoPressureR analysis, answer questions about the code and the method, and help you share or reuse data. The geopressure skill, from GeoPressureSkills, tells the assistant where each kind of answer lives (this manual, the function reference, the papers, the forum) and how to work with you.
Claude Code (the command-line tool, or the Code tab of the Claude desktop app) can run R on your computer, so it can set up a GeoPressureTemplate project and run the analysis with you:
/plugin marketplace add GeoPressure/GeoPressureSkills /plugin install geopressure@geopressureClaude.ai or the Claude desktop chat: download
geopressure.zipfrom the latest release and upload it at claude.ai/customize/skills (+, Create skill, Upload a skill). Without R, the assistant answers questions and writes scripts for you to run.Other assistants that read skills: copy the
plugins/geopressure/skills/geopressurefolder to the folder your assistant reads skills from.
Projects created from GeoPressureTemplate also include an AGENTS.md file, which guides any assistant through the analysis, with or without the skill.
You stay in charge of the judgement calls: the assistant prepares and checks, but you label the flights in trainset() and decide on the settings. Check its results as you would a colleague’s, and never paste a key or password into the chat (see below).
A.5 Accounts and keys
Most of a GeoPressureR analysis needs no account. Pressure maps and ERA5 time series are computed through the GeoPressure API, which is free and needs no key. A few steps need your own account:
| Account | Needed for | Required? |
|---|---|---|
| Copernicus Climate Data Store (ECMWF) | Downloading wind with tag_download_wind(). When a key is stored, geopressure_timeseries() and pressurepath_create() also read ERA5 from ECMWF’s ARCO service instead of the GeoPressure API (see their source argument). |
Only for wind |
| Zenodo | Publishing a GeoLocator Data Package, and checking a draft with GeoLocatoR::read_zenodo(draft = TRUE) |
Only to publish |
| GitHub | Creating a project with “Use this template” and archiving your code on Zenodo. GeoLocatoR::create_geopressuretemplate() needs git installed, but no account. |
Optional |
| CARTO, Mapbox, MapTiler | More basemap styles in the interactive maps | Optional |
Keys are personal. Store each one once in your system keyring, as shown below, so that it never appears in a script, in config.yml or in a repository. Do not paste a key into a chat or share it with an AI assistant: run the commands yourself. keyring::key_list() lists the stored services without showing the keys.
A.5.1 Copernicus Climate Data Store
- Create an ECMWF account on the Climate Data Store.
- Accept the “Licence to use Copernicus Products” in the Licences tab of the ERA5 pressure levels dataset. Requests fail until the licence is accepted.
- Copy your Personal Access Token from your profile page.
- Store it with
ecmwfr, which calls it a key:
GeoPressureR then finds the key by itself. The CDS limits how many requests each account can have queued; see Trajectory with wind for downloading wind.
A.5.2 Zenodo
- Create a Zenodo account. You can sign in with ORCID or GitHub.
- Create a personal access token in your Zenodo token settings.
- Store it in the keyring.
key_set()asks for the token, so it is not saved in your R history:
keyring::key_set("ZENODO_TOKEN")read_zenodo() also reads the token from a ZENODO_TOKEN environment variable. See Publish your data for the publishing steps.
A.5.3 Map tiles
Interactive GeoPressureR maps use a basemap to provide geographic context. GeoPressureViz, GeoLightViz, plot() maps, and plot_path() all show the same basemap selector.
Esri’s Gray Canvas, imagery, and topographic basemaps are always available. You can add CARTO, Mapbox, or MapTiler styles by storing a provider key once in your system keyring.
keyring::key_set_with_value("CARTO_API_KEY", password = "<your CARTO API key>")
keyring::key_set_with_value("MAPBOX_ACCESS_TOKEN", password = "<your Mapbox token>")
keyring::key_set_with_value("MAPTILER_API_KEY", password = "<your MapTiler API key>")Only store a public, read-only Mapbox token: rendered Leaflet maps send map tokens to the web browser. Do not put keys in analysis scripts or commit them to version control. Create keys at CARTO, Mapbox, or MapTiler.
Each configured provider adds useful styles to the selector: CARTO Dark Matter with and without labels; Mapbox Dark, Outdoors, Satellite, and Satellite Streets; and MapTiler DataViz Dark, Topographic, Satellite, and Hybrid. Choose a dark no-label layer for likelihood maps, a topographic layer for terrain context, and satellite or hybrid imagery for local detail.