Land, building, and total assessed values for all Cook County parcels, from 1999 to present. The Assessor's Office 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 in three stages: 1) mailed, these are the initial values estimated by the Assessor's Office and mailed to taxpayers. 2) certified, these are values after the Assessor's Office closes appeals. 3) Board of Review certified, these are values after the Board of Review closes appeals. The values in this data are assessed values, NOT market values. Assessed values must be adjusted by their level of assessment to arrive at market value. Note that levels of assessment have changed throughout the time period covered by this data set. This data set will be updated roughly contemporaneously (monthly) with the Assessor's website as values are mailed and certified. However, note that there may be small discrepancies between the Assessor's site and this data set, as each pulls from a slightly different system. If you find a discrepancy, please email the Data Department using the contact link below. This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that. Rowcount for a given year is final once the Assessor has certified the assessment roll all townships. Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time.For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub. Read about the Assessor's 2025 Open Data Refresh.

Update 10/31/2023: Sales are no longer filtered out of this data set based on deed type, sale price, or recency of sale for a given PIN with the same price. If users wish to recreate the former filtering schema they should set sale_filter_same_sale_within_365, sale_filter_less_than_10k, and sale_filter_deed_type to False. Parcel sales for real property in Cook County, from 1999 to present. The Assessor's Office uses this data in its modeling to estimate the fair market value of unsold properties. 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. Sale document numbers correspond to those of the Cook County Clerk, and can be used on the Clerk's website to find more information about each sale. NOTE: These sales are filtered, but likely include non-arms-length transactions - sales less than $10,000 along with quit claims, executor deeds, beneficial interests are excluded. While the Data Department will upload what it has access to monthly, sales are reported on a lag, with many records not populating until months after their official recording date. Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time. For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub. Read about the Assessor's 2025 Open Data Refresh.

The NIST Chemistry WebBook provides users with easy access to chemical and physical property data for chemical species through the internet. The data provided in the site are from collections maintained by the NIST Standard Reference Data Program and outside contributors. Data in the WebBook system are organized by chemical species. The WebBook system allows users to search for chemical species by various means. Once the desired species has been identified, the system will display data for the species. Data include thermochemical properties of species and reactions, thermophysical properties of species, and optical, electronic and mass spectra.

Commercial valuation data collected and maintained by the Cook County Assessor's Office, from 2021 to present. The office uses this data primarily for valuation and reporting. This dataset consolidates the individual Excel workbooks available on the Assessor's website into a single shared format. Properties are valued using similar valuation methods within each model group, per township, per year (in the year the township is reassessed). This dataset has been cleaned minimally, only enough to fit the source Excel workbooks together - because models are updated for each township in the year it is reassessed, users should expect inconsistencies within columns across time and townships. 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 property-level. Each 14-digit key PIN represents one commercial property. Commercial properties can and often do encompass multiple PINs. Additional notes: Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time. Data will be updated yearly, once the Assessor has finished mailing first pass values. If users need more up-to-date information they can access it through the Assessor's website. The Assessor's Office reassesses roughly one third of the county (a triad) each year. For commercial valuations, this means each year of data only contain the triad that was reassessed that year. Which triads and their constituent townships have been reassessed recently as well the year of their reassessment can be found in the Assessor's assessment calendar. One KeyPIN is one Commercial Entity. Each KeyPIN (entity) can be comprised of one single PIN (parcel), or multiple PINs as designated in the pins column. Additionally, each KeyPIN might have multiple rows if it is associated with different class codes or model groups. This can occur because many of Cook County's parcels have multiple class codes associated with them if they have multiple uses (such as residential and commercial). Users should not expect this data to be unique by any combination of available columns. Commercial properties are calculated by first determining a property’s use (office, retail, apartments, industrial, etc.), then the property is grouped with similar or like-kind property types. Next, income generated by the property such as rent or incidental income streams like parking or advertising signage is examined. Next, market-level vacancy based on location and property type is examined. In addition, new construction that has not yet been leased is also considered. Finally, expenses such as property taxes, insurance, repair and maintenance costs, property management fees, and service expenditures for professional services are examined. Once a snapshot of a property’s income statement is captured based on market data, a standard valuation metric called a “capitalization rate” to convert income to value is applied. This data was used to produce initial valuations mailed to property owners. It does not incorporate any subsequent changes to a property’s class, characteristics, valuation, or assessed value from appeals.Township codes can be found in the legend of this map. For more information on the sourcing of attached data and the preparation of this datase

