Plumas County, CA Parcels & GIS Data

Plumas County, CA parcel data: 25,998 property records with owner names, assessed values, land use, acreage, and addresses. Preview and download.

Land Records publishes Plumas County, California parcel data covering 25,998 property records.

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

Plumas County is a county located in the Sierra Nevada of the U.S. state of California. As of the 2020 United States census, the population was 19,790. The county seat is Quincy, and the only incorporated city is Portola.

FIPS 06063

Official county website: https://www.plumascounty.us/

The FIPS code for Plumas County is 06063.

LassenTehamaShastaButteYubaSierraPlumas
Hosted Web API$200/mo

Attribute coverage

Plumas County contains 25,998 parcels in the current dataset. Column coverage is the percentage of those parcels for which the attribute is populated (non-NULL). For the LBCS columns, only real classifications count: the to-be-determined and not-applicable placeholder codes are excluded.

ColumnCoverageRecords populated
lrid100%25,998
parcelid100%25,998
parcelid270.9%18,438
ogparcelid100%25,998
ogparcelid20.4%91
parentid<0.1%0
stackid<0.1%0
geoid100%25,998
statefp100%25,998
countyfp100%25,998
countyname100%25,998
cousubfp100%25,998
cousubname100%25,998
tractce100%25,998
tractname100%25,998
taxacctnum<0.1%0
taxyear100%25,998
taxdistrict<0.1%0
usecode99.8%25,957
usedesc99.8%25,954
zoningcode100%25,997
zoningdesc100%25,993
numbldgs34.5%8,980
numunits32.0%8,308
yearbuilt<0.1%0
numfloors27.2%7,059
bldgsqft99.6%25,903
bedrooms<0.1%0
halfbaths<0.1%0
fullbaths<0.1%0
imprvalue0.2%47
landvalue99.8%25,950
agvalue0.2%47
totalvalue51.0%13,262
taxacres99.6%25,903
calcarea100%25,998
saleamt<0.1%0
saledate35.9%9,334
ownertype55.7%14,481
ownername55.1%14,335
owneraddr54.4%14,138
ownercity54.1%14,069
ownerstate54.3%14,123
ownerzip54.4%14,139
parceladdr85.3%22,176
parcelcity86.9%22,605
parcelstate100%25,998
parcelzip96.1%24,987
legaldesc<0.1%0
township100%25,993
section100%25,993
qtrsection100%25,993
range100%25,993
plssdesc100%25,993
book<0.1%0
page<0.1%0
block<0.1%0
lot<0.1%0
parceltype7.0%1,814
accesstype7.0%1,814
iucnclass6.5%1,697
placename9.4%2,434
placetype9.5%2,475
firmid100%25,998
firmdate100%25,998
fldzone100%25,998
zonesubty77.6%20,178
staticbfe<0.1%9
elevmin95.1%24,712
elevmax95.1%24,712
elevavg95.1%24,712
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
naicscode9.5%2,460
frsid<0.1%3
dfrurl<0.1%3
caapermit<0.1%3
cwapermit<0.1%3
rcrapermit<0.1%3
updated100%25,998
centroidx100%25,998
centroidy100%25,998
surfpointx100%25,998
surfpointy100%25,998
geom100%25,998
extras100%25,998
ownerlist0.3%85
placefp79.8%20,736
zoningurl59.8%15,550
lbcsactivity93.2%24,232
lbcsfunction90.8%23,602
lbcstype91.2%23,708
lbcscharacter94.7%24,620
lbcsownership59.4%15,442
sourceurl55.6%14,450

Schema mapping

