The Geographic Information Systems (GIS) Unit falls under the purview of the County of Santa Cruz Information Services Department. The GIS Unit serves all County departments and external customers and provides data on land, features and people of Santa Cruz County. Santa Cruz County encompasses 4 cities and approximately 265,000 people. This coverage can be used for basic applications such as viewing, querying and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.

The Geographic Information Systems (GIS) Unit falls under the purview of the County of Santa Cruz Information Services Department. The GIS Unit serves all County departments and external customers and provides data on land, features and people of Santa Cruz County. Santa Cruz County encompasses 4 cities and approximately 265,000 people. This coverage can be used for basic applications such as viewing, querying and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.

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

Parcel Map Index is a Polygon FeatureClass showing approximate boundaries of Parcel Map recorded at Santa Clara County Clerk Recorders Office. Records are indexed by City assigned Parcel Map number. It is primarily used as a reference layer. The layer is updated as needed by the GIS Division. Parcel Map Index has the following fields:

OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

Parcel: The Assessor's Parcel Number type: String, length: 7, domain: none

created_date: The date the database row was initially created type: Date, length: 8, domain: none

last_edited_date: The date the database row was last updated type: Date, length: 8, domain: none

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

BookPage:

type: String, length: 50, domain: none

Shape.STArea():

The area of the shape - in square feet type: Double, length: 0, domain: none

Shape.STLength():

The length of the shape - in feet type: Double, length: 0, domain: none

This layer was created as an update the existing San Jose Parks Layer (PRK.PARKS). The existing layer has been maintained by the City of San Jose Department of Public Works and had not been updated in some time. This layer is a draft as of (05.02.2014) and has not been fully reviewed to assure complete accuracy of boundaries. Nevertheless it is an improvement over the existing layer and has had park boundaries adjusted to reflect PRNS management authority to the curb and gutter. This layer is also primarily based upon satellite imagery and visible property lines with the Santa Clara County parcel layer used as a guide in certain circumstances where boundaries could not be identified. The PRK.PARKS layer on the other hand , appeared to be based upon the Santa Clara Parcel layer, which did not include sidewalk and curb areas of the parks. In addition many parcel maps features included sections of roadway or overlapped into neighboring properties when compared with the aerial. Park chains have yet to be reviewed and revised. It is our intent to adjust these features to show only secured or quasi-government lands in which development in unlikely to occur. In addition, park chain lands may be adjusted to reflect underpasses where trails and public access is permitted.

© City of San Jose

Parcels is a Polygon FeatureClass representing land parcels around the City of Cupertino. Coverage includes the following subclasses: parcel polygon, parcel arcs, apn, address, street name inside of rights-of-way, street name outside of rights-of-way It is primarily used as a reference layer. The layer is reconciled with Santa Clara County Land Parcel data annually around Aug (downloaded from https://www.sccgov.org/sites/gis/GISData/Pages/Available-GIS-Data.aspx). Parcels has the following fields:

OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

APN_SPACE: The Assessor's Parcel Number type: String, length: 12, domain: none

CITY: The city in which the parcel is located type: String, length: 10, domain: none

COMMENTS: Any relevant comments relating to the feature type: String, length: 60, domain: none

UpdateDate: The date the database row was last updated type: Date, length: 8, domain: none

CreateDate: The date the database row was initially created type: Date, length: 8, domain: none DataSource

The methodology used to digitize the data type: string, length: 100, domain: DataSource

domain values:['Approximated Historical Source', 'Cogo from Plans', 'Digitized Landbase as Reference', 'Digitized Ortho as Reference', 'Digitized Plan as Reference', 'GPS SubMeter', 'GPS SubFoot', "iStreetView', 'Need Verification', 'Unknown Source', 'Legacy WO System', 'Field Verified']

X: The X coordinate of the parcel type: Double, length: 8, domain: none

Y: The Y coordinate of the parcel type: Double, length: 8, domain: none

UseCode: The land use code associated with the parcel type: SmallInteger, length: 2, domain: LandUseCodes

IsLeased: Field indicating whether the parcel is leased type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: nonehasADUField that denotes if the property has an associated accessory dwelling unit type: String, length: 3, domain: shdBooleanYesNodomain values:['Yes', 'No']

FlagLot:

type: String, length: 255, domain: shdBooleanYesNo domain values:['Yes', 'No']hasResidential:Field indicating whether the parcel is residentialtype: String, length: 3, domain: shdBooleanYesNodomain values:['Yes', 'No'] Shape.STArea():

The area of the shape - in square feet type: Double, length: 0, domain: none

Shape.STLength():

The length of the shape - in feet type: Double, length: 0, domain: none