Dendritic Forest Management

The Landscape Package

One JSON file carries a landscape's corridor layers between the mapping workspace, VergeCommon and your own tools. Lengths are meters and areas are square meters. Coordinates are WGS84 longitude and latitude.

Layers

LayerGeometryProperties that matter
coreAreasPolygondfm_id; core_class: old-growth-candidate, old-growth-verified (needs evidence_id), riparian-core or reserve; optional temp_c for climate routes, and stand_age or remnant, stand_origin and native_share for projections, as for retained habitat
retainedPolygonRetained habitat: riparian buffers, corridors, retained stands, prairie or wetland patches. For projections, optional stand_age in years (a stand's age, or years since a prairie was seeded), or remnant: true with remnant_source for ground never plowed or cleared, which counts at old-growth age from the start. Optional stand_origin with origin_source: natural, planted or plantation, as FAO defines them; a plantation never counts at old-growth age. Optional native_share from 0 to 1 with composition_source: the share of cover or basal area in native species
roadsLine or polygonwidth_m for a centerline, or the package's roadWidthM
waterPolygonOpen water; buffer stream centerlines into polygons first
crossingsPointpassage: verified, assumed or none
treatmentsPolygondfm_id, period, intensity; inside a corridor only with corridor_permitted, a light intensity and a reason. Light intensities: single-tree-selection, light-thinning, invasive-removal and restoration-planting, and the upkeep grassland needs: prescribed-burn, prescribed-grazing, late-season-mowing and brush-management. A restoration-planting may list species, each {"name", "native"}, with native_status_source; inside a corridor it stays permitted only if every species is native
boundaryPolygonOutline of the planning area; carried for reference, not used by the check
parcelsPolygonconsent: covered or none; corridor on covered parcels counts as committed. Optional consent_year for when consent began, or planned_year for a parcel expected to join
streamsLineOptional, for the old-growth spine: dfm_id and stream_order, the Strahler order from 1 to 12
connectorsLineOptional, for the old-growth spine: dfm_id and kind. Landforms: ridge, valley, saddle, swale, escarpment, moraine or shoreline. Land use: right-of-way, field-margin or hedgerow. Or planned, for a link drawn where neither carries one. Optional width_m with width_source when the land fixes the width
exitsPolygonOptional, for climate routes: where the spine continues into the next landscape. dfm_id, temp_c of the ground it leads to, and optional toward

A package without streams, connectors or exits, or without stand origin, native share and species records, reads exactly as before, with the same checksum.

Parameters

Every width, distance, age and temperature that changes a result is recorded with its source, so a reviewer can see where it came from.

ParameterUsed byMeaning
minWidthM, minWidthSourceEvery checkThe minimum corridor width and why it was chosen. Required.
roadWidthMEvery checkWidth of road centerlines that have no width_m of their own
pinchFractionEvery checkLinks narrower than the minimum plus this share are flagged as pinch points. Default 0.1
gapCrossingM, gapCrossingSourceEvery checkStepping stones: patches of habitat at least the minimum width across count as linked when the gap between them is at most this many meters, up to 1,000. A gap never crosses a road without a recorded crossing. Choose it from a dispersal study for the species the corridors serve; leave it unset for corridors only
nativeStatusSourceEvery checkWhere the native status of planted species comes from, such as a state flora or the USDA PLANTS database. When set, every restoration planting inside a corridor must list its species
spineWidthByOrderM, spineWidthSourceSpineCorridor width by stream order, for example {"1": 115, "2": 140, "3": 180}. Each is at least the minimum and never narrower for a larger river
connectorWidthM, connectorWidthSourceSpineWidth of links that record no width_m of their own
junctionSnapMSpineA line that ends within this distance of another joins it. Default 5, at most 10
disturbanceWidthMSpineWidth of the single disturbance the network is tested against. Default: the widest corridor plus 2 m, or with stepping stones, wide enough that a cut across that corridor leaves a gap longer than gapCrossingM
ageAsOfYearProjectionsThe year habitat ages and consent are recorded for
oldGrowthAgeYears, oldGrowthAgeSourceProjectionsThe age at which retained habitat counts as old enough; remnants count from the start. Age is not condition
milestoneYearsProjectionsUp to 12 years to project, from ageAsOfYear on
nativeShareMin, nativeShareSourceProjectionsThe share of native species, from 0 to 1, that habitat must record to count at old-growth age. Habitat with no recorded native_share never counts. Leave it unset to project by age alone
coreTempSourceClimate routesWhere the temp_c values of cores and exits come from, such as a 30-year climate normal
climateWarmingC, climateSourceClimate routesThe warming to plan for: a route must reach a core or exit at least this much cooler

A minimal package

{
  "dfm_package": "1.0",
  "crs": "EPSG:4326",
  "units": { "length": "m", "area": "m2" },
  "params": {
    "minWidthM": 100,
    "minWidthSource": "Co-op woodland policy, section 4",
    "roadWidthM": 6
  },
  "sources": { "roads": { "title": "County road centerlines", "date": "2026-05-01" } },
  "layers": { "coreAreas": [], "retained": [], "roads": [], "water": [],
              "crossings": [], "treatments": [], "parcels": [], "boundary": [] }
}

Run the check with the open-source dfm-core package. It is not on npm yet; install it from the repository until it is published.

import { checkConnectivity, fromLandscapePackage } from '@viridis/dfm-core';
const result = await checkConnectivity(fromLandscapePackage(pkg));
// result.status is 'pass', 'fail' or 'incomplete', with reasons

The old-growth spine

Five functions work from the same package. Each returns ok or incomplete with reasons, records its engine version and an input checksum, and states its limits.

import { deriveSpine, spineNetwork, projectSpine,
         climateRoutes, buildOutFrontier } from '@viridis/dfm-core';
const input = fromLandscapePackage(pkg);
const draft = deriveSpine(input);     // corridors along streams and links
const network = spineNetwork(input);  // links, loops, single points of failure
// A steward reviews the draft, records stand_age (or remnant,
// for never-plowed ground), and stand_origin and native_share where
// known, on each piece and saves it as retained habitat, beside any
// patches already mapped:
const plan = { ...input, retained: [...draft.features, ...input.retained] };
const outlook = projectSpine(plan);   // committed and old-age links by year
const routes = climateRoutes(plan);   // linked routes toward cooler cores or exits
const next = buildOutFrontier(plan);  // parcels that would extend the spine

Projections never count a plantation at old-growth age, and with nativeShareMin they count only habitat recorded as native enough. They assume no fire, storm or new road, and use ages and join years as recorded. Climate routes use the temperatures you supply. Neither predicts what species will do.

JSON Schemas for the package and the results

Moving a package to other tools

A Landscape Package converts to a Land Package, an open file format shared with the other Viridis tools, and back again without any change. The converter is one Python file in the open-source land-package repository.

python land_package.py from-dfm my-landscape.json my-land-package.json
python land_package.py to-dfm my-land-package.json my-landscape.json

Dendritic Forest Management itself reads and writes Landscape Packages only. A converted package keeps every layer and parameter; a package that records no sources is flagged as such.