tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
Comparison · Analytics
geodist vs vellum
A side-by-side editorial comparison of geodist and vellum — release velocity, themes, recent moves, and the top alternatives to consider.
geodist vs vellum: at a glance
What is geodist?
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.
What is vellum?
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
geodist vs vellum: editorial side-by-side
geodist
0.0ANALYTICS
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
vellum
5.0ANALYTICS
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
◆ Current state
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
◆ Where it's heading
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
◆ Prediction
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
Alternatives to geodist and vellum
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 vellum.
tern.mmrm
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
ggmagnify
A single-purpose ggplot2 inset tool, refining the same three arguments.
symengine
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools
gtfstools stopped guarding its own object model and started accepting everyone else's.
quantities
The glue package that makes R carry units and uncertainty through the same calculation.
See all geodist alternatives → · See all vellum alternatives →
Recent activity from geodist and vellum
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agovellumLinter grows to 20 rules and stops firing on every plot
- 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
- 14d agovellumPick table now reports device pixels instead of two coordinate systems
- 15d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
- 15d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
- 15d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
- 1y agogeodistgeodist 0.1.1 clears a clang warning in geodesic.c
- 2y agogeodistgeodist 0.1.0 adds geodist_min() for nearest matches
- 3y agogeodistgeodist 0.0.8 updates geodesic source, fixes clang warnings
- 5y agogeodistgeodist 0.0.7 improves lon/lat column matching and tibbles
- 5y agogeodistgeodist 0.0.6 warns when cheap distances exceed 100km
- 6y agogeodistgeodist 0.0.4 adds geodist_vec() for vector inputs
Frequently asked questions
What is the difference between geodist and vellum?
They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 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.
Is geodist better than vellum?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum is currently shipping more aggressively (velocity 5.0 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.
What are the best alternatives to geodist?
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.
What are the best alternatives to vellum?
Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.