- What is the Crime incident rate per 100,000 people?
- What is the Population Count?
- What is the Population Density?
- What is the Land Area?
- What is the Percent who did not finish the 9th grade?
- What is the Median Earnings?
- What is the Number of Employees?
- What is the Population Rate of Change?
- What is the Water Area?
- What is the High School Graduation Rate?
The crime incident count of Mount Pleasant, SC was 113 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 Mount Pleasant, SC
- API data.montgomerycountymd.gov | Last Updated 2020-10-28T07:30:43.000Z
Updated daily postings on Montgomery County’s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions – of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by “EJustice”, a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims’ privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation. dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect: -Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law.] Update Frequency: Daily
- API data.lacity.org | Last Updated 2020-09-30T17:15:36.000Z
This dataset reflects arrest incidents in the City of Los Angeles from 2010 to 2019. This data is transcribed from original arrest reports that are typed on paper and therefore there may be some inaccuracies within the data. Some location fields with missing data are noted as (0.0000°, 0.0000°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.
- 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-10-27T10:45:25.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.everettwa.gov | Last Updated 2020-10-28T10:15:51.000Z
Police Cases represent all police incidents that result in a police report being generated by the responding officer. Case reports involving domestic violence, child abuse, or sex offenses involving minors are not reported.
- 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 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.lacity.org | Last Updated 2020-09-30T17:22:20.000Z
This dataset reflects arrest incidents in the City of Los Angeles from 2020 to present. This data is transcribed from original arrest reports that are typed on paper and therefore there may be some inaccuracies within the data. Some location fields with missing data are noted as (0.0000°, 0.0000°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.
- API stat.cityofgainesville.org | Last Updated 2018-02-02T14:54:55.000Z
- API data.ct.gov | Last Updated 2014-10-29T14:57:20.000Z
The Uniform Crime Reporting Program measures the extent, fluctuation and distribution of crime throughout the United States. After counting Crime Index offenses reported, minus any unfounded complaints, contributors provide the number of “actual offenses” and the number of crimes cleared. For a criminal offense to be “cleared,” either of the following situations must prevail: (1) at least one person is arrested, charged, and turned over to the court for prosecution; or (2) some element beyond police control precludes the physical arrest of the offender (e.g., death of offender, victim refuses to cooperate, confession by offender already in police custody), resulting in the offense being cleared by “exceptional means.” Contributing agencies also include data on the value of property stolen and recovered in connection with the reported offenses, plus specific information regarding homicides, officers assaulted and arson.