Field Descriptions Crime Dashboard Document - https://www.minneapolismn.gov/government/government-data/datasource/crime-dashboard/crime-dashboard-document/

The data set is refreshed on a daily basis by 9:30 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.

This dataset contains all current and active business licenses issued by the Department of Business Affairs and Consumer Protection. This dataset contains a large number of records /rows of data and may not be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Notepad or Wordpad, to view and search.

Data fields requiring description are detailed below.

APPLICATION TYPE: 'ISSUE' is the record associated with the initial license application. 'RENEW' is a subsequent renewal record. All renewal records are created with a term start date and term expiration date. 'C_LOC' is a change of location record. It means the business moved. 'C_CAPA' is a change of capacity record. Only a few license types my file this type of application. 'C_EXPA' only applies to businesses that have liquor licenses. It means the business location expanded.

LICENSE STATUS: 'AAI' means the license was issued.

Business license owners may be accessed at: http://data.cityofchicago.org/Community-Economic-Development/Business-Owners/ezma-pppn To identify the owner of a business, you will need the account number or legal name.

Data Owner: Business Affairs and Consumer Protection

Time Period: Current

Frequency: Data is updated daily

Analysis of ‘Green Infrastructure Water Capture Capacity’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/affffc4c-2ee8-4cae-9362-73ddf0be9ca1 on 26 January 2022.

--- Dataset description provided by original source is as follows ---

Green infrastructure is designed to capture and infiltrate or filter stormwater runoff through natural systems. This dataset is used in combination with precipitation numbers to update the stormwater dashboard (in progress) and Sustainable City pLAn. It is refreshed as new projects are created.

--- Original source retains full ownership of the source dataset ---

Green infrastructure is designed to capture and infiltrate or filter stormwater runoff through natural systems. This dataset is used in combination with precipitation numbers to update the stormwater dashboard (in progress) and Sustainable City pLAn. It is refreshed as new projects are created.