Parcels with property tax-exempt status across all of Cook County per tax year, from Tax Year 2022 on, with geographic coordinates and addresses.

As of 2017 owner names in this dataset are no longer being regularly updated. We are trying to figure out a solution to this problem.

Properties of religious, charitable, and educational organizations, as well as units of federal, state and local governments, can be eligible for exemption from property taxes. The Illinois Department of Revenue (IDOR) ultimately grants qualified organizations with property tax exempt status, with additional administration by the Board of Review and/or Assessor. Learn more new>here, and see the Assessor's guidance for religious organizations new>here.

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.

Additional notes:Parcel entroids are based on Cook County parcel shapefiles.

Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service.

Exempt status for parcels changes regularly depending on the use and owner of a given parcel. Please contact Assessor.Exempt@cookcountyil.gov if you need additional information about parcels excluded from this dataset.

Data will be updated monthly.

This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values and property tax-exempt status for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that.

Rowcount for a given year is final once the Assessor has certified the assessment roll all townships.

Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time.

For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub.

Read about the Assessor's 2023 Open Data Refresh.

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

October 2025

A complete, historic universe of Cook County parcels with attached geographic, governmental, and spatial data.

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.

Additional notes:Non-taxing district data is attached via spatial join (st_contains) to each parcel's centroid.

Tax district data (school district, park district, municipality, etc.) are attached by a parcel's assigned tax code.

Centroids are based on Cook County parcel shapefiles.

Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile).

Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service.

This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that.

Rowcount for a given year is final once the Assessor has certified the assessment roll all townships.

Data will be updated monthly.

Depending on the time of year, some third-party and internal data will be missing for the most recent year. Assessments mailed this year represent values from last year, so this isn't an issue. By the time the Data Department models values for this year, those data will have populated.

Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time.

Due to decrepencies between the systems used by the Assessor and Clerk's offices, taxdistrictcode is not currently up-to-date in this table.

For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub.

Read about the Assessor's 2023 Open Data Refresh.

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

This is a preliminary version of a new open data asset and will be updated later this year once the Assessor's Office has finished reassessing commercial properties, then once annually. Use accordingly.

Commercial valuation data collected and maintained by the Cook County Assessor's Office, from 2021 to present. The office uses this data primarily for valuation and reporting. This dataset consolidates the individual Excel workbooks available on the Assessor's website into a single shared format. Properties are valued using similar valuation methods within each modelgroup, per township, per year (in the year the township is reassessed). This dataset has been cleaned minimally, only enough to fit the source Excel workbooks together - because models are updated for each township in the year it is reassessed, users should expect inconsistencies within columns across time and townships.

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 property-level. Each 14-digit key PIN represents one commercial property. Commercial properties can and often do encompass multiple PINs. Additional notes: Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time.

Data will be updated yearly, once the Assessor has finished mailing first pass values. If users need more up-to-date information they can access it through the Assessor's website.

The Assessor's Office reassesses roughly one third of the county (a triad) each year. For commercial valuations, this means each year of data only contain the triad that was reassessed that year. Which triads and their constituent townships have been reassessed recently as well the year of their reassessment can be found in the Assessor's assessment calendar.

Commercial properties are calculated by first determining a property’s use (office, retail, apartments, industrial, etc.), then the property is grouped with similar or like-kind property types. Next, income generated by the property such as rent or incidental income streams like parking or advertising signage is examined. Next, market-level vacancy based on location and property type is examined. In addition, new construction that has not yet been leased is also considered. Finally, expenses such as property taxes, insurance, repair and maintenance costs, property management fees, and service expenditures for professional services are examined. Once a snapshot of a property’s income statement is captured based on market data, a standard valuation metric called a “capitalization rate” to convert income to value is applied.

This data was used to produce initial valuations mailed to property owners. It does not incorporate any subsequent changes to a property’s class, characteristics, valuation, or assessed value from appeals.Township codes can be found in the legend of this map.

For more information on the sourcing of attached data and the preparation of this dataset, see the Assessor's Standard Operating Procedures for Open Data on GitHub.

Read about the Assessor's 2023 Open Data Refresh.

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

