OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
Comparison · Analytics
EpiNow2 vs geoarrow-r
A side-by-side editorial comparison of EpiNow2 and geoarrow-r — release velocity, themes, recent moves, and the top alternatives to consider.
EpiNow2 vs geoarrow-r: at a glance
What is EpiNow2?
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
What is geoarrow-r?
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
geoarrow gives R zero-copy access to geospatial data in the Arrow columnar format, with conversions to and from sf and wk. The package is thin by design — most of the work lives in vendored copies of geoarrow-c and nanoarrow — and its release notes reflect that: the substantive one in the window implemented GeoArrow 0.2 specification features, and everything since has been compiler warnings and a test fixed for a new sf version.
EpiNow2 vs geoarrow-r: editorial side-by-side
EpiNow2
0.0ANALYTICS
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
◆ Current state
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
◆ Where it's heading
The package spent this window paying down interface debt and is now extending from the tidier base. Options that existed only for `estimate_infections()` have been propagated outward: `estimate_truncation()` gained the full `dist_spec` delay families, `obs_opts()` observation model selection between Poisson and negative binomial, and the `likelihood` and `return_likelihood` settings that make prior-only fits and loo-compatible output possible. Hardcoded assumptions are being replaced by specifiable ones in the same motion — the truncation model's additive noise term was a fixed `sigma ~ normal(0, 1)` prior and is now a `dist_spec` argument.
◆ Prediction
Expect the remaining modelling functions to keep converging on the shared options interface, since the last two releases have each moved another function onto it. A new `estimate_dist()` for interval-censored linelist data suggests delay estimation is the area still gaining surface.
geoarrow-r
0.0ANALYTICS
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
◆ Current state
geoarrow gives R zero-copy access to geospatial data in the Arrow columnar format, with conversions to and from sf and wk. The package is thin by design — most of the work lives in vendored copies of geoarrow-c and nanoarrow — and its release notes reflect that: the substantive one in the window implemented GeoArrow 0.2 specification features, and everything since has been compiler warnings and a test fixed for a new sf version.
◆ Where it's heading
Development is downstream of two things the package does not control: the GeoArrow specification and the C libraries it vendors. When the spec added non-PROJJSON CRS types and spheroidal edge interpolations, the R package followed; when the geoarrow.box type appeared, it gained conversions to and from wk::rct(). Between those, releases exist to keep CRAN builds green. The type-selection work in 0.4.0 — letting callers force geoarrow.wkb output when converting from sf — is the only recent change driven by R-side ergonomics rather than upstream.
◆ Prediction
Given that every feature release so far has implemented a spec revision, the next one likely arrives when GeoArrow publishes its next set of extension types rather than on any schedule of its own.
Alternatives to EpiNow2 and geoarrow-r
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 EpiNow2 or geoarrow-r.
fastplyr
A fast dplyr stand-in that keeps finding new places to skip work entirely.
trias
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
icesSAG
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
dggridR
A discrete global grid generator grew cell traversal and became a usable spatial index.
vegan
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all EpiNow2 alternatives → · See all geoarrow-r alternatives →
Recent activity from EpiNow2 and geoarrow-r
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoEpiNow2estimate_truncation gains full delay and observation options
- 2mo agogeoarrow-rgeoarrow 0.4.3
- 6mo agoEpiNow2Unified return objects and shared accessors across all models ⚡
- 8mo agogeoarrow-rgeoarrow 0.4.1
- 10mo agogeoarrow-rgeoarrow lets callers choose the geometry type when converting from sf
- 1y agogeoarrow-rgeoarrow implements the GeoArrow 0.2 specification features
- 1y agoEpiNow2Patch for an upstream rstan issue
- 1y agoEpiNow2Accumulation for irregularly reported data; unified priors
- 1y agoEpiNow2Matern kernel spectral density fix and GP prior revert
- 1y agoEpiNow2Gaussian Process model improvements and explicit defaults
- 2y agogeoarrow-rgeoarrow 0.2.1
- 2y agogeoarrow-rLegacy geoarrow tagged before the rewrite
Frequently asked questions
What is the difference between EpiNow2 and geoarrow-r?
They serve adjacent needs but don't currently overlap on shipped themes. EpiNow2 and geoarrow-r are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is EpiNow2 better than geoarrow-r?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EpiNow2 and geoarrow-r are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to EpiNow2?
Top EpiNow2 alternatives in Analytics are ranked by recent ship velocity. Browse the "EpiNow2 alternatives" section above for the current picks, or visit /alternatives/epinow2 for the full list with editorial commentary on each.
What are the best alternatives to geoarrow-r?
Top geoarrow-r alternatives in Analytics are ranked by recent ship velocity. Browse the "geoarrow-r alternatives" section above for the current picks, or visit /alternatives/geoarrow-r for the full list with editorial commentary on each.