Timber REITs · USDA Forest Service
USDA Forest Service FIA DataMart
Datadory delivers usda forest service fia datamart data covering America's official forest census: plot, tree, condition, seedling and population tables spanning all 50 states, resolved to individual stems with species codes, diameters, heights and cubic-foot volumes, joined through CN keys, with observed inventory panels reaching from 1984 into current cycles, delivered daily, weekly, or hourly.
API, files, or your warehouse. Daily, weekly, or hourly.
What is USDA Forest Service FIA DataMart?
USDA Forest Service FIA DataMart is the Timber REITs catalog's window onto the Forest Inventory and Analysis Database (FIADB) - the United States' standing census of its own forestland. Where the markets half of this slice tracks what timberland-owning companies report, this record measures the trees themselves: extent, ownership, species composition, volume, biomass, growth, removals and mortality, collected on permanent ground plots and organized as roughly 59 table types per state.
The unit of observation is what makes it valuable. The PLOT table carries 63 columns of plot-level spine - identification, coordinates, elevation - while TREE runs to 105 columns per individual stem, from species code and diameter through net and gross cubic-foot volume to tree age. A companion estimation engine turns those plots into population estimates with sampling errors, and an urban-forestry wing extends the same plot design into cities. Datadory scores the record 9 out of 10 against a catalog mean of 7.81. Get a sample of this dataset cut to the states and tables your models need.
What do sample rows look like?
One row per measured thing, tables stitched together by CN keys. Three rows straight from the record's own sample:
table : WY_PLOT
STATECD : 1
UNITCD : 3
COUNTYCD : 123
PLOT : 90042
INVYR : 1990
LAT : 32.850131
LON : -85.835005
ELEV : 980
table : WY_SURVEY
STATECD : 56
STATENM : Wyoming
INVYR : 2011
ANN_INVENTORY: Y
NOTES : Annual 01 of 10 subcycles
table : AL_TREE
PLT_CN : 157499420010854
STATUSCD : 1
SPCD : 693
DIA : 10.2
VOLCFNET : 6.573Read together, they show the shape of the whole system. The first row is a plot's identifying spine - state, survey unit and county codes stacking into a location, an inventory year, coordinates and elevation in feet. The second is survey bookkeeping, its note field recording that a state's panel rotates through ten annual subcycles. The third is the payoff: a single live stem - STATUSCD 1 - carrying species code 693, a 10.2-inch diameter and 6.573 net cubic feet of volume, tied back to its parent plot through the PLT_CN key. Every published estimate about US forests bottoms out in rows like that one.
What fields does the dataset include?
Twenty-four fields anchor the dictionary below, each definition checked against the source's published references during the August 2026 research pass. They organize into four families. Identity and join keys (CN, and PLT_CN as it appears in TREE) stitch the tables to one another. Geography codes (STATECD, UNITCD, COUNTYCD, PLOT) stack into a location, with LAT/LON and ELEV adding physical position. Measurement lives in the TREE family (STATUSCD, SPCD, DIA, HT, VOLCFNET, VOLCFGRS). The COND family describes the ground a stem stands on: ownership group, forest type, stand age, productivity class and site index.
Columns that appear only inside particular tables or subsets fold under additional fields on request: the remainder of TREE's 105 columns, the growth-and-mortality transition family, regeneration and site-tree tables, the coarse-woody-debris and soils extensions, and the evaluation-unit bookkeeping behind population estimates. Name the ones your models need and the sample ships with them documented.
What does coverage look like across geography, time and granularity?
Geography - all 50 states plus territories, organized state by state so a region resolves cleanly. One constraint matters for mapping: public plot coordinates are deliberately fuzzed or swapped, and precise locations publish only for plots numbered above 40,000.
Temporal - annual inventory panels state by state, with observed collections running from early panels in 1984 through current 2022-2024 cycles. States entered annual sampling at different times, so depth varies by state rather than by decree.
Granularity - tree-level and plot-level records joined through CN keys, rolling up through counties and survey units to population-evaluation units. A single state's TREE table alone reaches 541 MB, which is what 105 columns times millions of stems looks like at rest.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Your cadence is your call regardless of how the underlying panels move - a monthly warehouse load keeps supply dashboards fed between inventory cycles nobody has to babysit. Every delivery ships the complete field dictionary above, the sample rows and the coverage profile mapped to the states and tables you named.
Who uses this data, and for what?
- Timber-supply and biomass modeling - join plot- and tree-level tables across all 50 states into standing-volume and biomass baselines that wood-product models actually rest on.
- Timberland valuation inputs - site index, productivity class and stand age per condition class give growth-rate assumptions for discounted-cash-flow land math.
- Ownership-mix analysis - detailed ownership codes separate national forest from corporate private timberland, the comparison timberland investors keep asking for.
- Regional fiber-supply sizing - state inventory panels quantify what roundwood and sawnwood supply a region can support ahead of mill and logistics decisions.
- Citation-grade sourcing - stories, theses and filings anchored to the national forest census, defensible because the methodology is published alongside the numbers.
Which personas get the most value?
Data scientists and ML engineers (relevance 3/3) get tree-level features - species, diameter, height, volume - joinable across every state under one key structure; see data scientists use cases. Developers and data-product builders (3/3) get typed tabular layouts that drop straight into pipelines; see developers builders use cases. Journalists, academics and students (3/3) get the authoritative national inventory with published methodology behind every figure; see journalists academics use cases. Investors and quant researchers (2/3) read standing-volume and removals trends as supply signals behind wood-product equities; see investors quants use cases. Market researchers and consultants (2/3) size regional fiber supply from state panels; see market researchers use cases. Competitive intelligence and product teams (1/3) should calibrate expectations: this data describes forests, not the companies operating on them.
How does it compare to alternatives in its slice?
Within timber reits data, this record owns the physical layer: the trees, acres and ownership lines underneath every equity story in the sector. The neighbors own the financial layers. FAO Forest Product Statistics counts what the world's forest sector produces and trades each year across roughly 285 areas since 1961 - global flows where this record gives American stems; the head-to-head lives at FAO Forest Product Statistics vs USDA Forest Service FIA DataMart. SEC EDGAR XBRL Company Facts API - Weyerhaeuser (CIK 106535) carries disclosed timberland balances and depletion per filer - company-reported acreage worth crossing against what the inventory says is actually standing nearby. Quote-history records for Weyerhaeuser add market prices, and the same agency's wider record - FIA DataMart and Timber Products Output - adds mill-level production tables to the same inventory base. If the question is what physically exists on US forestland, this is the set that answers it.
What should I know before requesting a sample?
Three things worth knowing upfront.
First, exact plot locations do not exist in this corpus. Public coordinates are fuzzed or swapped to protect landowner privacy, with full precision publishing only above plot number 40,000. Anyone promising stem-level geolocation from this data is selling something else.
Second, the schema speaks in codes. Species, ownership, forest type, productivity and status all arrive as integers that resolve against reference tables. The dictionary above documents the load-bearing ones; the complete code lists ride along with every delivery.
Third, variable definitions live in the program's documentation rather than inside the files themselves, so columns beyond the twenty-four verified above are confirmed present in the corpus but documented table by table at sampling. Say which states, tables and inventory years matter when you request a sample - the extract comes back cut to exactly that shape.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
CN | string | Unique sequence-generated record identifier used to join tables - PLOT.CN is referenced by TREE.PLT_CN. | 157499420010854 |
INVYR | integer | Inventory year in which the plot data were collected. | 2022 |
STATECD | integer | FIPS state code. | 56 |
UNITCD | integer | FIA survey unit code within the state. | 22 |
COUNTYCD | integer | FIPS county code within the state. | 3 |
PLOT | integer | Plot number within county; public coordinates publish only above 40,000 for privacy. | 90042 |
LAT | number | Latitude of the plot in decimal degrees - fuzzed or swapped in the public release. | 32.850131 |
LON | number | Longitude of the plot in decimal degrees - fuzzed or swapped in the public release. | -85.835005 |
ELEV | integer | Elevation of the plot in feet. | 980 |
STATUSCD | integer | TREE table: status of the tree - 1 = live, 2 = removed or dead per the program's code definitions. | 1 |
SPCD | integer | Species code referencing the program's species reference table. | 693 |
DIA | number | Diameter at breast height in inches, current measurement. | 10.2 |
HT | integer | Total height of the tree in feet. | 68 |
VOLCFNET | number | Net cubic-foot volume in the saw-log portion and above. | 6.573 |
VOLCFGRS | number | Gross cubic-foot volume before defect deduction. | 6.573 |
COND_STATUS_CD | integer | COND table: condition class status such as accessible forest land, nonforest, censused water. | 1 |
OWNCD | integer | COND table: detailed ownership group code - national forest versus corporate private timberland drives the REIT comparisons. | 40 |
OWNGRPCD | integer | COND table: broad ownership group - federal, state, private, Native American. | 40 |
FORTYPCD | integer | COND table: forest type code, e.g. loblolly-shortleaf pine. | 161 |
STDAGE | integer | COND table: average stand age in years. | 35 |
SITECLCD | integer | COND table: site productivity class code. | 3 |
SICOND | number | COND table: site index (base age 50) in feet - a key growth-rate input for timberland valuation. | 66 |
CREATED_DATE | datetime | Row creation timestamp in the database. | 2010-01-25 12:54:43 |
MODIFIED_DATE | datetime | Last modification timestamp carried on the row. | 2026-05-14 08:13 |
Questions buyers ask
What does the USDA Forest Service FIA DataMart cover?
The full FIADB table set: plot, tree, condition, seedling and site-tree tables plus population-estimation tables and soils, lichen, ozone and vegetation subplots - roughly 59 table types per state. Together they describe US forest extent, ownership, species composition, volume, biomass, growth, removals and mortality.
How far back does FIA inventory data go?
Observed collections reach back to early panels in 1984, and states moved onto annual sampling at different dates, with current cycles running 2022-2024. Depth varies state by state rather than uniformly, so multi-decade trend work starts by checking a given state's panel history.
What resolution does the data reach - tree, plot, or county?
Individual trees. Each stem carries species code, diameter, height, status and cubic-foot volume, nested in plots, condition classes and counties, with population estimates rolling up to evaluation units. County and state summaries are derivable, but the atomic row is one measured tree on one measured plot.
Are exact plot coordinates included?
No. Public coordinates are deliberately fuzzed or swapped to protect landowner privacy, and full precision publishes only for plots numbered above 40,000. Mapping at county or survey-unit grain works well; parcel-level geolocation is structurally impossible with what this corpus publishes.
Does the dataset identify corporate timberland ownership?
Ownership arrives as coded classes: a broad grouping - federal, state, private, Native American - with a detailed breakdown beneath it that distinguishes corporate private timberland from other private categories. It separates corporate from non-corporate holdings; it does not name the company holding them.
Can a sample be cut to specific states and tables?
Yes. Name the states, tables and inventory years you care about - TREE for one state, COND for several, population estimates for a region - and the sample arrives shaped to that scope with the complete field dictionary attached. Samples precede any commitment.
Notes on this record
- Coordinates arrive fuzzed Privacy protection is built into the publication: public plot coordinates are swapped or jittered, so mapping holds at county grain and stops pretending past it.
- Forests, not companies The inventory measures land and stems; it names no firms. Pair it with company filings when the question is who owns what stands where.
- Scored near the top of the catalog Datadory scores this record 9/10 against a catalog mean of 7.81 - one of 534 datasets to score nine out of 1,744 cataloged.
Datasets that pair with this one
- USDA Forest Service FIA DataMart and Timber Products Output (TPO) The same national inventory base paired with Timber Products Output tables - production and removals at the point processing happens.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.