← Back to home
Comparison · Analytics

riem vs taxizedb

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

Shared themes:ropensci

riem vs taxizedb: at a glance

Featureriemtaxizedb
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesweather-data, api-client, r-package, ropenscitaxonomy, biodiversity-data, sqlite, ropensci
Last editorial update58m ago4h ago
WebsiteVisit →Visit →

What is riem?

A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.

riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.

Read the full riem 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 →

riem vs taxizedb: editorial side-by-side

R
riem
ANALYTICS
0.0

A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.

◆ Current state

riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.

◆ Where it's heading

The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.

◆ Prediction

With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing 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 riem 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 riem or taxizedb.

See all riem alternatives → · See all taxizedb alternatives →

Recent activity from riem 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 agoriem1.0.0 removes defaults and adds query arguments
  3. 1y agoriemDrops the last vcr usage in favour of httptest2
  4. 2y agoriemTimezone and timestamp-parsing fixes
  5. 3y agotaxizedbPatch release for a maintainer change
  6. 4y agoriemMoves to httr2 and httptest2
  7. 4y agoriemSwitches to newer IEM metadata web services
  8. 5y agotaxizedbtaxa_at() retrieves ancestors at a named rank
  9. 5y agotaxizedbFixes failing tests
  10. 6y agotaxizedbSQLite everywhere, three new sources, taxize verbs ported
  11. 9y agotaxizedbTracks the dplyr split that introduced dbplyr
  12. 9y agoriemReduces dependencies to tibble alone

Frequently asked questions

What is the difference between riem and taxizedb?

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

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

Top riem alternatives in Analytics are ranked by recent ship velocity. Browse the "riem alternatives" section above for the current picks, or visit /alternatives/riem 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.