graphicalMCP
graphicalMCP is a narrow statistical tool being hardened rather than grown.
Comparison · Analytics
mapsf vs waywiser
A side-by-side editorial comparison of mapsf and waywiser — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
mapsf vs waywiser: at a glance
What is mapsf?
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.
What is waywiser?
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.
mapsf vs waywiser: editorial side-by-side
mapsf
0.0ANALYTICS
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
waywiser
0.0ANALYTICS
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
◆ Current state
waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.
◆ Where it's heading
The package has reached the point where the interesting bugs are cross-platform and cross-package rather than statistical. Its main function, ww_multi_scale(), has been the focus of nearly every release since 0.4.0, working through units handling, aggregation ordering, raster inputs and metric-type dispatch. The dependency on vip and the tidymodels metric machinery means a share of releases exist only to track breaking changes elsewhere.
◆ Prediction
Expect the next substantive release to continue on ww_multi_scale() edge cases, given that it has absorbed most of the fixes in this window. The recent run of CRAN-compliance patches suggests no feature work is currently in flight.
Alternatives to mapsf and waywiser
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 mapsf or waywiser.
rtflite
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
git2rdata
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
osmextract
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
See all mapsf alternatives → · See all waywiser alternatives →
Recent activity from mapsf and waywiser
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agomapsfLabel placement arguments and deterministic distribution plots
- 2mo agomapsfBackground and extent control across the drawing functions
- 7mo agomapsfPNG resolution control and legend number formatting
- 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments ⚡
- 1y agowaywiserStops downloading data during CRAN checks
- 1y agowaywiserVignettes no longer write to CRAN directories
- 1y agowaywiserKeeps the R version floor below 4.1
- 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
- 2y agomapsfGraticule label display fix
- 2y agowaywiserNaN results become NA; raster metrics dispatch correctly
- 2y agowaywiserGuards against ignored grid arguments; faster on sf data
- 2y agowaywiserFixes wrong observation counts and ignored grid units
Frequently asked questions
What is the difference between mapsf and waywiser?
Both compete on the same themes — r-package — within Analytics. mapsf and waywiser 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 mapsf better than waywiser?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapsf and waywiser 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 mapsf?
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.
What are the best alternatives to waywiser?
Top waywiser alternatives in Analytics are ranked by recent ship velocity. Browse the "waywiser alternatives" section above for the current picks, or visit /alternatives/waywiser for the full list with editorial commentary on each.