OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
Comparison · Analytics
geoarrow-r vs units
A side-by-side editorial comparison of geoarrow-r and units — release velocity, themes, recent moves, and the top alternatives to consider.
geoarrow-r vs units: 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 units?
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
geoarrow-r vs units: 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.
units
0.0ANALYTICS
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
◆ Current state
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
◆ Where it's heading
The long 0.8-x run was accretion — ggplot2 scales absorbed from ggforce, ud_convert(), matrix methods, steady performance work — while known parsing defects stayed in place. The 1.0 release finally traded backwards compatibility for correct parsing, and 1.0-1's pointer-wrapping and exception-propagation work suggests the C++ glue is being hardened behind it. Fixes cluster at the udunits2 boundary, which remains the main source of surprises.
◆ Prediction
Expect continued patch releases against udunits2 quirks and the new tokenizer's fallout rather than new surface area, with the ggplot2 integration and conversion helpers already in place.
Alternatives to geoarrow-r and units
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 units.
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 geoarrow-r alternatives → · See all units alternatives →
Recent activity from geoarrow-r and units
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agogeoarrow-rgeoarrow 0.4.3
- 5mo agounitsMemory-leak and udunits2 parsing fixes after 1.0
- 8mo agogeoarrow-rgeoarrow 0.4.1
- 10mo agounitsNew tokenizer parses compound units correctly ⚡
- 10mo agogeoarrow-rgeoarrow lets callers choose the geometry type when converting from sf
- 1y agogeoarrow-rgeoarrow implements the GeoArrow 0.2 specification features
- 1y agounitsCopy semantics fix in ud_convert(); C++17 for old R
- 1y agounitscbind/rbind methods, ud_convert() and broad fixes
- 1y agounitsSilences a CRAN compiler warning
- 2y agogeoarrow-rgeoarrow 0.2.1
- 2y agogeoarrow-rLegacy geoarrow tagged before the rewrite
- 2y agounitsRestores simplify=FALSE for identical units
Frequently asked questions
What is the difference between geoarrow-r and units?
They serve adjacent needs but don't currently overlap on shipped themes. geoarrow-r and units 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 units?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geoarrow-r and units 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 units?
Top units alternatives in Analytics are ranked by recent ship velocity. Browse the "units alternatives" section above for the current picks, or visit /alternatives/units-r for the full list with editorial commentary on each.