← Back to home
Comparison · Analytics

regfusionr vs soilDB

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

Shared themes:r-package

regfusionr vs soilDB: at a glance

FeatureregfusionrsoilDB
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesneuroimaging, coordinate-mapping, freesurfer, r-packagesoil-data, usda-nasis, ssurgo, spatial-queries
Last editorial update1h ago46m ago
WebsiteVisit →Visit →

What is regfusionr?

Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed

regfusionr maps coordinates between volumetric brain templates (MNI152, Colin27) and the fsaverage surface. After four dormant years it returned in July 2026 with a release that fixes a coordinate-indexing bug, unblocks a previously disabled function, and completes the template-by-method matrix so all four combinations answer point queries. It also breaks compatibility by switching to the standard FREESURFER_HOME environment variable.

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

regfusionr vs soilDB: editorial side-by-side

R
regfusionr
ANALYTICS
3.8

Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed

◆ Current state

regfusionr maps coordinates between volumetric brain templates (MNI152, Colin27) and the fsaverage surface. After four dormant years it returned in July 2026 with a release that fixes a coordinate-indexing bug, unblocks a previously disabled function, and completes the template-by-method matrix so all four combinations answer point queries. It also breaks compatibility by switching to the standard FREESURFER_HOME environment variable.

◆ Where it's heading

The package moved from a partial implementation to a complete one in a single release. Before this, vol_coords_to_fsaverage returned coordinates indexed by query position rather than by vertex index — results that looked plausible and were wrong — and fsaverage_to_vol was guarded behind a stop(). Both are now resolved, and the new Colin27 and MNI152 convenience functions make the mapping bidirectional. The sibling package haze shipped a maintenance release 56 minutes later, marking this as a coordinated sweep across the maintainer's neuroimaging stack.

◆ Prediction

With the four template-by-method combinations closed and the coordinate bug fixed, the next release is more likely to be CRAN-adjacent packaging or documentation than new mapping capability.

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

See all regfusionr alternatives → · See all soilDB alternatives →

Recent activity from regfusionr and soilDB

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

  1. 18d agoregfusionrVersion 0.3.0 -- vol_to_fsaverage, many convenience functions and fixes
  2. 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
  3. 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed
  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. 4y agoregfusionrv0.2.0 -- surface to volume data projection
  9. 4y agoregfusionrv0.1.0: Initial release

Frequently asked questions

What is the difference between regfusionr and soilDB?

Both compete on the same themes — r-package — within Analytics. regfusionr is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 regfusionr better than soilDB?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. regfusionr is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 regfusionr?

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