rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of dtplyr and taxa — release velocity, themes, recent moves, and the top alternatives to consider.
dtplyr stopped hijacking data.table objects and became an opt-in translator
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
The package is trailing dplyr's own feature releases rather than leading them, adding each new verb once it settles upstream. Performance work is targeted at specific verbs where data.table has a faster primitive: setorder() for arrange(), reference drops for select(), rleid() for consecutive_id(). Release cadence has thinned considerably since 2023.
Expect further one-for-one translations as dplyr adds verbs, and continued fixes around .by and non-standard column names; the entries show no sign of a broader redesign.
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
The rewrite has not landed. `taxmap`, the class most users came for, was never reimplemented in the new design, and the only releases since are CRAN compliance. Meanwhile metacoder still carries the old taxa, which means the ecosystem is running on the version the rewrite was meant to replace. This reads as a stalled migration rather than an active one.
Nothing in the entries indicates the rewrite is resuming; the likely next release is another CRAN-check fix. Whether `taxmap` ever arrives in the new design is unresolved.
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 dtplyr or taxa.
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.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dtplyr and taxa 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. dtplyr and taxa 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 dtplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dtplyr alternatives" section above for the current picks, or visit /alternatives/dtplyr for the full list with editorial commentary on each.
Top taxa alternatives in Analytics are ranked by recent ship velocity. Browse the "taxa alternatives" section above for the current picks, or visit /alternatives/taxa-r for the full list with editorial commentary on each.