← Back to home
Comparison · Analytics

rgbif vs taxize

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

rgbif vs taxize: at a glance

Featurergbiftaxize
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgbif, biodiversity-data, bulk-downloads, sql-queriestaxonomy, api-aggregation, upstream-churn, deprecation
Last editorial update1h 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 taxize?

taxize spends its releases absorbing other people's API changes, one dead source at a time.

The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.

Read the full taxize trajectory →

rgbif vs taxize: 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.

T
taxize
ANALYTICS
0.0

taxize spends its releases absorbing other people's API changes, one dead source at a time.

◆ Current state

The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.

◆ Where it's heading

taxize's job is aggregating a dozen taxonomic databases, so most of its engineering is downstream of decisions it does not control — sources go away, endpoints change, rate limits appear. The visible trend is consolidation: fewer, better-maintained backends rather than broader coverage. Release cadence has thinned to roughly one a year, and the rredlist coupling means it now inherits that package's breaking changes too.

◆ Prediction

Expect the next release to track another upstream source change rather than add new databases; the deprecated-parameter aliases from the 0.9.97 rename are also overdue for removal.

Alternatives to rgbif and taxize

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 taxize.

See all rgbif alternatives → · See all taxize alternatives →

Recent activity from rgbif and taxize

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

  1. 4mo agorgbifrgbif 3.8.5 adds occurrence download statistics functions
  2. 5mo agotaxizetaxize 0.10.1 lowers gna_verifier batch size
  3. 8mo agorgbifrgbif 3.8.4 moves name matching to GBIF API v2
  4. 11mo agorgbifrgbif 3.8.3 adds GRSciColl search, relays GBIF paging throttle
  5. 1y agorgbifrgbif 3.8.2 resolves download DOIs to keys
  6. 1y agotaxizetaxize 0.10.0 migrates to GNA and the new rredlist API
  7. 1y agorgbifrgbif 3.8.1 adds SQL-based occurrence downloads
  8. 2y agorgbifrgbif 3.8.0 soft-deprecates occ_data(), adds download describe
  9. 5y agotaxizetaxize 0.9.99 retires tnrs(), paginates WORMS queries
  10. 5y agotaxizetaxize 0.9.98 adds NCBI and zoological rank names
  11. 6y agotaxizetaxize 0.9.97 standardises parameter names package-wide
  12. 6y agotaxizetaxize 0.9.96 updates NatureServe for its new API

Frequently asked questions

What is the difference between rgbif and taxize?

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

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

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