This point shapefile represents communities in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

Geospatial data about Yuba County, California Railways. Export to CAD, GIS, PDF, CSV and access via API.

This line shapefile represents highways in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

Geospatial data about Yuba County, California Centerlines. Export to CAD, GIS, PDF, CSV and access via API.

This polygon shapefile represents zoning designations in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

This dataset includes one file for each of the 51 counties that were collected, as well as a CA_Merged file with the parcels merged into a single file.Note – this data does not include attributes beyond the parcel ID number (PARNO) – that will be provided when available, most likely by the state of California.DownloadA 1.6 GB zipped file geodatabase is available for download - click here.DescriptionA geodatabase with parcel boundaries for 51 (out of 58) counties in the State of California. The original target was to collect data for the close of the 2013 fiscal year. As the collection progressed, it became clear that holding to that time standard was not practical. Out of expediency, the date requirement was relaxed, and the currently available dataset was collected for a majority of the counties. Most of these were distributed with minimal metadata.The table “ParcelInfo” includes the data that the data came into our possession, and our best estimate of the last time the parcel dataset was updated by the original source. Data sets listed as “Downloaded from” were downloaded from a publicly accessible web or FTP site from the county. Other data sets were provided directly to us by the county, though many of them may also be available for direct download. Â These data have been reprojected to California Albers NAD84, but have not been checked for topology, or aligned to county boundaries in any way. Tulare County’s dataset arrived with an undefined projection and was identified as being California State Plane NAD83 (US Feet) and was assigned by ICE as that projection prior to reprojection. Kings County’s dataset was delivered as individual shapefiles for each of the 50 assessor’s books maintained at the county. These were merged to a single feature class prior to importing to the database.The attribute tables were standardized and truncated to include only a PARNO (APN). The format of these fields has been left identical to the original dataset. The Data Interoperablity Extension ETL tool used in this process is included in the zip file. Where provided by the original data sources, metadata for the original data has been maintained. Please note that the attribute table structure changes were made at ICE, UC Davis, not at the original data sources.Parcel Source InformationCountyDateCollecDateCurrenNotesAlameda4/8/20142/13/2014Download from Alamenda CountyAlpine4/22/20141/26/2012Alpine County PlanningAmador5/21/20145/14/2014Amador County Transportation CommissionButte2/24/20141/6/2014Butte County Association of GovernmentsCalaveras5/13/2014Download from Calaveras County, exact date unknown, labelled 2013Contra Costa4/4/20144/4/2014Contra Costa Assessor’s OfficeDel Norte5/13/20145/8/2014Download from Del Norte CountyEl Dorado4/4/20144/3/2014El Dorado County AssessorFresno4/4/20144/4/2014Fresno County AssessorGlenn4/4/201410/13/2013Glenn County Public WorksHumboldt6/3/20144/25/2014Humbodt County AssessorImperial8/4/20147/18/2014Imperial County AssessorKern3/26/20143/16/2014Kern County AssessorKings4/21/20144/14/2014Kings CountyLake7/15/20147/19/2013Lake CountyLassen7/24/20147/24/2014Lassen CountyLos Angeles10/22/201410/9/2014Los Angeles CountyMadera7/28/2014Madera County, Date Current unclear likely 7/2014Marin5/13/20145/1/2014Marin County AssessorMendocino4/21/20143/27/2014Mendocino CountyMerced7/15/20141/16/2014Merced CountyMono4/7/20144/7/2014Mono CountyMonterey5/13/201410/31/2013Download from Monterey CountyNapa4/22/20144/22/2014Napa CountyNevada10/29/201410/26/2014Download from Nevada CountyOrange3/18/20143/18/2014Download from Orange CountyPlacer7/2/20147/2/2014Placer CountyRiverside3/17/20141/6/2014Download from Riverside CountySacramento4/2/20143/12/2014Sacramento CountySan Benito5/12/20144/30/2014San Benito CountySan Bernardino2/12/20142/12/2014Download from San Bernardino CountySan Diego4/18/20144/18/2014San Diego CountySan Francisco5/23/20145/23/2014Download from San Francisco CountySan Joaquin10/13/20147/1/2013San Joaquin County Fiscal year close dataSan Mateo2/12/20142/12/2014San Mateo CountySanta Barbara4/22/20149/17/2013Santa Barbara CountySanta Clara9/5/20143/24/2014Santa Clara County, Required a PRA requestSanta Cruz2/13/201411/13/2014Download from Santa Cruz CountyShasta4/23/20141/6/2014Download from Shasta CountySierra7/15/20141/20/2014Sierra CountySolano4/24/2014Download from Solano Couty, Boundaries appear to be from 2013Sonoma5/19/20144/3/2014Download from Sonoma CountyStanislaus4/23/20141/22/2014Download from Stanislaus CountySutter11/5/201410/14/2014Download from Sutter CountyTehama1/16/201512/9/2014Tehama CountyTrinity12/8/20141/20/2010Download from Trinity County, Note age of data 2010Tulare7/1/20146/24/2014Tulare CountyTuolumne5/13/201410/9/2013Download from Tuolumne CountyVentura11/4/20146/18/2014Download from Ventura CountyYolo11/4/20149/10/2014Download from Yolo CountyYuba11/12/201412/17/2013Download from Yuba County

