← Back to home
Comparison · Analytics

rgbif vs stacks

A side-by-side editorial comparison of rgbif and stacks — release velocity, themes, recent moves, and the top alternatives to consider.

rgbif vs stacks: at a glance

Featurergbifstacks
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgbif, biodiversity-data, bulk-downloads, sql-queriestidymodels, ensembling, parallel-processing, future-framework
Last editorial update55m ago1h ago
WebsiteVisit →Visit →

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()`.

Read the full rgbif trajectory →

What is stacks?

Model stacking in tidymodels, quietly migrating off foreach and onto future

stacks builds ensembles from tidymodels tuning results, and its release history is dominated by one long project: replacing foreach-based parallelism with the future framework. That transition completed in 1.1.0, where foreach backends began being ignored with a warning and the minimum R version rose to 4.1. Releases are infrequent and small, with the most recent being a CRAN re-submission rather than a change.

Read the full stacks trajectory →

rgbif vs stacks: editorial side-by-side

R
rgbif
ANALYTICS
0.0

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.

S
stacks
ANALYTICS
0.0

Model stacking in tidymodels, quietly migrating off foreach and onto future

◆ Current state

stacks builds ensembles from tidymodels tuning results, and its release history is dominated by one long project: replacing foreach-based parallelism with the future framework. That transition completed in 1.1.0, where foreach backends began being ignored with a warning and the minimum R version rose to 4.1. Releases are infrequent and small, with the most recent being a CRAN re-submission rather than a change.

◆ Where it's heading

The package is mature and its remaining work is compatibility rather than capability — tracking the parallelism story across tidymodels, keeping object sizes sane after butchering and reloading, and staying aligned with recipes deprecations. The augment() method added for vetiver compatibility shows the same instinct: fit into the surrounding ecosystem rather than grow independently of it. Nothing in the visible history suggests new ensembling methods are being pursued.

◆ Prediction

With the future migration finished, the next release is most likely maintenance keeping pace with tune and recipes rather than anything users would notice.

Alternatives to rgbif and stacks

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 rgbif or stacks.

See all rgbif alternatives → · See all stacks alternatives →

Recent activity from rgbif and stacks

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agorgbifrgbif 3.8.5 adds occurrence download statistics functions
  2. 8mo agorgbifrgbif 3.8.4 moves name matching to GBIF API v2
  3. 11mo agorgbifrgbif 3.8.3 adds GRSciColl search, relays GBIF paging throttle
  4. 1y agorgbifrgbif 3.8.2 resolves download DOIs to keys
  5. 1y agostacksstacks 1.1.1 re-released to clear a CRAN check note
  6. 1y agostacksstacks 1.1.0 completes the move to future-based parallelism
  7. 1y agorgbifrgbif 3.8.1 adds SQL-based occurrence downloads
  8. 2y agostacksstacks 1.0.5 fixes butchered stack size inflation
  9. 2y agorgbifrgbif 3.8.0 soft-deprecates occ_data(), adds download describe
  10. 2y agostacksstacks 1.0.4 introduces future-based parallel processing
  11. 2y agostacksstacks 1.0.3 clears recipes deprecations and a type-check bug
  12. 3y agostacksstacks 1.0.2 adds an augment() method for vetiver compatibility

Frequently asked questions

What is the difference between rgbif and stacks?

They serve adjacent needs but don't currently overlap on shipped themes. rgbif and stacks 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 rgbif better than stacks?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rgbif and stacks 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 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.

What are the best alternatives to stacks?

Top stacks alternatives in Analytics are ranked by recent ship velocity. Browse the "stacks alternatives" section above for the current picks, or visit /alternatives/stacks for the full list with editorial commentary on each.