Parcels within San Joaquin County limits. Updated: 6/2025

{{description}}

Transportation Segments in San Joaquin County

{{description}}

{{description}}

This shapefile contains tax rate area (TRA) boundaries in San Joaquin County for the specified assessment roll year. Boundary alignment is based on the 2022 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 data represents a land use survey of San Joaquin County conducted by the California Department of Water Resources, North Central Region Office staff. Land use field boundaries were digitized with ArcGIS 10.5.1 using 2016 NAIP as the base, and Google Earth and Sentinel-2 imagery website were used as reference as well. Agricultural fields were delineated by following actual field boundaries instead of using the centerlines of roads to represent the field borders. Field boundaries were not drawn to represent legal parcel (ownership) boundaries and are not meant to be used as parcel boundaries. The field work for this survey was conducted from July 2017 through August 2017. Images, land use boundaries and ESRI ArcMap software were loaded onto Surface Pro tablet PCs that were used as the field data collection tools. Staff took these Surface Pro tablet into the field and virtually all agricultural fields were visited to identify the land use. Global positioning System (GPS) units connected to the laptops were used to confirm the surveyor's location with respect to the fields. Land use codes were digitized in the field using dropdown selections from defined domains. Agricultural fields the staff were unable to access were designated 'E' in the Class field for Entry Denied in accordance with the 2016 Land Use Legend. The areas designated with 'E' were also interpreted using a combination of Google Earth, Sentinel-2 Imagery website, Land IQ (LIQ) 2017 Delta Survey, and the county of San Joaquin 2017 Agriculture GIS feature class. Upon completion of the survey, a Python script was used to convert the data table into the standard land use format. ArcGIS geoprocessing tools and topology rules were used to locate errors for quality control. 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. Rural residential land use was delineated by drawing polygons to surround houses and other buildings along with some of the surrounding land. These footprint areas do not represent the entire footprint of urban land. Water source information was not collected for this land use survey. Therefore, the water source has been designated as Unknown. Before final processing, standard quality control procedures were performed jointly by staff at DWR’s North Central Region, and at DRA's headquarters office under the leadership of Muffet Wilkerson, 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 orthorectified NAIP imagery, is approximately 6 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. The 2017 San Joaquin County land use survey data was developed by the State of California, Department of Water Resources (DWR) through its Division of Regional Assistance (DRA). Land use boundaries were digitized, and land use was mapped by staff of DWR’s North Central Region using 2016 United States Department of Agriculture (USDA) National Agriculture Imagery Program (NAIP) one-meter resolution digital imagery, Sentinel-2 satellite imagery, and the Google Earth website. Land use polygons in agricultural areas were mapped in greater detail than areas of urban or native vegetation. Quality control procedures were performed jointly by staff at DWR’s DRA headquarters, and North Central Region. 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.

This shapefile contains the General Plan land use designations in the City of Tracy General Plan adopted February 1, 2011. The shapefile was created by Design, Community & Environment (DC) based on parcel data acquired from the San Joaquin County Assessor's Office that was last updated March 6, 2003. Some parcel boundary outlines have been adjusted to account for land use designation changes, as indicated below. Please note that Figure 2-2 of the General Plan, the adopted land use map, uses the original 2003 Assessor parcel boundary outlines rather than the outlines of this dataset. The attributes in this dataset are described below: FID -- a unique number assigned to each feature Shape -- a default field that indicates that the features in this dataset are polygons DCE_Acres -- a field calculated using GIS that indicates the acreage of each feature FINAL_GPLU -- General Plan Land Use designation APN -- the Assessor's parcel number for each feature LAND_VALUE -- land value according to the Assessor's Office STRUCTURE_ -- value of on-site structures according to the Assessor's Office IMPROVEMEN -- value of on-site improvements according to the Assessor's Office USECODE -- existing land use according to the Assessor's Office OWNENAME -- the name of the parcel owner according to the Assessor's Office DCE_SOI -- indicates whether a parcel is in the city limits, Sphere of Influence (SOI), Planning Area, or Area of Interest according to DC DCE_CityLi -- indicates whether a parcel is within the city limits according to DC Label -- contains labels for schools and parks DCE_School -- indicates schools DCE_Park -- indicates parks DCE_Other -- indictates certain land types (such as rights of way) CountyGPLU -- San Joaquin County General Plan land use designations ExistingLU -- existing land use according to DC (based on Assessor data and refined by DC) 1993_UMP -- General Plan land use designations of the City of Tracy's 1993 Urban Management Plan IL_Ratio -- indicates improvement-to-land ratio, a calculation of on-site improvements divided by land value GPLUChgmap -- indicates whether the General Plan land use designation for a parcel has been changed under the adopted General Plan; used for Figure 3-6 of the General Plan EIR APN_REVSD -- notes parcel boundaries that have been changed Ellis_Poly -- notes polygons created to show the General Plan land use desgination in the Ellis area that do not align with parcel boundaries. This file was edited on June 6, 2012 to change the Final_GPLU of 2 polygons in the Eastlake\Hidden Lake subdivision from Public Facilities to Residential Low per K. Matlock\Tracy DES.

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

The 1998 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. The finalized data include a shapefile covering the major agricultural and urban areas of Kern County, primarily in western Kern County (land use vector data) and JPEG files (raster data from aerial imagery). Important Points about Using this Data Set: 1. The land use boundaries were either drawn on-screen using developed photoquads, or 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 information was not collected for this survey. 5. Not all land use codes will be represented in the survey.