View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
ArcGIS Earth
ArcGIS Pro
Service Description: This feature class is used for cartographic purposes, for generating staistical data, and for clipping data. Ideally, state and federal agencies should be using the same framework data for common themes such as county boundaries. This layer provides an initial offering as "best available" at 1:24,000 scale.
Map Name: Layers
Legend
All Layers and Tables
Dynamic Legend
Dynamic All Layers
Layers:
Description:
Service Item Id: 9f4ee131afb44cda8041f8bf60270557
Copyright Text: U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire Protection, National Oceanic and Atmospheric Administration
Spatial Reference:
102100
(3857)
Single Fused Map Cache: false
Initial Extent:
XMin: -1.4039921211048333E7
YMin: 4142565.8163839383
XMax: -1.2514292844351666E7
YMax: 5379328.041087017
Spatial Reference: 102100
(3857)
Full Extent:
XMin: -1.38492322818E7
YMin: 3833650.4456999972
XMax: -1.27049817736E7
YMax: 5162403.2491
Spatial Reference: 102100
(3857)
Units: esriMeters
Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP
Document Info:
Title: California County Boundaries
Author:
Comments: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>***** BACKGROUND *****</SPAN></SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN><SPAN>A dataset named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 dataset was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the dataset to county24k. </SPAN></SPAN></P><P><SPAN><SPAN>In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has was renamed cnty24k09_1. </SPAN></SPAN></P><P><SPAN><SPAN>***** THIS VERSION*****</SPAN></SPAN></P><P><SPAN><SPAN>This version of the county dataset was created as a result of an effort to improve the coastal linework. It uses the previous interior linework from the cnty24k13_1 data, but replaces the coastal linework (including islands and inlets) based on NOAA's ERMA coastal dataset (which used NAIP 2010). In addition to the improved linework, additional coding was added to differentiate inlets and bays, islands, and manmade structures such as piers and breakers. Note that some of this coding may not be featured in this specific dataset.</SPAN></SPAN></P><P><SPAN><SPAN>This dataset is one of several available datasets that were created as a group designed to work in topological sync with each other. These "paired" datasets include a full county dataset (cnty18_1_full), a basic state dataset (state18_1), an ocean dataset (ocean18_1), and country/state datasets (both full and neighbor-only - cntrystate18_1_full and cntrystate18_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. </SPAN></SPAN></P><P><SPAN><SPAN>This specific dataset represents the basic (ie simplified) county dataset without the extra coding that can be found in the "full" dataset. 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 dataset is the same as the cnty18_1_basic, except for the addition of the Channel Islands. </SPAN></SPAN></P><P><SPAN><SPAN>In November 2015, the dataset was adjusted to include a change in the Yuba-Placer county boundary from 2010 that was not yet included in the 14_1 version of the dataset (ord No 5546-B). This change constitutes the diffrence between the 18_1 and 15_1 versions of this dataset.</SPAN></SPAN></P><P><SPAN><SPAN>In March 2018, the dataset was adjusted to include a legal boundary change between Santa Clara and Santa Cruz Counties (December 11, 1998) as stated in Resolution No. 98-11 (Santa Clara) and Resolution No. 432-98 (Santa Cruz). This change constitutes the diffrence between the 18_1 and 15_1 versions of this dataset.</SPAN></SPAN></P></DIV></DIV></DIV>
Subject: This feature class is used for cartographic purposes, for generating staistical data, and for clipping data. Ideally, state and federal agencies should be using the same framework data for common themes such as county boundaries. This layer provides an initial offering as "best available" at 1:24,000 scale.
Category:
Keywords: government,county boundaries,county boundary,county line,county,counties,boundary,border,borders,boundaries,location
AntialiasingMode: None
TextAntialiasingMode: Force
Supports Dynamic Layers: true
Resampling: false
MaxRecordCount: 1000
MaxImageHeight: 4096
MaxImageWidth: 4096
Supported Query Formats: JSON, geoJSON, PBF
Supports Query Data Elements: true
Min Scale: 0
Max Scale: 0
Supports Datum Transformation: true
Child Resources:
Info
Dynamic Layer
Supported Operations:
Export Map
Identify
QueryLegends
QueryDomains
Find
Return Updates