Geospatial data about Yuba County, California Waterbodies. Export to CAD, GIS, PDF, CSV and access via API.

Geospatial data about Yuba County, California Parcels. Export to CAD, GIS, PDF, CSV and access via API.

This shapefile contains tax rate area (TRA) boundaries in Yuba County for the specified assessment roll year. Boundary alignment is based on the 2009 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

Geospatial data about Yuba County, California Health Clinics. Export to CAD, GIS, PDF, CSV and access via API.

This shapefile contains tax rate area (TRA) boundaries in Yuba County for the specified assessment roll year. Boundary alignment is based on the 2009 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

This line shapefile represents waterways in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

The 1995 Yuba 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 Central District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and Central 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. Not all land use codes will be represented in the survey.

This polygon shapefile represents the boundaries of the Linda Community Service District in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

Boundary Sierra Nevada Conservancy (SNC) boundary. The boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in SB 208 (2022). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Siskiyou, Tehama, Trinity, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope’s blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and up to the southern boundary of the Pit River watershed where Bear Creek Mountain Road and Dry Creek Road intersect; the southern boundary of the Pit River watershed; the western boundary of the upper Trinity watershed in the County of Trinity; on the north by the boundary of the upper Trinity watershed in the County of Trinity and the upper Sacramento, McCloud, and Pit River watersheds in the County of Siskiyou; and within the County of Modoc, the easterly boundary of the Klamath River watershed; and on the north in the County of Modoc by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 6605.5 of the Government Code, where it is defined as "region" (2) The San Joaquin River Parkway, as described in Section 32510.According to GreenInfo Network and the California Department of Fish and Game, the blue oak woodland used to define a portion of the Sierra Nevada Conservancy's western boundary was delineated using referenced vegetation and imagery data.Subregions“Subregions” means the six subregions in which the Sierra Nevada Region is located, described as follows:(1) The northwest Sierra subregion, comprising the Counties of Shasta, Siskiyou, Tehama, and Trinity.(2) The northeast Sierra subregion, comprising the Counties of Lassen, Modoc, Plumas, and Sierra.(3) The north central Sierra subregion, comprising the Counties of Butte, Nevada, Placer, and Yuba.(4) The south central Sierra subregion, comprising the Counties of Amador, Calaveras, El Dorado, and Tuolumne.(5) The southeast Sierra subregion, comprising the Counties of Alpine, Inyo, Kern, and Mono.(6) The southwest Sierra subregion, comprising the Counties of Fresno, Madera, Mariposa, and Tulare.

