rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of ggeffects and rgbif — release velocity, themes, recent moves, and the top alternatives to consider.
ggeffects hands its contrast engine to modelbased and keeps the interface
ggeffects computes and plots marginal effects for a long tail of R model classes. Its recent line has two threads: steadily broadening model support and argument surface, and repeatedly absorbing breaking changes from the packages it computes on top of. In 2.2.0 it stopped absorbing them and delegated test_predictions() and johnson_neyman() to modelbased instead.
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()`.
ggeffects computes and plots marginal effects for a long tail of R model classes. Its recent line has two threads: steadily broadening model support and argument surface, and repeatedly absorbing breaking changes from the packages it computes on top of. In 2.2.0 it stopped absorbing them and delegated test_predictions() and johnson_neyman() to modelbased instead.
The package is settling into a front-end role — a consistent predict_response() interface over other people's estimation engines — rather than owning the computation itself. The 2.x releases also show a pattern of removing deprecated arguments and clarifying mixed-model semantics, so the interface is being tightened as the backend is outsourced.
Expect the features lost in the modelbased handover to return as that package's contrast and slope estimation matures, rather than being reimplemented locally.
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.
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 ggeffects or rgbif.
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 ggeffects alternatives → · See all rgbif alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ggeffects and rgbif 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. ggeffects and rgbif 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 ggeffects alternatives in Analytics are ranked by recent ship velocity. Browse the "ggeffects alternatives" section above for the current picks, or visit /alternatives/ggeffects for the full list with editorial commentary on each.
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.