chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
Comparison · Analytics
mapsf vs osmapiR
A side-by-side editorial comparison of mapsf and osmapiR — release velocity, themes, recent moves, and the top alternatives to consider.
mapsf vs osmapiR: 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 osmapiR?
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
mapsf vs osmapiR: 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.
osmapiR
0.0ANALYTICS
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
◆ Current state
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
◆ Where it's heading
Four consecutive releases open with the same line — documentation and code updated for server-side changes, cited by OSM wiki revision range. That is a maintainer treating an evolving remote API as a versioned contract and auditing against it each cycle, which is unusual discipline and the main reason to trust this client over a hand-rolled wrapper. The second thread is fitting into R's spatial conventions rather than exposing OSM's, visible in the bbox coercion work and the httr2 upgrades landing with upstream help.
◆ Prediction
The pattern is stable enough to call: another release synchronised to the next OSM wiki revision range, adding whatever endpoints appeared and adjusting whatever changed shape.
Alternatives to mapsf and osmapiR
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 osmapiR.
cloudml
Six years since the last functional change, and Google renamed the service it wraps in the release before that
tidymodels
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
datapack
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
USAboundaries
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
slider
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
See all mapsf alternatives → · See all osmapiR alternatives →
Recent activity from mapsf and osmapiR
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
- 5mo agoosmapiRbbox arguments accept sf and terra objects
- 7mo agomapsfPNG resolution control and legend number formatting
- 0y agoosmapiRNote search defaults to creation order; JSON for GPX metadata
- 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments ⚡
- 1y agoosmapiRNote subscriptions and user block endpoints added
- 1y agoosmapiRChangeset queries gain from and to parameters
- 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
- 1y agoosmapiRJOSS citation added; single-tag conversion fixed
- 2y agomapsfGraticule label display fix
- 2y agoosmapiRComplete OSM API coverage arrives in one release ⚡
Frequently asked questions
What is the difference between mapsf and osmapiR?
They serve adjacent needs but don't currently overlap on shipped themes. mapsf and osmapiR 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 osmapiR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapsf and osmapiR 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 osmapiR?
Top osmapiR alternatives in Analytics are ranked by recent ship velocity. Browse the "osmapiR alternatives" section above for the current picks, or visit /alternatives/osmapir for the full list with editorial commentary on each.