← Back to home
Comparison · Analytics

hydroloom vs r-owidapi

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

Shared themes:r-package

hydroloom vs r-owidapi: at a glance

Featurehydroloomr-owidapi
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themeshydrology, network-analysis, geospatial, r-packageopen-data, our-world-in-data, r-package, api-wrapper
Last editorial update1h ago42m ago
WebsiteVisit →Visit →

What is hydroloom?

USGS puts a type system over its river network toolkit so errors surface at dispatch

hydroloom builds and navigates hydrologic flow networks, carrying functionality migrated out of nhdplusTools. Version 1.2.0 introduces an S3 class hierarchy — hy_topo, hy_leveled, hy_node, hy_flownetwork — assigned automatically by hy() and by producer functions, letting the package validate input at dispatch time and emit guided errors. Outlet detection is now defined explicitly: a row is an outlet when its toid is not in id, with reserved values, NA and implicit absence all accepted.

Read the full hydroloom trajectory →

What is r-owidapi?

The R client for Our World in Data found its search had been reading a tenth of the catalog.

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

Read the full r-owidapi trajectory →

hydroloom vs r-owidapi: editorial side-by-side

H
hydroloom
ANALYTICS
0.0

USGS puts a type system over its river network toolkit so errors surface at dispatch

◆ Current state

hydroloom builds and navigates hydrologic flow networks, carrying functionality migrated out of nhdplusTools. Version 1.2.0 introduces an S3 class hierarchy — hy_topo, hy_leveled, hy_node, hy_flownetwork — assigned automatically by hy() and by producer functions, letting the package validate input at dispatch time and emit guided errors. Outlet detection is now defined explicitly: a row is an outlet when its toid is not in id, with reserved values, NA and implicit absence all accepted.

◆ Where it's heading

The package spent its first releases porting and broadening — non-dendritic network support, divergence routing, subsetting that follows diversions out of a basin — and has now turned to making that surface safe to use. The class hierarchy is the structural expression of that turn: instead of every function re-checking whether a data frame has the columns it needs, the type carries the guarantee. The explicit outlet rule resolves a category of failure where valid networks errored on NA or orphan toid values.

◆ Prediction

The release notes flag that subclass attributes are stripped by standard dplyr operations, which is the kind of rough edge that usually generates follow-up work — expect attribute preservation or restoration helpers next.

R
r-owidapi
ANALYTICS
2.5

The R client for Our World in Data found its search had been reading a tenth of the catalog.

◆ Current state

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

◆ Where it's heading

Development is about making a thin wrapper trustworthy against an upstream that moves without notice. The truncation fix pages through the catalog properly; a separate fix stops the function breaking when Our World in Data dropped a column, by parsing typed columns only when present. Tests moved to mocked responses, with a small live suite retained purely to detect schema drift and skipped on CRAN — a sensible design for a package whose main risk is that the API changes shape rather than that the code is wrong. The user-facing surface has not grown since the initial release; the work is in defending it.

◆ Prediction

On this pattern the next release is likelier to be another upstream-compatibility fix than new functionality, with the schema-drift tests the mechanism that surfaces it.

Alternatives to hydroloom and r-owidapi

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 hydroloom or r-owidapi.

See all hydroloom alternatives → · See all r-owidapi alternatives →

Recent activity from hydroloom and r-owidapi

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

  1. 20d agor-owidapiCatalog was silently capped at 1000 charts; now paged in full
  2. 2mo agohydroloomhydroloom v1.2.0
  3. 5mo agohydroloomTest tolerances relaxed for CRAN Fedora checks
  4. 5mo agohydroloomNetwork subsetting and divergence-routed accumulation
  5. 10mo agohydroloomSort and indexing fixes
  6. 1y agor-owidapiRequest logic consolidated, with graceful catalog errors
  7. 1y agor-owidapiFirst release: data, metadata, catalog and search
  8. 1y agohydroloomUpmain and downmain navigation for non-dendritic networks
  9. 2y agohydroloomInitial release completing the nhdplusTools migration

Frequently asked questions

What is the difference between hydroloom and r-owidapi?

Both compete on the same themes — r-package — within Analytics. r-owidapi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is hydroloom better than r-owidapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r-owidapi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to hydroloom?

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

What are the best alternatives to r-owidapi?

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