This feature class contains center lines for many of the public and private roads, dirt roads, and highways in the County of Kern. The data includes road names, address range, road type, road class, and municipal information.

© Kern County Public Works Department Kern County Planning and Natural Resources Department Kern County Sheriff's Office Kern County Fire Department City of Bakersfield, IT Division, GIS Services This layer is sourced from maps.co.kern.ca.us.

This feature class contains "land" (surface rights) parcel boundaries delineated for property tax assessment purposes.This feature class includes all private, tax-exempt, and state-assessed land parcels listed on the secured tax roll, but does not include mineral rights (subsurface) parcels, mobilehomes, or unsecured entities.Parcels are modeled as planimetric polygons in a seamless fabric comprising the spatial extent of the County of Kern, in the State of California.Tax Roll Data is available in separate database tables, which can be joined to the feature class using the APN field as a key.

© Kern Council of Governments. Merced County Association of Governments. City of Bakersfield, IT Division, GIS Services. City of Shafter, IT Department, GIS Division. Kern County Assessor's Office, Mapping Section.

This layer is a component of Dev Assessor mxd.

Historically, the earliest Bakersfield “urban” subdivisions were not called tracts. The downtown area was subdivided into blocks and lots. Early citywide maps show the city blocks numbered from 1 to over 700. Some blocks were designated by letters rather than numbers. Each block was further subdivided into numbered lots. Thereafter housing subdivisions were called tracts and initially were named (example; Lowell Addition). Many of these “Named” tracts were also subdivided into blocks and lots. The earliest rural land subdivisions are the Sales Map Lands of J. B. Haggin and the Sales Map Lands of the Kern County l Land Company. The legal description of most modern lots is comprised of some combination of the fields: Document Type, Map Number, Phase and Lot Number. A “Block” field should be added for old parcels whose legal description is comprised of tract, block and lot (or just block and lot). The legal description fields for most of the older parcels are not populated at this time. PARCEL FEATURE CLASS ATTRIBUTES Document Type (Domain)Aliquot – subdivision of a public land survey system section i.e. the northeast quarter of the south east quarter of the southwest quarter of section 10 of T28S, R27ETract MapParcel Map Lot Line Adjustment (ex. LLA17-0684)Parcel Map Waiver (ex. PMW17-0398)Parcel Merger (ex. LM17-0695)Map Number Tracts – Old named tracts and numbered tracts, currently into the 7000’sParcel maps – numbered, currently into the 12,000’sMinor land subdivisions (lot line adjustments, parcel map waivers, parcel mergers) format YY-NNNN, where YY is a 2-digit designation of the year and NNNN is a zero-filled number (county files is reversed, ex. NN – YY)Phase Applicable to tract and parcel maps only; i.e. 1, 2, 3 etc. or A, B, C etc. Lot Number i.e. 1, 2, 3 etc. or A, B, C etc. Quality (Domain)In reference to the geometric and positional accuracy of the parcel features. All COGO’d parcels are considered “Excellent” quality User Flag This field is for temporary data storage. However the following user flag values provide information about how the parcel features originally built or subsequently edited: CAD CONVERSION - parcels were developed from georeferenced CAD data. Quality is considered excellent. COGO - parcels were first developed employing COGO editing tools. Quality is considered excellent REBUILT - parcels were originally Valleywide GIS features that were rebuilt using COGO and other editing tools. Quality is considered excellent except parcels that were rebuilt where only assessor maps were available. SHIFTED - original parcels were considered geometrically adequate but required a slight positional shift. Whole blocks of contiguous lots were shifted together. Quality is considered good. Class(Domain)This field provides an opportunity to classify lots for specific purposes. The Private road lot class was created so these lots could be neglected when exporting parcels for the Community Maps Project. Landscape lot Private road lot School lot Sump lot Water Well lot Additional classes could be developed. For the vast majority of parcels the class field is not populated. Address The street address of a lot can be populated if the address point feature class objects have already been created and populated by the GIS Analyst at Community Development. Where there are multiple addresses on a parcel, this data is captured on the Address Point feature class. Assessor Parcel Number (APN) and Assessor Tax Numbers (ATN)The most important parcel layer attributes are the APN and ATN values that are assigned by the Kern County Assessor. An 8 digit APN is assigned to a property that has a specific geometry as defined by a legal description. If any new change occurs such as a lot line adjustment, then the geometry of the parcel(s) are changed and the APN’s for the affected properties are dropped and are never re-assigned. New unique APN’s are assigned to the affected properties and remain as long as the legal description of the geometry does not change. It usually takes at least a few months after a tract is recorded and the parcel feature class objects are developed before the County assigns APN’s to those parcels. The APN field is populated with “NEW” until such time as values are assigned. Parcel APNs can be acquired from the following sources: https://kernpublicworks.com/maps/parcel-maps/, Preliminary (January) and final (July) Kern County parcel GIS releases. Some Condominium common areas do not have an APN. The APN field is populated with “CONDOLOT”. These parcels are retained in order to preserve road right of ways. Compare City parcel layer features with County features to visualize why we retain these parcels.

