Description: ***** BACKGROUND *****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 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. 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. ***** THIS VERSION*****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.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 (cnty15_1_full), a basic state dataset (state15_1), an ocean dataset (ocean15_1), and country/state datasets (both full and neighbor-only - cntrystate15_1_full and cntrystate15_1_neighbor, respectively). Further details about these paired datasets can be found in their respective metadata. 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. 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 15_1 and 14_1 versions of this dataset.
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
Description: This feature class contains data about the centerline of an embankment for controlling the waters of the sea, river, or other water bodies. This dataset has been developed to establish a levee database for all levees and levee systems in the State of California, in support of the Department of Water Resources floodplain mapping program for the State.
BANK_D
(
type: esriFieldTypeString, alias: Area Bankside Code, length: 25
, Coded Values:
[Non Riverine: Location other than river system (lake, ocean, or other water body)]
, [Left Descending: Left descending bank]
, [Right Descending: Right descending bank]
)
COORDINATE_METHOD_D
(
type: esriFieldTypeString, alias: Coordinate Capture Method, length: 40
, Coded Values:
[Digitized off of quad sheets: Digitized off of quad sheets]
, [Other: Other]
, [Using photogrammetric techniques: Using photogrammetric techniques]
, ...9 more...
)
Description: This feature class contains data about the centerline of an embankment for controlling the waters of the sea, river, or other water bodies. This dataset has been developed to establish a levee database for all levees and levee systems in the State of California, in support of the Department of Water Resources floodplain mapping program for the State.
BANK_D
(
type: esriFieldTypeString, alias: Area Bankside Code, length: 25
, Coded Values:
[Non Riverine: Location other than river system (lake, ocean, or other water body)]
, [Left Descending: Left descending bank]
, [Right Descending: Right descending bank]
)
COORDINATE_METHOD_D
(
type: esriFieldTypeString, alias: Coordinate Capture Method, length: 40
, Coded Values:
[Digitized off of quad sheets: Digitized off of quad sheets]
, [Other: Other]
, [Using photogrammetric techniques: Using photogrammetric techniques]
, ...9 more...
)
Description: the following data types are excluded from this shapefile:
CanalDitch (Ftype = 336)
Pipeline (Ftype = 428)
Coastline (Ftype = 566)
This is also the "Medium" definition coverage
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Awareness floodplains identify the 100-year flood hazard areas using approximate assessment procedures. These floodplains will be shown simply as flood prone areas without specific depths and other flood hazard data. Data provided by DWR
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: The Regulated Streams dataset was compiled from the High Resolution National Hydrography Dataset for California. The reaches included are based on Table 8.1 - Regulated Streams and Nonpermissible Work Periods found in Barclays California Code of Regulations. The High Resolution NHD is based on 1:24,000 topographic mapping. The start and endpoints of the Regulated Streams have been detemined, where possible, by the descriptions found in Table 8.1. Those reaches lacking specifically defined start and endpoints in Table 8.1 have been included in their entirety within each county specified in the "County-Limits" column of Table 8.1. All reaches described in this table were found in the NHD except for Globe Slough and Five-Mile Slough in Fresno County, Hughes Creek in Kings County, Moody Slough in Solano County, and Mud Slough Creek in Butte County. Additionally, the linework in this dataset representing Colusa Bypass and Moulton Bypass and Weir in Colusa County were not found in the NHD. These lines have been digitized from the lines on the 7.5' USGS topographic quadrangles. The linework representing Ida Island in Sacramento County was derived from gaps in the NHD polygon feature class representing Sacramento River in the vicinity of the island. The linework representing Yolo Bypass in Yolo and Solano counties is comprised of the High Resolution NHD polyline features contained within the California Levee Database (DFM_CALeveeDatabase_v22_R2_20110128_93.mdb) levee centerlines that define the boundaries of Yolo Bypass. The linework representing Sutter Bypass in Sutter County is also comprised of the NHD polyline features within the CLD levee centerlines that define the boundaries of Sutter Bypass. The linework representing Atherton Cove (northeast bank) in San Joaquin County is a segment of the levee centerline from the CLD.The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.
Description: The Designated Floodways in this dataset are derived from the Designated Floodway Maps on the CVFPB ftp site. The scanned Designated Floodway Maps are available as .tifs on the ftp site. These scanned images were georectified using reference points, when available, that matched reference points on the current Bing aerial imagery service. Due to the resolution and quality of the scanned images, the lack of orthorectified base imagery on the scans, and/or changed ground conditions, many of the Designated Floodway maps are not able to be reconciled precisely with current ground conditions. Therefore the boundaries represented in this feature class represent the closest approximation possible of the Designated Floodways drawn on the scanned Designated Floodway Maps. There are instances where levee centerlines in the California Levee Database (DFM_CALeveeDatabase_v22_R2_20110128_93.mdb) are coincident with the designated floodways drawn on the scanned images. In these cases the surveyed levee centerlines in the CLD were used to determine the respective boundaries of the designated floodways. There are surveyed levee centerlines in the database that diverge from the designated floodway boundaries drawn on the scanned images; these surveyed lines were not used and the lines on the scanned images were digitized to represent the designated floodway boundaries. Additionally, there are levee centerlines in the CLD that were created using other methods including heads-up digitizing. These lines may or may not have been incorporated into the designated floodway feature class depending on their accuracy and proximity to the designated floodway lines drawn on the scanned images. The Notes field indicates designated floodways that incorporate portions of the CLD levee centerlines into this feature class.There are instances where the scanned images could not be precisely reconciled with current ground conditions but the designated floodways appear to be coincident with features visible on the current aerial imagery such as roads or levees that likely define the floodways. In these instances the designated floodways have been digitized while referencing the feature apparent on the aerial in conjunction with the designated floodway on the scanned image rather than directly from the scanned image.Sheets S43-S46 were not found for the Tuolumne River, Mitchell Road to Whitmore Road reach in Stanislaus County. The designated floodway has been approximated in this area based on the the western terminus of this reach on the preceding sheets, the eastern terminus of the San Joaquin River to extension of Whitmore Road reach, and the current Bing aerial imagery service.The scanned images for Cottonwood Creek in Tulare County from Cross Creek to Grapevine Creek included A and B zones; these have both been included in the digitized designated floodway feature class. The scanned images for Mokelumne River in San Joaquin and Sacramento counties included portions of the 100 year floodzone estimated boundary outside of the designated floodway boundaries; these have been included in the designated floodway feature class and noted as such. No sheets were found for the Yuba River in Yuba County on the CVFPB ftp site other than an index sheet. The designated floodway for this reach has been digitized from the index sheet and incorporates surveyed levee centerlines from the CLD as its outermost boundaries. The index also includes Areas A, B and C within the outermost boundaries; these areas in the feature class are based on the designated floodway lines drawn on the scanned index. Attribute information for this dataset is from the Designated Floodway Program.