How source columns from the acquired Plumas 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 — Plumas County, California (06063) 2 entities · most recent acquisition per entity · generated 2026-10-10 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 apn scag_luco scag_lu zoning bui_area land_val area_ac full_add city zip_code geom 21 cols ⇢ parcelid usecode usedesc zoningcode bldgsqft landvalue taxacres parceladdr parcelcity parcelzip geom extras ZONING geom regional_d ecoregion_ ecoregion1 ecoregio_1 ecoregio_2 ecoregio_3 calvegzone tile usgs_ander usgs_and_1 physiognom physiogn_1 physiogn_2 physiogn_3 saf_cover_ srm_cover_ aggregatio covertype os_tree_di regional_1 os_tree__1 regional_2 con_cfa hdw_cfa shb_cfa heb_cfa data_sourc r05_data_s source_dat map_update cause_date rev_date total_tree tree_cfa_c prod canopystru reforestat origin_yea whrlifefor whrtype whrsize whrdensity globalid geom zoningcode extras determined · ground truth 100% lrid 100% geoid 100% statefp 100% countyfp 100% countyname 100% cousubfp 100% cousubname 100% tractce 100% tractname 100% taxyear 100% updated geom · derived from geometry geom dem.us_1m · USGS 1m DEM 95.1% elevmin 95.1% elevmax 95.1% elevavg s_fld_haz_ar · FEMA NFHL 100% fldzone 77.6% zonesubty 0.0% staticbfe 100% firmdate 100% firmid supplemented · derived / other pipelines 70.9% parcelid2 100% zoningdesc 51.0% totalvalue 55.7% ownertype 55.1% ownername 54.4% owneraddr 54.1% ownercity 54.3% ownerstate 54.4% ownerzip 100% parcelstate 100% township 100% section 100% qtrsection 100% range 100% plssdesc 79.8% placefp 59.8% zoningurl 93.2% lbcsactivity 90.8% lbcsfunction 91.2% lbcstype 94.7% lbcscharacter 59.4% lbcsownership 55.6% sourceurl lrid parcelid parcelid2 ogparcelid geoid statefp countyfp countyname cousubfp cousubname tractce tractname taxyear usecode usedesc zoningcode zoningdesc bldgsqft landvalue totalvalue taxacres calcarea ownertype ownername owneraddr ownercity ownerstate ownerzip parceladdr parcelcity parcelstate parcelzip township section qtrsection range plssdesc firmid firmdate fldzone zonesubty staticbfe elevmin elevmax elevavg updated centroidx centroidy surfpointx surfpointy geom extras placefp zoningurl lbcsactivity lbcsfunction lbcstype lbcscharacter lbcsownership sourceurl publish.parcel_layer columns not fed by these sources (41) — empty or below 50% fill in this county ogparcelid2, parentid, stackid, taxacctnum, taxdistrict, numbldgs, numunits, yearbuilt, numfloors, bedrooms, halfbaths, fullbaths, imprvalue agvalue, saleamt, saledate, legaldesc, book, page, block, lot, parceltype, accesstype, iucnclass, placename, placetype, fireplaces, heating heatfuel, cooling, foundation, roofcover, siding, bldgtype, naicscode, frsid, dfrurl, caapermit, cwapermit, rcrapermit, ownerlist PARCEL 11 mapped · 1 transformed · 21 kept in extras · 43 unmapped (NULL) SOURCE COLUMNS HARMONIZED → PARCEL apn scag_luco scag_lu zoning bui_area land_val area_ac full_add city zip_code geom parcelid usecode usedesc zoningcode bldgsqft landvalue taxacres parceladdr parcelcity parcelzip NULLIF(zip_code, 0)::text geom extras · 21 source columns preserved as json house_num, prefix_dir, st_name, st_type, unit, full_stna land_use, fhsz_code, fhsz_desc, flo_code, flo_desc, faultzone landslide, liq_zone, drought, dro_desc, sol_rad, wind_sp, tax ownership, area_sqft extras not present in source — filled with NULL (43) parcelid2, taxacctnum, taxyear, zoningdesc, numbldgs, numunits, yearbuilt, numfloors, bedrooms, halfbaths, fullbaths, imprvalue, agvalue totalvalue, saleamt, saledate, ownername, owneraddr, ownercity, ownerstate, ownerzip, parcelstate, legaldesc, township, section, qtrsection range, plssdesc, book, page, block, lot, updated, sourceurl, taxdistrict, parentid, heatfuel, fireplaces, heating, cooling, foundation roofcover, siding ZONING 3 mapped · 2 transformed · 7 unmapped (NULL) SOURCE COLUMNS HARMONIZED → ZONING geom regional_d ecoregion_ ecoregion1 ecoregio_1 ecoregio_2 ecoregio_3 calvegzone tile usgs_ander usgs_and_1 physiognom physiogn_1 physiogn_2 physiogn_3 saf_cover_ srm_cover_ aggregatio covertype os_tree_di regional_1 os_tree__1 regional_2 con_cfa hdw_cfa shb_cfa heb_cfa data_sourc r05_data_s source_dat map_update cause_date rev_date total_tree tree_cfa_c prod canopystru reforestat origin_yea whrlifefor whrtype whrsize whrdensity globalid geom zoningcode COALESCE(NULLIF(TRIM(regional_d::text), ''), 'UNKNOWN')::text extras ( json_build_object( 'ecoregion_', NULLIF(TRIM(ecoregion_::text… not present in source — filled with NULL (7) zoningdesc, zoningtype, ordinance, setbacks, restrictions, notes, sourceurl

Neighboring counties

Parcel data for counties bordering Plumas County:

Frequently asked questions

Where can I find Plumas County, CA parcel and GIS data?

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

How many parcels are in Plumas County, CA?

The current dataset contains 25,998 parcel records for Plumas County, CA, each with its boundary geometry and assessor attributes.

What is the FIPS code for Plumas County, CA?

The FIPS code for Plumas County, CA is 06063.

What information does each Plumas County, CA parcel record include?

Each Plumas County, CA 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 Plumas County, CA parcel data free?

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

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

On this page