RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/ropensci/software-review/issues/675 below:

extending targets to work with geospatial data · Issue #675 · ropensci/software-review · GitHub

Date accepted: 2025-03-11

Submitting Author Name: Nicholas Tierney
Submitting Author Github Handle: @njtierney
Other Package Authors Github handles: @Aariq @brownag
Repository: https://github.com/njtierney/geotargets
Version submitted: 0.2.0.9000
Submission type: Standard
Editor: @ldecicco-USGS
Reviewers: @amart90, @lidefi87

Archive: TBD
Version accepted: TBD
Language: en

Paste the full DESCRIPTION file inside a code block below:

Package: geotargets
Title: 'Targets' Extensions for Geospatial Formats
Version: 0.2.0.9000
Authors@R: c(
    person(
      given = "Nicholas", 
      family = "Tierney", 
      email = "nicholas.tierney@gmail.com", 
      role = c("aut", "cre"),
      comment = c(ORCID = "0000-0003-1460-8722")
      ),
    person(
      given = "Eric",
      family = "Scott",
      role = c("aut"),
      comment = c(ORCID = "0000-0002-7430-7879")
    ),
    person(
      given = "Andrew",
      family = "Brown",
      role = c("aut"),
      comment = c(ORCID = "0000-0002-4565-533X")
    )
    )
Description: Provides extensions for various geospatial file formats, 
  such as shapefiles and rasters. Currently provides support for the 'terra'
  geospatial formats. See the vignettes for worked examples, demonstrations, 
  and explanations of how to use the various package extensions.
License: MIT + file LICENSE
Encoding: UTF-8
Language: en-GB
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.2
Imports: 
    targets (>= 1.8.0),
    rlang (>= 1.1.3),
    cli (>= 3.6.2),
    terra (>= 1.7.71),
    withr (>= 3.0.0),
    zip,
    lifecycle
Suggests: 
    crew (>= 0.9.2),
    knitr,
    ncmeta,
    rmarkdown,
    sf,
    stars,
    testthat (>= 3.0.0),
    fs
Config/testthat/edition: 3
URL: https://github.com/njtierney/geotargets, https://njtierney.github.io/geotargets/
BugReports: https://github.com/njtierney/geotargets/issues
VignetteBuilder: knitr

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
- text analysis
Explain how and why the package falls under these categories (briefly, 1-2 sentences):

The geotargets package builds upon the targets package to facilitate geospatial computation, and skip up-to-date operations in geospatial pipelines. geotargets means the user doesn't need to write custom targets code to manage the special read/write/wrap/unwrap that is required when using packages like terra. It also facilitates dynamic branching, so a raster can be split into parts and then jobs farmed out in parallel and later combined.

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

The geotargets package is for people working with geospatial data with packages like terra. Workflows include analysis of sea ice changes over time (https://github.com/njtierney/icebreaker), through to creating statistical pipelines to estimate mosquito insecticide resistance (https://github.com/idem-lab/map-ir-pipeline).

Are there other R packages that accomplish the same thing? If so, how does yours differ or meet our criteria for best-in-category?

The targets package does provide workflow automation, but in order for it to work with geospatial data it requires custom code. The geotargets package helps users continue working with targets with minimal changes to workflow. Other packages like chopin provide ways to parallelise spatial operations, but this seems distinct from automation, although related.

(If applicable) Does your package comply with our guidance around Ethics, Data Privacy and Human Subjects Research?

N/A

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.

N/A

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

── geotargets 0.2.0.9000 ─────────────────────────────────────────────────

✔ Package name is available
✔ has a 'codemeta.json' file.
✔ has a 'contributing' file.
✔ uses 'roxygen2'.
✔ 'DESCRIPTION' has a URL field.
✔ 'DESCRIPTION' has a BugReports field.
✔ Package has at least one HTML vignette
✔ All functions have examples.
✔ Package has continuous integration checks.
✔ Package coverage is 97.7%.
✖ R CMD check found 1 error.
✔ R CMD check found no warnings.
ℹ Function names are duplicated in other packages

ℹ Current status:
✖ This package is not ready to be submitted.

I could not find the R CMD Check error, and all checks pass on GitHub Actions - https://github.com/njtierney/geotargets/actions/workflows/R-CMD-check.yaml

Technical checks

Confirm each of the following by checking the box.

I have read the rOpenSci packaging guide.
I have read the author guide and I expect to maintain this package for at least 2 years or to find a replacement.

This package:

does not violate the Terms of Service of any service it interacts with.
has a CRAN and OSI accepted license.
contains a README with instructions for installing the development version.
includes documentation with examples for all functions, created with roxygen2.
contains a vignette with examples of its essential functions and uses.
has a test suite.
has continuous integration, including reporting of test coverage.

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)

We would be interested in submitting this to JOSS, if possible.

Code of conduct

I agree to abide by rOpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

adamhsparks, e-kotov and lidefi87

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4