rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
osmdata vs rredlist
A side-by-side editorial comparison of osmdata and rredlist — release velocity, themes, recent moves, and the top alternatives to consider.
osmdata vs rredlist: at a glance
What is osmdata?
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
The last two releases are the substantive ones. 0.4.0 lets `getbb()` resolve OSM relations via Wikidata ids, adds `filter_osm_user()` to Overpass query objects, and corrects metadata typing so timestamps are POSIXct rather than locale-dependent strings. 0.3.0 dropped the re-exported magrittr pipe, raised the R floor to 4.1 for the base pipe, and fixed polygon output to follow the OGC simple-features model instead of treating every ring as an independent polygon. Earlier entries are CRAN repairs and query-construction fixes.
What is rredlist?
rredlist threw out its species-centric API in 1.0.0 and rebuilt around assessments.
rredlist 1.0.0 is a hard break: the IUCN Red List API moved to v4, and the package followed by dropping v3 support entirely, reorganising around assessments rather than species, renaming or removing most functions, changing returned data structures, and requiring users to generate a new API key. The two releases since are consolidation on that new shape — `rl_assessment_list()` and `rl_assessment_extract()` for retrieving and unpacking many assessments at once, a `scope` argument on the `*_latest()` functions, and NULL-safe extraction.
osmdata vs rredlist: editorial side-by-side
osmdata
0.0ANALYTICS
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
◆ Current state
The last two releases are the substantive ones. 0.4.0 lets `getbb()` resolve OSM relations via Wikidata ids, adds `filter_osm_user()` to Overpass query objects, and corrects metadata typing so timestamps are POSIXct rather than locale-dependent strings. 0.3.0 dropped the re-exported magrittr pipe, raised the R floor to 4.1 for the base pipe, and fixed polygon output to follow the OGC simple-features model instead of treating every ring as an independent polygon. Earlier entries are CRAN repairs and query-construction fixes.
◆ Where it's heading
The pattern is deliberate correctness work: each release accepts a small breaking change to make returned objects match the standard they claim to follow, whether that is OGC polygon structure, POSIXct timestamps, or UTF-8 metadata columns. Alongside it, the Overpass query builder keeps gaining filters — by area, by out type, by osm_types, now by user and via Wikidata. The package is maturing rather than expanding.
◆ Prediction
More Overpass filter and query-object composition helpers are the likeliest next additions, since that is where both recent releases put their new surface.
rredlist
0.0ANALYTICS
rredlist threw out its species-centric API in 1.0.0 and rebuilt around assessments.
◆ Current state
rredlist 1.0.0 is a hard break: the IUCN Red List API moved to v4, and the package followed by dropping v3 support entirely, reorganising around assessments rather than species, renaming or removing most functions, changing returned data structures, and requiring users to generate a new API key. The two releases since are consolidation on that new shape — `rl_assessment_list()` and `rl_assessment_extract()` for retrieving and unpacking many assessments at once, a `scope` argument on the `*_latest()` functions, and NULL-safe extraction.
◆ Where it's heading
Post-1.0.0 work is clearly aimed at bulk use: fetch many assessments, pull a chosen field out of each. That is a different usage pattern from the one-species-at-a-time queries the v3-era functions encouraged, and it suits the conservation-analysis workloads the package is actually used for. Deprecated v3 functions are still present and flagged for eventual removal.
◆ Prediction
The deprecated v3-era functions are the obvious next thing to disappear, and further bulk-retrieval helpers are likely given both post-1.0 releases went that way.
Alternatives to osmdata and rredlist
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 osmdata or rredlist.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all osmdata alternatives → · See all rredlist alternatives →
Recent activity from osmdata and rredlist
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoosmdataosmdata 0.4.0
- 11mo agorredlistrredlist 1.1.1 extracts multiple assessment elements
- 11mo agoosmdataosmdata 0.3.0
- 1y agorredlistrredlist 1.1.0 adds bulk assessment retrieval and extraction
- 1y agorredlistrredlist 1.0.0 rebuilds on IUCN Red List API v4 ⚡
- 2y agoosmdataosmdata 0.2.5 resubmitted after CRAN removal
- 3y agoosmdataosmdata 0.2.3 fixes test broken by sp deprecation
- 3y agoosmdataosmdata 0.2.2 adds out:csv queries and centre coordinates
- 3y agorredlistrredlist 0.7.1 changes maintainer
- 3y agoosmdataosmdata 0.2.1 deprecates nodes_only, fixes memory leaks
- 5y agorredlistrredlist 0.7.0 adds vignette and HTTPS base URL
- 6y agorredlistrredlist 0.6.0 improves docs and NA handling
Frequently asked questions
What is the difference between osmdata and rredlist?
They serve adjacent needs but don't currently overlap on shipped themes. osmdata and rredlist 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 osmdata better than rredlist?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmdata and rredlist 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 osmdata?
Top osmdata alternatives in Analytics are ranked by recent ship velocity. Browse the "osmdata alternatives" section above for the current picks, or visit /alternatives/osmdata for the full list with editorial commentary on each.
What are the best alternatives to rredlist?
Top rredlist alternatives in Analytics are ranked by recent ship velocity. Browse the "rredlist alternatives" section above for the current picks, or visit /alternatives/rredlist for the full list with editorial commentary on each.