- 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 West St. Paul, MN was 51 for aggravated assault in 2017.
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 West St. Paul, MN
- API information.stpaul.gov | Last Updated 2019-07-16T17:41:43.000Z
This data was provided by the St. Paul Police Department and contains all available information relating to bike and pedestrian crashes in St. Paul. As part of its commitment to improving pedestrian and bike safety, the city of St. Paul began aggressively tracking bike and pedestrian crashes in 2016. Data comes from traditional sources such as the State of MN Police Crash Report System and police reports. It also comes from social media, community conversations, police calls (911 and non-emergency) where no report was made, and other non-traditional ways to verify that a crash occurred. By collecting this level of detail for every pedestrian and bike crash in St. Paul, we are hoping to find patterns and answers to help us reach our goal of reducing the number of crashes and improving safety for all residents and visitors of St. Paul. For more information, please visit the city of Saint Paul's website: https://www.stpaul.gov/departments/police/pedestrian-and-bike-crash-data-city-st-paul
- API information.stpaul.gov | Last Updated 2019-03-06T16:07:33.000Z
In 2001, the Saint Paul Police Department began collecting data on traffic stops as part of an agreement with the Saint Paul Chapter of the NAACP. The department uses a data collection system to gather information about all traffic stops made by its officers. This data includes: • Total number of traffic stops • Traffic stops by race and gender • Driver searches by race and gender • Vehicle searches by race and gender • Reason for stop (available starting in 2017) The maps and graphs on this site are the police department’s best effort to show and understand the data. While reviewing the information, please note: • Graphs and charts are created using raw data • Data reflects traffic stops originating by St. Paul Police Officers • Race is based on officers’ perceptions • Fields indicating “No Data” may be due to a variety of factors, including: - Age data is only collected when a citation is issued - Reason for stop data was not collected before 2017 - Technology changes over time - Technical errors - Lack of available information To better understand how the data reflects officers’ day-to-day activities, please click on the maps below. It may be helpful to see where most of the calls for service originate, where traffic crashes occur, and in which grids stops are made. About the Saint Paul Police Department: The Saint Paul Police Department employs approximately 800 people, including more than 625 sworn officers. The department responds to approximately 300,000 calls for service and investigates about 13,000 Part I crimes each year. Officers and employees work to promote safe and healthy neighborhoods by providing Trusted Service with Respect. Additional City of Saint Paul demographics data may be found at https://www.stpaul.gov/books/race
- API data.montgomerycountymd.gov | Last Updated 2019-09-21T07:30:38.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.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.pa.gov | Last Updated 2019-09-11T15:51:05.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 stat.cityofgainesville.org | Last Updated 2018-02-02T14:54:55.000Z
- API data.colorado.gov | Last Updated 2019-06-04T20:32:20.000Z
Crime stats for the State of Colorado from 1997 to 2015. Data provided by the CDPS and the FBI's Crime Data Explorer (CDE).
- API data.ct.gov | Last Updated 2014-09-23T19:30:41.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.
- API data.ct.gov | Last Updated 2014-11-13T16:01:54.000Z
Arrests are the number of persons arrested, cited or summoned for all criminal acts in Part I and Part II Crimes