West Virginia

West Virginia

Program and model No adopted WUI code we can source here. IBHS Wildfire Prepared asks for the inspection measures, and the 2024 IWUIC model says the same floor.

No statewide construction book — sourced Last verified 2026-08-26

One local briefing, built from separate evidence layers: what the state has published, where an instrument is documented to apply, what still depends on a map or project fact, and which plant records are documented in West Virginia. A ZIP personalizes priority; it does not decide a parcel boundary.

What is established here

West Virginia does not adopt a statewide WUI construction book. 87CSR4 adopts the 2018 IBC, IPC, IMC, IFGC, IRC, and IEBC, the 2015 IECC, ASHRAE 90.1-2013, A117.1-2017, the 2020 NEC, and the 2018 ISPSC. IWUIC is not that rule. Confirm with the building official.

No exact code-application record is normalized for this state. A source node alone does not activate requirements.

Open the Build rules for West Virginia →

What is not established

A ZIP in West Virginia is a postal match, not a parcel, map, or permit. No city or county briefing is open here yet.

What differs here

Object records that name West Virginia (not reprinted here):

Child-place and sibling claims stay on those place pages, their object URLs, and the JSON twin.

Plants documented in West Virginia

State distribution, native range, invasive status, hardiness, and fire evidence answer different questions. None is a planting approval. The list itself is on Grow — this page carries the aggregates.

792 plant records documented in the state. 0 explicitly document West Virginia as native range. 172 carry an invasive or noxious flag applying here. 1 fire-evidence sources name West Virginia in publication scope.

Plant groups in West Virginia →

Human page and machine twin

This briefing is the place answer. The claim graph lives on object pages and the JSON twin. Methodology · West Virginia JSON · place node JSON