The crime incident count of Alhambra, CA was 88 for aggravated assault in 2018. The crime incident count of Tustin, CA was 58 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 Alhambra, CA or Tustin, CA
- API performance.smcgov.org | Last Updated 2016-08-31T20:40:07.000Z
Violent and property crime rates per 100,000 population for San Mateo County and the State of California. The total crimes used to calculate the rates for San Mateo County include data from: Sheriff's Department Unincorporated, Atherton, Belmont, Brisbane, Broadmoor, Burlingame, Colma, Daly City, East Palo Alto, Foster City, Half Moon Bay, Hillsborough, Menlo Park, Millbrae, Pacifica, Redwood City, San Bruno, San Carlos, San Mateo, South San Francisco, Bay Area DPR, BART, Union Pacific Railroad, and CA Highway Patrol.
- API data.marincounty.org | Last Updated 2020-07-11T03:05:07.000Z
Reported crimes of the Marin County Sheriff's Department. Data is updated every four hours. Data begins as of January 1, 2013. Each reported crime includes its date/time, approximate location, crime type, and crime classification. NOTE: For the safety and security of victims of crimes, street address locations, other than reported street intersections or highway locations, are not exact. They are adjusted to the nearest block level. There are two columns of city/town information. The first is the reported city/town name in the crime records. The second, which is not in the crime records, is a translation of it into the more commonly known city/town name, or into Marin County when it appears to be in an unincorporated area. For example, Almonte and Tam Valley are reported city/town names, but they are both in the more commonly known city of Mill Valley. Lucas Valley translates to San Rafael, etc. We hope that the translated city/town column will facilitate analysis.
- 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.sfgov.org | Last Updated 2020-07-01T19:04:13.000Z
This dataset contains information on all cases entering the District Attorney's Office for prosecution. More information on the incoming caseload can be found here: https://sfdistrictattorney.org/incoming-caseload This dataset includes information on all incoming cases except for a small selection of infrequent or inactive disposition codes, as well as those cases that have been sealed or expunged due to record clearance protocols
- API data.pa.gov | Last Updated 2020-04-14T18:52:58.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 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 data.cityofchicago.org | Last Updated 2020-07-10T21:55:31.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 stat.cityofgainesville.org | Last Updated 2018-02-02T14:54:55.000Z
- API www.transparentrichmond.org | Last Updated 2020-07-10T15:00:11.000Z
Officers engaged in police pursuits must continually balance the safety of the public and themselves against law enforcement's duty to apprehend law violators. Officers must discontinue a pursuit whenever circumstances indicate that continuation of the pursuit would be unsafe or when life or property is endangered. This dataset shows vehicle pursuit data provided to the California Highway Patrol.