County tax assessors tax lots, including rights of way, with associated property data, excluding ownership information. Selected items from each county assessor's file are included and standardized for all three counties. The tax lot spatial features and data associated with the tax lot are compiled by Metro from existing records created and maintained by the local county assessment and taxation offices. This is a downloadable zip file that includes the taxlots shapefile and layer files for visualizing taxlots with or without right of ways. Use the original feature layers if viewing the layers in ArcGIS Online: "Taxlots (Public)" or "Taxlots with Right of Way (Public)." Date of last data update: 2025-07-18 This is official RLIS data. Contact Person: Christine Rutan christine.rutan@oregonmetro.gov 503-797-1669 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3733 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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)

A current-year-only universe of Cook County parcels with attached geographic, governmental, and spatial data.

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.

Additional notes:

• Non-taxing district data is attached via spatial join (st_contains) to each parcel's centroid.
• Tax district data (school district, park district, municipality, etc.) are attached by a parcel's assigned tax code.
• Centroids are based on Cook County parcel shapefiles.
• Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile).
• Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service.
• This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that.
• Rowcount for a given year is final once the Assessor has certified the assessment roll all townships.
• Data will be updated monthly.
• Depending on the time of year, some third-party and internal data will be missing for the most recent year. Assessments mailed this year represent values from last year, so this isn't an issue. By the time the Data Department models values for this year, those data will have populated.
• Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time.
• Due to discrepancies between the systems used by the Assessor and Clerk's offices, tax_district_code is not currently up-to-date in this table.
• There are currently two different sources of parcel-level municipality available in this data set, and they will not always agree: tax and spatial records. Tax records from the Cook County Clerk indicate the municipality to which a parcel owner pays taxes, while spatial records, also from the Cook County Clerk, indicate the municipal boundaries within which a parcel lies.

Read about the Assessor's 2025 Open Data Refresh.

Soil Pits represent the most detailed descriptions made of a soil profile. They are used for classification of the soil series. For generating standard property information on a series base it was necessary to check and simplify some of the more critical properties of the profile such as the series and subgroup classification.

For more information, please visit HART.ubc.ca. Housing Assessment Resource Tools (HART) This database was created to accompany a report prepared by Joe Daniels, PhD, and Martine August, PhD, entitled “Acquisitions Programs for Affordable Housing: Creating non-market supply and preserving affordability with existing multi-family housing.” The database and report form part of the work performed under the HART project, and the report can be found at HART’s website: HART.ubc.ca. The database is a single table that summarizes 11 key elements, plus notes and references, of a growing list of policies from governments across the world. There are currently 108 policies included in the database. The authors expect to update this database with additional policies from time to time. The authors hope this database will serve as a resource for governments looking to become familiar with a variety of policies in order to help them evaluate what policies might be most applicable in their communities. Data Fields: List of data fields (15 total): 1. Government Order 2. Government Jurisdiction 3. Policy Name/Action 4. Acquisition Target 5. Years Active 6. Funder/Funding 7. Funding Amount (Program) 8. Funding Form 9. Affordability Standard 10. Affordability Term 11. Features/Requirements 12. Comments 13. Reference link 1 14. Reference link 2 15. Reference link 3 Description of data fields (15) 1. Government Order: - Categorizes the relative political authority in terms of one of three categories: Municipal (responsible for a city or small region), Provincial (responsible for multiple municipalities), or Country (responsible for multiple provinces; highest political authority). - This field may be used to help identify those policies most relevant to the reader. 2. Government Jurisdiction: - Indicates the name of the government. - For example, a country might be named “Canada,” a province might be named “Quebec,” and a municipality might be named “Calgary.” 3. Policy Name/Action: - Indicates the name of the policy. - This generally serves as the unique identifier for the record. However, there may be some programs that are only known by a common term; for example, “Right of First Refusal.” 4. Acquisition Target: - Describes the type of housing asset that the policy is concerned with. For example, acquiring land, acquiring existing rental buildings, renovating existing supportive housing. 5. Years Active: - The time period that the policy has been active. - Typically formatted as “[Year started] - [Year ended]”. If just a single year is listed (e.g. “2009”) that means the policy was only active that one year. - If the policy is active with no end date, then the format will be “[Year started] - ongoing.” If the policy has a specified end date in the future, that year will be listed instead: “[Year started] – [Expected final year].” 6. Funder/Funding: - The government, government agency, or organization responsible for the use of those funds made available through the policy. 7. Funding Amount (Program): - The dollar value of funds connected to the policy. - Sometimes this is the total value of funds available to the policy, and sometimes it is the actual value of funds that were used. - The funds indicated here do not necessarily correspond to the time period indicated in the ‘Years Active’ field. Additional detail will be added to clarify whenever possible. - If policy has “N/A” listed here, see ‘Features/Requirements’ for more information. 8. Funding Form: - Indicates the type of financial tools available to the policy. For example, “capital funding,” “forgivable loans,” or “rent supplements.” - If policy has “N/A” listed here, see ‘Features/Requirements’ for more information. 9. Affordability Standard: - Indicates whether the policy includes an explicit standard or benchmark of affordability that is used to guide or otherwise inform the policy’s goals. 10. Affordability Term: - Indicates whether the affordability standard applies to a specific time period. - This field may also contain other information on time periods that are relevant to the policy; for example, an operating loan guaranteed to be active for a specific number of years. 11. Features/Requirements: - Describes the broad objectives of the policy as well as any specific guidelines that the policy must follow. 12. Comments: - Author’s commentary on the policy. 13. Reference link 1: - A web address (URL) or citation indicating the source of the details on the policy. 14. Reference link 2: - A second web address (URL) or citation indicating the source of the details on the policy. 15. Reference link 3: - A third web address (URL) or citation indicating the source of the details on the policy. File list (1): 1. Property Acquisition Policy Database.xlsx

