r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of osmextract and slider — release velocity, themes, recent moves, and the top alternatives to consider.
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
osmextract downloads OpenStreetMap extracts from Geofabrik, BBBike and openstreetmap.fr and translates them into sf objects via GDAL. The 0.6.0 release moved its download cache from `tempdir()` to a persistent `tools::R_user_dir()` location and raised the R floor to 4.1.0 to get it. It also made spatial `place` inputs self-clipping: pass an sf or bbox object and the boundary is now set to match, so only the relevant slice of a country-sized extract is processed.
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.
osmextract downloads OpenStreetMap extracts from Geofabrik, BBBike and openstreetmap.fr and translates them into sf objects via GDAL. The 0.6.0 release moved its download cache from `tempdir()` to a persistent `tools::R_user_dir()` location and raised the R floor to 4.1.0 to get it. It also made spatial `place` inputs self-clipping: pass an sf or bbox object and the boundary is now set to match, so only the relevant slice of a country-sized extract is processed.
Two threads run through every release. One is chasing GDAL — SQL syntax adjusted for 3.10, ogr2ogr options fixed for 3.9, and an `osmconf.ini` that 0.6.0 finally keeps automatically in sync with whatever sf or GDAL provides rather than shipping a snapshot. The other is the road-network extraction added experimentally in 0.3.1, which has been quietly accumulating real routing semantics since: `access = no` links retained when the mode-specific tag permits them, a `oneway` column by default for driving, and `motor_vehicle` always included.
Given that `oe_get_network()` has gained transport-mode detail in three separate releases while remaining flagged as experimental, the next substantive work is most likely there — either more modes or a formal exit from experimental status.
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.
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.
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.
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 osmextract or slider.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all osmextract alternatives → · See all slider alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. osmextract 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmextract 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.
Top osmextract alternatives in Analytics are ranked by recent ship velocity. Browse the "osmextract alternatives" section above for the current picks, or visit /alternatives/osmextract for the full list with editorial commentary on each.
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.