The National Fire Incident Reporting System (NFIRS) is a reporting standard that fire departments nationwide use to uniformly report on the full range of fire department activities. This dataset emcompasses all fire incidents reported to NFIRS that were responded to by the Cincinnati Fire Department in the year 2018.

Data Description: The National Fire Incident Reporting System (NFIRS) is a reporting standard that fire departments nationwide use to uniformly report on the full range of fire department activities. This dataset emcompasses all fire incidents reported to NFIRS that were responded to by the Cincinnati Fire Department in the year 2018.

Data Creation: NFIRS was created in 1976 to address the United State’s fire problem and is jointly managed by the U.S Fire Administration (USFA) and the National Fire Information Council (NFIC). Over the life of the system, all 50 states, more than 40 major metropolitan areas, and more than 15,000 fire departments have participated in NFIRS. Fore more information please visit: https://www.usfa.fema.gov/data/nfirs/about/index.html

Data Created By: The source of this data is the Cincinnati Fire Department.

Refresh Frequency: This dataset is static and posted annually.

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

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

Data Description: The National Fire Incident Reporting System (NFIRS) is a reporting standard that fire departments nationwide use to uniformly report on the full range of fire department activities. This dataset encompasses all fire incidents reported to NFIRS that were responded to by the Cincinnati Fire Department in the year 2019.

Data Creation: NFIRS was created in 1976 to address the United State’s fire problem and is jointly managed by the U.S Fire Administration (USFA) and the National Fire Information Council (NFIC). Over the life of the system, all 50 states, more than 40 major metropolitan areas, and more than 15,000 fire departments have participated in NFIRS. Fore more information please visit: https://www.usfa.fema.gov/data/nfirs/about/index.html

Data Created By: The source of this data is the Cincinnati Fire Department.

Refresh Frequency: This dataset is static and posted annually.

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

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

Data Description: This data set is all closed Citizen Complaint Authority (CCA) complaints that have been received in the past five years. This data set contains complaints that are processed, investigated and closed by CCA. It includes data such as the type of event reported, date and time of incident, officer and citizen demographics, and allegation investigated.

Data Creation: This data is created when a citizen files a complaint against a Cincinnati Police officer.

Data Created By: The source of this data is the Citizen Complaint Authority (CCA).

Refresh Frequency: This data is updated 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

Disclaimer: The attribute unique case identifier is the ID for one incident. One incident can contain multiple allegations and involve multiple officers and citizens. 2. Geo location information is not provided for incidents that are not CAGIS verified addresses or if the incident occurs at the residence of a complainant. This is done to protect the individual's privacy
In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

Data Description: This dataset captures all Cincinnati Police Department stops of pedestrians. This data includes time of incident, officer assignment, race/sex of stop subject, and outcome of the stop ("Action taken").. Individual pedestrian stops may populate multiple data rows to account for multiple outcomes: "interview number" is the unique identifier for every one (1) pedestrian stop.

Data Creation: This data is created when CPD completes a pedestrian stop and logs the interview via Contact Cards. Contact Cards are a result of the Collaborative Agreement. Contact Cards are manually entered and may experience lags in data entry.

Data Created by: This data is created by the Cincinnati Police Department.

Refresh Frequency: This data is updated daily.

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/gw5q-kjng

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

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

Data Description: This data set contains the daily count of Streetcar ridership throughout the City of Cincinnati.

Data Creation: Streetcar Ridership data is created via an Automated Passenger Counter (APC) system installed in the doorways of each streetcar vehicle. APC devices uses infrared lights to approximate the number of entering and exiting riders.

Data Created By: Southwest Ohio Regional Transit Authority (SORTA)

Refresh Frequency: Daily

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/n7hm-3f4b

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

This guide provides step by step instructions on using the data provided through the City of Cincinnati Office of Performance and Data Analytics Open Data Portal.

Data Description: This data set includes the approved budget for every department each fiscal year from 2004 to present. This data is structured to report how much money is budgeted for each object code and object category by department and fiscal year.

Data Creation: When the City Annual Budget is approved at the end of the fiscal year the budgets of each department are entered into the Cincinnati Financial System for reporting purposes.

Data Created By: The Cincinnati Financial System (CFS)

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

Data Description: Vision Zero is a strategy to eliminate all traffic-related deaths and severe injuries, while increasing safe, healthy, equitable mobility for all. This data set is a log of funded projects through the Vision Zero Initiative from 2019 to present.

For more information on the City's Vision Zero Initiative visit: https://www.cincinnati-oh.gov/visionzero/

Data Creation: Manual collection by the Department of Transportation and Engineering

Data Created By: Department of Transportation and Engineering

Refresh Frequency: This data is updated as projects are planned or completed.

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/8icv-g4s9

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

Data Description: This data set is a log of any instance that causes a delay within the streetcar system where a streetcar is physically blocked from moving. A blockage is defined as any delay that exceeds 2 minutes and is not caused due to heavy traffic. While blockages can occur at any point along the track, the data is tracked by location at the intersection or mid-block.

Data Creation: TransDev

Data Created By: TransDev

Refresh Frequency: Daily

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/Streetcar-Blockages-and-Delays/iq5g-qgvu/

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

FY2020 Performance Agreements for City of Cincinnati departments and offices.