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.

The 1998 Kern County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography and extensive field visits, the land use boundaries and attributes were digitized, and the resultant data went through standard quality control procedures before finalizing. The land uses that were gathered were detailed agricultural land uses, and lesser detailed urban and native vegetation land uses. The data was gathered and digitized by staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. The finalized data include a shapefile covering the major agricultural and urban areas of Kern County, primarily in western Kern County (land use vector data) and JPEG files (raster data from aerial imagery). Important Points about Using this Data Set: 1. The land use boundaries were either drawn on-screen using developed photoquads, or hand drawn directly on USGS quad maps and then digitized. They were drawn to depict observable areas of the same land use. They were not drawn to represent legal parcel (ownership) boundaries, or meant to be used as parcel boundaries. 2. This survey was a "snapshot" in time. The indicated land use attributes of each delineated area (polygon) were based upon what the surveyor saw in the field at that time, and, to an extent possible, whatever additional information the aerial photography might provide. For example, the surveyor might have seen a cropped field in the photograph, and the field visit showed a field of corn, so the field was given a corn attribute. In another field, the photograph might have shown a crop that was golden in color (indicating grain prior to harvest), and the field visit showed newly planted corn. This field would be given an attribute showing a double crop, grain followed by corn. The DWR land use attribute structure allows for up to three crops per delineated area (polygon). In the cases where there were crops grown before the survey took place, the surveyor may or may not have been able to detect them from the field or the photographs. For crops planted after the survey date, the surveyor could not account for these crops. Thus, although the data is very accurate for that point in time, it may not be an accurate determination of what was grown in the fields for the whole year. If the area being surveyed does have double or multicropping systems, it is likely that there are more crops grown than could be surveyed with a "snapshot". 3. If the data is to be brought into a GIS for analysis of cropped (or planted) acreage, two things must be understood: a. The acreage of each field delineated is the gross area of the field. The amount of actual planted and irrigated acreage will always be less than the gross acreage, because of ditches, farm roads, other roads, farmsteads, etc. Thus, a delineated corn field may have a GIS calculated acreage of 40 acres but will have a smaller cropped (or net) acreage, maybe 38 acres. b. Double and multicropping must be taken into account. A delineated field of 40 acres might have been cropped first with grain, then with corn, and coded as such. To estimate actual cropped acres, the two crops are added together (38 acres of grain and 38 acres of corn) which results in a total of 76 acres of net crop (or planted) acres. 4. Water source information was not collected for this survey. 5. Not all land use codes will be represented in the survey.The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.3, dated April 13, 2022. DWR makes no warranties or guarantees - either expressed or implied - as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov.

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.

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.

URL from idinfo/citation in CSDGM metadata.

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.

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset was made available (approximately 2004) through CALFIRE - FRAP and the California Spatial Information Library (CaSIL), with additional updates throughout subsequent years. More recently, an effort was made to improve the coastal linework by using the previous interior linework from the 24k data, but replacing the coastal linework based on NOAA's ERMA coastal dataset (which used NAIP 2010). In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included, with the exception of the Channel Islands which ARE included.This service represents the latest released version, and is updated when new versions are released. As of June, 2019 it represents cnty19_1.

These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale CONUS and Hawaii, 1:25,000-scale Alaska, and 1:20,000-scale Puerto Rico / US Virgin Island topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.Metadata Link for the USGS 1/3 arc-second Contour Downloadable Data Collectionhttps://www.sciencebase.gov/catalog/file/get/4f70ab22e4b058caae3f8deb?f=_disk_35%2F1e%2F20%2F351e2044b02ae4f163c2cdcaa66fda19a32a4ba4&transform=1&allowOpen=true

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

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.

