← Back to home
Comparison · Analytics

fillpattern vs hydroloom

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

Shared themes:r-package

fillpattern vs hydroloom: at a glance

Featurefillpatternhydroloom
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, data-visualization, accessibility, graphicshydrology, network-analysis, geospatial, r-package
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is fillpattern?

Pattern fills for ggplot2, hardened against the ways users write sizes

fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.

Read the full fillpattern trajectory →

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 →

fillpattern vs hydroloom: editorial side-by-side

F
fillpattern
ANALYTICS
0.0

Pattern fills for ggplot2, hardened against the ways users write sizes

◆ Current state

fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.

◆ Where it's heading

Development is slow and entirely reactive to how the string-based size interface fails. The pattern across releases is the same: a user hits an edge — very small fill areas in 1.0.2, malformed unit strings in 1.0.3 — and the fix is either a graceful fallback or a clearer error. Leaning on R's newer graphics engine rather than reimplementing pattern rendering keeps the package small at the cost of raising its version floor.

◆ Prediction

Expect further releases to stay in the same register: parsing and validation fixes for the size and unit interface, with the pattern set itself unlikely to change.

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.

Alternatives to fillpattern and hydroloom

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 fillpattern or hydroloom.

See all fillpattern alternatives → · See all hydroloom alternatives →

Recent activity from fillpattern and hydroloom

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

  1. 2mo agohydroloomhydroloom v1.2.0
  2. 5mo agohydroloomTest tolerances relaxed for CRAN Fedora checks
  3. 5mo agohydroloomNetwork subsetting and divergence-routed accumulation
  4. 6mo agofillpatternSize string parsing fixed; invalid units now report instead of crash
  5. 10mo agohydroloomSort and indexing fixes
  6. 1y agohydroloomUpmain and downmain navigation for non-dendritic networks
  7. 2y agofillpatternSmall fill areas no longer crash; min_size falls back to solid
  8. 2y agofillpatternfillpattern 1.0.1
  9. 2y agohydroloomInitial release completing the nhdplusTools migration

Frequently asked questions

What is the difference between fillpattern and hydroloom?

Both compete on the same themes — r-package — within Analytics. fillpattern and hydroloom 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 fillpattern better than hydroloom?

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

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

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.