osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
datefixR vs mapsf
A side-by-side editorial comparison of datefixR and mapsf — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
datefixR vs mapsf: at a glance
What is datefixR?
The messy-date parser rewrote its core in Rust and came out 300x faster.
datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.
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.
datefixR vs mapsf: editorial side-by-side
datefixR
0.0ANALYTICS
The messy-date parser rewrote its core in Rust and came out 300x faster.
◆ Current state
datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.
◆ Where it's heading
Two long arcs meet here. The first is localization: Russian, Indonesian, German, Spanish month abbreviations, and experimental Roman numeral months accumulated release by release, with full translation of user-facing messages treated as a goal rather than a bonus. The second is the migration off R for the parsing hot path — internals began moving to C++ around 1.3.1 before the Rust rewrite replaced that work entirely. The 2.0.1 regressions show the cost of that move, since behavior that was implicit in the R implementation had to be re-specified.
◆ Prediction
The Rust core is one release into stabilization and 2.0.1 was entirely regression repair, so expect further correctness fixes against pre-2.0.0 behavior before any new format support lands.
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.
Alternatives to datefixR and mapsf
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 datefixR or mapsf.
ymlthis
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all datefixR alternatives → · See all mapsf alternatives →
Recent activity from datefixR and mapsf
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
- 3mo agodatefixRRust rewrite regressions repaired, silent NA casting stopped
- 7mo agomapsfPNG resolution control and legend number formatting
- 11mo agodatefixRParsing core rewritten in Rust for a 300x speedup ⚡
- 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments ⚡
- 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
- 1y agodatefixRIndonesian month names and translations added
- 2y agomapsfGraticule label display fix
- 2y agodatefixR'ene' and 'ener' recognized as January
- 3y agodatefixRRussian localization, Roman numeral months, Windows freeze fix
- 3y agodatefixRExcel leap-year offset and single-digit day fixes
Frequently asked questions
What is the difference between datefixR and mapsf?
Both compete on the same themes — r-package — within Analytics. datefixR 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.
Is datefixR better than mapsf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. datefixR 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.
What are the best alternatives to datefixR?
Top datefixR alternatives in Analytics are ranked by recent ship velocity. Browse the "datefixR alternatives" section above for the current picks, or visit /alternatives/datefixr for the full list with editorial commentary on each.
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.