← Back to home
Comparison · Analytics

fluxnet-package vs tbrf

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

fluxnet-package vs tbrf: at a glance

Featurefluxnet-packagetbrf
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeseddy covariance, environmental data, duckdb, data accessrolling-statistics, water-quality, time-series, environmental-data
Last editorial update7h ago46m ago
WebsiteVisit →Visit →

What is fluxnet-package?

fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.

fluxnet gives R users access to FLUXNET eddy covariance data: listing sites, downloading, quality control and citation. Two releases in three months replaced the parts underneath the user-facing functions — 0.3.0 moved downloading off httr2 onto the fluxnet_shuttle Python library, and 0.6.0 added experimental DuckDB ingest so data can be queried with dplyr without being read into memory. The API around them has been churning in step, with site_ids='all' deprecated and max_gapfill renamed to threshold.

Read the full fluxnet-package trajectory →

What is tbrf?

Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.

tbrf computes rolling statistics over time windows rather than fixed row counts — geometric means, confidence intervals and related summaries indexed by date. That distinction matters for irregularly sampled environmental monitoring data, where a fixed-width window spans different amounts of real time. Version 0.1.7 folds in stat_stepribbon() from ggalt, ships an Entero example dataset for lognormal workflows, and adds na.pad across the tbr_ family.

Read the full tbrf trajectory →

fluxnet-package vs tbrf: editorial side-by-side

F0.0

fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.

◆ Current state

fluxnet gives R users access to FLUXNET eddy covariance data: listing sites, downloading, quality control and citation. Two releases in three months replaced the parts underneath the user-facing functions — 0.3.0 moved downloading off httr2 onto the fluxnet_shuttle Python library, and 0.6.0 added experimental DuckDB ingest so data can be queried with dplyr without being read into memory. The API around them has been churning in step, with site_ids='all' deprecated and max_gapfill renamed to threshold.

◆ Where it's heading

The direction is toward handling data volumes that do not fit the read-it-all-into-R model, and toward borrowing rather than reimplementing — a Python library for transfers, DuckDB for storage. That comes with dependency weight the package now has to manage itself, which is what flux_install_shuttle() and its virtualenv handling exist for. Renames and deprecations in nearly every release suggest the interface is being fixed as the backend settles rather than the other way around.

◆ Prediction

The DuckDB functions are marked experimental and cover connect, build and update only, so the next step is most likely stabilising them and routing the existing quality-control and extraction functions through the database rather than around it.

T
tbrf
ANALYTICS
0.0

Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.

◆ Current state

tbrf computes rolling statistics over time windows rather than fixed row counts — geometric means, confidence intervals and related summaries indexed by date. That distinction matters for irregularly sampled environmental monitoring data, where a fixed-width window spans different amounts of real time. Version 0.1.7 folds in stat_stepribbon() from ggalt, ships an Entero example dataset for lognormal workflows, and adds na.pad across the tbr_ family.

◆ Where it's heading

The package spent its middle releases absorbing upstream breakage — a lubridate duration redefinition, a tibble 3.0.0 subassignment change, tidyselect internals. The 0.1.7 release breaks that pattern: it is the first in five years to add capability rather than repair it, and it does so by internalising a stat from an abandoned dependency instead of relying on it. Cadence remains very low, with a five-year gap between 0.1.5 and 0.1.6.

◆ Prediction

Absorbing stat_stepribbon() directly suggests further vendoring of the plotting layer rather than new statistical functions. The entries do not indicate which rolling statistics, if any, are queued next.

Alternatives to fluxnet-package and tbrf

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 fluxnet-package or tbrf.

See all fluxnet-package alternatives → · See all tbrf alternatives →

Recent activity from fluxnet-package and tbrf

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

  1. 1mo agofluxnet-packageExperimental DuckDB backend for out-of-memory queries
  2. 1mo agofluxnet-packageflux_qc() handles hourly data; max_gapfill renamed to threshold
  3. 2mo agofluxnet-packageflux_citations() for site-level citation output
  4. 3mo agofluxnet-packageFix for multiple site_ids regression
  5. 3mo agofluxnet-packagesite_ids='all' deprecated in favour of NULL
  6. 3mo agofluxnet-packageDownloads move to the fluxnet_shuttle Python library
  7. 0y agotbrfstat_stepribbon vendored in, plus na.pad on all rolling functions
  8. 1y agotbrfgm_mean_ci forwards na.rm and zero.propagate correctly
  9. 6y agotbrfFix internals broken by tibble 3.0.0 subassignment
  10. 6y agotbrfDate windows recomputed with intervals and periods

Frequently asked questions

What is the difference between fluxnet-package and tbrf?

They serve adjacent needs but don't currently overlap on shipped themes. fluxnet-package and tbrf 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 fluxnet-package better than tbrf?

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

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

What are the best alternatives to tbrf?

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