This Power BI dashboard shows the COVID-19 vaccination rate by key demographics including age groups, race and ethnicity, and sex for Tempe zip codes.Data Source: Maricopa County GIS Open Data weekly count of COVID-19 vaccinations. The data were reformatted from the source data to accommodate dashboard configuration. The Maricopa County Department of Public Health (MCDPH) releases the COVID-19 vaccination data for each zip code and city in Maricopa County at ~12:00 PM weekly on Wednesdays via the Maricopa County GIS Open Data website (https://data-maricopa.opendata.arcgis.com/). More information about the data is available on the Maricopa County COVID-19 Vaccine Data page (https://www.maricopa.gov/5671/Public-Vaccine-Data#dashboard). The dashboard’s values are refreshed at 3:00 PM weekly on Wednesdays. The most recent date included on the dashboard is available by hovering over the last point on the right-hand side of each chart. Please note that the times when the Maricopa County Department of Public Health (MCDPH) releases weekly data for COVID-19 vaccines may vary. If data are not released by the time of the scheduled dashboard refresh, the values may appear on the dashboard with the next data release, which may be one or more days after the last scheduled release.Dates: Updated data shows publishing dates which represents values from the previous calendar week (Sunday through Saturday). For more details on data reporting, please see the Maricopa County COVID-19 data reporting notes at https://www.maricopa.gov/5460/Coronavirus-Disease-2019.

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

Note: 11/1/2023: Publication of the COVID data will be delayed because of technical difficulties. Note: 9/20/2023: With the end of the federal emergency and reporting requirements continuing to evolve, the Indiana Department of Health will no longer publish and refresh the COVID-19 datasets after November 15, 2023 - one final dataset publication will continue to be available. Note: 5/10/2023: Due to a technical issue updates are delayed for COVID data. New files will be published as soon as they are available. Note: 3/22/2023: Due to a technical issue updates are delayed for COVID data. New files will be published as soon as they are available. Valid COVID vaccinations broken down by Indiana zip codes. This dataset is a running summation of the valid vaccinations by zip code. Historical data will continue to change as new information is reported to ISDH. This dataset should not be used to determine new vaccinations occurring in the past week as it includes new historical cases as well. Historical Changes: 1/5/2023: Due to a technical issue the COVID datasets were not updated on 1/4/23. Updates will be published as soon as they are available. 9/29/22: Due to a technical difficulty, the weekly COVID datasets were not generated yesterday. They will be updated with current data today - 9/29 - and may result in a temporary discrepancy with the numbers published on the dashboard until the normal weekly refresh resumes 10/5. 9/27/2022: As of 9/28, the Indiana Department of Health (IDOH) is moving to a weekly COVID update for the dashboard and all associated datasets to continue to provide trend data that is applicable and usable for our partners and the public. This is to maintain alignment across the nation as states move to weekly updates. 8/19/2022 - The first and second dose columns are being removed as of 8/22/22 as the Health department has transitioned to reporting on Fully/Partially vaccinated. The final historical file including these columns from 8/19 will continue to be available. 2/10/2022: Data was not published on 2/9/2022 due to a technical issue, but updated data was released 2/10/2022. 11/8/2021: The population column has been renamed: eligible_population, and now includes all population 5+. Vaccination data has been updated with 5+ age ranges included. 10/13/2021: There has been an increase in all doses administered because of the addition of booster shot data. 06/23/2021: COVID Hub files will no longer be updated on Saturdays. The normal refresh of these files has been changed to Mon-Fri. 06/10/2021: COVID Hub files will no longer be updated on Sundays. The normal refresh of these files has been changed to Mon-Sat. 06/07/2021: Today’s new counts include doses newly reported to the Indiana Department of Health on Saturday and Sunday. 06/03/2021: Individuals are able to update their personal and demographic information during the vaccination registration process. Today’s data reflects changes made by individuals to their race, ethnicity, or county of residence over the course of their vaccination series. 05/13/2021: The "population_16_and_over" column has been replaced by "population_12_and_over" and the "population_margin_of_error" has been removed going forward. Ages 12-15 have been added into the dataset.

The Public Service Commission’s (PSC) Staffing Dashboard provides timely and relevant data on staffing activities and trends that will give deputy heads, hiring managers and human resources specialists a broader understanding of staffing within their organizations and the public service as a whole. The Staffing Dashboard is an integral feature of the PSC’s New Direction in Staffing (NDS), which includes the renewed Appointment Policy and delegation instrument, effective as of April 1, 2016. The Staffing Dashboard contains information on organizations subject to the Public Service Employment Act only. The purpose of the Staffing Dashboard is to share data available at the PSC with organizations. It is designed to allow organizations to have a snapshot of their staffing activities and to identify key data trends. It also provides the ability for organizations to compare their data with other organizations, including similar-sized or similarly mandated organizations, or to the public service as a whole The Staffing Dashboard is published on a quarterly basis. Data for a specific quarter may change over the course of the current fiscal year, as data are updated. The notes for each section will provide users with additional details. Please visit the Public Service Commission’s Staffing Dashboard to see the interactive visualisation tool that makes use of the datasets in this collection.

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

Stop relying on outdated and inaccurate Linkedin Data and let Wiza be your source of truth for all use cases.

Why we're different: Wiza is not a static Linkedin Data Database that gets refreshed on occasion. Every Linkedin datapoint is sourced the moment that you receive the information. This ensures that each person in your dataset has 100% accuracy by leveraging Linkedin Data sourced through their live Linkedin profile.

Key Features:

Comprehensive Data Coverage: Stop contacting the same people as everyone else. Wiza's Data is sourced live, not stored in a limited database. We can source Linkedin Data from any Linkedin URL, Linkedin Sales Navigator URL, Linkedin Recruiter URL, or even just based on search criteria that you give us.

Linkedin Data: Wiza is able to provide Linkedin Data points, sourced live from each person's Linkedin profile, including Subtitle, Bio, Job Title, Job Description, Skills, Languages, Certifications, Work History, Education, Open to Work, Premium Status, Length of Employment at current role and company, and more!

Data Use-Cases: Wiza's Linkedin Data, B2B Contact Data, B2C Contact Data (personal emails and mobile phone numbers), Email Data, Phone Number Data, and Company Data can be used for a large variety of use-cases. We see startups and Fortune 100 companies leverage the breadth and quality of Wiza's data capabilities.

Data Description: This data set contains a record of all Citizen Service Requests (CSRs) feedback survey responses. When CSRs are closed out by the City, customers who provide an email address are automatically sent a notification that their work has been completed, as well as a link to a customer service satisfaction survey. Customers are able to provide feedback on work completion, satisfaction level, and any additional information. No identifying personal customer/citizen information (name, contact information, or additional comments) is included in this data.

Data Creation: Data generated when CSR feedback surveys are submitted

Data Created By: DPS

Refresh Frequency:

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/Customer-Service-CSR-Satisfaction/ks8a-xggj/

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 dataset captures all traffic stops involving motor vehicles. Time of incident, officer assignment, race/sex of stop subject, and outcome of the stop ("Action taken") are also included in this data. Individual traffic stops may populate multiple data rows to account for multiple outcomes: "interview number" is the unique identifier for every one (1) traffic stop.

Data Creation: Cincinnati Police Department (CPD) officers record all traffic stops involving motor vehicles via Contact Cards. Contact Cards are completed every time a CPD officer stops vehicles or pedestrians. The use of Contact Cards came out of the Collaborative Agreement.

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/h48j-wkz6

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

Newer version of the Agency Profile Report as of FY20. This dashboard provides Department-level views of obligation aggregates by various breakdowns: Tier, Contract, Vendor, etc. Also provides counts of Expiring contracts and awards as well as purchasing vehicle types.

Data Description: This dataset contains all Customer/Citizen Service Request (CSR) records for all City of Cincinnati departments. Data set includes close time, service request type, service request group, current service request status, and time resolved/closed. A Citizen Service Requests (CSR) gives Cincinnati residents the opportunity to submit service request for concerns like furniture pick-up, tall grass and pothole repairs. 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 to be completed.

Data Creation: Data is generated when a CSR is submitted through mobile app, online portal, or through the hotline

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/Customer-Service-Citizen-Service-Request-CSR-/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

Data Description: This data set contains all City of Cincinnati expenses by object code and day. The object code is the descriptor explaining the nature of the expense (personnel; overtime; office supplies; etc.)

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

Data Created By: The Cincinnati Financial System (CFS)

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/City-Spending/cuw9-nu34/

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

All data displayed on this Dashboard is near real-time, automatically updating at regular intervals. Web Services used in the dashboard: (visit link to learn more about each service) IRWIN - The Integrated Reporting of Wildland-Fire Information (IRWIN) service is an investment intended to enable “end-to-end” fire reporting capability. IRWIN provides data exchange capabilities between existing applications used to manage data related to wildland fire incidents. IRWIN focuses on the goals of reducing redundant data entry, identifying authoritative data sources, and improving the consistency, accuracy, and availability of operational data.IRWIN can be thought of as a central hub that orchestrates data between the various applications. Users continue to utilize existing applications. Data is synchronized between participating applications to ensure the most current data is available in near real time. IRWIN supports conflict detection and resolution on all new wildfire incidents to support a unique record for each incident.NOAA nowCOAST - Provides web services of near real-time observations, analyses, tide predictions, model guidance, watches/warnings, and forecasts for the coastal United States by integrating data and information across NOAA, other federal agencies and regional ocean and weather observing systems (source). All layers below automatically refresh every five minutes.Tornado Warning - National Weather Service warning for short duration hazard.Severe Thunderstorm Warning - National Weather Service warning for short duration hazard.Flash Flood Warning - National Weather Service warning for short duration hazard.Red Flag Warning - National Weather Service warning for long duration hazard.nowCOAST Lightning Strike Density - 15-minute Satellite Emulated Lightning Strike Density imagery for the last several hours.nowCOAST Radar - Weather Radar (NEXRAD) Reflectivity Mosaics from NOAA MRMS for Alaska, CONUS, Puerto Rico, Guam, and Hawaii for last several hours.Data in each MapLast 24 Hours Map:New Starts - IRWIN Data where any incident that has occured within the last 24 hour time period.Current Large Incidents - IRWIN Data where incidents that have created an ICS 209 document at the type 3 Incident Commander (IC) level and above and are less than 100% contained.Ongoing - IRWIN Data where incidents that do not have a containment, control, or out date.Contained - IRWIN Data where incidents with a containment date but no control or out date.Season Summary Map:Fires by Cause - IRWIN data where any incident (Wildfire) that has occurred year to date displayed by cause. National Incident Feature Service 2019 (Fire Perimeters) - Must be set to 'Approved' and 'Public' to be displayed on the map. Automatically refreshes every five minutes. Data collected using Collector and the National InterAgency Fire Centers ArcGIS OnLine softwareNonActive Fires - Idaho's archived fire perimeters. Fires that are no longer available in the National Incident Feature Service 2019 (Fire Perimeters) because they have been inactive (out) for over a week.Fire History Map:Fire Ignition Points (Current Year) - IRWIN Data where any incident (Wildfire) that has occurred year to date displayed by daily acres Fire Ignition Points (Last 20yrs) - Idaho Fire Management Plan (FMP) locations of wildfire starts occur and a note of general causes for wildfires, since 1980Fire Frequency (Last 20yrs) - Idaho Fire Management Plan (FMP) determining how frequently a piece of ground is ignited and burns. Fires greated then 10 acres only were used in determining frequency. It is known that historical data from prior to the 1980s was inconsistantly recorded and therefore the information reflected in this dataset may not be complete and should be used with discretion.

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.