URL from idinfo/citation in CSDGM metadata.

The California Department of Conservation, Division of Oil, Gas and Geothermal Resources publishes a GIS feature class of well locations across the state for use by the public. This shapefile is the same as the data displayed in the Division's WellFinder application (http://maps.conservation.ca.gov/doggr/index.html) as of July 6, 2016. This shapefile is provided in geographic coordinates on the North American Datum of 1983. A partial description of the attributes contained in this feature class is listed on the WellFinder application's Help system (see entity and attributes section in this metadata). Geothermal wells have been excluded from this shapefile.The DOGGR Wells layer in WellFinder is also available as a WFS service at http://spatialservices.conservation.ca.gov/arcgis/rest/services/DOMS/DOMS_Wells/MapServer/WFSServer?/.Well Attributes: API Number, Well Number, Well Status, GIS Symbol, Operator Code, Operator Name, Lease Name, Field Name, Area Name, District, County, Section, Township, Range, Base Meridian, Latitude, Longitude, Elevation, Total Depth, Redrill Footage, Redrill Cancel Flag, Location Description, Comments, GIS Source Code, Dry Hole, Confidential Well, Directionally Drilled, Hydraulically Fractured, BLM Well, EPA Well, Spud Date, Completion Date, Abandoned Date

© Division of Oil, Gas and Geothermal Resources

This layer is a component of Geology & Geography.

Digital Terrain Model

URL from idinfo/citation in CSDGM metadata.

The District boundary definitions are primarily based on the California county boundaries. The Board of Equalization (BOE) County and City Boundary web service is the authoritative source of County boundaries and this was used to digitize the district boundaries based on the data from March 2023. This data is solely for informational purposes. District 9 has been operating independent of the Central Region since November 1, 2015. Kern County remains the only split county in the state, between Districts 6 and 9 respectively. The BOE data was also used to create the district boundary layers along the coastline.

This a digitize outline of the Kern River by an aerial when the river was filled.

This layer is a component of KernBase1.

The general plan is a composite of many policies, programs and intended actions to govern the future physical development of the five million acres of unincorporated Kern County. This feature layer is updated periodically throughout each year. For Land Use Descriptions, please see the Land Use, Open Space, and Conservation Element of the Kern County General Plan document located at https://kernplanning.com/planning/planning-documents/general-plans-elements/. Last update: April 2025

This shapefile contains tax rate area (TRA) boundaries in Kern County for the specified assessment roll year. Boundary alignment is based on the 2020 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

URL from idinfo/citation in CSDGM metadata.

This data comes from Kern County Fire. The City GIS checks once a year on July 1st.

This layer is a component of KernBase1.

This shapefile contains tax rate area (TRA) boundaries in Kern County for the specified assessment roll year. Boundary alignment is based on the 2020 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

This layer is a component of KernBase1.

