PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
Comparison · Analytics
hydroloom vs rphylopic
A side-by-side editorial comparison of hydroloom and rphylopic — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
hydroloom vs rphylopic: at a glance
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.
What is rphylopic?
The R package that puts organism silhouettes on plots keeps widening where they can be drawn.
rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.
hydroloom vs rphylopic: editorial side-by-side
hydroloom
0.0ANALYTICS
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.
rphylopic
0.0ANALYTICS
The R package that puts organism silhouettes on plots keeps widening where they can be drawn.
◆ Current state
rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.
◆ Where it's heading
Development is expanding the set of places a silhouette can appear rather than changing what the package does. Base plots came first, then ggplot2 aesthetics and legend glyphs, then trees, then network vertices via an igraph shape registered automatically when both packages load. The other running thread is defensive maintenance against upstream churn: retries on failed API calls, fixes for ggplot2 4.0.0, and now an in-memory cache so repeated calls stop hammering the PhyloPic API. The ysize and size deprecation, opened in 1.5.0, is now complete and the arguments are scheduled for removal.
◆ Prediction
The deprecated ysize and size arguments look set to be removed in the next release, and on the pattern of the last four, another plotting context is a likelier addition than a change to the retrieval layer.
Alternatives to hydroloom and rphylopic
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 rphylopic.
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
contentanalysis
A scientific-text analysis package moved from counting citations to classifying argument structure.
relialearnr
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
See all hydroloom alternatives → · See all rphylopic alternatives →
Recent activity from hydroloom and rphylopic
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agorphylopicSilhouettes become igraph vertices; API responses cached
- 2mo agohydroloomhydroloom v1.2.0 ⚡
- 5mo agohydroloomTest tolerances relaxed for CRAN Fedora checks
- 5mo agohydroloomNetwork subsetting and divergence-routed accumulation
- 8mo agorphylopicBase R phylogenies gain silhouette annotation
- 10mo agohydroloomSort and indexing fixes
- 1y agorphylopicExplicit width and height replace the old sizing arguments
- 1y agohydroloomUpmain and downmain navigation for non-dendritic networks
- 2y agorphylopicSilhouette legends and attribution permalinks
- 2y agorphylopicSilhouette resolution helper and safer colour defaults
- 2y agorphylopicRendering dependencies bumped for grImport2 and rsvg
- 2y agohydroloomInitial release completing the nhdplusTools migration
Frequently asked questions
What is the difference between hydroloom and rphylopic?
Both compete on the same themes — r-package — within Analytics. hydroloom and rphylopic 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 hydroloom better than rphylopic?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hydroloom and rphylopic 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 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 rphylopic?
Top rphylopic alternatives in Analytics are ranked by recent ship velocity. Browse the "rphylopic alternatives" section above for the current picks, or visit /alternatives/rphylopic for the full list with editorial commentary on each.