Salt Lake City, Utah

Salt Lake City

Local adoption Salt Lake City adopted 2006 Utah UWUI. This is the rule.

Sourced local code city in Utah · last verified 2026-08-27

Salt Lake City is a sourced city record in Utah. The construction answer is the application of Salt Lake City 2006 Utah UWUI application. A ZIP is a postal lead, not a parcel.

What is established here

Salt Lake City · active application documented

Salt Lake City 2006 Utah UWUI application

Salt Lake City Code 18.44.010.B applies the Utah Wildland Urban Interface Code named by 15A-2-103 to property on the official City WUI map. The 22 joined rows are an edition-specific product-semantic subset; map inclusion, Table 503.1 outcome, project, effective date, and official confirmation remain required.

Scope: mapped area

Official map required; link not located. City Code requires the Salt Lake City Wildland Urban Interface Map to be kept by the City Recorder, but this review did not locate a current public official map URL. A ZIP does not establish inclusion. Read source →

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.

22 joined requirements · Salt Lake City Code 18.44.010 International Fire Code and Standards Adopted · source accessed 2026-08-27

Open the Build rules for Salt Lake City →

What is not established — the contrast

Utah has 2 sourced local nodes; 2 have a sourced construction application. A ZIP is a postal lead; confirm official boundaries and project conditions.

What meets the rule here

What differs here

Object records that name Salt Lake City (not reprinted here):

3 more on the JSON twin.

Inherited and sibling claims stay on their object pages and on Salt Lake City JSON. 6 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:

12 requirement rows have no matched product in the directory
  • roofing: utah-uwui-2006-class-2-3-noncombustible-roof-covering
  • windows: utah-uwui-2006-class-1-2-20-minute-exterior-glazing
  • doors: utah-uwui-2006-class-1-2-20-minute-exterior-glazing
  • doors: utah-uwui-2006-class-1-2-multilayered-glazing
  • doors: utah-uwui-2006-class-1-2-noncombustible-exterior-door
  • doors: utah-uwui-2006-class-1-2-solid-core-exterior-door
  • doors: utah-uwui-2006-class-1-2-tempered-glazing
  • siding: utah-uwui-2006-table-503-nc-exterior-wall
  • decking: utah-uwui-2006-class-1-2-noncombustible-appendage
  • eaves: utah-uwui-2006-class-1-one-hour-eave
  • eaves: utah-uwui-2006-class-2-solid-eave-enclosure
  • gutters: utah-uwui-2006-class-1-2-noncombustible-gutters

Plant context for Salt Lake City

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

Plant groups in Salt Lake City →

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 · Salt Lake City JSON