rjd3highfreq
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
Comparison · Analytics
geoarrow-r vs gtsummary
A side-by-side editorial comparison of geoarrow-r and gtsummary — release velocity, themes, recent moves, and the top alternatives to consider.
geoarrow-r vs gtsummary: at a glance
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.
What is gtsummary?
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
geoarrow-r vs gtsummary: editorial side-by-side
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.
gtsummary
0.0ANALYTICS
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
◆ Current state
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
◆ Where it's heading
The ARD work is the through-line. Table IDs exist so gather_ard() can return a named list; hierarchical tables gained per-level sorting and targeted filtering; ARD inputs are pre-processed so sorting applies to non-standard shapes. The package is becoming a structured-results engine that happens to render tables, rather than a renderer alone. Alongside that, 2.2.0 restored data pre-processing that 2.0 had removed after the reduced functionality hurt users — a maintainer willing to reverse a major-version decision.
◆ Prediction
Expect the hierarchical and ARD functions, introduced as a preview without a full deprecation cycle, to keep stabilizing toward a settled API rather than new table types appearing.
Alternatives to geoarrow-r and gtsummary
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 geoarrow-r or gtsummary.
audubon
audubon's release feed is almost entirely Renovate bumping the JavaScript toolchain behind its Japanese text splitter.
affiner
affiner is quietly turning a grid transformation helper into a small computational geometry library.
ageproR
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
r-ledger
ledger adds a Rust toolchain fallback, so beancount imports work whether or not the Python tooling is installed.
gridpattern
gridpattern keeps widening its catalogue, and the newest patterns finally use the device's own line rendering.
See all geoarrow-r alternatives → · See all gtsummary alternatives →
Recent activity from geoarrow-r and gtsummary
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agogeoarrow-rgeoarrow 0.4.3
- 2mo agogtsummaryTheme elements no longer evaluated by default
- 8mo agogtsummaryARD strata functions and finer theme control
- 8mo agogeoarrow-rgeoarrow 0.4.1
- 10mo agogeoarrow-rgeoarrow lets callers choose the geometry type when converting from sf
- 11mo agogtsummaryPer-level hierarchical sorting and labeled stacking
- 1y agogtsummaryTable splitting, ID labeling, and add_difference_row
- 1y agogeoarrow-rgeoarrow implements the GeoArrow 0.2 specification features
- 1y agogtsummaryData pre-processing restored after the 2.0 removal
- 1y agogtsummarytbl_merge gains explicit merge columns
- 2y agogeoarrow-rgeoarrow 0.2.1
- 2y agogeoarrow-rLegacy geoarrow tagged before the rewrite
Frequently asked questions
What is the difference between geoarrow-r and gtsummary?
They serve adjacent needs but don't currently overlap on shipped themes. geoarrow-r and gtsummary 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 geoarrow-r better than gtsummary?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geoarrow-r and gtsummary 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 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.
What are the best alternatives to gtsummary?
Top gtsummary alternatives in Analytics are ranked by recent ship velocity. Browse the "gtsummary alternatives" section above for the current picks, or visit /alternatives/gtsummary-r for the full list with editorial commentary on each.