RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of camtrapdp and modeltime.resample — release velocity, themes, recent moves, and the top alternatives to consider.
camtrapdp has become a full read-edit-write toolkit for camera trap datasets, then went quiet
camtrapdp reads, filters and writes Camera Trap Data Packages in R, with export paths to Darwin Core and EML for GBIF publication. The round trip closed at 0.4.0, when write_camtrapdp() joined the existing reader; everything since has been standard-version upkeep and dependency alignment. The latest release does no user-facing work at all — it raises the R floor to 4.1.0, switches to base pipes, and pins {frictionless} >= 1.3.0.
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
camtrapdp reads, filters and writes Camera Trap Data Packages in R, with export paths to Darwin Core and EML for GBIF publication. The round trip closed at 0.4.0, when write_camtrapdp() joined the existing reader; everything since has been standard-version upkeep and dependency alignment. The latest release does no user-facing work at all — it raises the R floor to 4.1.0, switches to base pipes, and pins {frictionless} >= 1.3.0.
Development tracks two things it does not control: the Camtrap DP specification and the frictionless package underneath it. Each release so far has absorbed a spec bump (1.0.1, then 1.0.2) or an upstream API change, with the package's own surface largely settled since contributors(), individuals() and taxa() landed. The metadata-scope logic — filters rewriting spatial, temporal and taxonomic scope automatically — is the one genuinely opinionated piece and it has not been revisited.
The next release is most likely another spec-tracking one, upgrading datasets to whatever Camtrap DP version follows 1.0.2, since that has been the trigger for every release after the write path closed.
modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.
Every entry here is compatibility work against something upstream — hardhat 1.0.0, workflows regression mode, then tune 2.0.0 twice. The 0.3.0 notes show a second concern emerging alongside it: making failures legible, with .notes on failed fits, actionable errors from unnest_modeltime_resamples(), and fallback logic when prediction columns go missing across versions. Reproducibility gets the same treatment through explicit seeding.
Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either camtrapdp or modeltime.resample.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all camtrapdp alternatives → · See all modeltime.resample alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. camtrapdp is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. camtrapdp is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top camtrapdp alternatives in Analytics are ranked by recent ship velocity. Browse the "camtrapdp alternatives" section above for the current picks, or visit /alternatives/camtrapdp for the full list with editorial commentary on each.
Top modeltime.resample alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.resample alternatives" section above for the current picks, or visit /alternatives/modeltime-resample for the full list with editorial commentary on each.