Every published digital survey is designated as either ‘Final’, or ‘Provisional’, depending upon its status in a peer review process. Final surveys are peer reviewed with extensive quality control methods to confirm that field attributes reflect the most detailed and specific land-use classification available, following the standard DWR Land Use Legendspecific to the survey year. Data sets are considered ‘final’ following the reconciliation of peer review comments and confirmation by the originating Regional Office. During final review, individual polygons are evaluated using a combination of aerial photointerpretation, satellite image multi-spectral data and time series analysis, comparison with other sources of land use data, and general knowledge of land use patterns at the local level.Provisional data sets have been reviewed for conformance with DWR’s published data record format, and for general agreement with other sources of land use trends. Comments based on peer review findings may not be reconciled, and no significant edits or changes are made to the original survey data.The 2005 Yuba 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 Northern District (ND). Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and ND, under the supervision of Tito Cervantes, Senior Land and Water Use Scientist. This data was developed to aid DWR’s ongoing efforts to monitor land use for the main purpose of determining current and projected water uses. 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 Standards version 2.1, dated March 9, 2016. 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. This data represents a land use survey of Butte County conducted by DWR, Northern District Office staff, under the leadership of Tito Cervantes, Senior Land and Water Use Supervisor. The field work for this survey was conducted during the summer of 2004. ND staff physically visited each delineated field, noting the crops grown at each location. Field survey boundary date was developed using: 1. The aerial photography used for this survey was taken in June of 2005. 9”x9” color photographs were generated from an altitude of about 6,000 feet above ground to produce a 1:24,000 scale photo. 2. The 9”x9” photos were taken to the field and virtually all the areas were visited to positively identify the land use. Site visits occurred July through September 2005. Land use codes were hand written on the photos. 3. Using AUTOCAD, the land use boundaries were digitized from USGS Digital Orthophoto Quarter Quadrangles (DOQQs) and attributes were entered from the field photos (using a standardized digitizing process). 4. After quality control/assurance procedures were completed on each file (DWG), the data was finalized. 5. The linework and attributes from each DWG quad file were brought into ARCINFO and both quad and survey wide coverages were created, and underwent quality checks. The survey wide coverage was then converted to a shapefile using ARCVIEW. The primary focus of this land use survey is mapping agricultural fields. Urban residences and other urban areas were delineated using aerial photo interpretation. Some urban areas may have been missed, especially in forested areas. Before final processing, standard quality control procedures were performed jointly by staff at DWR's Northern District, and at DPLA headquarters under the leadership of Jean Woods, Senior Land and Water Use Supervisor. After quality control procedures were completed, the data was finalized. The positional accuracy of the digital line work, which is based upon the 9' x 9' color photos, is approximately 23 meters. The land use attribute accuracy for agricultural fields is high, because almost every delineated field was visited by a surveyor. The accuracy is 95 percent because some errors may have occurred. Possible sources of attribute errors are: a) Human error in the identification of crop types, b) Data entry errors.

This polygon shapefile represents Board of Supervisors districts in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

Description for i03_DAU_county_cnty2018 is as follows:Detailed Analysis Unit-(DAU) Convergence via County Boundary cnty18_1 for Cal-Fire, (See metadata for CAL-FIRE cnty18_1), State of California.The existing DAU boundaries were aligned with cnty18_1 feature class.Originally a collaboration by Department of Water Resources, Region Office personnel, Michael L. Serna, NRO, Jason Harbaugh - NCRO, Cynthia Moffett - SCRO and Robert Fastenau - SRO with the final merge of all data into a cohesive feature class to create i03_DAU_COUNTY_cnty24k09 alignment which has been updated to create i03_DAU_COUNTY_cnty18_1.This version was derived from a preexisting “dau_v2_105, 27, i03_DAU_COUNTY_cnty24k09” Detailed Analysis Unit feature class's and aligned with Cal-Fire's 2018 boundary.Manmade structures such as piers and breakers, small islands and coastal rocks have been removed from this version. Inlets waters are listed on the coast only.These features are reachable by County\DAU. This allows the county boundaries, the DAU boundaries and the State of California Boundary to match Cal-Fire cnty18_1.DAU BackgroundThe first investigation of California's water resources began in 1873 when President Ulysses S. Grant commissioned an investigation by Colonel B. S. Alexander of the U.S. Army Corps of Engineers. The state followed with its own study in 1878 when the State Engineer's office was created and filled by William Hammond Hall. The concept of a statewide water development project was first raised in 1919 by Lt. Robert B. Marshall of the U.S. Geological Survey.In 1931, State Engineer Edward Hyatt introduced a report identifying the facilities required and the economic means to accomplish a north-to-south water transfer. Called the "State Water Plan", the report took nine years to prepare. To implement the plan, the Legislature passed the Central Valley Act of 1933, which authorized the project. Due to lack of funds, the federal government took over the CVP as a public works project to provide jobs and its construction began in 1935.In 1945, the California Legislature authorized an investigation of statewide water resources and in 1947, the California Legislature requested that an investigation be conducted of the water resources as well as present and future water needs for all hydrologic regions in the State. Accordingly, DWR and its predecessor agencies began to collect the urban and agricultural land use and water use data that serve as the basis for the computations of current and projected water uses.The work, conducted by the Division of Water Resources (DWR’s predecessor) under the Department of Public Works, led to the publication of three important bulletins: Bulletin 1 (1951), "Water Resources of California," a collection of data on precipitation, unimpaired stream flows, flood flows and frequency, and water quality statewide; Bulletin 2 (1955), "Water Utilization and Requirements of California," estimates of water uses and forecasts of "ultimate" water needs; and Bulletin 3 (1957), "The California Water Plan," plans for full practical development of California’s water resources, both by local projects and a major State project to meet the State's ultimate needs. (See brief addendum below* “The Development of Boundaries for Hydrologic Studies for the Sacramento Valley Region”)DWR subdivided California into study areas for planning purposes. The largest study areas are the ten hydrologic regions (HR), corresponding to the State’s major drainage basins. The next levels of delineation are the Planning Areas (PA), which in turn are composed of multiple detailed analysis units (DAU). The DAUs are often split by county boundaries, so are the smallest study areas used by DWR.The DAU/counties are used for estimating water demand by agricultural crops and other surfaces for water resources planning. Under current guidelines, each DAU/County has multiple crop and land-use categories. Many planning studies begin at the DAU or PA level, and the results are aggregated into hydrologic regions for presentation.Since 1950 DWR has conducted over 250 land use surveys of all or parts of California's 58 counties. Early land use surveys were recorded on paper maps of USGS 7.5' quadrangles. In 1986, DWR began to develop georeferenced digital maps of land use survey data, which are available for download. Long term goals for this program is to survey land use more frequently and efficiently using satellite imagery, high elevation digital imagery, local sources of data, and remote sensing in conjunction with field surveys.There are currently 58 counties and 278 DAUs in California.Due to some DAUs being split by county lines, the total number of DAU’s identifiable via DAU by County is 782.**ADDENDUM**The Development of Boundaries for Hydrologic Studies for the Sacramento Valley Region[Detailed Analysis Units made up of a grouping of the Depletion Study Drainage Areas (DSA) boundaries occurred on the Eastern Foothills and Mountains within the Sacramento Region. Other DSA’s were divided into two or more DAU’s; for example, DSA 58 (Redding Basin) was divided into 3 DAU’s; 143,141, and 145. Mountain areas on both the east and west side of the Sacramento River below Shasta Dam went from ridge top to ridge top, or topographic highs. If available, boundaries were set adjacent to stream gages located at the low point of rivers and major creek drainages.Later, as the DAU’s were developed, some of the smaller watershed DSA boundaries in the foothill and mountain areas were grouped. The Pit River DSA was split so water use in the larger valleys (Alturas area, Big Valley, Fall River Valley, Hat Creek) could be analyzed. A change in the boundary of the Sacramento Region mountain area occurred at this time when Goose Lake near the Oregon State Line was included as part of the Sacramento Region.The Sacramento Valley Floor hydrologic boundary was at the edge of the alluvial soils and slightly modified to follow the water bearing sediments to a depth of 200 feet or more. Stream gages were located on incoming streams and used as an exception to the alluvial soil boundary. Another exception to the alluvial boundary was the inclusion of the foothills between Red Bluff and the Redding Basin. Modifications of the valley floor exterior boundary were made to facilitate analysis; some areas at the northern end of the valley followed section lines or other established boundaries.Valley floor boundaries, as originally shown in Bulletin 2, Water Utilization and Requirements of California, 1955 were based on physical topographic features such as ridges even if they only rise a few feet between basins and/or drainage areas. A few boundaries were based on drainage canals. The Joint DWR-USBR Depletion Study Drainage Areas (DSA) used drainage areas where topographic highs drained into one drainage basin. Some areas were difficult to study, particularly in areas transected by major rivers. Depletion Study Drainage Areas containing large rivers were separated into two DAU’s; one on each side of the river. This made it easier to analyze water source, water supply, and water use and drainage outflow from the DAU.Many of the DAUs that consist of natural drainage basins have stream gages located at outfall gates, which provided an accurate estimate of water leaving the unit. Detailed Analysis Units based on political boundaries or other criteria are much more difficult to analyze than those units that follow natural drainage basins.]**END ADDENDUM**.............................................................................................................................................cnty18_1 metadata Summary:(*See metadata for CAL-FIRE cnty18_1). CAL-FIRE cnty18_1 boundary feature class is used for cartographic purposes, for generating statistical 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.cnty18_1 metadata Description:(*See metadata for CAL-FIRE cnty18_1).cnty18_1 metadata Credits:CAL-FIRE cnty18_1 metadata comment:This specific dataset represents the full detailed county dataset with all coding (islands, inlets, constructed features, etc.). The user has the freedom to use this coding to create definition queries, symbolize, or dissolve to create a more generalized dataset as needed.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 difference between the 15_1 and 14_1 versions of this dataset.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 difference between the 18_1 and 15_1 versions of this dataset.(*See metadata for CAL-FIRE cnty18_1). - U.S. Bureau of Reclamation, California Department of Conservation, California Department of Fish and Game, California Department of Forestry and Fire protection

This polygon shapefile represents areas in the General Plan for Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.

This point shapefile represents bridges in Yuba County, California. This layer is a part of a collection of data obtained from the Yuba County GIS data catalog. Last Updated 5/13/2019.