rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
mlr3tuning vs rgbif
A side-by-side editorial comparison of mlr3tuning and rgbif — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3tuning vs rgbif: at a glance
What is mlr3tuning?
mlr3tuning is rebuilding its async machinery under a stable public surface
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
What is rgbif?
rgbif is steadily pushing users off paged searching and onto real downloads.
rgbif ships several times a year and the recent releases cluster around downloads. 3.8.1 added `occ_download_sql()` for SQL-based occurrence downloads; 3.8.2 added DOI-to-download-key resolution and institutionKey downloads; 3.8.3 relayed GBIF's new throttling of bulk paging through `occ_search()` with a message pointing users at `occ_download()`; 3.8.5 added a family of `occ_download_stats_*()` functions plus multiple-taxonomy and verbatim-extension downloads. Alongside that, `name_backbone()` moved to GBIF API v2, and 3.8.0 soft-deprecated `occ_data()`.
mlr3tuning vs rgbif: editorial side-by-side
mlr3tuning
2.5ANALYTICS
mlr3tuning is rebuilding its async machinery under a stable public surface
◆ Current state
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
◆ Where it's heading
Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.
◆ Prediction
With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.
rgbif
0.0ANALYTICS
rgbif is steadily pushing users off paged searching and onto real downloads.
◆ Current state
rgbif ships several times a year and the recent releases cluster around downloads. 3.8.1 added `occ_download_sql()` for SQL-based occurrence downloads; 3.8.2 added DOI-to-download-key resolution and institutionKey downloads; 3.8.3 relayed GBIF's new throttling of bulk paging through `occ_search()` with a message pointing users at `occ_download()`; 3.8.5 added a family of `occ_download_stats_*()` functions plus multiple-taxonomy and verbatim-extension downloads. Alongside that, `name_backbone()` moved to GBIF API v2, and 3.8.0 soft-deprecated `occ_data()`.
◆ Where it's heading
Two things are happening at once. GBIF is discouraging bulk retrieval through the search API, and rgbif is building out the download path fast enough to absorb the traffic — SQL queries, DOI round-tripping, format description, and now statistics about the downloads themselves. Metadata coverage has expanded in parallel, with a dozen `dataset_*()` functions in 3.7.9 and GRSciColl institution search in 3.8.3. The deprecations are consistent: `occ_data()`, `occ_facet()`, `occ_count(type=)` all retired in favour of narrower replacements.
◆ Prediction
The download surface is where the next additions will land — likely more SQL-download tooling and further statistics endpoints, following 3.8.1 and 3.8.5.
Alternatives to mlr3tuning and rgbif
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 mlr3tuning or rgbif.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
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.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all mlr3tuning alternatives → · See all rgbif alternatives →
Recent activity from mlr3tuning and rgbif
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
- 4mo agorgbifrgbif 3.8.5 adds occurrence download statistics functions
- 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
- 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
- 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
- 8mo agorgbifrgbif 3.8.4 moves name matching to GBIF API v2
- 11mo agorgbifrgbif 3.8.3 adds GRSciColl search, relays GBIF paging throttle
- 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
- 1y agorgbifrgbif 3.8.2 resolves download DOIs to keys
- 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage
- 1y agorgbifrgbif 3.8.1 adds SQL-based occurrence downloads ⚡
- 2y agorgbifrgbif 3.8.0 soft-deprecates occ_data(), adds download describe
Frequently asked questions
What is the difference between mlr3tuning and rgbif?
They serve adjacent needs but don't currently overlap on shipped themes. mlr3tuning is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is mlr3tuning better than rgbif?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3tuning is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to mlr3tuning?
Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.
What are the best alternatives to rgbif?
Top rgbif alternatives in Analytics are ranked by recent ship velocity. Browse the "rgbif alternatives" section above for the current picks, or visit /alternatives/rgbif for the full list with editorial commentary on each.