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

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 Santa Clara County Planning Office is part of the Department of Planning and Development. Their primary function is to plan and regulate land use and development within the unincorporated portions of Santa Clara County. Other responsibilities include policy analysis, GIS services, research and technical assistance relating to land use, housing, environmental protection, historic preservation and demographics. The Geographic Information Services Department has taken on all those activities related to GIS data and GIS process and procedures that cross organizational boundaries. Santa Clara County encompasses 15 cities and approximately 1.7 million 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.

Linear referencing route system on major creeks in Santa Clara County.

Land-Use Data Quality ControlEvery 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 2014 Santa Clara County land use survey data was developed by the State of California, Department of Water Resources (DWR) through its Division of Integrated Regional Water Management (DIRWM) and Division of Statewide Integrated Water Management (DSIWM). Land use boundaries were digitized and land use data were gathered by staff of DWR’s North Central Region using extensive field visits and aerial photography. 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 DSIWM headquarters, under the leadership of Jean Woods, and North Central Region, under the supervision of Kim Rosmaier. 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 Santa Clara County conducted by the California Department of Water Resources, North Central Regional Office staff. Land use field boundaries were digitized with ArcGIS 10.3 using 2012 U.S.D.A National Agriculture Imagery Program (NAIP) one-meter imagery as the base. Agricultural fields were delineated by following actual field boundaries instead of using the centerlines of roads to represent the field borders. Field boundaries were reviewed and updated using 2014 Landsat 8 imagery and 2014 U.S.D.A National Agriculture Imagery Program (NAIP) one-meter imagery after it became available in late 2014. The county boundary is based on the CalFire updated State and County boundary layer dated 2009. 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 June 16, 2014 through July 24, 2014. Images, land use boundaries and ESRI ArcMap software were loaded onto laptop computers that were used as the field data collection tools. Staff took these laptops 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. 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. Sources of irrigation water were not identified for most areas. The exception is the area of the Corde Valle Golf Course near San Martin and a few nearby fields where recycled water is used as a water source in addition to groundwater. Before final processing, standard quality control procedures were performed jointly by staff at DWR’s North Central Region, and at DSIWM 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 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.

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

Polygon Layer showing FEMA Flood Zones in Santa Clara County

This polygon shapefile represents land use and land cover for the Pajaro River and San Benito River Watershed in San Benito, Santa Clara, and Santa Cruz counties of California for 2005. This shapefile was extracted from a generalized land use/land cover database of the Salinas-Pajaro region. Map unit categories were based on a modified Anderson Level II hierarchy. Mapping generally adhered to a 0.5 acre Minimum Mapping Unit (MMU) for riparian and agriculture types and 1 acre MMU for all upland, urban, or other land use types. Vegetation percent cover classes were assigned to the tree and shrub layers for each stand. Herbaceous vegetation was not assigned a cover class. All density values are measured in absolute cover, not relative cover. If tree cover is equal to or greater than 40% then the shrub cover is assigned a Not Assessed value of 9. The minimum mapping unit (MMU) resolution size of the land use/land cover polygons is twofold. In the intense agricultural region and for wetland and riparian areas the polygons have a 0.5 acre MMU. In the remainder of the study area, composed of non-agricultural areas, upland vegetation, and urban areas, the MMU is 1 acre. For thin linear-shaped polygons the MMU for width is one half the width of a full MMU square. Exceptions to the MMU guidance are noted in further criteria below. Because of the agricultural emphasis of the project, large urban developed areas, such as cities, towns, and villages, were not typically further subdivided other than for agricultural uses within their extents. The MMU size for these agricultural uses within urban areas is 0.5 acres. As noted above, the study area overlaps with the 2005 mapping of the Salinas River and San Benito river major riparian corridors that Aerial Information Systems, Inc. conducted for the Nature Conservancy. The MMU for the original projects was <0.5 acres. Where those units had not changed for 2005 and 2012 mapping, the map units were kept at the original polygon size. The 0.5 acre MMU is used for new mapping of riparian and wetland map units. Other Mapping Criteria includes photo interpretation of land cover is based on state-wide criteria for vegetation mapping.

Building Footprint is a Polygon FeatureClass representing the building footprints for the City of Cupertino, California. The mapped geographic area includes 11.3 square miles of western Santa Clara County in California. The building footprints data layer was originally based on aerial photographs from 2011. Continual updates are made as needed. Most updates come from digitized plat/plan approvals or from completed City project plans. Mapping accuracy meets National Map Accuracy Standards for +/-2.5 US feet. Spatial coordinate system is California State Plane West, zone III Fipszone 0403 Adszone 3326, NAD83. Scale of true display is 1:1200 (100' scale). Building Footprints has the following fields: OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

LEVEL_DESC: A general description of what type of structure the polygon represents type: String, length: 18, domain: none

BLDG_HIGH: The height of the highest point on the polygon - feet above sea level type: String, length: 50, domain: none

BLDG_LOW: The height of the lowest point on the polygon - feet above see level type: String, length: 50, domain: none

FloorNumbe: The number of floors the building has type: Integer, length: 4, domain: none

AssetID: Cupertino maintained GIS primary key type: String, length: 50, domain: none

Year_Built: The year the building was built type: Date, length: 8, domain: none

Bldg_Age: The age of the building type: Single, length: 4, domain: none

LegacyID: Old identifiers used to track asset migration type: Integer, length: 4, domain: none

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

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: noneShape.STArea():The area of the building footprinttype: double, length: none, domain: none Shape.STLength(): The length of the perimeter of the building footprinttype: double, length: none, domain: none BLDG_HEIGHT: The height of the building, calculated by subtracting the highest and lowest points type: double, length: none, domain: none

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

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

Saw someone carrying gun, knife, or other weapon on school property in the past 12 months by sex, race/ethnicity, and grade, California Healthy Kids Survey, 2015-16METADATA:Notes (String): Lists table title, sourceYear (String): Year of surveyCategory (String): Lists the category representing the data: Santa Clara County is for total surveyed population, sex: Male and Female, race/ethnicity: African American, Asian/Pacific Islander, Latino and White (non-Hispanic White only) and grade level (7th, 9th, 11th, or non-traditional).Percent (Numeric): Percentage of middle and high school students who saw someone carrying gun, knife, or other weapon on school property in the past 12 months

Contour2006 is a Polyline Shapefile of contours generated from LiDAR data for the San Jose Phase 3 project of Santa Clara County, Ca. The purpose of the bare-earth LiDAR Point and Breakline data is to provide ground surface data and one-foot (Valley Area) and five-foot (Mountain Areas) contour generation, and the delineation of watercourse ( Top of Bank ). LAS format files, raw LiDAR data in its native format, classified bare-earth LiDAR DEM and photogrammetrically derived breaklines generated from LiDAR Intensity stereo-pairs. Breakline, Top of Bank, and contour files in ESRI personal geodatabase format, Microstation V8 .dgn format, and AutoCAD 2004 formats for the San Jose Phase 3 project of Santa Clara County, Ca. It is primarily used to model elevation and as a reference layer. Contour2006 has the following fields:

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

TYPE: The type of contour line type: String, length: 25, domain: none

ELEVATION: The elevation of the contour line - in feet type: Double, length: 8, domain: none

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

TILE_ID: The unique ID associated with the tile type: String, length: 9, domain: none

ObjectID: Unique identifier automatically generated by Esri type: Integer, length: 4, domain: none

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

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

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.