← Back to home
Comparison · Analytics

riem vs webchem

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

Shared themes:ropensci

riem vs webchem: at a glance

Featureriemwebchem
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesweather-data, api-client, r-package, ropenscicheminformatics, web-apis, data-access, ropensci
Last editorial update57m 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 webchem?

Adding chemical databases with one hand while public ones close programmatic access with the other.

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

Read the full webchem trajectory →

riem vs webchem: 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.

W
webchem
ANALYTICS
0.0

Adding chemical databases with one hand while public ones close programmatic access with the other.

◆ Current state

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

◆ Where it's heading

Two opposing forces run through these entries. The package keeps widening its coverage — ChEMBL in 1.2.0, LIPID MAPS and SwissLipids identifiers via Wikidata, structure images, Mol export — while the open, unauthenticated end of the chemical web keeps contracting. The other consistent thread is interface harmonisation: successive releases have converged the get_* functions on the same query and from arguments, tibble returns, and CAS reformatting, so the package feels like one interface rather than a dozen wrappers.

◆ Prediction

Expect further defunct functions and URL repairs as more providers move behind keys or shut down, alongside occasional additions of sources that remain open. The entries show no sign of a general credential-management layer, which is what a package facing this trend would eventually need.

Alternatives to riem and webchem

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

See all riem alternatives → · See all webchem alternatives →

Recent activity from riem and webchem

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

  1. 1y agowebchemRepairs broken URLs; ChemSpider check now needs a key
  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 agowebchemChemIDplus and PAN queries removed as sources shut down
  6. 3y agowebchemAdds ChEMBL access for bioactive compound data
  7. 4y agowebchemcir_query() returns a tibble, a breaking change
  8. 4y agoriemMoves to httr2 and httptest2
  9. 4y agoriemSwitches to newer IEM metadata web services
  10. 4y agowebchemAdds Mol structure export; aw_query renamed to bcpc_query
  11. 5y agowebchemFetches LIPID MAPS and SwissLipids identifiers from Wikidata
  12. 9y agoriemReduces dependencies to tibble alone

Frequently asked questions

What is the difference between riem and webchem?

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

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

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