The crime incident count of Chandler, AZ was 333 for aggravated assault in 2018. The crime incident count of Gilbert, AZ was 125 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.
Public Safety and Crime Datasets Involving Gilbert, AZ or Chandler, AZ
- API 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 data.cityofchicago.org | Last Updated 2020-11-27T11:46:02.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 firstname.lastname@example.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 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 citydata.mesaaz.gov | Last Updated 2020-11-27T14:15:24.000Z
Calls for service dispatched to Mesa Police Patrol Officers. Calls are modified for public use, obfuscating the address number through rounding it to the 100 block. Note that these are calls for service and may not necessarily correspond to the data located in the Police Incidents dataset. Crimes reported in this data set have not been adjudicated in a court of law for final determination. Sensitive crimes are listed but the address of their occurrence will NOT be included. In this way aggregate totals of crimes will be accurate, without providing sensitive information. Addresses where the following crime types occur will NOT be captured: Sexual abuse, Sexual assault, Suicide, Incest, Molestation of a child and Homicide. Emergency (E) Calls: Life threatening or confrontations which may threaten life or safety of a person. Priority One Call: In progress crime that could result in a threat to injure or possible major property loss or immediate apprehension of a suspect. Accidents with injury or other traffic incidents that create a traffic hazard. Priority Two Calls: Minor in-progress/just occurred calls, where there is no threat of injury or major property loss. Priority Three Calls: Nuisance calls, civil standbys, delayed reports where reporting party (RP) is at public location. Priority Four Calls: Calls where a delay will not result in a crime occurring or the loss of an apprehension or an injured person not receiving aid. Priority Five Calls: Calls with no time requirement for dispatch. Calls where a delay will not result in a crime occurring or the loss of an apprehension or an injured person not receiving aid where the priority is approved by a supervisor. Priority Six Calls: On-view calls. An officer on view or officer initiated case.
- API 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 datahub.transportation.gov | Last Updated 2020-06-23T04:14:30.000Z
The WZDx Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones into vehicles to help automated driving systems (ADS) and human drivers navigate more safely. MCDOT leads the effort to aggregate and collect work zone data from the AZTech Regional Partners. A continuously updating archive of the WZDx feed data can be found at <a href="http://usdot-its-workzone-public-data.s3.amazonaws.com/index.html" target="_blank" rel="noopener">ITS WorkZone Data Sandbox</a>. The live feed is currently compliant with <a href="https://github.com/usdot-jpo-ode/jpo-wzdx/tree/v1.1" target="_blank" rel="noopener">WZDx specification version 1.1</a>.
- API stat.cityofgainesville.org | Last Updated 2018-02-02T14:54:55.000Z
- API datahub.transportation.gov | Last Updated 2020-10-14T14:23:10.000Z
The WZDx Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones into vehicles to help automated driving systems (ADS) and human drivers navigate more safely. MCDOT leads the effort to aggregate and collect work zone data from the AZTech Regional Partners. A continuously updating archive of the WZDx feed data can be found at <a href="http://usdot-its-workzone-public-data.s3.amazonaws.com/index.html" target="_blank" rel="noopener">ITS WorkZone Data Sandbox</a>. The live feed is currently compliant with <a href="https://github.com/usdot-jpo-ode/jpo-wzdx/tree/v3.0" target="_blank" rel="noopener">WZDx specification version 3.0</a>.