bittermelon
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
A side-by-side editorial comparison of affiner and geoarrow-r — release velocity, themes, recent moves, and the top alternatives to consider.
affiner is quietly turning a grid transformation helper into a small computational geometry library.
An R package that began as a wrapper around grid's affine transformation primitives, with an angle vector class supporting degrees, radians, half-turns, turns and gradians so users need not convert by hand. Four releases in roughly eighteen months. The recent two have expanded well past that starting point into geometric objects and the predicates that operate on them.
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.
An R package that began as a wrapper around grid's affine transformation primitives, with an angle vector class supporting degrees, radians, half-turns, turns and gradians so users need not convert by hand. Four releases in roughly eighteen months. The recent two have expanded well past that starting point into geometric objects and the predicates that operate on them.
The direction is clear from the order things arrived. Version 0.2.1 added the predicate layer first — has_intersection(), intersection(), is_equivalent() and is_parallel() as S3 generics working across angle vectors, points, lines and planes. Version 0.3.1 then supplied the objects those generics need, with Ellipse2D, Polygon2D and Segment2D R6 classes plus constructors for rectangles, regular n-gons and isotoxal star polygons, and dot products at one, two and three dimensions. Building the operations before the shapes is unusual ordering but it means each new object type arrives already composable with everything else.
Expect more 2D and 3D object types filling out the same generic interface, and the geometry side to keep outgrowing the grid-transformation wrapper the package was named for.
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.
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.
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.
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 affiner or geoarrow-r.
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
epiworldR is a thin R shell whose releases track the C++ simulator underneath it
A groundwater database client that has started doing the domain analysis too
A thin R wrapper over Flemish geospatial services, adding one standard at a time
Fluent Bit keeps two lines alive while the 5.x branch quietly opens 5.1.
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
See all affiner alternatives → · See all geoarrow-r alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. affiner and geoarrow-r 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. affiner and geoarrow-r 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 affiner alternatives in Analytics are ranked by recent ship velocity. Browse the "affiner alternatives" section above for the current picks, or visit /alternatives/affiner-r for the full list with editorial commentary on each.
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.