← Back to home
Comparison · Analytics

b3gbi vs sdsfun

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

b3gbi vs sdsfun: at a glance

Featureb3gbisdsfun
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesbiodiversity, gbif, uncertainty, bootstrappingspatial-statistics, geodetector, spatial-clustering, rcpp
Last editorial update7h ago1h ago
WebsiteVisit →Visit →

What is b3gbi?

b3gbi pulled confidence intervals out of its indicator workflow and handed them to dubicube.

b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.

Read the full b3gbi trajectory →

What is sdsfun?

A spatial-statistics utility package exists to be depended on, and is built accordingly.

sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.

Read the full sdsfun trajectory →

b3gbi vs sdsfun: editorial side-by-side

B
b3gbi
ANALYTICS
2.5

b3gbi pulled confidence intervals out of its indicator workflow and handed them to dubicube.

◆ Current state

b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.

◆ Where it's heading

Two forces are shaping releases. Internally, the uncertainty split produced an indicator-specific rule book — species-level indicators bootstrap the whole cube, raw counts resample within year, evenness gets a logit transform — and that rule book is where the statistical thinking now lives. Externally, GBIF's taxonomic backbone migration to the Catalogue of Life forced string taxon keys through process_cube() and the plotting paths, while recurring EEA and MGRS grid-code fixes mark coordinate parsing as the least settled area.

◆ Prediction

The 0.9.4 notes are entirely JOSS review items — contributors, examples, tracked datasets — so the next release is most likely a JOSS-accepted 1.0 rather than new indicator work.

S
sdsfun
ANALYTICS
0.0

A spatial-statistics utility package exists to be depended on, and is built accordingly.

◆ Current state

sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.

◆ Where it's heading

This is infrastructure for a family of packages rather than an end-user tool, and the changelog says so directly — functions were added to support gdverse and sesp, and moran_test was migrated in from geocomplexity. That migration pattern is the defining move: capability consolidates here so the downstream packages can share it instead of each carrying its own copy. Growth has slowed as that consolidation completed, leaving correctness and dependency upkeep.

◆ Prediction

Given the package moves when its dependents need something, the next release most likely brings in another shared function or responds to a downstream requirement rather than following its own plan. Armadillo and CRAN check changes remain the reliable source of maintenance work.

Alternatives to b3gbi and sdsfun

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 b3gbi or sdsfun.

See all b3gbi alternatives → · See all sdsfun alternatives →

Recent activity from b3gbi and sdsfun

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

  1. 4d agob3gbiJOSS review fixes: contributors, examples, tracked data
  2. 1mo agob3gbiEEA grid coordinates no longer scaled by resolution
  3. 1mo agob3gbiadd_ci() no longer crashes on completeness indicators
  4. 1mo agob3gbiString taxon keys for GBIF's Catalogue of Life backbone
  5. 1mo agob3gbiUncertainty split out of the indicator workflow into add_ci()
  6. 1mo agob3gbiFAIR column mapping doc and Zenodo DOI badge
  7. 10mo agosdsfunPackage load stops touching the RNG state
  8. 1y agosdsfunUnified partial correlation testing and head/tails discretization
  9. 1y agosdsfunMissing-value handling added to linear trend removal
  10. 1y agosdsfunCovariate-based detrending and long-to-matrix spatial reshaping
  11. 1y agosdsfunSpatially constrained hierarchical clustering and SPADE estimation
  12. 1y agosdsfunFast geodetector q-value estimator added

Frequently asked questions

What is the difference between b3gbi and sdsfun?

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

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

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

What are the best alternatives to sdsfun?

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