← Back to home
Comparison · Analytics

brglm2 vs soilDB

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

Shared themes:r-package

brglm2 vs soilDB: at a glance

Featurebrglm2soilDB
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, regression, bias-reduction, high-dimensionalsoil-data, usda-nasis, ssurgo, spatial-queries
Last editorial update52m ago2h ago
WebsiteVisit →Visit →

What is brglm2?

A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression

brglm2 fits generalized linear models using mean and median bias reduction rather than plain maximum likelihood, which matters most when ML estimates are infinite or badly biased. The 0.7-0.9 line broadened coverage — negative binomial via brnb(), ordinal superiority measures, the expo() method for exponentiated parameters, add1()/drop1() so step() stops silently producing nonsense. Version 1.0.0 in August 2025 added mdyplFit(), estimating logistic regression by maximum Diaconis-Ylvisaker prior penalized likelihood with optional high-dimensional corrections. The two releases since have tuned that new path.

Read the full brglm2 trajectory →

What is soilDB?

The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.

soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.

Read the full soilDB trajectory →

brglm2 vs soilDB: editorial side-by-side

B
brglm2
ANALYTICS
0.0

A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression

◆ Current state

brglm2 fits generalized linear models using mean and median bias reduction rather than plain maximum likelihood, which matters most when ML estimates are infinite or badly biased. The 0.7-0.9 line broadened coverage — negative binomial via brnb(), ordinal superiority measures, the expo() method for exponentiated parameters, add1()/drop1() so step() stops silently producing nonsense. Version 1.0.0 in August 2025 added mdyplFit(), estimating logistic regression by maximum Diaconis-Ylvisaker prior penalized likelihood with optional high-dimensional corrections. The two releases since have tuned that new path.

◆ Where it's heading

The package's older work assumed the classical regime where observations comfortably outnumber parameters. mdyplFit() and its hd_correction argument target the opposite case, and the follow-up releases are almost entirely about it — Pearson residuals on original responses, aliased parameter handling, the sloe() signal-strength estimator ignoring leverage-one observations. Meanwhile the older surface gets graceful-failure work: brglm_fit() now returns its latest estimates with warnings rather than aborting.

◆ Prediction

Given that 1.0.1 and 1.1.0 are both dominated by mdyplFit follow-ups while the classical path receives only robustness fixes, further work on high-dimensional corrections is the likeliest direction.

S
soilDB
ANALYTICS
0.0

The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.

◆ Current state

soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.

◆ Where it's heading

The arc points at offline and local-first workflows. downloadSSURGO() and createSSURGO() keep gaining arguments for building and querying local SSURGO databases, and the query internals were rewritten as common table expressions so identical code runs against the remote service or a local file. Coverage is widening in parallel: FY26 SoilWeb maps now reach most OCONUS surveys, while fetchHWSD() and fetchSOLUS() pull in datasets outside the core NASIS/SSURGO pair. Federal URL churn — EDIT, SoilWeb, S3-hosted geometry — is a recurring maintenance tax the package absorbs on users' behalf.

◆ Prediction

Expect the next releases to keep extending parallel and offline SSURGO handling, since LAPPLY.FUN has just opened the door to arbitrary parallel backends, and to fold more curated SoilWeb and FAO datasets behind fetch* wrappers.

Alternatives to brglm2 and soilDB

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 brglm2 or soilDB.

See all brglm2 alternatives → · See all soilDB alternatives →

Recent activity from brglm2 and soilDB

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

  1. 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
  2. 3mo agobrglm2brglm2 v1.1.0
  3. 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed
  4. 8mo agobrglm2brglm2 v1.0.1
  5. 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
  6. 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
  7. 11mo agobrglm21.0.0 adds maximum DY-prior penalized likelihood for logistic regression
  8. 1y agobrglm2brglm2 v0.9.3
  9. 1y agobrglm2brglm2 v0.9.2
  10. 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
  11. 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support
  12. 3y agobrglm2brglm2 v0.9.1

Frequently asked questions

What is the difference between brglm2 and soilDB?

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

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

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

What are the best alternatives to soilDB?

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