Data Description: This dataset lists all current City of Cincinnati employees, including full names, department, position title, full-time employee status, employee age range, employee race, and annual salary rate.

Data Creation: This data is pulled directly from the City's HR software; which centralizes all department HR actions city wide.

Data Created By: City Human Resource Information System (CHRIS)

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/Employee-Profile/wjqv-hgc9/

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 contains all code enforcement data, including abandoned vehicles; building code enforcement; demolition program; property enforcement; and zoning enforcement. This includes complaints, inspections, and violations from both residential and commercial properties. For more information visit: https://www.cincinnati-oh.gov/buildings/property-maintenance-code-enforcement/

Data Creation: The content of this data is entered and updated by respective enforcing agencies, and is maintained and stored by the Cincinnati Area Geographic Information Systems consortium (CAGIS).

Data Created By: CAGIS

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/Code-Enforcement/eb9h-rrpu/

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 dataset provides information about the number of properties, residents, and average property values for Home City Avenue cross streets in Cincinnati, OH.

U.S. Census Bureau QuickFacts statistics for Cincinnati city, Ohio. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.

Data Description: This dataset captures All Cincinnati 311 (Non-Emergency) Service Requests from 2012 to present including how long customer service requests have been open, by location, service request type, and department work group. Citizen Service Requests (CSR) give Cincinnati residents the opportunity to submit service request for concerns like potholes, tall grass and missed trash pick-up.

Data Creation: Using the Fix It Cincy! Mobile App, the customer service request online portal and the hotline (513-591-6000), citizen service requests are routed directly to City departments, including Transportation & Engineering, Buildings & Inspections, Health and Public Services. Once the department's work on the service request ticket is completed and the request is marked as "closed," customers receive an email notification that the work has been completed, followed by a link to an optional customer service feedback survey.

Data Created By: The source of this data is the CAGIS.

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/ve9a-xare

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 purpose of the study was to evaluate the implementation of the Safe City crime prevention model that was implemented in designated retail areas in jurisdictions across the United States. The model involved frequent meetings and information-sharing among the police, Target, and neighboring retailers, along with the implementation of enhanced technology. The first step in the Safe City evaluation involved selecting evaluation sites. The final sites selected were Chula Vista, California, and Cincinnati, Ohio. Next, for each of the two sites, researchers selected a site that had a potential for crime displacement caused by the intervention area, and a matched comparison area in another jurisdiction that would likely have been selected as a Safe City site. For Chula Vista, the displacement area was 2 miles east of the intervention area and the comparison area was in Houston, Texas. For Cincinnati, the displacement area was 1.5 miles north of the intervention area and the comparison area was in Buffalo, New York. In Chula Vista, the Safe City intervention activities were focused on gaining a better understanding of the nature and underlying causes of the crime and disorder problems occurring in the designated Safe City site, and strengthening pre-existing partnerships between law enforcement and businesses affected by these problems. In Cincinnati, the Safe City intervention activities centered on increasing business and citizen awareness, communication, and involvement in crime control and prevention activities. The research team collected pre- and post-intervention crime data from local police departments (Part 1) to measure the impact of the Safe City initiatives in Chula Vista and Cincinnati. The 981 records in Part 1 contain monthly crime counts from January 2004 to November 2008 for various types of crime in the retail areas that received the intervention in Chula Vista and Cincinnati, and their corresponding displacement zones and matched comparison areas. Using the monthly crime counts contained in the Safe City Monthly Crime Data (Part 1) and estimations of the total cost of crime to society for various offenses from prior research, the research team calculated the total cost of crimes reported during the month/year for each crime type that was readily available (Part 2). The 400 records in the Safe City Monthly Cost Benefit Analysis Data (Part 2) contain monthly crime cost estimates from January 2004 to November 2008 for assaults, burglaries, larcenies, and robberies in the retail areas that received the intervention in Chula Vista and Cincinnati, and their corresponding displacement zones and matched comparison areas. The research team also received a total of 192 completed baseline and follow-up surveys with businesses in Chula Vista and Cincinnati in 2007 and 2008 (Part 3). The surveys collected data on merchants' perceptions of crime and safety in and around businesses located in the Safe City areas. The Safe City Monthly Crime Data (Part 1) contain seven variables including the number of crimes in the target area, the month and year the crime was committed, the number of crimes in the displacement area, the number of crimes in a comparable area in a comparable city, the city, and the crime type. The Safe City Monthly Cost Benefit Analysis Data (Part 2) contain seven variables including the cost of the specified type of crime occurring in the target area, the month and year the cost was incurred, the cost of the specified type of crime in the displacement area, the cost of the specified type of crime in a matched comparison area, the city, and the crime type. The Safe City Business Survey Data (Part 3) contain 132 variables relating to perceptions of safety, contact with local police, experience and reporting of crime, impact of crime, crime prevention, community connections, and business/employee information.

This dataset provides information about the number of properties, residents, and average property values for Cincinnati Avenue cross streets in Egg Harbor City, NJ.

The Cincinnati City Boundary layer displays the area covered by the city of Cincinnati and its boundaries. The Cincinnati city area covers 79,72 sq.mi. and is composed of 52 neighborhoods. These neighborhoods are: - Avondale- Bond Hill- California- Camp Washington- Carthage- Clifton- College Hill- Columbia Tusculum - Corryville - CUF- Downtown/Riverfront- East End- East Price Hill- East Walnut Hills- East Westwood- English Woods- Evanston- Hartwell- Heights- Hyde Park- Kennedy Heights- Linwood- Lower Price Hill- Madisonville- Millvale- Mount Adams- Mount Airy- Mount Auburn- Mount Lookout- Mount Washington- North Avondale- North Fairmount- Northside- Oakley- Over-the-Rhine (OTR)- Paddock Hills- Pendleton- Pleasant Ridge- Queensgate- Riverside- Roselawn- Sayler Park- Sedamsville- South Cumminsville- South Fairmount- Spring Grove Village- Village of Roll Hill- Walnut Hills- West End- West Price Hill- Westwood- Winton Hills

This dataset provides information about the number of properties, residents, and average property values for Cincinnati Avenue cross streets in Panama City, FL.

This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.

Data Description: This data represents use of force incidents by the Cincinnati Police Department. Use of force can generally be defined as the means of compelling compliance or overcoming resistance to an officer’s command(s) in order to protect life or property or to take a person into custody.

Data Creation: This data is created through reporting by the Cincinnati Police Department.

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

Refresh Frequency: This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.

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/quk6-rcaw

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 dataset captures all Cincinnati Police Department Calls for Service. The City of Cincinnati's Computer Aided Dispatch (CAD) system records police incident response activity, which includes all calls for service to emergency operators, 911, alarms, police radio and non-emergency calls. CAD records all dispatch information, which is used by dispatchers, field supervisors, and on-scene officers to determine the priority, severity, and response needs surrounding the incident. Once an officer responds to a call, he/she updates the disposition to reflect findings on-scene. This dataset includes both proactive and reactive police incident data.

Data Creation: This data is created through the City’s computer-aided dispatch (CAD) system.

Data Created By: The source of this data is 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/xw7t-5phj

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.

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.

Data Description: Fire Incident data includes all fire incident responses. This includes emergency medical services (EMS) calls, fires, rescue incidents, and all other services handled by the Fire Department. All runs are coded according to classification: for EMS, this includes ALS (advanced life support); BLS (basic life support); etc.

Data Creation: This data is created when a run is entered into the City of Cincinnati’s computer-aided dispatch (CAD) database.

Data Created By: The source of this data is the City of Cincinnati's computer aided dispatch (CAD) database.

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/6jrc-cmn5

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 dataset captures confirmed shooting events in the City of Cincinnati. Shootings events are captured in the Computer Aided Dispatch System (CAD), and are ultimately stored in the City's Records Management System (RMS).

No personal or identifying (or otherwise sensitive) victim or suspect information is included in this data set.

Data Creation: This data is created through the City’s computer-aided dispatch (CAD) system.

Data Created By: The source of this data is 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/xw7t-5phj

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: 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 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

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.

Building permits issued by the City of Cincinnati in previous calendar years.

Data Description: This dataset contains the minimum and maximum pay by hour and by annual salary for each City of Cincinnati employee position listed. It also contains the salary plan code, position grade, and date that the position was created.

Data Creation: This data is pulled directly from the City's HR software; which centralizes all department HR actions city wide.

Data Created By: City Human Resource Information System (CHRIS)

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/Employee-Profile/wjqv-hgc9/

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

ParkServe® includes a comprehensive standardized database of local parks in nearly 14,000 cities, towns and communities. Census designated urban areas were used to define where to collect and create local data for cities, towns and communities. For each city, town and community, geographic boundaries were obtained from the US Census 2010 Places geospatial dataset and associated population estimates are derived from ESRI’s 2018 Demographic Forecasts. The ParkServe® team attempted to contact each city, town and community with a request for their parks data. If no GIS data was provided, the ParkServe® team created GIS data for the place based on available resources, such as park information from municipal websites, GIS data available from counties and states, and satellite imagery.Cities, towns and communities were then emailed a link to view the park data compiled in their area to verify the boundaries and attributes of the parks in the database through our custom web-based ParkReviewer™ application.ParkServe® Data InclusionProperty eligibility criteria for ParkServe®:- Publicly-owned local, state, and national parks- School parks with a joint-use agreement with the local government. Considering the scale of the project, only the joint-use agreements collected through ParkScore® were used.- Privately-owned parks that are managed for full public useExamples of property types not included in ParkServe®:- Golf courses- CemeteriesFor field descriptions, see: https://www.tpl.org/parkserve/downloads

Median Home Sale Price: All Residential: Cincinnati, OH data was reported at 223.000 USD th in Jul 2020. This records an increase from the previous number of 215.000 USD th for Jun 2020. Median Home Sale Price: All Residential: Cincinnati, OH data is updated monthly, averaging 153.000 USD th from Feb 2012 (Median) to Jul 2020, with 102 observations. The data reached an all-time high of 223.000 USD th in Jul 2020 and a record low of 110.000 USD th in Feb 2012. Median Home Sale Price: All Residential: Cincinnati, OH data remains active status in CEIC and is reported by Redfin. The data is categorized under Global Database’s United States – Table US.EB056: Median Home Sale Price: by Metropolitan Areas.