rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of feasts and taxize — release velocity, themes, recent moves, and the top alternatives to consider.
feasts is splitting itself in two, moving every plot into ggtime
feasts provides feature extraction and statistics for tsibble time series. The last two releases are dominated by one decision: all of its gg_*() plotting functions are being moved out into a separate ggtime package. 0.4.2 announced the deprecation and 0.5.0 makes ggtime a dependency with soft-deprecation messages on every re-export.
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`.
feasts provides feature extraction and statistics for tsibble time series. The last two releases are dominated by one decision: all of its gg_*() plotting functions are being moved out into a separate ggtime package. 0.4.2 announced the deprecation and 0.5.0 makes ggtime a dependency with soft-deprecation messages on every re-export.
The package is narrowing to its stated purpose — features and statistics — and shedding graphics entirely over a deliberately slow two-year window. Everything else in the recent history is ggplot2 compatibility work and narrow seasonal-plot bug fixes, which is consistent with a maintainer trimming surface area rather than growing it.
The next releases should be compatibility upkeep while the ggtime deprecation runs its course; the re-exports stay until the announced window closes.
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`.
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.
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.
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 feasts or taxize.
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.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all feasts alternatives → · See all taxize alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — deprecation — within Analytics. feasts 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. feasts 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.
Top feasts alternatives in Analytics are ranked by recent ship velocity. Browse the "feasts alternatives" section above for the current picks, or visit /alternatives/feasts for the full list with editorial commentary on each.
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.