← Back to home
Comparison · Analytics

gigs vs taxizedb

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

Shared themes:ropensci

gigs vs taxizedb: at a glance

Featuregigstaxizedb
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgrowth-standards, neonatal-health, r-package, ropenscitaxonomy, biodiversity-data, sqlite, ropensci
Last editorial update58m ago4h ago
WebsiteVisit →Visit →

What is gigs?

gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.

gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.

Read the full gigs trajectory →

What is taxizedb?

Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.

taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.

Read the full taxizedb trajectory →

gigs vs taxizedb: editorial side-by-side

G
gigs
ANALYTICS
0.0

gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.

◆ Current state

gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.

◆ Where it's heading

The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.

◆ Prediction

With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.

T
taxizedb
ANALYTICS
0.0

Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.

◆ Current state

taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.

◆ Where it's heading

The package is trading convenience for independence. Each release removes another thing that has to be working elsewhere for the package to function: hosted database preparation is gone, and where a provider disappears the package documents it rather than pretending otherwise — db_download_tpl() is now defunct because The Plant List no longer exists, though previously downloaded copies still query fine. Release cadence is slow, with multi-year gaps and a maintainer handover in 2023.

◆ Prediction

Expect further releases to track data sources appearing and disappearing rather than adding features, since that has driven every recent change. Local conversion also shifts cost onto users, so build time and memory for the larger sources are the plausible next thing to need attention.

Alternatives to gigs and taxizedb

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 gigs or taxizedb.

See all gigs alternatives → · See all taxizedb alternatives →

Recent activity from gigs and taxizedb

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

  1. 9mo agotaxizedbDatabases now built locally from raw data, not the cloud
  2. 1y agogigsDocs and Zenodo archiving
  3. 1y agogigsDocs-only release; nothing changed internally
  4. 1y agogigsConversion API rewritten around data frames and classify_growth()
  5. 2y agogigsDocumentation fixes for autotest compliance
  6. 2y agogigsINTERGROWTH-21st fetal standards and input validation
  7. 2y agogigsPatch release with documentation update
  8. 3y agotaxizedbPatch release for a maintainer change
  9. 5y agotaxizedbtaxa_at() retrieves ancestors at a named rank
  10. 5y agotaxizedbFixes failing tests
  11. 6y agotaxizedbSQLite everywhere, three new sources, taxize verbs ported
  12. 9y agotaxizedbTracks the dplyr split that introduced dbplyr

Frequently asked questions

What is the difference between gigs and taxizedb?

Both compete on the same themes — ropensci — within Analytics. gigs and taxizedb 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 gigs better than taxizedb?

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

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

What are the best alternatives to taxizedb?

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