Data Description: This data set contains all inspections issued/performed by City of Cincinnati Departments (including Buildings & Inspections; Cincinnati Fire Department; Cincinnati Health Department; Cincinnati Parks; and Trade/Development), as well as Inspections Bureau Inc (IBI) and Hamilton County departments.

Inspections range from electrical surveys, to swimming pools/spas, to elevator inspections, daycare inspections, and more. This data covers inspections since 1999 through present day.

Data Creation: All data is input by respective agencies, and maintained/stored by Cincinnati Area Geographic Information Systems (CAGIS), and is additionally available on CAGIS Property Activity Report website: http://cagismaps.hamilton-co.org/PropertyActivity/cagisreport

Data Created By: CAGIS

Refresh Frequency: Daily

Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

The BEPS Program was created by Title III of the Clean Energy DC Omnibus Act of 2018. The BEPS is a minimum threshold of energy performance that will be no lower than the local median ENERGY STAR score by property type (or equivalent metric). The standards were created to drive energy performance in existing buildings to help meet the energy and climate goals of the Sustainable DC plan — to reduce greenhouse gas emissions and energy consumption by 50% by 2032. DOEE established the first set of Standards on January 1, 2021. Standards will then be set every 6 years, creating BEPS Periods (BEPS Period 1, BEPS Period 2, etc.). The 2021 Building Energy Performance Standards and a Guide to the 2021 BEPS are available for viewing on DOEE’s website.To improve transparency and help building owners understand how their building performs relative to the BEPS, DOEE is publishing this BEPS Disclosure that compares a building’s benchmarking data with the BEPS and provides an estimate of the building’s distance from the standard and estimated performance requirement.Please note that this dataset is based on information currently available to DOEE using calendar year 2019 benchmarking data provided by the building owner. Some buildings are still being evaluated and therefore have been designated as “Under Review” in this dataset. Building owners that believe their 2019 calendar year data is incorrect should contact the Benchmarking Help Center (info.benchmark@dc.gov). Additionally, buildings that meet certain criteria may request a variance from the standards by submitting a variance request form on the DOEE website.

What is in this layer?By Right permits, which are also referred to as ministerial permits or simply permits, are granted if the proposed project complies with established standards set forth in the City of Tucson’s Unified Development Code (UDC) and the accompanying Technical Standards. These permits, since they are not discretionary, are not subject to public review, are reviewed by PDSD staff for compliance with the code and standards, and are issued administratively by PDSD staff. What is NOT included in this layer?PDSD issues around 10,000 permits a year, many for small activities that are have little to no visibility or impact outside the property in question. Because there are so many permits for projects such as solar installations, water heater replacements, installation of fences or walls, and installations of pools and spas, these permits are excluded from the layer. For more information on all activities associated with a specific property, go to Property Research Online.A list of all the permits shown on the Development Activity Map can be found here.Data in this layer is updated daily from the City of Tucson's permitting system of record.

