Skip to content

Pre-submission Inquiry: GeoPressureR #757

@Rafnuss

Description

@Rafnuss

Submitting Author Name: Raphaël Nussbaumer
Submitting Author Github Handle: @Rafnuss
Other Package Authors Github handles:
Repository: https://github.com/Rafnuss/GeoPressureR
Version submitted: v3.5.1
Submission type: Standard
Editor: TBD
Reviewers: TBD

Archive: TBD
Version accepted: TBD
Language: en


  • Paste the full DESCRIPTION file inside a code block below:
Package: GeoPressureR
Title: Global Positioning by Atmospheric Pressure
Version: 3.5.1
Authors@R: c(
    person("Raphaël", "Nussbaumer", , "rafnuss@gmail.com", role = c("aut", "cre", "cph"),
           comment = c(ORCID = "0000-0002-8185-1020")),
    person("Mathieu", "Gravey", , "mathieu@mgravey.com", role = "aut",
           comment = c(ORCID = "0000-0002-0871-1507"))
  )
Description: R package to determine the position and trajectory of a bird based on light-weight data-logger measuring at lease atmospheric pressure.
License: GPL (>= 3)
URL: https://github.com/Rafnuss/GeoPressureR,
    https://raphaelnussbaumer.com/GeoPressureR/
BugReports: https://github.com/Rafnuss/GeoPressureR/issues
Depends: 
    R (>= 4.1.0)
Imports: 
    cli,
    config,
    EBImage,
    future,
    future.apply,
    ggplot2,
    glue,
    httr2 (>= 1.0.0),
    jsonlite,
    leaflet (>= 2.2.0),
    lifecycle,
    Matrix,
    methods,
    plotly,
    pracma,
    progressr,
    RColorBrewer,
    stats,
    suntools,
    terra,
    utils
Suggests: 
    callr,
    assertthat,
    BiocManager,
    covr,
    ecmwfr (>= 2.0.0),
    knitr,
    leaflet.providers,
    maps,
    rnaturalearth,
    rnaturalearthdata,
    ncdf4,
    readxl,
    shiny,
    shinyjs,
    shinyWidgets,
    testthat (>= 3.0.0),
    withr
biocViews:
Config/testthat/edition: 3
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.3
Language: en-GB

Scope

  • Please indicate which category or categories from our package fit policies this package falls under: (Please check an appropriate box below. If you are unsure, we suggest you make a pre-submission inquiry.):

    • data retrieval
    • data extraction
    • data munging
    • data deposition
    • data validation and testing
    • workflow automation
    • version control
    • citation management and bibliometrics
    • scientific software wrappers
    • field and lab reproducibility tools
    • database software bindings
    • geospatial data
    • translation
  • Explain how and why the package falls under these categories (briefly, 1-2 sentences):

GeoPressureR ingests geolocator/tag data and labelled CSVs, retrieves external environmental data via the GeoPressure API/ERA5 and related services, and munges these into geospatial likelihood maps and reconstructed trajectories. It also supports exporting/producing analysis-ready outputs (e.g., label files/pressurepaths) and provides template-style functions to run the full workflow.

  • Who is the target audience and what are scientific applications of this package?

Researchers and practitioners in movement ecology and ornithology (and more broadly bio-logging/animal tracking) who work with geolocator tag data, especially pressure and light loggers, and need to reconstruct migration routes and stationary periods.

Reconstructing animal trajectories and stopover locations from pressure/light data; generating spatial likelihood maps from atmospheric reanalysis (ERA5) and twilight information; integrating wind fields to model movement; supporting reproducible migration analyses and quality control of tag-derived tracks.

See for more details:

Nussbaumer, R., Gravey, M., Briedis, M., & Liechti, F. (2023). Global positioning with animal-borne pressure sensors. Methods in Ecology and Evolution, 14(4), 1104–1117. https://doi.org/10.1111/2041-210X.14043

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(4), 1–32. https://doi.org/10.1111/2041-210X.14082

Nussbaumer, R., & Nussbaumer, A. (2024). GeoPressureManual: Learn how to use GeoPressureR with examples. Zenodo. https://doi.org/10.5281/zenodo.10799355. Available at: https://github.com/Rafnuss/GeoPressureManual

No other R pacakge.

Not applicable

  • If you made a pre-submission inquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted.

Not applicable

  • Explain reasons for any pkgcheck items which your package is unable to pass.

✖ avoid long code lines, it is bad for readability. Also, many people
prefer editor windows that are about 80 characters wide. Try make your lines
shorter than 80 characters
We are using Air, and define a max line of 100 characters.

✖ Package has no HTML vignettes
We are using a quatro book for more complete examples and details information: https://raphaelnussbaumer.com/GeoPressureManual/

Note that the package does not comply with https://devguide.ropensci.org/pkg_building.html#packages-wrapping-web-resources-api-clients. We have several function calling internal API (https://github.com/Rafnuss/GeoPressureAPI). I'm not sure what would be the best practice for this. As a starting point here is what Codex 5.2 is suggesting me: GeoPressure/GeoPressureR#152

Technical checks

Confirm each of the following by checking the box.

This package:

Publication options

  • Do you intend for this package to go on CRAN?

  • Do you intend for this package to go on Bioconductor?

  • Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution? If so:

MEE Options
  • The package is novel and will be of interest to the broad readership of the journal.
  • The manuscript describing the package is no longer than 3000 words.
  • You intend to archive the code for the package in a long-term repository which meets the requirements of the journal (see MEE's Policy on Publishing Code)
  • (Scope: Do consider MEE's Aims and Scope for your manuscript. We make no guarantee that your manuscript will be within MEE scope.)
  • (Although not required, we strongly recommend having a full manuscript prepared when you submit here.)
  • (Please do not submit your package separately to Methods in Ecology and Evolution)

Code of conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions