tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of geodist and watina — release velocity, themes, recent moves, and the top alternatives to consider.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
A groundwater database client that has started doing the domain analysis too
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
The package is drifting from a database client toward a domain toolkit. Early releases fought the data layer — connection handling moved to inbodb, sorting semantics changed, defunct dbplyr calls worked around. Recent work assumes retrieval is solved and adds hydrochemical analysis on top, along with defensive handling for the physically impossible inputs that analysis exposes, such as zero conductivity in the warehouse.
Expect further chemistry analysis and plotting helpers rather than new retrieval functions, since that is where the newest release invested and where the accompanying vignette points.
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 geodist or watina.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all geodist alternatives → · See all watina alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. geodist and watina 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geodist and watina 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.
Top geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.
Top watina alternatives in Analytics are ranked by recent ship velocity. Browse the "watina alternatives" section above for the current picks, or visit /alternatives/watina-r for the full list with editorial commentary on each.