← Back to home
Comparison · Analytics

mapsf vs riem

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

Shared themes:r-package

mapsf vs riem: at a glance

Featuremapsfriem
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themescartography, thematic-maps, spatial, base-graphicsweather-data, api-client, r-package, ropensci
Last editorial update3h ago56m 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 riem?

A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.

riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.

Read the full riem trajectory →

mapsf vs riem: 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.

R
riem
ANALYTICS
0.0

A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.

◆ Current state

riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.

◆ Where it's heading

The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.

◆ Prediction

With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing again.

Alternatives to mapsf and riem

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

See all mapsf alternatives → · See all riem alternatives →

Recent activity from mapsf and riem

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. 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments
  5. 1y agoriem1.0.0 removes defaults and adds query arguments
  6. 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
  7. 1y agoriemDrops the last vcr usage in favour of httptest2
  8. 2y agomapsfGraticule label display fix
  9. 2y agoriemTimezone and timestamp-parsing fixes
  10. 4y agoriemMoves to httr2 and httptest2
  11. 4y agoriemSwitches to newer IEM metadata web services
  12. 9y agoriemReduces dependencies to tibble alone

Frequently asked questions

What is the difference between mapsf and riem?

Both compete on the same themes — r-package — within Analytics. mapsf and riem 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 riem?

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

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