rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of desirability2 and rotl — release velocity, themes, recent moves, and the top alternatives to consider.
desirability2 is making multi-metric model selection a first-class tidymodels step.
desirability2 implements desirability functions, which map several metrics onto a common 0-1 scale so they can be combined into a single objective. The package is young: three releases, the first of which only added a NEWS file. Its substance arrived in 0.1.0 with hooks into tidymodels' tune package.
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.
desirability2 implements desirability functions, which map several metrics onto a common 0-1 scale so they can be combined into a single objective. The package is young: three releases, the first of which only added a NEWS file. Its substance arrived in 0.1.0 with hooks into tidymodels' tune package.
The direction is integration rather than standalone use. Version 0.1.0 added select_best_desirability() and show_best_desirability() to resolve a tuning run against several metrics at once; 0.2.0 exported make_desirability_cols() so other packages can build on it and made data-driven limits the default, removing the need to state ranges by hand. Both releases move work from the user into the package.
The exported helper and the developer-facing desirability() API point to adoption by other tidymodels packages as the next step rather than new functionality here.
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.
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.
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.
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 desirability2 or rotl.
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all desirability2 alternatives → · See all rotl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. desirability2 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. desirability2 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.
Top desirability2 alternatives in Analytics are ranked by recent ship velocity. Browse the "desirability2 alternatives" section above for the current picks, or visit /alternatives/desirability2 for the full list with editorial commentary on each.
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.