- 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 41 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 West St. Paul, MN
- API www.dallasopendata.com | Last Updated 2021-10-22T10:46:06.000Z
The calls listed here are only those where the element assigned to the call has arrived and is currently working the call. It does not include any calls for service, whether currently being worked or not, that are not releasable due to privacy laws.
- 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 www.dallasopendata.com | Last Updated 2021-10-21T13:01:34.000Z
Dallas Police Public Data - Unknown Suspects
- API www.dallasopendata.com | Last Updated 2021-10-18T13:06:42.000Z
Dallas Police Public Data - Officer Involved Shootings City Of Dallas
- API information.stpaul.gov | Last Updated 2021-05-28T21:18:45.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 an authorized strength of 620 sworn officers. The department responds to approximately 250,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 2021-10-22T07:30:54.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.ramseycounty.us | Last Updated 2021-10-01T17:04:08.000Z
This dataset shows calls for service for police and fire agencies served by Ramsey County Emergency Communications Center. Geolocation references city and zip code, not a precise location.
- API www.dallasopendata.com | Last Updated 2021-08-13T14:39:26.000Z
Police: 2015 Response to Resistance
- API data.austintexas.gov | Last Updated 2021-04-14T22:07:43.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 2021-10-21T10:52:43.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 <a href="mailto:email@example.com?subject=Arrests Access Request">firstname.lastname@example.org</a> with the subject line: <b>Arrests Access Request</b>. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup. 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.