Land Records Logo

Land Records

Iron County, UT Parcels & GIS Data

Iron County, UT parcel data: 58,457 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Iron County, Utah parcel data covering 58,457 property records.

This page documents parcel-level coverage for Iron County, Utah. Each parcel record carries its boundary polygon (GIS geometry) along with attributes such as the parcel ID/APN, owner name and mailing address, situs (property) address, assessed land and improvement values, acreage, land-use and zoning codes, year built, and most recent sale price and date. Exact fill rates for Iron County are listed in the attribute-coverage table below. Preview the data in the interactive explorer, or download the complete Iron County property dataset.

Iron County is a county in southwestern Utah, United States. As of the 2020 United States census, the population was 57,289. Its county seat is Parowan, and the largest city is Cedar City. The Cedar City, UT Micropolitan Statistical Area includes all of Iron County.

FIPS 49021

Official county website: http://www.ironcounty.net

The FIPS code for Iron County is 49021.

ExploreBuyDownload Iron County data
KaneGarfieldBeaverLincolnWashingtonIron
Hosted Web API$200/mo

Attribute coverage

Iron County contains 58,457 parcels in the current dataset. Column coverage is the percentage of those parcels for which the attribute is populated (non-NULL).

ColumnCoverageRecords populated
lrid100%58,457
parcelid98.6%57,648
parcelid2<0.1%0
ogparcelid100%58,457
ogparcelid2<0.1%0
parentid<0.1%0
stackid<0.1%0
geoid100%58,457
statefp100%58,457
countyfp100%58,457
countyname100%58,457
cousubfp100%58,457
cousubname100%58,457
tractce100%58,457
tractname100%58,457
taxacctnum99.5%58,175
taxyear<0.1%0
taxdistrict<0.1%0
usecode<0.1%0
usedesc<0.1%0
zoningcode<0.1%0
zoningdesc<0.1%0
numbldgs50.1%29,283
numunits<0.1%0
yearbuilt<0.1%0
numfloors<0.1%0
bldgsqft<0.1%0
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue<0.1%0
landvalue<0.1%0
agvalue<0.1%0
totalvalue<0.1%0
taxacres<0.1%0
calcarea100%58,457
saleamt<0.1%0
saledate<0.1%0
ownertype77.1%45,042
ownername77.1%45,042
owneraddr77.0%45,040
ownercity77.0%45,025
ownerstate76.9%44,969
ownerzip<0.1%0
parceladdr71.0%41,499
parcelcity59.0%34,475
parcelstate100%58,457
parcelzip100%58,457
legaldesc<0.1%0
township100%58,430
section100%58,430
qtrsection100%58,430
range100%58,430
plssdesc100%58,430
book<0.1%0
page<0.1%0
block14.9%8,701
lot26.4%15,434
parceltype1.3%741
accesstype1.3%741
iucnclass1.1%657
placename3.6%2,084
placetype3.5%2,030
firmid0.7%388
firmdate0.7%388
fldzone0.7%388
zonesubty0.7%388
staticbfe<0.1%0
elevmin96.6%56,479
elevmax96.6%56,479
elevavg96.6%56,479
fireplaces<0.1%0
heating<0.1%0
heatfuel<0.1%0
cooling<0.1%0
foundation<0.1%0
roofcover<0.1%0
siding<0.1%0
bldgtype<0.1%0
naicscode3.6%2,090
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated77.1%45,042
centroidx100%58,457
centroidy100%58,457
surfpointx100%58,457
surfpointy100%58,457
geom100%58,457
extras100%58,457
ownerlist77.0%45,030
placefp47.0%27,481
zoningurl<0.1%0

Schema mapping

How source columns from the acquired Iron County GIS layers map into the harmonized entity schemas and assemble into the published parcel table, alongside supplemented fields (elevation, flood zone) and deterministic columns.

