Soil carbon projects that run biogeochemical models (BGCMs) can now use digital soil mapping (DSM) to initialize and run those models under VT0014, the Verra-approved tool for quantifying soil carbon using digital soil mapping. How the two are paired, at individual points or across whole areas, changes how the project's uncertainty is calculated and how heavily it weighs on the result.
There are two ways to bring DSM into a BGCM-based project.
In a point-based approach, DSM predictions feed the model at specific latitude/longitude locations, treated exactly as soil samples would be. In an area-based approach, DSM predictions cover the full project area, and an estimate of SOC for each stratum feeds a single simulation representing that stratum.
DSM error is there in both cases. It rolls several sources into one number, including the error that comes from representing a project with a limited set of points. What changes between the two approaches is where that error sits and how big it ends up. The total error from DSM is lower when the model is run on an area basis, and the computational burden is lower with it.
Here's how each approach works, and what it means when you're deciding how to structure or restructure a project.
How does point-based modeling work?
In point-based BGCM modeling, the model runs simulations at specific points. It uses each point's latitude/longitude to derive biophysical inputs (soil texture, moisture, climate, precipitation) and combines those with the field's management data. DSM predictions at those same points provide the SOC values used to initialize and generate the runs.
The model simulates a subset of the project area rather than all of it, so project-level estimates carry three things: BGCM model prediction error, which is how far the model's simulated SOC values sit from measured reality; sampling error, which is the error introduced by representing a whole project with a limited set of modeled points; and DSM error, the uncertainty in the SOC values feeding the model, propagated via Monte Carlo simulation.
The model isn't run everywhere because running it everywhere is computationally expensive. That is also where the cost of the Monte Carlo step lands, because propagating DSM uncertainty in a point-based setup takes many BGCM runs per point.
Point-based modeling keeps the familiar structure of a sample-based project. The SOC values feeding the model come from DSM predictions instead of laboratory measurements, and DSM error is propagated through the Monte Carlo simulations.
How does area-based modeling work?
In an area-based approach, DSM predictions are generated wall-to-wall across the project area. An estimate of SOC for a given area, a stratum for example, initializes one BGCM simulation representing that stratum. The model runs for every stratum, so the full project area is represented in model runs.
This changes the uncertainty math. DSM covers the entire project and the BGCM simulates the entire project (the sum of all strata), so no extra error is introduced by representing the project with a subset of points. That error sits inside the DSM error instead of being calculated as its own term, and the total error from DSM is lower on an area basis.
Monte Carlo propagation is still required, but the total computational burden is much lower.
To make that concrete: in a point-based project, the number of Monte Carlo runs scales with the number of points. In an area-based project, it scales with the number of strata. The number of points is always much larger than the number of strata, so area-based calculations significantly reduce computational burden. In the example above, a project with 1,000 points across 10 strata that uses 1,000 Monte Carlo iterations requires 1,000,000 model runs. The same project under an area-based approach requires 10,000 runs, 1,000 in each of 10 strata.
Area-based modeling does put more weight on stratification. The BGCM needs a parameter set that reflects the biophysical and management conditions of each stratum, and the stratification can be done by parameter set.
One practical note: VM0042 v2.0-2.2 requires point-based modeling unless a deviation is approved. Moving to an area basis is possible, but it's a documented design decision, not a default. VM0042 v3.0, currently in revision, is expected to allow BGCM simulations on an area basis.
Why this matters for your project
In carbon projects, uncertainty translates directly into deductions from the emission reductions and removals a project can credit. Less total error means lower uncertainty deductions, and lower deductions mean more saleable credits from the same fields.
If your project is already validated and running point-based BGCM simulations, integrating DSM at those points is the easier path. If you're designing a new project, or planning a broader transition to DSM, running the modeling on an area basis lowers the total error from DSM and cuts the Monte Carlo burden by orders of magnitude at the same time.
Where Perennial fits
Perennial led the development of VT0014. DSM + BGCM is one of the three monitoring paths in our Adaptable MMRV framework, alongside DSM alone and measure-remeasure. When DSM strengthens a BGCM-based project, it fills spatial gaps and sharpens calibration: even with 10x fewer samples, DSM can generate up to 20x more SOC inputs for the BGCM.
Which basis fits your project depends on your methodology version, your validation stage, and your existing sampling design. Sometimes the pragmatic answer is point-based integration now with an area-based transition later. We'll tell you when that's the case.
