← Back to home
Comparison · Analytics

flashlight vs soilDB

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

Shared themes:r-package

flashlight vs soilDB: at a glance

FeatureflashlightsoilDB
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmodel-interpretability, explainable-ai, deprecation, api-contractionsoil-data, usda-nasis, ssurgo, spatial-queries
Last editorial update42m ago4h ago
WebsiteVisit →Visit →

What is flashlight?

flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.

flashlight computes model-agnostic interpretability output — variable importance, partial dependence and effect profiles, breakdown plots — for fitted models in R. Version 1.0.0 in October 2025 executed a contraction announced two years earlier: add_shap() is deprecated in favour of the separate kernelshap and fastshap packages, type = "shap" is gone from every light_* function that accepted it, and eight previously exported helpers became internal. The release also restored compatibility with ggplot2 v4.

Read the full flashlight 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 →

flashlight vs soilDB: editorial side-by-side

F
flashlight
ANALYTICS
0.0

flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.

◆ Current state

flashlight computes model-agnostic interpretability output — variable importance, partial dependence and effect profiles, breakdown plots — for fitted models in R. Version 1.0.0 in October 2025 executed a contraction announced two years earlier: add_shap() is deprecated in favour of the separate kernelshap and fastshap packages, type = "shap" is gone from every light_* function that accepted it, and eight previously exported helpers became internal. The release also restored compatibility with ggplot2 v4.

◆ Where it's heading

The package is narrowing rather than growing, and doing it on a published schedule — 0.9.0 listed the breaking changes, 1.0.0 applied them essentially unchanged. Handing SHAP computation to dedicated packages leaves flashlight as an effects-and-profiles visualization layer rather than an all-purpose interpretability toolkit. Removing the ability to rename result columns via options() points the same way: fewer configuration surfaces, a smaller contract to maintain.

◆ Prediction

With the deprecation list from 0.9.0 now fully applied, the next releases most likely remove the functions currently deprecated rather than adding capability, and continue tracking ggplot2. The entries show no new analysis method in progress.

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

See all flashlight alternatives → · See all soilDB alternatives →

Recent activity from flashlight and soilDB

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

  1. 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
  2. 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed
  3. 10mo agoflashlightSHAP handed off to kernelshap as the public API shrinks
  4. 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
  5. 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
  6. 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
  7. 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support
  8. 3y agoflashlightBreaking changes for 1.0.0 announced two years ahead
  9. 4y agoflashlightMaintenance release covering package generation
  10. 5y agoflashlightggpubr dependency removed

Frequently asked questions

What is the difference between flashlight and soilDB?

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

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

Top flashlight alternatives in Analytics are ranked by recent ship velocity. Browse the "flashlight alternatives" section above for the current picks, or visit /alternatives/flashlight 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.