Schema mapping — Iron County, Utah (49021) 1 entity · most recent acquisition per entity · generated 2026-08-30 direct column transformed (expression) geometry extras json supplemented determined ALL ENTITIES → FINAL PARCEL SCHEMA Harmonized entity columns assemble into publish.parcel_layer — matched by column name. Supplemented fields show their fill rate in this county. SOURCE COLUMNS HARMONIZED ENTITIES PUBLISH.PARCEL_LAYER PARCEL parcel_id account_num parcel_add parcel_city parcel_zip coparcel_url geom 5 cols ⇢ parcelid taxacctnum parceladdr parcelcity parcelzip sourceurl geom extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname 77.1% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 96.6% elevmin 96.6% elevmax 96.6% elevavg s_fld_haz_ar · FEMA NFHL 0.7% fldzone 0.7% zonesubty 0.7% firmdate 0.7% firmid supplemented · derived / other pipelines 50.1% numbldgs 77.1% ownertype 77.1% ownername 77.0% owneraddr 77.0% ownercity 76.9% ownerstate 100% parcelstate 100% township 100% section 100% qtrsection 100% range 100% plssdesc 77.0% ownerlist lrid parcelid ogparcelid geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxacctnum numbldgs calcarea ownertype ownername owneraddr ownercity ownerstate parceladdr parcelcity parcelstate parcelzip township section qtrsection range plssdesc firmid firmdate fldzone zonesubty elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras ownerlist publish.parcel_layer columns not fed by these sources (52) — empty or below 50% fill in this county parcelid2, ogparcelid2, parentid, stackid, taxyear, taxdistrict, usecode, usedesc, zoningcode, zoningdesc, numunits, yearbuilt, numfloors bldgsqft, bedrooms, halfbaths, fullbaths, imprvalue, landvalue, agvalue, totalvalue, taxacres, saleamt, saledate, ownerzip, legaldesc, book page, block, lot, parceltype, accesstype, iucnclass, placename, placetype, staticbfe, fireplaces, heating, heatfuel, cooling, foundation roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit, placefp, zoningurl PARCEL 7 mapped · 5 kept in extras · 47 unmapped (NULL) SOURCE COLUMNS HARMONIZED → PARCEL parcel_id account_num parcel_add parcel_city parcel_zip coparcel_url geom parcelid taxacctnum parceladdr parcelcity parcelzip sourceurl geom extras · 5 source columns preserved as json own_type, recorder, parcelscur, parcelnotes, county extras not present in source — filled with NULL (47) parcelid2, taxyear, usecode, usedesc, zoningcode, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bldgsqft, bedrooms, halfbaths fullbaths, imprvalue, landvalue, agvalue, totalvalue, taxacres, saleamt, saledate, ownername, owneraddr, ownercity, ownerstate, ownerzip parcelstate, legaldesc, township, section, qtrsection, range, plssdesc, book, page, block, lot, updated, taxdistrict, parentid, fireplaces heating, cooling, foundation, roofcover, siding, heatfuel

Neighboring counties

Parcel data for counties bordering Iron County:

Frequently asked questions

Where can I find Iron County, UT parcel and GIS data?

Land Records publishes a Iron County, UT parcel dataset in which every parcel carries its boundary polygon (GIS geometry) along with ownership, assessed value, land use, acreage, and sale history. Preview it in the interactive explorer on this page, or download the full Iron County, UT dataset as a GeoPackage or CSV.

How many parcels are in Iron County, UT?

The current dataset contains 58,457 parcel records for Iron County, UT, each with its boundary geometry and assessor attributes.

What is the FIPS code for Iron County, UT?

The FIPS code for Iron County, UT is 49021.

What information does each Iron County, UT parcel record include?

Each Iron County, UT parcel record includes the parcel ID/APN, owner name and mailing address, situs (property) address, assessed land and improvement values, acreage, land-use and zoning codes, year built, and the most recent sale price and date — plus the parcel boundary polygon. Per-attribute fill rates are listed in the coverage table on this page.

Is Iron County, UT parcel data free?

You can preview Iron County, UT parcels for free in the interactive explorer. The complete dataset is available as a one-time download or through the nationwide parcel web service; see the download options on this page for current pricing.

Does Iron County, UT have an official GIS or property records website?

Yes — the official Iron County, UT government website is linked in the county details above. Land Records standardizes Iron County, UT assessor and recorder records into a single nationwide parcel schema with GIS boundary geometry.

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated