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.

The Street Centerlines layer is a series of lines (or polylines) digitized along the center of streets. These lines connected at intersections creating a street network. Each line carries attributes for the street name, address range, road class, jurisdiction and other data items.

Street centerlines are one of the most fundamental and useful G.I.S. layers. There are many applications that require accurate and comprehensive street centerlines datasets.
Main applications:
Networking (routing, navigating etc.)
Geocoding - assigning a geographic location to an address based on the address ranges stored in the street data.

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

Cincinnati Hillside Overlay Districts layer displays hillside areas where the existence of a 20% slope, is combined with the KOPE geologic formation. The Hillside Overlay District states regulations are necessary to establish standards to assist in the development of land and structures in existing hillside areas so that development will be compatible with the natural environment and respect the quality of the urban environment in those locations where the hillsides are of significant public value as determined by the City policy as outlined in the document “A Hillside Protection Strategy for Greater Cincinnati”, 1991.

Cincinnati Neighborhood Business Districts layer displays 38 Business districts.

Data Description: This dataset contains cleanings of greenspace sites in the 2016 Greenspace Maintenance Plan. This data is for site cleanings from January 2016 to April 2018.

Data Creation: Department of Public Services (DPS) recorded data on all greenspace site cleanings.

Data Created By: DPS

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/wh9h-zdqz

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.).

This data set contains meeting summaries, presentation slide decks, and data reports from CincyStat meetings.

This data set is updated as needed each week based on the CincyStat meeting schedule.

NOTE: Some meetings do not have slide decks or data sets associated: this means that all relevant data is contained within the meeting summary document.

Data Description: This data set contains updates on Plan Cincinnati. Plan Cincinnati is the City of Cincinnati's comprehensive plan that guides future planning and development in the City. More information about Plan Cincinnati is available here: https://www.cincinnati-oh.gov/planning/plan-cincinnati/

Data Creation: This data is collected and maintained by the City Planning Department

Data Created By: City Planning Department

Refresh Frequency: As Needed

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/uxm3-hyjp

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 Zoning Designation layer displays Zoning in the city of Cincinnati, Anderson Township, Blue Ash, Cheviot, Colerain Township, Columbia Township, Crosby Township, Forest Park, Green Township, Harrison Township, Lockland, Miami Township, Montgomery, North Bend, Norwood, Springfield Township, Sycamore township, Symmes Township. The Rural Zoning Commission (RZC) serves the Board of County Commissioners by administering and enforcing zoning in four townships, or parts thereof, and by providing contract services to a number of townships and villages in Hamilton County.
The layer isn't displayed when zoomed out beyond 1:115,000.

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

Data Creation: This data is created when CPD completes a pedestrian or traffic 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.

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.