rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
osmdata vs rotl
A side-by-side editorial comparison of osmdata and rotl — release velocity, themes, recent moves, and the top alternatives to consider.
osmdata vs rotl: 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 rotl?
rotl's whole release history is keeping name matching honest against a moving taxonomy.
Nearly every entry concerns `tnrs_match_names()`, the function that maps user-supplied names onto Open Tree taxonomy ids. 3.1.0 changed which taxon wins a multi-way match — highest matching score rather than lowest OTT id, reversing the rule 3.0.4 introduced. 3.0.12 defaulted `context_name` to 'All life' so a context inferred from the first name could not silently skew later ones. 3.0.11 made a total failure to match return an empty tibble with a warning instead of an error. The rest are small fixes tracking Open Tree API changes.
osmdata vs rotl: 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.
rotl
0.0ANALYTICS
rotl's whole release history is keeping name matching honest against a moving taxonomy.
◆ Current state
Nearly every entry concerns `tnrs_match_names()`, the function that maps user-supplied names onto Open Tree taxonomy ids. 3.1.0 changed which taxon wins a multi-way match — highest matching score rather than lowest OTT id, reversing the rule 3.0.4 introduced. 3.0.12 defaulted `context_name` to 'All life' so a context inferred from the first name could not silently skew later ones. 3.0.11 made a total failure to match return an empty tibble with a warning instead of an error. The rest are small fixes tracking Open Tree API changes.
◆ Where it's heading
The recurring problem is ambiguity: names match several taxa, and the package has changed its tie-breaking rule twice while making failures and edge cases return predictable objects rather than errors. Nothing here expands what rotl can retrieve; it makes what it retrieves reproducible. The feed also stops in mid-2023, so the package appears dormant.
◆ Prediction
Nothing in the window suggests new capability. If a release comes, the pattern says it will follow an Open Tree API change or another matching-behaviour correction.
Alternatives to osmdata and rotl
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 rotl.
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.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all osmdata alternatives → · See all rotl alternatives →
Recent activity from osmdata and rotl
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoosmdataosmdata 0.4.0
- 11mo agoosmdataosmdata 0.3.0
- 2y agoosmdataosmdata 0.2.5 resubmitted after CRAN removal
- 3y agorotlrotl 3.1.0 matches on score instead of lowest OTT id
- 3y agoosmdataosmdata 0.2.3 fixes test broken by sp deprecation
- 3y agoosmdataosmdata 0.2.2 adds out:csv queries and centre coordinates
- 3y agoosmdataosmdata 0.2.1 deprecates nodes_only, fixes memory leaks
- 4y agorotlrotl 3.0.12 defaults matching context to All life
- 5y agorotlrotl 3.0.11 returns empty tibble when no names match
- 6y agorotlrotl 3.0.10 tracks Open Tree API updates
- 7y agorotlrotl 3.0.9 tracks Open Tree API updates
- 7y agorotlrotl 3.0.7 updates vignette for TNRS endpoint change
Frequently asked questions
What is the difference between osmdata and rotl?
They serve adjacent needs but don't currently overlap on shipped themes. osmdata and rotl 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 rotl?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmdata and rotl 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 rotl?
Top rotl alternatives in Analytics are ranked by recent ship velocity. Browse the "rotl alternatives" section above for the current picks, or visit /alternatives/rotl for the full list with editorial commentary on each.