This is the Feature Class for Kern County Boundary.Projected Coordinate System: NAD_1983_StatePlane_California_V_FIPS_0405_Feet

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

URL from idinfo/citation in CSDGM metadata.

Pursuant to Section 51237 of the State of California Government Code, agricultural preserve boundaries are filed and kept current by the Planning and Natural Resources Department.This layer contains the boundaries for the agricultural preserves for the County of Kern. "An agricultural preserve defines the boundary of an area within which a city or county will enter into contracts with landowners. The boundary is designated by resolution of the board of supervisors (board) or city council (council) having jurisdiction. Only land located within an agricultural preserve is eligible for a Williamson Act contract. Preserves are regulated by rules and restrictions designated in the resolution to ensure that the land within the preserve is maintained for agricultural or open space use (California Dept. of Conservation)."This should be used with the "agricultural preserve included" layer to determine what property is eligible for a Williamson Act contract. Last Updated: 2020

This layer is a component of KernBase1.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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.

This dataset contains Tract Map boundaries within the County of Kern. Updated 4-29-2025

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 TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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 data is intended to provide a reasonable representation of parcels, as defined for property tax assessment purposes, that can be used easily in a computerized geographic information system. This data is not intended to replace the hardcopy assessment maps or any other official or unofficial county maps, and it is not to be construed as portraying legal ownership or divisions of land for purposes of zoning or subdivision law.

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 APN9 field as the SQL join key.

The defined boundaries of the 26th, 32nd, 34th, and 36th Assembly Districts within the County of Kern.

© County of Kern - Elections Department Last Updated 06/29/2017 - Joshua Roberts

This layer is a component of Districts & Precincts.

City boundaries.

An agricultural preserve defines the boundary of an area within which a city or county will enter into contracts with landowners. The boundary is designated by resolution of the board of supervisors (board) or city council (council) having jurisdiction. Only land located within an agricultural preserve is eligible for a Williamson Act contract. Preserves are regulated by rules and restrictions designated in the resolution to ensure that the land within the preserve is maintained for agricultural or open space use (California Dept. of Conservation)."This should be used with the "agricultural preserve boundary" layer to determine what property is eligible for a Williamson Act contract.Last Updated 4/30/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

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

Analysis of ‘Kern County Land Use Survey 2006’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/d678cf89-392c-4ea7-96a2-16286668cb5e on 28 January 2022.

--- Dataset description provided by original source is as follows ---

--- Original source retains full ownership of the source dataset ---

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.