Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of bittermelon and spatstat.geom — release velocity, themes, recent moves, and the top alternatives to consider.
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
The package manipulates bitmap fonts and bitmaps in R, and the recent direction is widening what a glyph can be. v2.3.1 adds greyscale font support by reading the experimental yaff levels property into pixmap glyphs with alpha derived from the level fraction, and makes writing a multi-colored glyph an error rather than silently clamping it. Earlier releases built out the same surface: bm_extract(), an interactive pixel picker, data frame coercion, and format support for other packages' bitmap types.
The geometry layer under spatstat, steadily absorbing 3D patterns and missing-data semantics
spatstat.geom holds the spatial data structures and geometric operations the rest of the spatstat family builds on — windows, tessellations, images, point patterns and the operations that move between them. Recent releases split their attention between extending those structures to three dimensions and hardening the discretisation code where polygonal geometry meets a pixel grid. 3.8-2 adds more capabilities for three-dimensional point patterns.
The package manipulates bitmap fonts and bitmaps in R, and the recent direction is widening what a glyph can be. v2.3.1 adds greyscale font support by reading the experimental yaff levels property into pixmap glyphs with alpha derived from the level fraction, and makes writing a multi-colored glyph an error rather than silently clamping it. Earlier releases built out the same surface: bm_extract(), an interactive pixel picker, data frame coercion, and format support for other packages' bitmap types.
Two things are converging. The representation is moving beyond one-bit glyphs — pixmaps, color, and now greyscale levels with transparency — while the API gets stricter about the boundary between them, refusing to quietly downcast a color glyph on write. Separately, the package has been shedding weight: the embedded monobit copy was removed once it outgrew CRAN size limits, pushing format breadth onto a user-installed dependency.
Expect further greyscale and color work now that levels parsing exists — most likely writing that format rather than only reading it, since the write path is where the current release chose to draw a hard error instead.
spatstat.geom holds the spatial data structures and geometric operations the rest of the spatstat family builds on — windows, tessellations, images, point patterns and the operations that move between them. Recent releases split their attention between extending those structures to three dimensions and hardening the discretisation code where polygonal geometry meets a pixel grid. 3.8-2 adds more capabilities for three-dimensional point patterns.
Two threads run through this window. The first is a family-wide push into 3D that originated in the simulation package and has now reached the geometry layer. The second is a slower semantic change: 3.5-0 introduced missing or unavailable (NA) spatial objects, and 3.6-0 followed with more facilities for handling them, meaning an absent window or image became a representable value rather than an error. Around both, the plotting and discretisation code accretes steadily — nonlinear colour maps, plot backgrounds, transparency control, signed distance transforms, and repeated attention to boundary pixels.
Expect the 3D surface here to keep filling in behind the simulation package rather than leading it, given that 3.8-2 follows the 3D simulation release by two months. The entries give no indication that the NA work is finished, since it has already spanned two releases.
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 bittermelon or spatstat.geom.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
See all bittermelon alternatives → · See all spatstat.geom alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. spatstat.geom is currently shipping more aggressively (velocity 2.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. spatstat.geom is currently shipping more aggressively (velocity 2.5 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.
Top bittermelon alternatives in Analytics are ranked by recent ship velocity. Browse the "bittermelon alternatives" section above for the current picks, or visit /alternatives/bittermelon-r for the full list with editorial commentary on each.
Top spatstat.geom alternatives in Analytics are ranked by recent ship velocity. Browse the "spatstat.geom alternatives" section above for the current picks, or visit /alternatives/spatstat-geom for the full list with editorial commentary on each.