Eagle

Local adoption Eagle adopted iwuic 2018. This is the rule.

Sourced local code city in Idaho · last verified 2026-08-26

Eagle is a sourced city record in Idaho. The construction answer is the application of Eagle 2018 IWUIC overlay application. A ZIP is a postal lead, not a parcel.

What is established here

Eagle has a current 2018 IWUIC application inside the Ordinance 947 WUI Overlay District, with parcel, full Table 503.1 outcome, project, Fire Protection Plan, date, and official determinations still required. The 15 modeled material rows are a conservative partial subset.

Eagle · active application documented

Eagle 2018 IWUIC overlay application

Eagle applies its locally amended 2018 IWUIC inside the Ordinance 947 overlay to named project classes, subject to the official mapped boundary, the full Table 503.1 outcome, the City-approved Fire Protection Plan exemption, project exceptions, effective-date, and code-official determinations. The 15 joined rows are a conservative subset of product-field paths for IR1, IR2, and IR3; they do not project Table 503.1's IR1 + N.C., Not Required, or Not Permitted outcomes.

Scope: mapped area

Official map linked. Eagle publishes the Ordinance 947 WUI Overlay District Map as the controlling mapped-area starting point; parcel inclusion and current boundary status remain official determinations. Open official map →

Still verify with the authority

Confirm the parcel is inside the cited authority or boundary.
Check the parcel in the official hazard map.
Obtain the official site hazard classification.
Confirm that the project type and permit scope trigger the provision.
Confirm the ordinance's effective date for this project.
Confirm the result with the authority having jurisdiction.

15 joined requirements · Eagle City Code 7-1G-3 International Wildland-Urban Interface Code Adopted · source accessed 2026-08-26

Official map: Open the cited map tool →

Open the Build rules for Eagle →

What is not established — the contrast

Idaho has 2 sourced local nodes; 1 has a sourced construction application. Adoption is not statewide by implication: Boise has none sourced here. A ZIP is a postal lead; confirm official boundaries and project conditions.

What meets the rule here

2 vents products match the governing requirement → Adopted
11 roofing products match the governing requirement → Adopted
25 windows products match the governing requirement → Adopted
3 doors products match the governing requirement → Adopted
11 siding products match the governing requirement → Adopted
No sourced decking product matches the governing requirement yet → Adopted
1 eaves product matches the governing requirement → Adopted
No sourced gutters product matches the governing requirement yet → Adopted
25 fencing products match the governing requirement → Voluntary program
1 landscaping product matches the governing requirement → Voluntary program

What differs here

Object records that name Eagle (not reprinted here):

Inherited and sibling claims stay on their object pages and on Eagle JSON. 7 place-focused guides → Learn.

What we do not have

These checks stay open because the sourced instrument leaves them to the official record, not because this page skipped them:

Whether the instrument is in force for this project's date.
The official boundary that would put a parcel inside the application.
Confirmation from the building official for this project.
The official hazard class for the lot.
The official hazard or WUI map for the lot.
Whether this project type is in scope of the instrument.

6 requirement rows have no matched product in the directory

doors: iwuic-2018-class-1-2-multilayered-glazing
doors: iwuic-2018-class-1-2-noncombustible-exterior-door
doors: iwuic-2018-class-1-2-solid-core-exterior-door
decking: iwuic-2018-class-1-2-noncombustible-deck
eaves: iwuic-2018-class-2-solid-eave-enclosure
gutters: iwuic-2018-noncombustible-gutters

Plant context for Eagle

Grow for this city is the state plant pool cut to USDA half-zones observed on ZIPs that resolve here (7a). Zone is not a fire rating. 661 records document distribution in Idaho; 0 explicitly document native range; 104 carry an invasive or noxious flag that applies in the state.

Plant groups in Eagle →

What to verify before acting

Confirm the official boundary or hazard map, the adopted instrument and effective date, the project type, and the exact product model or plant conditions. Methodology · Eagle JSON