rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of rgbif and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
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()`.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
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()`.
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.
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.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
The feature era ended before this window opened. Deploying to SageMaker, generating Docker files, storing renv lockfiles in model metadata and supporting keras, luz and recipes all landed in 0.2.1 and 0.2.2; nothing since has extended what vetiver does. What it does now is track the rest of tidymodels — when recipes gains a prototype API or probably becomes something a workflow can contain, vetiver adds a line. That is a package holding its position rather than advancing it.
The entries do not support a confident prediction of new capability. On this pattern the next release tracks another tidymodels change, most likely the postprocessing stage that workflows added in 1.3.0.
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 vetiver.
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.
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.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all rgbif alternatives → · See all vetiver alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rgbif and vetiver 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. rgbif and vetiver 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 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.
Top vetiver alternatives in Analytics are ranked by recent ship velocity. Browse the "vetiver alternatives" section above for the current picks, or visit /alternatives/vetiver-r for the full list with editorial commentary on each.