The crime incident count of Orlando, FL was 1,415 for aggravated assault in 2018. The crime incident count of Tampa, FL was 1,139 for aggravated assault in 2018.

Crime Incident Count

Crime Incident Rate per 100,000 People

Crime statistics are sourced from the FBI Uniform Crime Reporting Program and aggregated across year and crime type. The FBI does not gather statistics for all jurisdictions, so some localities may be missing. Normalization is based on the population values published with the UCR data itself, so rather than on US Census data, as the jurisdiction of the data may vary. Crime rates are normalized on a per 100K basis; specifically, the crime count is divided by the population count, the result is then multiplied by 100K and rounded to the nearest integer value. Latest data, displayed in charts and other visualizations, is from 2014.

Above charts are based on data from the FBI Uniform Crime Reporting Program | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to http://opendatanetwork.com. Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Public Safety and Crime Datasets Involving Orlando, FL or Tampa, FL

  • API

    OPD Crimes

    data.cityoforlando.net | Last Updated 2020-09-29T13:47:19.000Z

    This dataset comes from the Orlando Police Department records management system. It includes all Part 1 and Part 2 crimes as defined by the FBI’s Uniform Crime Reporting standards. When multiple crimes are committed the highest level of crime is what is shown. The data includes only Open and Closed cases and does not include informational cases without arrests. This data excludes crimes where the victim or offender data is or could be legally protected. Those include: Cases that are flagged as: Domestic Violence Elderly Abuse Exempt from Public Record Witness Protection Cases where the offender was charged with the following case codes/state statutes: Sexual Battery Child Abuse Aggravated Stalking/Harassment Obscene or harassing telephone calls Aggravated Battery Domestic Violence Injunctions Lewd,Lascivious or Indecent Assault upon or in the presence of a child Elder Abuse Baker Act Obscenity Forcible Rape Forcible Sodomy Forcible Fondling Cases where the a juvenile is arrested Fields in the OPD Crimes Data Set: Case Number - Automatically assigned at the time the incident is created in OPD records management system. First four characters indicate the year the incident was created in the system. Case Date Time - Day and time of the incident Case Location - Block level address or intersection of the location Case Offense Category - Category of the highest crime committed attempted Case Offense Type - Type of the highest crime committed or attempted Case Offense Charge Type - Indication of if the crime was committed or attempted Case Disposition - Indication of the status or disposition given for this case Status - This is an information only field to designate if the City was able to map the Incident Location to a latitude and longitude Location - Mapped latitude and longitude to the center of the block at the middle of the street of Incident Location Disclaimer: The data is derived from the Orlando Police Department’s Records Management Systems, we acknowledge there is always the possibility of mechanical or human error. The City of Orlando does not guarantee the accuracy of the information. The City of Orlando will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. Additionally, because OPD policy and operations regarding reporting might change, the data may have limited value for comparisons over time

  • API

    Police Calls

    stat.stpete.org | Last Updated 2020-10-19T20:15:39.000Z

    The following data is from the St. Petersburg Police Department’s Computer-Aided Dispatch (CAD) system. Under Florida State Statute 119.071, victim information (i.e. addresses) associated with Sexual Battery, Sexual Offenses, Child Abuse, and Adult Abuse are considered confidential and exempt from public release. The data includes all officer responses to Priority 1, 2, 3, 4, 6, 7 and 9, calls for service. These calls for service don’t necessarily result in official police reports under UCR (Uniform Crime Reporting) standards. The calls do not include the Forensic Technicians, Off Duty, Administrative or similarly classified calls.

  • API

    Adult Arrests

    fortlauderdale.data.socrata.com | Last Updated 2020-10-19T06:04:13.000Z

    Adult arrests in Fort Lauderdale 2015-2020

  • API

    Crime Responses

    data.cityofgainesville.org | Last Updated 2020-10-19T16:36:44.000Z

    Crime Responses is provided by the Gainesville Police Department (GPD) to document initial details surrounding an incident to which GPD officers respond. This dataset contains crime incidents from 2011 to present and includes a reduced set of fields focused on capturing the type of incident as well when and where an incident occurred. The Incident location addresses have been rounded off and are not the exact location due to the constitutional amendment known as "Marsy's Law"

  • API

    Racial Profiling Dataset 2015- Citations

    data.austintexas.gov | Last Updated 2019-07-29T17:18:39.000Z

    In order to protect the privacy of crime victims, addresses are generalized to the block level only and specific locations are not identified. Due to several factors (offense reclassification, reported versus occurred dates, etc.) comparisons should not be made between numbers generated with this database to any other official police reports. Data provided represents only calls for police service where a report was written. Totals in the database may vary considerably from official totals following investigation and final categorization. Therefore, the data should not be used for comparisons with Uniform Crime Report statistics. The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided. This Racial Profiling dataset (citations) provides the raw data needed to identify trends in traffic stops. It is used to help identify potential improvements in department policy, tactics, and training. Corresponding report: This data is used to produce the annual Racial Profiling report, posted on APD's website here: http://www.austintexas.gov/page/racial-profiling-reports

  • API

    Arrests

    data.cityofchicago.org | Last Updated 2020-10-19T10:46:03.000Z

    Each record in this dataset shows information about an arrest executed by the Chicago Police Department (CPD). Source data comes from the CPD Automated Arrest application. This electronic application is part of the CPD CLEAR (Citizen Law Enforcement Analysis and Reporting) system, and is used to process arrests Department-wide. A more detailed version of this dataset is available to media by request. To make a request, please email dataportal@cityofchicago.org. New data fields may be added to this public dataset in the future. The data is limited to adult arrests, defined as any arrest where the arrestee was 18 years of age or older on the date of arrest. The data excludes arrest records expunged by CPD pursuant to the Illinois Criminal Identification Act (20 ILCS 2630/5.2). Department members use charges that appear in Illinois Compiled Statutes or Municipal Code of Chicago. Arrestees may be charged with multiple offenses from these sources. Each record in the dataset includes up to four charges, ordered by severity and with CHARGE1 as the most severe charge. Severity is defined based on charge class and charge type, criteria that are routinely used by Illinois court systems to determine penalties for conviction. In case of a tie, charges are presented in the order that the arresting officer listed the charges on the arrest report. By policy, Department members are provided general instructions to emphasize seriousness of the offense when ordering charges on an arrest report. Each record has an additional set of columns where a charge characteristic (statute, description, type, or class) for all four charges, or fewer if there were not four charges, is concatenated with the | character. These columns can be used with the Filter function's "Contains" operator to find all records where a value appears, without having to search four separate columns. Users interested in learning more about CPD arrest processes can review current directives, using the CPD Automated Directives system (http://directives.chicagopolice.org/directives/). Relevant directives include: • Special Order S06-01-11 – CLEAR Automated Arrest System: describes the application used by Department members to enter arrest data. • Special Order S06-01-04 – Arrestee Identification Process: describes processes related to obtaining and using CB numbers. • Special Order S09-03-04 – Assignment and Processing of Records Division Numbers: describes processes related to obtaining and using RD numbers. • Special Order 06-01 – Processing Persons Under Department Control: describes required tasks associated with arrestee processing, include the requirement that Department members order charges based on severity.

  • API

    Opioid Seizures and Arrests CY 2013 - Current Quarterly County State Police

    data.pa.gov | Last Updated 2020-10-19T17:39:59.000Z

    This dataset contains summary information on opioid drug seizures and arrests made by Pennsylvania State Police (PSP) personnel, stationed statewide, on a quarterly basis. Every effort is made to collect and record all opioid drug seizures and arrests however, the information provided may not represent the totality of all seizures and opioid arrests made by PSP personnel. Data is currently available from January 1, 2013 through most current data available. Seizure Opioids seized as a result of undercover buys, search warrants, traffic stops and other investigative encounters. An incident is a Pennsylvania State Police (PSP) recorded violation of the Controlled Substance Act and an entry into the PSP Statistical Narcotics System. By regulation, entry is made by the PSP as stated in PSP Administrative Regulation 9-6: When violations of The Controlled Substance, Drug, Device and Cosmetic Act are reported, the required statistical information concerning the incident shall be entered into the Statistical Narcotic Reporting System (SNRS). Incidents may include undercover buys, search warrants, traffic stops and other investigative encounters So, an “incident” is not based on any arrest, but on a reported violation, though it often can include arrests. The incidents that are selected and forwarded to the portal are those that include a record of one or more seizures of the opioid drugs. In turn, a subset of those selected incidents also contains a record of one or more arrests. This is PSP data only, it would not include any Federal case/incident data.

  • API

    Tampa CV Pilot Basic Safety Message (BSM) Sample

    datahub.transportation.gov | Last Updated 2020-10-18T22:43:36.000Z

    The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Basic Safety Messages (BSMs) generated by participant and public transportation vehicles onboard units (OBU) and transmitted to road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, BSM data from Tampa CV Pilot can be found in the <a href="http://usdot-its-cvpilot-public-data.s3.amazonaws.com/index.html" target="_blank" >ITS Sandbox</a>. The data fields follow SAE J2735 and J2945/1 standards and adopted units of measure. This data set holds a flattened sample of the most recent BSM data from Tampa CV Pilot and is updated nightly. An extra geo column (coreData_position) was added to this dataset to allow for mapping of the geocoded BSM data within Socrata, and a column of random numbers (randomNum) was added to allow for random sampling of data points within Socrata.

  • API

    2017 Racial Profiling Dataset Citations

    data.austintexas.gov | Last Updated 2019-07-29T17:29:51.000Z

    AUSTIN POLICE DEPARTMENT DATA DISCLAIMER 1. The data provided are for informational use only and may differ from official APD crime data. 2. APD’s crime database is continuously updated, so reports run at different times may produce different results. Care should be taken when comparing against other reports as different data collection methods and different data sources may have been used. 3. The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided.

  • API

    GPD Metrics

    stat.cityofgainesville.org | Last Updated 2018-02-02T14:54:55.000Z