rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
rotl vs taxize
A side-by-side editorial comparison of rotl and taxize — release velocity, themes, recent moves, and the top alternatives to consider.
rotl vs taxize: at a glance
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.
What is taxize?
taxize spends its releases absorbing other people's API changes, one dead source at a time.
The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.
rotl vs taxize: editorial side-by-side
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.
taxize
0.0ANALYTICS
taxize spends its releases absorbing other people's API changes, one dead source at a time.
◆ Current state
The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.
◆ Where it's heading
taxize's job is aggregating a dozen taxonomic databases, so most of its engineering is downstream of decisions it does not control — sources go away, endpoints change, rate limits appear. The visible trend is consolidation: fewer, better-maintained backends rather than broader coverage. Release cadence has thinned to roughly one a year, and the rredlist coupling means it now inherits that package's breaking changes too.
◆ Prediction
Expect the next release to track another upstream source change rather than add new databases; the deprecated-parameter aliases from the 0.9.97 rename are also overdue for removal.
Alternatives to rotl and taxize
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 rotl or taxize.
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.
osmdata
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
Recent activity from rotl and taxize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agotaxizetaxize 0.10.1 lowers gna_verifier batch size
- 1y agotaxizetaxize 0.10.0 migrates to GNA and the new rredlist API
- 3y agorotlrotl 3.1.0 matches on score instead of lowest OTT id
- 4y agorotlrotl 3.0.12 defaults matching context to All life
- 5y agotaxizetaxize 0.9.99 retires tnrs(), paginates WORMS queries
- 5y agorotlrotl 3.0.11 returns empty tibble when no names match
- 5y agotaxizetaxize 0.9.98 adds NCBI and zoological rank names
- 6y agotaxizetaxize 0.9.97 standardises parameter names package-wide
- 6y agotaxizetaxize 0.9.96 updates NatureServe for its new API
- 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 rotl and taxize?
They serve adjacent needs but don't currently overlap on shipped themes. rotl and taxize 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 rotl better than taxize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rotl and taxize 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 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.
What are the best alternatives to taxize?
Top taxize alternatives in Analytics are ranked by recent ship velocity. Browse the "taxize alternatives" section above for the current picks, or visit /alternatives/taxize for the full list with editorial commentary on each.