This map is designated as Final.Land-Use Data Quality ControlEvery published digital survey is designated as either ‘Final’, or ‘Provisional’, depending upon its status in a peer review process.Final surveys are peer reviewed with extensive quality control methods to confirm that field attributes reflect the most detailed and specific land-use classification available, following the standard DWR Land Use Legendspecific to the survey year. Data sets are considered ‘final’ following the reconciliation of peer review comments and confirmation by the originating Regional Office. During final review, individual polygons are evaluated using a combination of aerial photointerpretation, satellite image multi-spectral data and time series analysis, comparison with other sources of land use data, and general knowledge of land use patterns at the local level.Provisional datasets have been reviewed for conformance with DWR’s published data record format, and for general agreement with other sources of land use trends. Comments based on peer review findings may not be reconciled, and no significant edits or changes are made to the original survey data.The 2006 Kern County land use survey data was developed by the State of California, Department of Water Resources (DWR) through its Division of Planning and Local Assistance (DPLA). Digitized land use boundaries and associated attributes were gathered by staff from DWR’s San Joaquin District (SJD), using extensive field visits and aerial photography. Land use polygons in agricultural areas were mapped in greater detail than areas of urban or native vegetation. Prior to the summer field survey by SJD, DPLA staff analyzed Landsat 5 imagery to identify fields likely to have winter crops. The combined land use data went through standard quality control procedures before final processing. Quality control procedures were performed jointly by staff at DWR’s DPLA Land Use Unit and SJD. This data was developed to aid DWR’s ongoing efforts to monitor land use for the main purpose of determining current and projected water uses. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standards version 2.1, dated March 9, 2016. DWR makes no warranties or guarantees - either expressed or implied - as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov. This data represents a land use survey of Kern County conducted by DWR, SJD staff, under the leadership of David Scruggs, Senior Land and Water Use Supervisor. The field work for this survey was conducted during the summer of 2006. SJD staff physically visited each delineated field, noting the crops grown at each location. Field survey boundary data was developed using: 1. The county was surveyed with a combination of 2005 one meter and 2006 two meter NAIP imagery. 2. The 2005 images were used in the spring of 2006 to develop the land use field boundary lines that would be used for the summer survey. The 2006 imagery was used for identification in the field and to edit any boundary line changes from the 2005 imagery. 3. These images and land use boundaries were copied onto laptop computers that were used as the field collection tools. The staff took these laptops in the field and virtually all areas were visited to positively identify the land use. The site visits occurred from June through September 2006 (approx.). Land use codes were digitized directly into the laptop computers using AUTOCAD (and a standardized digitizing process) any land use boundaries changes were noted and corrected back in the office. 4. After quality control/assurance procedures were completed on each file (DWG), the data was finalized for the summer survey. The primary focus of this land use survey is mapping agricultural fields. Urban residences and other urban areas were delineated using aerial photo interpretation. Some urban areas may have been missed, especially in forested areas. Rural residential land use was delineated by drawing polygons to surround houses and other buildings along with some of the surrounding land. These footprint areas do not represent the entire footprint of urban land. Sources of irrigation water were identified for general areas and occasionally supplemented by information obtained from landowners. Water source information was not collected for each field in the survey, so the water source listed for a specific agricultural field may not be accurate. Before final processing, standard quality control procedures were performed jointly by staff at DWR's SJD, and at DSIWM headquarters under the leadership of Jean Woods, Senior Land and Water Use Supervisor. After quality control procedures were completed, the data was finalized. The positional accuracy of the digital line work, which is based upon the orthorectified NAIP imagery, is approximately 6 meters. The land use attribute accuracy for agricultural fields is high, because almost every delineated field was visited by a surveyor. The accuracy is 95 percent because some errors may have occurred. Possible sources of attribute errors are: a) Human error in the identification of crop types, b) Data entry errors.

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

Boundary Sierra Nevada Conservancy (SNC) boundary. The boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in SB 208 (2022). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Siskiyou, Tehama, Trinity, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope’s blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and up to the southern boundary of the Pit River watershed where Bear Creek Mountain Road and Dry Creek Road intersect; the southern boundary of the Pit River watershed; the western boundary of the upper Trinity watershed in the County of Trinity; on the north by the boundary of the upper Trinity watershed in the County of Trinity and the upper Sacramento, McCloud, and Pit River watersheds in the County of Siskiyou; and within the County of Modoc, the easterly boundary of the Klamath River watershed; and on the north in the County of Modoc by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 6605.5 of the Government Code, where it is defined as "region" (2) The San Joaquin River Parkway, as described in Section 32510.According to GreenInfo Network and the California Department of Fish and Game, the blue oak woodland used to define a portion of the Sierra Nevada Conservancy's western boundary was delineated using referenced vegetation and imagery data.Subregions“Subregions” means the six subregions in which the Sierra Nevada Region is located, described as follows:(1) The northwest Sierra subregion, comprising the Counties of Shasta, Siskiyou, Tehama, and Trinity.(2) The northeast Sierra subregion, comprising the Counties of Lassen, Modoc, Plumas, and Sierra.(3) The north central Sierra subregion, comprising the Counties of Butte, Nevada, Placer, and Yuba.(4) The south central Sierra subregion, comprising the Counties of Amador, Calaveras, El Dorado, and Tuolumne.(5) The southeast Sierra subregion, comprising the Counties of Alpine, Inyo, Kern, and Mono.(6) The southwest Sierra subregion, comprising the Counties of Fresno, Madera, Mariposa, and Tulare.

Sierra Nevada Conservancy (SNC) boundary. The boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in SB 208 (2022). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Siskiyou, Tehama, Trinity, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope’s blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and up to the southern boundary of the Pit River watershed where Bear Creek Mountain Road and Dry Creek Road intersect; the southern boundary of the Pit River watershed; the western boundary of the upper Trinity watershed in the County of Trinity; on the north by the boundary of the upper Trinity watershed in the County of Trinity and the upper Sacramento, McCloud, and Pit River watersheds in the County of Siskiyou; and within the County of Modoc, the easterly boundary of the Klamath River watershed; and on the north in the County of Modoc by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 6605.5 of the Government Code, where it is defined as "region" (2) The San Joaquin River Parkway, as described in Section 32510.

According to GreenInfo Network and the California Department of Fish and Game, the blue oak woodland used to define a portion of the Sierra Nevada Conservancy's western boundary was delineated using referenced vegetation and imagery data.

While Southern California Edison makes every effort to ensure the accuracy of DRPEP, the data provided is for information purposes only. Southern California Edison makes no guarantee, expressly or implied, for the outcome of an interconnection request.Note: ICA monthly refresh for JUNE 2025 is completed.