Version InformationThe data is updated annually with fire perimeters from the previous calendar year.Firep23_1 was released in May 2024. Two hundred eighty four fires from the 2023 fire season were added to the database (21 from BLM, 102 from CAL FIRE, 72 from Contract Counties, 19 from LRA, 9 from NPS, 57 from USFS and 4 from USFW). The 2020 Cottonwood fire, 2021 Lone Rock and Union fires, as well as the 2022 Lost Lake fire were added. USFW submitted a higher accuracy perimeter to replace the 2022 River perimeter. A duplicate 2020 Erbes fire was removed. Additionally, 48 perimeters were digitized from an historical map included in a publication from Weeks, d. et al. The Utilization of El Dorado County Land. May 1934, Bulletin 572. University of California, Berkeley. There were 2,132 perimeters that received updated attribution, the bulk of which had IRWIN IDs added. The following fires were identified as meeting our collection criteria, but are not included in this version and will hopefully be added in the next update: Big Hill #2 (2023-CAHIA-001020). YEAR_ field changed to a short integer type. San Diego CAL FIRE UNIT_ID changed to SDU (the former code MVU is maintained in the UNIT_ID domains). COMPLEX_INCNUM renamed to COMPLEX_ID and is in process of transitioning from local incident number to the complex IRWIN ID. Perimeters managed in a complex in 2023 are added with the complex IRWIN ID. Those previously added will transition to complex IRWIN IDs in a future update.If you would like a full briefing on these adjustments, please contact the data steward, Kim Wallin (kimberly.wallin@fire.ca.gov), CAL FIRE FRAP._CAL FIRE (including contract counties), USDA Forest Service Region 5, USDI Bureau of Land Management & National Park Service, and other agencies jointly maintain a fire perimeter GIS layer for public and private lands throughout the state. The data covers fires back to 1878. Current criteria for data collection are as follows:CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 damaged/ destroyed residential or commercial structures, and/or caused ≥1 fatality.All cooperating agencies submit perimeters ≥10 acres._Discrepancies between wildfire perimeter data and CAL FIRE Redbook Large Damaging FiresLarge Damaging fires in California were first defined by the CAL FIRE Redbook, and has changed over time, and differs from the definition initially used to define wildfires required to be submitted for the initial compilation of this digital fire perimeter data. In contrast, the definition of fires whose perimeter should be collected has changed once in the approximately 30 years the data has been in existence. Below are descriptions of changes in data collection criteria used when compiling these two datasets. To facilitate comparison, this metadata includes a summary, by year, of fires in the Redbook, that do not appear in this fire perimeter dataset. It is followed by an enumeration of each “Redbook” fire missing from the spatial data. Wildfire Perimeter criteria:~1991: 10 acres timber, 30 acres brush, 300 acres grass, damages or destroys three residence or one commercial structure or does $300,000 worth of damage 2002: 10 acres timber, 50 acres brush, 300 acres grass, damages or destroys three or more structures, or does $300,000 worth of damage~2010: 10 acres timber, 30 acres brush, 300 acres grass, damages or destroys three or more structures (doesn’t include out building, sheds, chicken coops, etc.)Large and Damaging Redbook Fire data criteria:1979: Fires of a minimum of 300 acres that burn at least: 30 acres timber or 300 acres brush, or 1500 acres woodland or grass1981: 1979 criteria plus fires that took ,3000 hours of California Department of Forestry and Fire Protection personnel time to suppress1992: 1981 criteria plus 1500 acres agricultural products, or destroys three residence or one commercial structure or does $300,000 damage1993: 1992 criteria but “three or more structures destroyed” replaces “destroys three residence or one commercial structure” and the 3,000 hours of California Department of Forestry personnel time to suppress is removed2006: 300 acres or larger and burned at least: 30 acres of timber, or 300 acres of brush, or 1,500 acres of woodland, or 1,500 acres of grass, or 1,500 acres of agricultural products, or 3 or more structures destroyed, or $300,000 or more dollar damage loss.2008: 300 acres and largerYear# of Missing Large and Damaging Redbook Fires197922198013198115198261983319842019855219861219875619882319898199091991219921619931719942219959199615199791998101999720004200152002162003520042200512006112007320084320093201022011020124201322014720151020162201711201862019220203202102022020230Total488Enumeration of fires in the Redbook that are missing from Fire Perimeter data. Three letter unit code follows fire name.1979-Sylvandale (HUU), Kiefer (AEU), Taylor(TUU), Parker#2(TCU), PGE#10, Crocker(SLU), Silver Spur (SLU), Parkhill (SLU), Tar Springs #2 (SLU), Langdon (SCU), Truelson (RRU), Bautista (RRU), Crocker (SLU), Spanish Ranch (SLU), Parkhill (SLU), Oak Springs(BDU), Ruddell (BDF), Santa Ana (BDU), Asst. #61 (MVU), Bernardo (MVU), Otay #20 1980– Lightning series (SKU), Lavida (RRU), Mission Creek (RRU), Horse (RRU), Providence (RRU), Almond (BDU), Dam (BDU), Jones (BDU), Sycamore (BDU), Lightning (MVU), Assist 73, 85, 138 (MVU)1981– Basalt (LNU), Lightning #25(LMU), Likely (MNF), USFS#5 (SNF), Round Valley (TUU), St. Elmo (KRN), Buchanan (TCU), Murietta (RRU), Goetz (RRU), Morongo #29 (RRU), Rancho (RRU), Euclid (BDU), Oat Mt. (LAC & VNC), Outside Origin #1 (MVU), Moreno (MVU)1982- Duzen (SRF), Rave (LMU), Sheep’s trail (KRN), Jury (KRN), Village (RRU), Yuma (BDF)1983- Lightning #4 (FKU), Kern Co. #13, #18 (KRN)1984-Bidwell (BTU), BLM D 284,337, PNF #115, Mill Creek (TGU), China hat (MMU), fey ranch, Kern Co #10, 25,26,27, Woodrow (KRN), Salt springs, Quartz (TCU), Bonanza (BEU), Pasquel (SBC), Orco asst. (ORC), Canel (local), Rattlesnake (BDF)1985- Hidden Valley, Magic (LNU), Bald Mt. (LNU), Iron Peak (MEU), Murrer (LMU), Rock Creek (BTU), USFS #29, 33, Bluenose, Amador, 8 mile (AEU), Backbone, Panoche, Los Gatos series, Panoche (FKU), Stan #7, Falls #2 (MMU), USFS #5 (TUU), Grizzley, Gann (TCU), Bumb, Piney Creek, HUNTER LIGGETT ASST#2, Pine, Lowes, Seco, Gorda-rat, Cherry (BEU), Las pilitas, Hwy 58 #2 (SLO), Lexington, Finley (SCU), Onions, Owens (BDU), Cabazon, Gavalin, Orco, Skinner, Shell, Pala (RRU), South Mt., Wheeler, Black Mt., Ferndale, (VNC), Archibald, Parsons, Pioneer (BDU), Decker, Gleason(LAC), Gopher, Roblar, Assist #38 (MVU)1986– Knopki (SRF), USFS #10 (NEU), Galvin (RRU), Powerline (RRU), Scout, Inscription (BDU), Intake (BDF), Assist #42 (MVU), Lightning series (FKU), Yosemite #1 (YNP), USFS Asst. (BEU), Dutch Kern #30 (KRN)1987- Peach (RRU), Ave 32 (TUU), Conover (RRU), Eagle #1 (LNU), State 767 aka Bull (RRU), Denny (TUU), Dog Bar (NEU), Crank (LMU), White Deer (FKU), Briceburg (LMU), Post (RRU), Antelope (RRU), Cougar-I (SKU), Pilitas (SLU) Freaner (SHU), Fouts Complex (LNU), Slides (TGU), French (BTU), Clark (PNF), Fay/Top (SQF), Under, Flume, Bear Wallow, Gulch, Bear-1, Trinity, Jessie, friendly, Cold, Tule, Strause, China/Chance, Bear, Backbone, Doe, (SHF) Travis Complex, Blake, Longwood (SRF), River-II, Jarrell, Stanislaus Complex 14k (STF), Big, Palmer, Indian (TNF) Branham (BLM), Paul, Snag (NPS), Sycamore, Trail, Stallion Spring, Middle (KRN), SLU-864 1988- Hwy 175 (LNU), Rumsey (LNU), Shell Creek (MEU), PG&E #19 (LNU), Fields (BTU), BLM 4516, 417 (LMU), Campbell (LNF), Burney (SHF), USFS #41 (SHF), Trinity (USFS #32), State #837 (RRU), State (RRU), State (350 acres), RRU), State #1807, Orange Co. Asst (RRU), State #1825 (RRU), State #2025, Spoor (BDU), State (MVU), Tonzi (AEU), Kern co #7,9 (KRN), Stent (TCU), 1989– Rock (Plumas), Feather (LMU), Olivas (BDU), State 1116 (RRU), Concorida (RRU), Prado (RRU), Black Mt. (MVU), Vail (CNF)1990– Shipman (HUU), Lightning 379 (LMU), Mud, Dye (TGU), State 914 (RRU), Shultz (Yorba) (BDU), Bingo Rincon #3 (MVU), Dehesa #2 (MVU), SLU 1626 (SLU)1991- Church (HUU), Kutras (SHF)1992– Lincoln, Fawn (NEU), Clover, fountain (SHU), state, state 891, state, state (RRU), Aberdeen (BDU), Wildcat, Rincon (MVU), Cleveland (AEU), Dry Creek (MMU), Arroyo Seco, Slick Rock (BEU), STF #135 (TCU)1993– Hoisington (HUU), PG&E #27 (with an undetermined cause, lol), Hall (TGU), state, assist, local (RRU), Stoddard, Opal Mt., Mill Creek (BDU), Otay #18, Assist/ Old coach (MVU), Eagle (CNF), Chevron USA, Sycamore (FKU), Guerrero, Duck1994– Schindel Escape (SHU), blank (PNF), lightning #58 (LMU), Bridge (NEU), Barkley (BTU), Lightning #66 (LMU), Local (RRU), Assist #22 & #79 (SLU), Branch (SLO), Piute (BDU), Assist/ Opal#2 (BDU), Local, State, State (RRU), Gilman fire 7/24 (RRU), Highway #74 (RRU), San Felipe, Assist #42, Scissors #2 (MVU), Assist/ Opal#2 (BDU), Complex (BDF), Spanish (SBC)1995-State 1983 acres, Lost Lake, State # 1030, State (1335 acres), State (5000 acres), Jenny, City (BDU), Marron #4, Asist #51 (SLO/VNC)1996- Modoc NF 707 (Ambrose), Borrego (MVU), Assist #16 (SLU), Deep Creek (BDU), Weber (BDU), State (Wesley) 500 acres (RRU), Weaver (MMU), Wasioja (SBC/LPF), Gale (FKU), FKU 15832 (FKU), State (Wesley) 500 acres, Cabazon (RRU), State Assist (aka Bee) (RRU), Borrego, Otay #269 (MVU), Slaughter house (MVU), Oak Flat (TUU)1997- Lightning #70 (LMU), Jackrabbit (RRU), Fernandez (TUU), Assist 84 (Military AFV) (SLU), Metz #4 (BEU), Copperhead (BEU), Millstream, Correia (MMU), Fernandez (TUU)1998- Worden, Swift, PG&E 39 (MMU), Chariot, Featherstone, Wildcat, Emery, Deluz (MVU), Cajalco Santiago (RRU)1999- Musty #2,3 (BTU), Border # 95 (MVU), Andrews,

