← Back to home
Comparison · Analytics

mapsf vs slider

A side-by-side editorial comparison of mapsf and slider — release velocity, themes, recent moves, and the top alternatives to consider.

mapsf vs slider: at a glance

Featuremapsfslider
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themescartography, thematic-maps, spatial, base-graphicssliding-windows, tidyverse, c-api-compliance, vctrs
Last editorial update2h ago45m ago
WebsiteVisit →Visit →

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.

Read the full mapsf trajectory →

What is slider?

Feature-complete since 2021, and every release since has been paying CRAN's C API bill

slider provides sliding-window and index-aware window functions for R, with a C implementation underneath and a specialised fast path for common aggregations. The user-facing surface has been stable since 0.3.0 in late 2022. Everything after that is compliance and platform work: STRING_PTR removed in 0.3.2, OBJECT() removed in 0.3.3, a vctrs callable's C signature corrected, and the minimum R version raised twice.

Read the full slider trajectory →

mapsf vs slider: editorial side-by-side

M
mapsf
ANALYTICS
0.0

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.

S
slider
ANALYTICS
0.0

Feature-complete since 2021, and every release since has been paying CRAN's C API bill

◆ Current state

slider provides sliding-window and index-aware window functions for R, with a C implementation underneath and a specialised fast path for common aggregations. The user-facing surface has been stable since 0.3.0 in late 2022. Everything after that is compliance and platform work: STRING_PTR removed in 0.3.2, OBJECT() removed in 0.3.3, a vctrs callable's C signature corrected, and the minimum R version raised twice.

◆ Where it's heading

Two forces set the release schedule, and neither is feature demand. The first is CRAN closing off non-API C entry points, which packages reaching into R internals for speed have to unwind one accessor at a time — slider is on its second such release with no visible loss of function. The second is vctrs, whose breaking changes slider absorbs ahead of time; 0.2.2 exists solely to prepare for one. The last release that added anything callers can see was 0.3.0's slider_plus() and slider_minus() extension hooks.

◆ Prediction

Expect the pattern to continue: another non-API accessor removal or a vctrs compatibility release, rather than new window functions. The C-level surface is the only part of this package still moving.

Alternatives to mapsf and slider

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 slider.

See all mapsf alternatives → · See all slider alternatives →

Recent activity from mapsf and slider

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agomapsfLabel placement arguments and deterministic distribution plots
  2. 2mo agomapsfBackground and extent control across the drawing functions
  3. 7mo agomapsfPNG resolution control and legend number formatting
  4. 9mo agosliderNon-API OBJECT() removed and a vctrs C signature fixed
  5. 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments
  6. 1y agosliderNon-API STRING_PTR removed; R 4.0.0 now required
  7. 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
  8. 2y agomapsfGraticule label display fix
  9. 2y agosliderValgrind test fixes and dependency version bumps
  10. 3y agosliderExtension hooks let clock and almanac types serve as an index
  11. 5y agosliderInternal vec_order usage updated ahead of a vctrs break
  12. 5y agosliderlong double alignment issue fixed for CRAN sanitisers

Frequently asked questions

What is the difference between mapsf and slider?

They serve adjacent needs but don't currently overlap on shipped themes. mapsf and slider 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 slider?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapsf and slider 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 slider?

Top slider alternatives in Analytics are ranked by recent ship velocity. Browse the "slider alternatives" section above for the current picks, or visit /alternatives/slider for the full list with editorial commentary on each.