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...
)
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...
)
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
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.