The project leads for the collection of this data were Julie Garcia and Evan King. Mule deer (32 adult females) from the Kern River herd were captured and equipped with Lotek LiteTrack Iridium collars, transmitting data from 2020-2021. GPS fixes were set for 2-hour intervals. The Kern River herd migrates from winter ranges in Sequoia National Forest north of Johnsondale and east of Slate Mountain northward to the area around Redrocks Meadows and along the Kern Canyon ridgeline to Sequoia National Park. Due to a high percentage of poor fixes, likely due to highly variable topographic terrain, between 2-18 percent of GPS locations per deer were fixed in 2-dimensional space and removed to ensure locational accuracy. The methodology used for this migration analysis allowed for the mapping of winter ranges and the identification of migration corridors and stopovers. Brownian Bridge Movement Models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 27 migrating deer, including 69 migration sequences, location, date, time, and average location error as inputs in Migration Mapper. The average migration time and average migration distance for deer was 15.38 days and 32.13 km, respectively. Corridors and stopovers were prioritized based on the number of animals moving through a particular area. Separate models using Brownian bridge movement models (BMMM) and fixed motion variances of 1000 were produced per migration sequence and compared for the entire dataset, with best models being combined prior to population-level analyses (10 percent of sequences selected with BMMM). Corridors were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Winter range analyses were based on data from 27 individual deer and 60 wintering sequences using a fixed motion variance of 1000. Winter range designations for this herd may expand with a larger sample, filling in some of the gaps between winter range polygons in the map. Additional migration routes and winter range areas likely exist beyond what was modeled in our output.Corridors are visualized based on deer use per cell in the BBMMs, with greater than or equal to 1 deer, greater than or equal to 3 deer (10 percent of the sample), and greater than or equal to 6 deer (20 percent of the sample) representing migration corridors, moderate use, and high use corridors, respectively. Stopovers were calculated as the top 10 percent of the population level utilization distribution during migrations and can be interpreted as high use areas. Stopover polygon areas less than 20,000 m2 were removed, but remaining small stopovers may be interpreted as short-term resting sites, likely based on a small concentration of points from an individual animal. Winter range is visualized as the 50th percentile contour of the winter range utilization distribution.

The Kern County Zoning layer contains all zoning districts for the county, with the exclusion of the incorporated cities. The Kern County Zoning Ordinance is Chapter 19 of the Code of Ordinances. This title is adopted to promote and protect the public health, safety, and welfare through the orderly regulation of land uses throughout the unincorporated area of the County.This feature layer is updated periodically throughout each year. For Zoning descriptions, please see the Kern County Zoning Ordinance document located at: https://kernplanning.com/planning/planning-documents/zoning-ordinance/. Last update: 4/30/2025