Land Records Logo

Land Records

Daggett County, UT Parcels & GIS Data

Daggett County, UT parcel data: 3,324 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Daggett County, Utah parcel data covering 3,324 property records.

This page documents parcel-level coverage for Daggett 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 Daggett County are listed in the attribute-coverage table below. Preview the data in the interactive explorer, or download the complete Daggett County property dataset.

Daggett County is a county in the northeastern corner of the U.S. state of Utah. As of the 2020 United States Census, the population was 935, making it the least populous county in Utah. Its county seat is Manila.

FIPS 49009

Official county website: http://www.daggettcounty.org

The FIPS code for Daggett County is 49009.

Explore Daggett County data
UintahMoffatSweetwaterSummitDuchesneDaggett
Buy dataset · $105.00One-time downloadSubscribe · $185.001 year of quarterly updates

Attribute coverage

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

ColumnCoverageRecords populated
lrid100%3,324
parcelid100%3,323
parcelid2<0.1%0
ogparcelid100%3,324
ogparcelid2<0.1%0
parentid<0.1%0
stackid<0.1%0
geoid100%3,324
statefp100%3,324
countyfp100%3,324
countyname100%3,324
cousubfp100%3,324
cousubname100%3,324
tractce100%3,324
tractname100%3,324
taxacctnum97.1%3,228
taxyear95.2%3,166
taxdistrict<0.1%0
usecode<0.1%0
usedesc<0.1%0
zoningcode16.0%532
zoningdesc15.2%506
numbldgs57.8%1,922
numunits<0.1%0
yearbuilt28.4%943
numfloors<0.1%0
bldgsqft28.7%954
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue36.6%1,218
landvalue83.5%2,777
agvalue<0.1%0
totalvalue85.7%2,849
taxacres<0.1%0
calcarea100%3,324
saleamt<0.1%0
saledate<0.1%0
ownertype95.3%3,167
ownername95.3%3,167
owneraddr93.1%3,094
ownercity<0.1%0
ownerstate<0.1%0
ownerzip<0.1%0
parceladdr85.8%2,851
parcelcity31.2%1,037
parcelstate100%3,324
parcelzip100%3,324
legaldesc<0.1%0
township99.8%3,319
section99.8%3,319
qtrsection99.8%3,319
range99.8%3,319
plssdesc99.8%3,319
book<0.1%0
page<0.1%0
block<0.1%0
lot<0.1%0
parceltype16.8%557
accesstype16.8%557
iucnclass16.8%557
placename17.7%589
placetype17.6%585
firmid<0.1%0
firmdate<0.1%0
fldzone<0.1%0
zonesubty<0.1%0
staticbfe<0.1%0
elevmin86.4%2,872
elevmax86.4%2,872
elevavg86.4%2,872
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
naicscode17.7%589
frsid<0.1%0
dfrurl<0.1%0
caapermit<0.1%0
cwapermit<0.1%0
rcrapermit<0.1%0
updated95.3%3,167
centroidx100%3,324
centroidy100%3,324
surfpointx100%3,324
surfpointy100%3,324
geom100%3,324
extras100%3,324
ownerlist91.3%3,034

Schema mapping

How source columns from the acquired Daggett 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 — Daggett County, Utah (49009) 1 entity · most recent acquisition per entity · generated 2026-08-08 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 95.2% taxyear 95.3% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 86.4% elevmin 86.4% elevmax 86.4% elevavg supplemented · derived / other pipelines 57.8% numbldgs 83.5% landvalue 85.7% totalvalue 95.3% ownertype 95.3% ownername 93.1% owneraddr 100% parcelstate 100% township 100% section 100% qtrsection 100% range 100% plssdesc 91.3% ownerlist lrid parcelid ogparcelid geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxacctnum taxyear numbldgs landvalue totalvalue calcarea ownertype ownername owneraddr parceladdr parcelcity parcelstate parcelzip township section qtrsection range plssdesc elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras ownerlist publish.parcel_layer columns not fed by these sources (53) — empty or below 50% fill in this county parcelid2, ogparcelid2, parentid, stackid, taxdistrict, usecode, usedesc, zoningcode, zoningdesc, numunits, yearbuilt, numfloors, bldgsqft bedrooms, halfbaths, fullbaths, imprvalue, agvalue, taxacres, saleamt, saledate, ownercity, ownerstate, ownerzip, legaldesc, book, page, block lot, parceltype, accesstype, iucnclass, placename, placetype, firmid, firmdate, fldzone, zonesubty, staticbfe, fireplaces, heating, heatfuel cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit 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 Daggett County:

Frequently asked questions

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

Land Records publishes a Daggett 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 Daggett County, UT dataset as a GeoPackage or CSV.

How many parcels are in Daggett County, UT?

The current dataset contains 3,324 parcel records for Daggett County, UT, each with its boundary geometry and assessor attributes.

What is the FIPS code for Daggett County, UT?

The FIPS code for Daggett County, UT is 49009.

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

Each Daggett 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 Daggett County, UT parcel data free?

You can preview Daggett 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 Daggett County, UT have an official GIS or property records website?

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

On this page

Attribute coverageSchema mappingNeighboring countiesFAQRelated