- 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 Fort Lee, NJ was 17 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 Fort Lee, NJ
- API data.cityofnewyork.us | Last Updated 2019-07-18T19:12:08.000Z
This is a breakdown of every arrest effected in NYC by the NYPD during the current year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning. Each record represents an arrest effected in NYC by the NYPD and includes information about the type of crime, the location and time of enforcement. In addition, information related to suspect demographics is also included. This data can be used by the public to explore the nature of police enforcement activity. Please refer to the attached data footnotes for additional information about this dataset.
- API data.cityofnewyork.us | Last Updated 2019-05-16T18:08:26.000Z
List of every arrest in NYC going back to 2006 through the end of the previous calendar year. This is a breakdown of every arrest effected in NYC by the NYPD going back to 2006 through the end of the previous calendar year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning before being posted on the NYPD website. Each record represents an arrest effected in NYC by the NYPD and includes information about the type of crime, the location and time of enforcement. In addition, information related to suspect demographics is also included. This data can be used by the public to explore the nature of police enforcement activity. Please refer to the attached data footnotes for additional information about this dataset.
- API data.ny.gov | Last Updated 2019-06-10T18:00:48.000Z
The Division of Criminal Justice Services (DCJS) collects personnel statistics from more than 500 New York State police and sheriffs’ departments. In New York State, law enforcement agencies use the Uniform Crime Reporting (UCR) system to report their annual personnel counts to DCJS.
- API data.ny.gov | Last Updated 2019-06-10T17:59:09.000Z
The Port Authority of NY & NJ annually reports on motor vehicle crashes throughout its facilities. The data reported in this dataset represents motor vehicle crashes of vehicles in transport on public trafficways within Port Authority jurisdiction. A crash is a harmful event which involves a motor vehicle in transport that strikes another motor vehicle, other property, debris, animal, pedestrian, or bicyclist, or in which a motor vehicle overturns (rolls over), jackknifes, catches fire or explodes while within the trafficway.
- 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.detroitmi.gov | Last Updated 2019-09-27T14:04:25.000Z
This data reflects reported criminal offenses that have occurred in the City of Detroit since December 6, 2016. Offense data was extracted from the Detroit Police Department's records management system. This data set contains the most recent data available and is updated anytime DPD sends official crime records contributing to the Michigan Incident Crime Reporting (MICR) or the National Incident Based Reporting systems (reflected by the IBR Date field). It should be noted that some incidents involve the commission of multiple offenses, such as a domestic assault where property was also vandalized. Accordingly, the data describe all offenses associated with all reported incidents. In order to protect the privacy of crime victims, addresses are shown at the block level only and the geographic coordinates (longitude and latitude) have been randomly offset by up to 180 feet along the street segment. See the Note on Anonymized Addresses below for more information. For data prior to December 6, 2016, go to https://data.detroitmi.gov/Public-Safety/DPD-All-Crime-Incidents-January-1-2009-December-6-/invm-th67. Please note that DPD launched a new system to collect crime reports on that date, and certain fields of information may not be appropriate to compare between the two systems. Both systems were used to enter reports on December 6, 2016, so neither dataset is inclusive alone of all reports entered on that day. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Intelligence Unit at 313-596-2250, or CrimeIntelligenceBureau@detroitmi.gov. Field Descriptions: Crime ID - text - Numeric offense identifier in Record Management System Report # - text - Unique ID in Record Management System (YYYYMMDD Report Number) Incident Address - text - Location of incident (see Note on Anonymized Addresses for more information) Offense Description - text - Detail about the offense reported Offense Category - text - Type of offense described in the report, categorized State Offense Code - text - Michigan State Police offense code Incident Date & Time - datetime - Date and time of incident Incident Time (24h) - text - Time of incident, based on 24-hour clock Day of Week (Sunday is 1) - number - Numeric code for the day of the week, where Sunday = 1, Monday = 2, etc. Hour of Day - number - Time of incident, based on the hour Year - number - Year of incident Scout Car Area - text - DPD Scout Car Area, a geography within a precinct Precinct Number - number - DPD Precinct IBR Report Date - datetime - The date and time that DPD sent official crime records to the Michigan Incident Crime Reporting (MICR) and the National Incident Based Reporting systems Location - location - Location field generated by Socrata Neighborhood - text - The neighborhood of the original XY coordinate, using the neighborhood file on the City’s Open Data Portal Census Block GEOID - text - The Census Block of the original XY coordinate, using the 2010 Census Blocks provided by the US Census Bureau Council District - text - The Detroit City Council District of the original XY coordinate Note on Anonymized Addresses: DPD works with the Department of Innovation and Technology (DoIT) to de-identify location information for both 911 calls and reported crimes to protect victim and caller information. Each record has two sets of location information - address and XY coordinates. The address field represents the location of the incident, and the XY coordinates are populated based on the geo-verified location of that address. The anonymization process systematically takes the point of the original XY coordinates and places them randomly within 180 feet along the street from the original point. If the point appears on either side of the street, it does so randomly, and it is not an indication of where the original event occurred. The XY coordinate fields provided in this dataset are t
- API apd-data.albanyny.gov | Last Updated 2019-08-25T16:01:18.000Z
Dataset highlighting arrests by Albany PD Officers for the past year to date GeoCoded by Neighborhood. It is the same data as Arrests by Beat and by Patrol Zone For purposes of crime statistics, the FBI Uniform Crime Report Hierarchy Rule requires when more than one offense occurs in an incident the highest priority crime is selected as the primary offense.
- API data.pa.gov | Last Updated 2019-10-07T17:29:19.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.cityofnewyork.us | Last Updated 2019-07-18T19:11:15.000Z
List of every shooting incident that occurred in NYC during the current calendar year. This is a breakdown of every shooting incident that occurred in NYC during the current calendar year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning before being posted on the NYPD website. Each record represents a shooting incident in NYC and includes information about the event, the location and time of occurrence. In addition, information related to suspect and victim demographics is also included. This data can be used by the public to explore the nature of police enforcement activity. Please refer to the attached data footnotes for additional information about this dataset.
- API apd-data.albanyny.gov | Last Updated 2019-08-25T16:01:19.000Z
Dataset highlighting arrests by Albany PD Officers for the past year to date GeoCoded by Patrol Zone. It is the same data as Arrests by Beat and by Neighborhood For purposes of crime statistics, the FBI Uniform Crime Report Hierarchy Rule requires when more than one offense occurs in an incident the highest priority crime is selected as the primary offense.