Land, building, and total assessed values, pre and post-appeal with the Cook County Assessor’s office, for all Cook County parcels, from 1999 to present. The Assessor's Office uses these values for reporting, evaluating assessment performance over time, and research.

When working with Parcel Identification 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 pre and post-appeal. Important notes:

• This dataset includes appeal cases that are currently open. Data for these cases is not final and is subject to change.
• Each row includes two stages: 1) mailed, these are the initial assessed values (AVs) estimated by the Assessor's Office and mailed to taxpayers. The columns mailed_bldg, mailed_land, and mailed_tot are the AVs for the building, land, and total, at the mailed stage. 2) certified, these are values after the Assessor's Office closes appeals. The columns certified_bldg, certified_land, and certified_tot are the AVs for the building, land, and total, after the Assessor has completed appeal decisions.
• Values in this dataset are not final assessed values for a given year as they are still subject to change if a taxpayer appeals to the Cook County Board of Review. At present, this dataset does not contain appeal decisions from this final third stage. However, the final stage AVs and appeal decisions can be downloaded from the Board of Review Appeal Decision History dataset.
• Due to the current transition from the county's legacy system to a modern system of record, appeal data is sparse prior to 2021. Values and change/no change decisions are available, but the reason, agent, and type fields will only be complete once the new system has been successfully batch updated with complete historical data.
• The values in this data are assessed values, NOT market values. Assessed values must be adjusted by their level of assessment to arrive at market value. Note that levels of assessment have changed throughout the time period covered by this data set.
• This data set will be updated monthly regardless of the Assessor's mailing and certification schedule. There may be small discrepancies between the Assessor's site and this data set, as each pulls from a slightly different system. If you find a discrepancy, please email the Data Department using the contact link below.
• This dataset contains data for the current tax year, which may not yet be complete or final. Assessed values for any given year are subject to change until review and certification of values by the Cook County Board of Review, though there are a few rare circumstances where values may change for the current or past years after that.
• Rowcount for a given year is final once the Assessor has certified the assessment roll all townships.
• Current property class codes, their levels of assessment, and descriptions can be found on the Assessor's website. Note that class codes details can change across time.

Read about the Assessor's 2025 Open Data Refresh.

The VIIRS/SNPP Cloud Properties Level 3 monthly, 1x1 degree grid product is designed to facilitate continuity in cloud property statistics between the MODIS on the Aqua and Terra platforms and the common continuity products generated for the VIIRS (Visible Infrared Imaging Radiometer Suite) and the MODIS Aqua instruments. CLDPROP Level-3 statistical routines include scalar and histograms (1-D and 2-D) that are calculated identically to statistical datasets in the MODIS standard Level-3 product (MOD08 and MYD08 for MODIS Terra and Aqua, respectively). In addition, the same dataset names are used for all common datasets provided in both the continuity and standard Level-3 files.

This feature layer provides digital tax parcels for the Organized Towns of the State of Maine. Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. "Maine Parcels Organized Towns Feature" and "Maine Parcels Organized Towns ADB" are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions. In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. "Maine Parcels Unorganized Territory Feature" is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of Maine Revenue Services (https://www.maine.gov/revenue/taxes/property-tax) to compile up-to-date parcel ownership information. Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.

This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (Maine GeoLibrary). Grant recipient parcel data submissions were guided by standards presented to the Maine GeoLibrary Board on May 21, 2005, which are outlined in the "Standards for Digital Parcel Files" document available on the Maine GeoLibrary publications page (https://www.maine.gov/geolib/policies/standards.html). This dataset also contains municipal parcel data acquired through other sources; the data sources are identified (where available) by the field “FMSCORG”. Note: Join this feature layer with the "Maine Parcels Organized Towns ADB" table (https://maine.hub.arcgis.com/maps/maine::maine-parcels-organized-towns-feature/about?layer=1) for available ownership information. A date field, “FMUPDAT”, is attributed with the most recent update date for each individual parcel if available. The "FMUPDAT" field will not match the "Updated" value shown for the layer. "FMUPDAT" corresponds with the date of update for the individual data, while "Updated" corresponds with the date of update for the ArcGIS Online layer as a whole. Many parcels have not been updated in several years; use the "FMUPDAT" field to verify currency.