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.

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. 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 Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

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

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 Address Ranges Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

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

In order to provide an accurate data set of service area boundaries for California drinking water systems, the Division of Drinking Water of the California Water Resources Control Board (SWRCB DDW) has undertaken a project to vet and verify the data collected by the Tracking California's Water Boundary Tool (WBT).Note: This feature layer is updated on a regular basis. However, in some locations where it is shared, it shows the “Data Updated” date as the last time the item has changed, not the data. To accurately determine when the data was last updated, open the data table and sort by Last Edited Date field.SWRCB DDW downloaded a copy of the current water system service areas loaded in the WBT as of June 27, 2019. Additional attribute fields indicating verification status, verification staff and system type were appended to the data set. SWRCB DDW staff are reviewing and validating the displayed boundaries of each service area as well as contacting the service providers regarding necessary corrections. The verification status of any particular service area may be found in the Verification Status field.For any questions regarding this dataset, please contact the Data Support Unit at DDW-DSU@waterboards.ca.gov.

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 defined boundaries of each of the 11 incorporated cities in Kern County. Current as of 7-7-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. 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 Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This digital dataset is comprised of two separate data files that contain total dissolved solids, well construction, and well identifying information for 1,131 petroleum wells used to map salinity in and around 31 southern and central California oil fields. Salinity mapping was done for 27 fields located in the southern San Joaquin Valley of Kern County (North Belridge, South Belridge, Canfield Ranch, North Coles Levee, South Coles Levee, Cymric, Edison, Elk Hills, Fruitvale, Greeley, Jasmin, Kern Bluff, Kern Front, Kern River, Lost Hills, Mount Poso, Mountain View, Poso Creek, Rio Bravo, Rosedale, Rosedale Ranch, Round Mountain, San Emidio Nose, Tejon, Ten Section, Wheeler Ridge, and Yowlumne), 3 fields in the Los Angeles (LA) Basin of Los Angeles County (Montebello, Santa Fe Springs, and Wilmington), and 1 field in the central coast area of Santa Barbara and San Luis Obispo Counties (Santa Maria Valley). Only petroleum wells that were located within the administrative 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

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. 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 Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

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.

This digital dataset defines the extent of the alluvial deposits in the Central Valley of California and encompasses the contiguous Sacramento, San Joaquin, and Tulare Lake groundwater basins defined by California's Department of Water Resources. The boundary encompasses an approximate 50,000 square-kilometer region of California. The boundary was used to define the lateral boundary of the area simulated by the transient Central Valley Hydrologic Model (CVHM) (Faunt, 2009). The CVHM is the most recent regional-scale model of the Central Valley developed by the U.S. Geological Survey (USGS). The CVHM was developed as part of the USGS Groundwater Resources Program (see "Foreword", Chapter A, page iii, for details).

City boundaries.

This data set maps and describes the geology of the Apache Canyon 7.5' quadrangle, Ventura and Kern Counties, California. Created using Environmental Systems Research Institute's ARC/INFO software, the data base consists of the following items: (1) a map coverage showing geologic contacts, faults and units, (2) a separate coverage layer showing structural data, (3) an additional point coverage which contains bedding data, (4) a point coverage containing sample localities, (5) a scanned topographic base at a scale of 1:24,000, and (6) attribute tables for geologic units (polygons), contacts (arcs), and site-specific data (points). The data base is accompanied by a readme file and this metadata file. In addition, the data set includes the following graphic and text products: (1) A jpg file (.jpg) containing a browse-graphic of the geologic map on a 1:24,000 topographic base. The map is accompanied by a marginal explanation consisting of a List of Map Units, a Correlation of Map Units, and a key to point and line symbols. (2) A .pdf file of a geologic explanation pamphlet that includes a Description of Map Units. (3) Two postScript graphic plot-files: one containing the geologic map on a 1:24,000 topographic base and the other, three accompanying structural cross sections. The geologic map database contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. The map was created by transferring lines and point data from the aerial photographs to a 1:24,000 topographic base by using a PG-2 plotter. The map was scribed, scanned, and imported into ARC/INFO, where the database was built. Within the database, geologic contacts are represented as lines (arcs), geologic units as polygons, and site-specific data as points. Polygon, arc, and point attribute tables (.pat, .aat, and .pat, respectively) uniquely identify each geologic datum and link it to other tables (.rel) that provide more detailed geologic information.

The 1990 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. Important Points about Using this Data Set: 1. The land use boundaries were 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 and irrigation method information was not collected for this survey. 5. During the transfer of data from the INTERGRAPH system to the AUTOCAD system, some attributes were lost. For those polygons that were attributed with either “D” (double cropped) or “I” (intercropped), the second crop has asterisks in the two fields “IRR_TYP2PA” (irrigated or non-irrigated) and “IRR_TYP2PB” (type of irrigation system). There should have been either and “i” or “n” in the “IRR_TYP2PA” field, and a “U” or “*” in the “IRR_TYP2PB” field. 6. Not all land use codes will be represented in the survey.