nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
A side-by-side editorial comparison of cffr and mapsf — release velocity, themes, recent moves, and the top alternatives to consider.
cffr keeps CITATION.cff generation in step with the standard and its R sources.
The package generates and validates CITATION.cff files from R package metadata. Recent work is validation and parsing accuracy rather than new outputs: cff_validate() moved onto the ajv engine through jsonvalidate for clearer errors, ROR identifiers act as a website fallback for people and entities, and DOIs are now detected in inst/CITATION url fields including dx.doi.org forms.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.
The package generates and validates CITATION.cff files from R package metadata. Recent work is validation and parsing accuracy rather than new outputs: cff_validate() moved onto the ajv engine through jsonvalidate for clearer errors, ROR identifiers act as a website fallback for people and entities, and DOIs are now detected in inst/CITATION url fields including dx.doi.org forms.
The package tracks two moving targets — the Citation File Format schema and R's own person and citation handling, which has broken extraction twice in recent releases. Between those, releases pick up ecosystem details: Codeberg recognised as a repository host, CRAN-to-SPDX licence mappings refreshed, GitHub Action defaults changed to save quota. The most recent release is an internal refactor carried out with AI assistance, with no user-facing change.
With validation migrated and the R 4.5 person changes absorbed, the next release most likely follows a Citation File Format schema update rather than adding capability.
mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.
The package has been consolidating control into fewer, more consistent places. Legend handling moved out to the maplegend package in 0.8.0 and the per-element mf_legend_* functions were deprecated in favor of arguments on the map calls themselves; theming replaced ad-hoc style arguments in 1.0.0; and recent releases keep propagating the same argument vocabulary — bg, extent, leg_val_rnd, leg_val_dec, leg_val_big — across every function that should accept it. Determinism is a visible concern too, with 1.2.1 fixing a seed so mf_distr() point positions stop moving between runs.
The recent releases are almost entirely argument-parity work across existing functions, so expect that to continue until the vocabulary is uniform rather than any new map type appearing.
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 cffr or mapsf.
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
S7 has stopped adding surface and started proving it holds up against R itself.
R's torchvision is porting PyTorch's vision stack one task at a time — instance segmentation just landed.
The messy-date parser rewrote its core in Rust and came out 300x faster.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cffr and mapsf 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. cffr and mapsf 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 cffr alternatives in Analytics are ranked by recent ship velocity. Browse the "cffr alternatives" section above for the current picks, or visit /alternatives/cffr for the full list with editorial commentary on each.
Top mapsf alternatives in Analytics are ranked by recent ship velocity. Browse the "mapsf alternatives" section above for the current picks, or visit /alternatives/mapsf for the full list with editorial commentary on each.