← Back to home
Comparison · Analytics

patentsview vs riem

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

Shared themes:api-clientr-package

patentsview vs riem: at a glance

Featurepatentsviewriem
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesapi-client, breaking-change, patent-data, r-packageweather-data, api-client, r-package, ropensci
Last editorial update5h ago1h ago
WebsiteVisit →Visit →

What is patentsview?

Dormant for years, then rewritten wholesale when the API underneath it broke.

patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.

Read the full patentsview trajectory →

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 →

patentsview vs riem: editorial side-by-side

P
patentsview
ANALYTICS
0.0

Dormant for years, then rewritten wholesale when the API underneath it broke.

◆ Current state

patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.

◆ Where it's heading

The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.

◆ Prediction

Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.

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.

Alternatives to patentsview and riem

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 patentsview or riem.

See all patentsview alternatives → · See all riem alternatives →

Recent activity from patentsview and riem

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

  1. 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints
  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. 4y agoriemMoves to httr2 and httptest2
  6. 4y agoriemSwitches to newer IEM metadata web services
  7. 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
  8. 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
  9. 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
  10. 8y agopatentsviewcast_pv_data() converts returned columns to real types
  11. 9y agopatentsviewFirst release: query DSL for the PatentsView API
  12. 9y agoriemReduces dependencies to tibble alone

Frequently asked questions

What is the difference between patentsview and riem?

Both compete on the same themes — api-client, r-package — within Analytics. patentsview and riem 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 patentsview better than riem?

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

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

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.