This data identifies current as well as proposed zoning and land use designations that are adopted by ordinances for unincorporated Pierce County. Zoning for cities is not included in this dataset. Zones are adopted by ordinances with specific technicalities for each community. Land Use designations offer a broad spectrum of allowable uses within a community. It is used to create a Comprehensive Plan Map or used for a Generalized Proposed Land Use Map or GPLUM. This dataset is also used to create the Land Use Designations theme, which covers proposed zoning use. The meaning of proposed is that the property might not be currently used for the purpose stated. It should be noted that Council adopted amendments to land use designations/zoning that will be effective at the beginning of 2006. Also, the Council is in the process of adopting the Mid-County Community Plan which amends land use designations/zoning as well. The Cities polygons found in the zoning data does not necessarily match the current cities boundaries. This is because the zoning data is updated once a year per the "Pierce County Comprehensive Plan" and does not allow for changes to be made during the year. The Comprehensive Plan is generally updated in November and generally becomes effective the following March. Use the "Cities in Pierce County" data set to determine current city boundaries. City boundaries can change more often than the current adopted Pierce County Zoning data. The zoning data contains the "Cities in Pierce County" boundaries at the time that the Pierce County Zoning was adopted. When determining the current zoning of a parcel near a city, the current "Cities in Pierce County" data set needs to be reviewed. Zoning codes for parcels within incorporated cities are determined by the city that the parcel is within. Please read metadata for additional information (https://matterhorn.piercecountywa.gov/GISmetadata/pdbplan_zoning.html). Any use or data download constitutes acceptance of the Terms of Use (https://matterhorn.piercecountywa.gov/disclaimer/PierceCountyGISDataTermsofUse.pdf).

Data is refreshed Jan, Mar, May, Jul, Sep, Nov. To determine the last date edited, refer to the Date_Changed/GIS_Edit_Date fields for each individual layer. To see the latest refresh date, refer to the Item updated date noted in the AGO Item Description page.Property information attributes in parcel polygons are refreshed monthly.To download the full Cadastral Dataset for Milwaukee County click here * Note: download will begin when link is clicked*Other Property Information related layers:Milwaukee County Parcels with Property InformationMilwaukee County Owned ParcelsMilwaukee County Cadastral DatasetMilwaukee County Tax Exempt Parcels

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

Parcel Viewer makes searching for King County parcel information easy. You can search by address, search by parcel number, or you can just zoom in on the map and click on a parcel. Once a parcel is selected, you will get direct links to the King County Assessor’s eReal Property report and the Districts and Development Conditions report.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Download In State Plane Projection Here. Boundaries of designated high quality ADID wetlands established as a result of a formal process under the direction of the U.S. Environmental Protection Agency. Part 404(b)(1) of the Clean Water Act authorizes the USEPA and the US Army Corps of Engineers to identify in advance of specific permit requests aquatic sites which will be considered as areas generally unsuitable for disposal of dredged or fill material. This process is called an Advanced Identification or ADID. Under the ADID process identification of an area as generally unsuitable for fill does not prohibit applications for permits to fill in these areas. Therefore the ADID designation of unsuitability is advisory not regulatory. An ADID designation lets a potential applicant know in advance that a proposal to fill such a site is not likely to be consistent with the 404(b)(1) guidelines, and the USEPA will probably request permit denial. ADID wetland information is also useful in watershed planning, land use planning, public land acquisition programs, natural resource studies and other purposes. The wetland selection criteria and methodology are documented in the publication entitled "Advanced Identification (ADID) Study, Lake County, Illinois. Final Report, November 1992" which is included in this download. Boundaries were delineated by the ADID project team on orthophotograph background with an intended usage scale of 1" = 400', a scale ratio of 1:4800.

This ownership dataset utilizes a methodology that results in a federal ownership extent that matches the Federal Responsibility Areas (FRA) footprint from CAL FIRE's State Responsibility Areas for Fire Protection (SRA) data. FRA lands are snapped to county parcel data, thus federal ownership areas will also be snapped. Since SRA Fees were first implemented in 2011, CAL FIRE has devoted significant resources to improve the quality of SRA data. This includes comparing SRA data to data from other federal, state, and local agencies, an annual comparison to county assessor roll files, and a formal SRA review process that includes input from CAL FIRE Units. As a result, FRA lands provide a solid basis as the footprint for federal lands in California (except in the southeastern desert area). The methodology for federal lands involves:

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributedGIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

This map service provides information about properties and parcel boundaries in the County of Los Angeles. The Office of the Assessor (click here for their website) maintains assessment records of real and personal property in the County of Los Angeles, as well as a GIS Tax Parcel Base Map. The Assessor has recently changed its policies and will be releasing a number of datasets publicly over time. They will be available here, as well as on the County’s Open Data Portal (click here to learn more). To access the Property Assessment Information System, where you can search for properties and see maps and imagery, go to the PAIS website.Do not download this parcel map service as a shapefile - you will get an error. To download a zipped file geodatabase, go to this Hub item: https://egis-lacounty.hub.arcgis.com/datasets/parcelsAll inquiries should be directed to the Mapping & GIS Services Section, LA County Office of the Assessor at gisinfo@assessor.lacounty.gov

To access the tax lot layer you will need to contact the county Assessor's office. ORMAP is a statewide digital cadastral base map that is publicly accessible, continually maintained, supports the Oregon property tax system, supports a multi-purpose land information system, strives to comply with appropriate state and national standards, and will continue to be improved over time.

The Hydrology Feature Dataset contains photogrammetrically compiled water drainage features and structures including rivers, streams, drainage canals, locks, dams, lakes, ponds, reservoirs and mooring cells. Rivers, Lakes, Ponds, Reservoirs, Hidden Lakes, Reservoirs or Ponds: If greater than 25 feet and less than 30 feet wide, is captured as a double line stream. If greater than 30 feet wide it is captured as a river. Lakes are large standing bodies of water greater than 5 acres in size. Ponds are large standing bodies of water greater than 1 acre and less than 5 acres in size. Polygons are created from Stream edges and River Edges. The Ohio River, Monongahela River and Allegheny River are coded as Major Rivers. All other River and Stream polygons are coded as River. If a stream is less than 25 feet wide it is placed as a single line and coded as a Stream. Both sides of the stream are digitized and coded as a Stream for Streams whose width is greater than 25 feet. River edges are digitized and coded as River.

A Drainage Canal is a manmade or channelized hydrographic feature. Drainage Canals are differentiated from streams in that drainage canals have had the sides and/or bottom stabilized to prevent erosion for the predominant length of the feature. Streams may have had some stabilization done, but are primarily in a natural state. Lakes are large standing bodies of water greater than five acres in size. Ponds are large standing bodies of water greater than one acre in size and less than five acres in size. Reservoirs are manmade embankments of water. Included in this definition are both covered and uncovered water tanks. Reservoirs that are greater than one acre in size are digitized. Hidden Streams, Hidden Rivers and Hidden Drainage Canal or Culverts are those areas of drainage where the water flows through a manmade facility such as a culvert. Hydrology Annotation is not being updated but will be preserved. If a drainage feature has been removed, as apparent on the aerial photography, the associated drainage name annotation will be removed. A Mooring Cell is a structure to which tows can tie off while awaiting lockage. They are normally constructed of concrete and steel and are anchored to the river bottom by means of gravity or sheet piling.

Mooring Cells do not currently exist in the Allegheny County dataset but will be added. Locks are devices that are used to control flow or access to a hydrologic feature. The edges of the Lock are captured. Dams are devices that are used to hold or delay the natural flow of water. The edges of the Dam are shown.

This dataset is harvested on a weekly basis from Allegheny County’s GIS data portal. The full metadata record for this dataset can also be found on Allegheny County's GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the “Explore” button (and choosing the "Go to resource" option) to the right of the "ArcGIS Open Dataset" text below.

Category: Environment

Department: Geographic Information Systems Group; Department of Administrative Services

Data Notes: Coordinate System: Pennsylvania State Plane South Zone 3702; U.S. Survey Foot

Development Notes: Original Lakes and Drainage datasets combined to create this layer. Data was updated as a result of a flyover in the spring of 2004. A database field has been defined for all map features named Update Year". This database field will define which dataset provided each map feature. Map features from the current map will be set to "2004". The earlier dataset map features the earlier dataset map features used to supplement the area near the county boundary will be set to "1993". All new or modified map data will have the value for "Update Year" set to "2004".

Data Dictionary: https://docs.google.com/spreadsheets/d/16BWrRkoPtq2ANRkrbG7CrfQk2dUsWRiaS2Ee1mTn7l0/edit?usp=sharing

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assinged a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory intestests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. NOTE: If the name of this layer includes "_NORTH", "_SOUTH", or "_EAST" it represents a subset of the entire San Diego County Parcel Base. That is, the "_NORTH" layer includes only parcels generally in the Northwestern portion of the County. The "_SOUTH" layer includes parcels in the Southwestern portion. And the "_EAST" layer includes parcels in the approximate Eastern half of the County.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

This map feeds into a web app that allows a user to examine the known status of structures damaged by the wildfire. If a structure point does not appear on the map it may still have been impacted by the fire. Specific addresses can be searched for in the search bar. Use the imagery and topographic basemaps and photos to positively identify a structure. Photos may only be available for damaged and destroyed structures.

Historic land, building, and total assessed values for all Cook County parcels appealed with the Board of Review, from 2010 to present. The Board of Review uses these values for reporting, evaluating assessment performance over time, and research.

When working with Parcel Index Numbers (PINs) make sure to zero-pad them to 14 digits. Some datasets may lose leading zeros for PINs when downloaded

This data is parcel-level. Each row contains the assessed values for a single PIN for a single year. Important notes: • Assessed values are available when the Board of Review closes appeals and certifies the values. • The values in this data are assessed values, NOT market values. Assessed values must be adjusted by their level of assessment (https://prodassets.cookcountyassessor.com/s3fs-public/form_documents/classcode.pdf) to arrive at market value. Note that levels of assessment may have changed throughout the time period covered by this data set. • This data set will be updated when each township is certified. However, note that there may be discrepancies between the Board of Review’s data and the Assessor's site and this data set, as each pull from a slightly different system. • Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website (https://prodassets.cookcountyassessor.com/s3fs-public/form_documents/classcode.pdf). Note that class codes details can change across time. • The Change Reason and No Change Reason fields are only populated starting with the 2015 year data.

All data provided here is prepared for internal purposes by the County of Cook only is provided to the public as a courtesy.

While efforts have been made to be as accurate as possible, Cook County provides the data for personal use “as is”. The data is not guaranteed to be accurate, correct, or complete. Information provided should not be used as a substitute for legal, business, tax, or other professional advice. The recipient/viewer should contact appropriate regulating agencies to determine accuracy or suitability of the data for a particular use. This data may not be used in states that do not allow the exclusion or limitation of incidental or consequential damages.

Cook County or its staff assume no liability whatsoever for any losses that might occur from the use, misuse, or inability to use its geospatial data, maps or websites. All materials appearing on a map, geospatial data or County web site are transmitted without warranty of any kind and are subject to the terms on this disclaimer.

The statewide composite of parcels (cadastral) data for New Jersey was developed during the Parcels Normalization Project in 2008-2014 by the NJ Office of Information Technology, Office of GIS (NJOGIS.) The normalized parcels data are compatible with the NJ Department of the Treasury system currently used by Tax Assessors, and those records have been joined in this dataset. This composite of parcels data serves as one of the framework GIS datasets for New Jersey. Stewardship and maintenance of the data will continue to be the purview of county and municipal governments, but the statewide composite will be maintained by NJOGIS.Parcel attributes were normalized to a standard structure, specified in the NJ GIS Parcel Mapping Standard, to store parcel information and provide a PIN (parcel identification number) field that can be used to match records with suitably-processed property tax data. The standard is available for viewing and download at https://njgin.state.nj.us/oit/gis/NJ_NJGINExplorer/docs/NJGIS_ParcelMappingStandardv3.2.pdf. The PIN also can be constructed from attributes available in the MOD-IV Tax List Search table (see below).This feature class includes a large number of additional attributes from matched MOD-IV records; however, not all MOD-IV records match to a parcel, for reasons explained elsewhere in this metadata record. The statewide property tax table, including all MOD-IV records, is available as a separate download "MOD-IV Tax List Search Plus Database of New Jersey." Users who need only the parcel boundaries with limited attributes may obtain those from a separate download "Parcels Composite of New Jersey". Also available separately are countywide parcels and tables of property ownership and tax information extracted from the NJ Division of Taxation database.The polygons delineated in this dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such. Please note that these parcel datasets are not intended for use as tax maps. They are intended to provide reasonable representations of parcel boundaries for planning and other purposes. Please see Data Quality / Process Steps for details about updates to this composite since its first publication.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.