I maintain tidycreel, which has just been accepted on CRAN as version 8.0.0.
Creel surveys use angler counts and interviews to estimate fishing effort, catch, and harvest. The analysis depends on how days, sites, and anglers were sampled. tidycreel provides a tidy, pipe-friendly interface for keeping that survey structure attached to the data, with the survey package supplying the design-based foundation.
The core workflow is to define a survey calendar and strata, attach count and interview data, check coverage and data quality, and estimate effort, rates, and totals with uncertainty. The distinction between completed access-point trips and incomplete roving interviews matters when choosing a rate estimator.
Install the CRAN release:
install.packages("tidycreel")
The source package is available now. Windows and macOS binaries are pending; I expect them within the next couple of days. Until then, use install.packages("tidycreel", type = "source") if a binary is unavailable. tidycreel itself has no compiled code, although source-built dependencies may need build tools.
For development changes ahead of CRAN:
install.packages("pak") # If needed
pak::pak("chrischizinski/tidycreel")
In 8.0.0, aerial catch, harvest, and release totals are underestimated; use the GitHub development version for those totals until 8.0.1 reaches CRAN (release notes). Non-aerial designs are unaffected.
There are 24 package vignettes, a practical blog series, and the companion book Modern Creel Survey Analysis in R. The book remains a work in progress and develops the sampling and statistical reasoning behind the workflows.
I also wrote a short release post with installation instructions and links to these resources.
I would welcome feedback from people working with creel or other field survey data, especially on data structures and diagnostics. What sampling or data coverage problems are hardest to make visible in your current workflow?
Source and issue tracker.