tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of geodist and parallelDist — 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.
parallelDist is in pure preservation mode — one build fix every few years.
parallelDist computes distance matrices across threads in C++ via RcppParallel and Armadillo. The feature set has been settled since 0.2.3 in 2018, which added hamming distance and cosine similarity; everything after that is compatibility work. The most recent release, 0.2.7, exists only to drop a C++11 pin that newer Armadillo versions no longer tolerate.
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.
parallelDist computes distance matrices across threads in C++ via RcppParallel and Armadillo. The feature set has been settled since 0.2.3 in 2018, which added hamming distance and cosine similarity; everything after that is compatibility work. The most recent release, 0.2.7, exists only to drop a C++11 pin that newer Armadillo versions no longer tolerate.
The package is being kept installable, not developed. The three most recent releases are a toolchain pin removal, a DESCRIPTION field removal, and a coercion change inherited from proxy — none originate from user-facing intent. Gaps of three to four years between releases are the norm now, and each one is triggered by something upstream breaking rather than by a roadmap.
The next release will almost certainly be another compatibility fix timed to whatever Armadillo, Rcpp or CRAN check policy changes next. Nothing in the entries points to new distance measures or API work.
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 parallelDist.
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 parallelDist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geodist and parallelDist 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 parallelDist 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 parallelDist alternatives in Analytics are ranked by recent ship velocity. Browse the "parallelDist alternatives" section above for the current picks, or visit /alternatives/paralleldist for the full list with editorial commentary on each.