57 datasets found
  1. O

    Law Enforcement Facilities

    • data.oregon.gov
    • hub.arcgis.com
    application/rdfxml +5
    Updated Jan 29, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2025). Law Enforcement Facilities [Dataset]. https://data.oregon.gov/dataset/Law-Enforcement-Facilities/fhzx-esp8
    Explore at:
    application/rdfxml, json, csv, tsv, application/rssxml, xmlAvailable download formats
    Dataset updated
    Jan 29, 2025
    Description

    Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 06/27/2006 and the newest record dates from 10/22/2009

  2. u

    HSIP Law Enforcement Locations in New Mexico

    • gstore.unm.edu
    • s.cnmilf.com
    • +1more
    Updated Feb 4, 2010
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2010). HSIP Law Enforcement Locations in New Mexico [Dataset]. http://gstore.unm.edu/apps/rgis/datasets/faeb3a73-8c0d-40f2-9d69-6075aa1e108e/metadata/ISO-19115:2003.html
    Explore at:
    Dataset updated
    Feb 4, 2010
    Time period covered
    Aug 14, 2006
    Area covered
    New Mexico, West Bound -108.84618475534 East Bound -103.049692021254 North Bound 36.9348613580651 South Bound 31.7845116518986
    Description

    Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes are included due to the fact that the New Mexico Mounted Police work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 08/14/2006 and the newest record dates from 10/23/2009

  3. FiveThirtyEight Police Locals Dataset

    • kaggle.com
    Updated Mar 26, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    FiveThirtyEight (2019). FiveThirtyEight Police Locals Dataset [Dataset]. https://www.kaggle.com/fivethirtyeight/fivethirtyeight-police-locals-dataset/code
    Explore at:
    CroissantCroissant is a format for machine-learning datasets. Learn more about this at mlcommons.org/croissant.
    Dataset updated
    Mar 26, 2019
    Dataset provided by
    Kagglehttp://kaggle.com/
    Authors
    FiveThirtyEight
    License

    https://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/

    Description

    Content

    Police Residence

    This folder contains data behind the story Most Police Don’t Live In The Cities They Serve.

    Includes the cities with the 75 largest police forces, with the exception of Honolulu for which data is not available. All calculations are based on data from the U.S. Census.

    The Census Bureau numbers are potentially going to differ from other counts for three reasons:

    1. The census category for police officers also includes sheriffs, transit police and others who might not be under the same jurisdiction as a city’s police department proper. The census category won’t include private security officers.
    2. The census data is estimated from 2006 to 2010; police forces may have changed in size since then.
    3. There is always a margin of error in census numbers; they are estimates, not complete counts.

    How to read police-locals.csv

    HeaderDefinition
    cityU.S. city
    police_force_sizeNumber of police officers serving that city
    allPercentage of the total police force that lives in the city
    whitePercentage of white (non-Hispanic) police officers who live in the city
    non-whitePercentage of non-white police officers who live in the city
    blackPercentage of black police officers who live in the city
    hispanicPercentage of Hispanic police officers who live in the city
    asianPercentage of Asian police officers who live in the city

    Note: When a cell contains ** it means that there are fewer than 100 police officers of that race serving that city.

    Context

    This is a dataset from FiveThirtyEight hosted on their GitHub. Explore FiveThirtyEight data using Kaggle and all of the data sources available through the FiveThirtyEight organization page!

    • Update Frequency: This dataset is updated daily.

    Acknowledgements

    This dataset is maintained using GitHub's API and Kaggle's API.

    This dataset is distributed under the Attribution 4.0 International (CC BY 4.0) license.

  4. Police Stations

    • gisnation-sdi.hub.arcgis.com
    • colorado-geospatial-cooit.hub.arcgis.com
    • +1more
    Updated Jun 30, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri U.S. Federal Datasets (2021). Police Stations [Dataset]. https://gisnation-sdi.hub.arcgis.com/maps/fedmaps::police-stations
    Explore at:
    Dataset updated
    Jun 30, 2021
    Dataset provided by
    Esrihttp://esri.com/
    Authors
    Esri U.S. Federal Datasets
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Law Enforcement StructuresThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Geological Survey (USGS), displays police and prison landmarks in the U.S. Per the USGS, "Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations."Police Stations and Prison Correctional FacilitiesData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Law Enforcement) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 135 (USGS National Structures Dataset - USGS National Map Downloadable Data Collection)OGC API Features Link: (Law Enforcement Structures - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: The National MapFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Theme CommunityThis data set is part of the NGDA Real Property Theme Community. Per the Federal Geospatial Data Committee (FGDC), Real Property is defined as "the spatial representation (location) of real property entities, typically consisting of one or more of the following: unimproved land, a building, a structure, site improvements and the underlying land. Complex real property entities (that is "facilities") are used for a broad spectrum of functions or missions. This theme focuses on spatial representation of real property assets only and does not seek to describe special purpose functions of real property such as those found in the Cultural Resources, Transportation, or Utilities themes."For other NGDA Content: Esri Federal Datasets

  5. A

    ‘Police Killings US’ analyzed by Analyst-2

    • analyst-2.ai
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com), ‘Police Killings US’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/kaggle-police-killings-us-57e7/747b1181/?iid=008-252&v=presentation
    Explore at:
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Analysis of ‘Police Killings US’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/azizozmen/police-killings-us on 13 February 2022.

    --- Dataset description provided by original source is as follows ---

    "In 2015, The Washington Post began to log every fatal shooting by an on-duty police officer in the United States. In that time there have been more than 5,000 such shootings recorded by The Post. After Michael Brown, an unarmed Black man, was killed in 2014 by police in Ferguson, Mo., a Post investigation found that the FBI undercounted fatal police shootings by more than half. This is because reporting by police departments is voluntary and many departments fail to do so. The Washington Post’s data relies primarily on news accounts, social media postings, and police reports. Analysis of more than five years of data reveals that the number and circumstances of fatal shootings and the overall demographics of the victims have remained relatively constant..." SOURCE ==> Washington Post Article

    For more information about this story

    This dataset has been prepared by The Washington Post (they keep updating it on runtime) with every fatal shooting in the United States by a police officer in the line of duty since Jan. 1, 2015.

    2016 PoliceKillingUS DATASET
    2017 PoliceKillingUS DATASET
    2018 PoliceKillingUS DATASET
    2019 PoliceKillingUS DATASET
    2020 PoliceKillingUS DATASET

    Features at the Dataset:

    The file fatal-police-shootings-data.csv contains data about each fatal shooting in CSV format. The file can be downloaded at this URL. Each row has the following variables:

    • id: a unique identifier for each victim
    • name: the name of the victim
    • date: the date of the fatal shooting in YYYY-MM-DD format
    • manner_of_death: shot, shot and Tasered
    • armed: indicates that the victim was armed with some sort of implement that a police officer believed could inflict harm
      • undetermined: it is not known whether or not the victim had a weapon
      • unknown: the victim was armed, but it is not known what the object was
      • unarmed: the victim was not armed
    • age: the age of the victim
    • gender: the gender of the victim. The Post identifies victims by the gender they identify with if reports indicate that it differs from their biological sex.
      • M: Male
      • F: Female
      • None: unknown
    • race:
      • W: White, non-Hispanic
      • B: Black, non-Hispanic
      • A: Asian
      • N: Native American
      • H: Hispanic
      • O: Other
      • None: unknown
    • city: the municipality where the fatal shooting took place. Note that in some cases this field may contain a county name if a more specific municipality is unavailable or unknown.
    • state: two-letter postal code abbreviation
    • signs of mental illness: News reports have indicated the victim had a history of mental health issues, expressed suicidal intentions or was experiencing mental distress at the time of the shooting.
    • threat_level: The threat_level column was used to flag incidents for the story by Amy Brittain in October 2015. http://www.washingtonpost.com/sf/investigative/2015/10/24/on-duty-under-fire/ As described in the story, the general criteria for the attack label was that there was the most direct and immediate threat to life. That would include incidents where officers or others were shot at, threatened with a gun, attacked with other weapons or physical force, etc. The attack category is meant to flag the highest level of threat. The other and undetermined categories represent all remaining cases. Other includes many incidents where officers or others faced significant threats.
    • flee: News reports have indicated the victim was moving away from officers
      • Foot
      • Car
      • Not fleeing

    The threat column and the fleeing column are not necessarily related. For example, there is an incident in which the suspect is fleeing and at the same time turns to fire at gun at the officer. Also, attacks represent a status immediately before fatal shots by police while fleeing could begin slightly earlier and involve a chase. - body_camera: News reports have indicated an officer was wearing a body camera and it may have recorded some portion of the incident.

    SOURCE

    --- Original source retains full ownership of the source dataset ---

  6. n

    Law Enforcement Locations

    • nconemap.gov
    • hub.arcgis.com
    • +1more
    Updated Dec 30, 2009
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NC OneMap / State of North Carolina (2009). Law Enforcement Locations [Dataset]. https://www.nconemap.gov/datasets/law-enforcement-locations
    Explore at:
    Dataset updated
    Dec 30, 2009
    Dataset authored and provided by
    NC OneMap / State of North Carolina
    License

    https://www.nconemap.gov/pages/termshttps://www.nconemap.gov/pages/terms

    Area covered
    Description

    Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 08/10/2006 and the newest record dates from 10/22/2009

  7. d

    Civilian Complaint Review Board: Complaints Against Police Officers

    • catalog.data.gov
    • data.cityofnewyork.us
    Updated Jun 29, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.cityofnewyork.us (2025). Civilian Complaint Review Board: Complaints Against Police Officers [Dataset]. https://catalog.data.gov/dataset/civilian-complaint-review-board-complaints-against-police-officers
    Explore at:
    Dataset updated
    Jun 29, 2025
    Dataset provided by
    data.cityofnewyork.us
    Description

    The primary table for all public data on complaints, including dates, locations and the outcomes of closed complaints received since the year 2000. The dataset is part of a database of all public police misconduct records the Civilian Complaint Review Board (CCRB) maintains on complaints against New York Police Department uniformed members of service received in CCRB's jurisdiction since the year 2000, when CCRB's database was first built. This data is published as four tables: Civilian Complaint Review Board: Police Officers Civilian Complaint Review Board: Complaints Against Police Officers Civilian Complaint Review Board: Allegations Against Police Officers Civilian Complaint Review Board: Penalties A single complaint can include multiple allegations, and those allegations may include multiple subject officers and multiple complainants. Public records exclude complaints and allegations that were closed as Mediated, Mediation Attempted, Administrative Closure, Conciliated (for some complaints prior to the year 2000), or closed as Other Possible Misconduct Noted. This database is inclusive of prior datasets held on Open Data (previously maintained as "Civilian Complaint Review Board (CCRB) - Complaints Received," "Civilian Complaint Review Board (CCRB) - Complaints Closed," and "Civilian Complaint Review Board (CCRB) - Allegations Closed") but includes information and records made public by the June 2020 repeal of New York Civil Rights law 50-a, which precipitated a full revision of what CCRB data could be considered public.

  8. d

    Law Enforcement Locations.

    • datadiscoverystudio.org
    • data.wu.ac.at
    Updated Dec 8, 2014
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2014). Law Enforcement Locations. [Dataset]. http://datadiscoverystudio.org/geoportal/rest/metadata/item/fa287428d04d4219aa88a9304bac46cd/html
    Explore at:
    Dataset updated
    Dec 8, 2014
    Description

    description: Law Enforcement Locations in Kansas Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS is deleting these locations as we become aware of them, but some probably still exist in this dataset. Personal homes, administrative offices and temporary locations are intended to be excluded from this dataset, but a few may be included. Personal homes of constables may exist due to fact that many constables work out of their home. FBI entites are intended to be excluded from this dataset, but a few may be included. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2006/06/27 and the newest record dates from 2008/03/06; abstract: Law Enforcement Locations in Kansas Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS is deleting these locations as we become aware of them, but some probably still exist in this dataset. Personal homes, administrative offices and temporary locations are intended to be excluded from this dataset, but a few may be included. Personal homes of constables may exist due to fact that many constables work out of their home. FBI entites are intended to be excluded from this dataset, but a few may be included. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2006/06/27 and the newest record dates from 2008/03/06

  9. T

    Utah Law Enforcement

    • opendata.utah.gov
    • opendata.gis.utah.gov
    • +2more
    application/rdfxml +5
    Updated Mar 20, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Utah Law Enforcement [Dataset]. https://opendata.utah.gov/dataset/Utah-Law-Enforcement/az9m-juif
    Explore at:
    tsv, json, csv, xml, application/rssxml, application/rdfxmlAvailable download formats
    Dataset updated
    Mar 20, 2020
    Area covered
    Utah
    Description

    Law Enforcement Locations in Utah Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS is deleting these locations as we become aware of them, but some probably still exist in this dataset. Personal homes, administrative offices and temporary locations are intended to be excluded from this dataset, but a few may be included. Personal homes of constables may exist due to fact that many constables work out of their home. FBI entites are intended to be excluded from this dataset, but a few may be included. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2006/06/27 and the newest record dates from 2013/05/20

    Last Update: March 6, 2014

  10. b

    US Crime Dataset

    • brightdata.com
    .json, .csv, .xlsx
    Updated May 21, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bright Data (2024). US Crime Dataset [Dataset]. https://brightdata.com/products/datasets/crime/us
    Explore at:
    .json, .csv, .xlsxAvailable download formats
    Dataset updated
    May 21, 2024
    Dataset authored and provided by
    Bright Data
    License

    https://brightdata.com/licensehttps://brightdata.com/license

    Area covered
    Worldwide, United States
    Description

    We will build you a custom US crime dataset based on your needs. Data points may include date, time, location, crime type, crime description, victim demographics, offender demographics, arrest records, charges filed, court outcomes, police department response time, incident outcome, weapon used, property stolen or damaged, crime location type, and other related data.

    Use our US crime datasets for a range of applications to enhance public safety and policy effectiveness. Analyzing these datasets can help organizations understand crime patterns and trends across different regions of the United States, enabling them to tailor their strategies and interventions accordingly. Depending on your needs, you may access the entire dataset or a customized subset.

    Popular use cases include: improving public safety measures, designing targeted crime prevention programs, resource allocation for law enforcement, and more.

  11. a

    Police Stations

    • digital.atlas.gov.au
    Updated Dec 11, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Digital Atlas of Australia (2023). Police Stations [Dataset]. https://digital.atlas.gov.au/datasets/police-stations/about
    Explore at:
    Dataset updated
    Dec 11, 2023
    Dataset authored and provided by
    Digital Atlas of Australia
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Abstract This dataset is a subset of The Emergency Management Facilities dataset and contains Police Stations. The Emergency Management Facilities dataset presents the spatial locations, in point format, of all known police stations, ambulance stations, metropolitan fire facilities, rural fire facilities, SES facilities and other (AFP and ACT ESA sites) within Australia. Currency Date modified: February 2023 Modification frequency: As needed Data extent Spatial extent North: -9° South: -44° East: 160° West: 92° Source information The primary information sources used to produce the Emergency Management Facilities Dataset was acquired from each Emergency Management State and Territory agency. Access to the required spatial data and attributes for each facility was coordinated with the support of Emergency Management Spatial Information Network Australia (EMSINA). Australian Capital Territory

    ACT Emergency Services Agency Australian Federal Police

    New South Wales

    Emergency Information Coordination Unit Australian Federal Police

    Northern Territory

    NT Police Fire & Emergency Services Australian Federal Police

    Queensland

    Qld Government Data Directory Australian Federal Police

    South Australia

    SA Country Fire Service SA State Emergency Service SA Government Data Directory SA Police Australian Federal Police

    Tasmania

    Department of Natural Resources and Environment Australian Federal Police

    Victoria

    Vic Government Data Directory Australian Federal Police

    Western Australia

    WA Government Data Directory St John Ambulance WA Australian Federal Police

    Geoscience Australia catalog entry: Emergency Management Facilities Database Lineage statement Using the previous Emergency Management Facilities datasets (2018) acquired from State and Territory agencies, the data was uploaded into an ArcSDE environment using Feature Manipulation Engine (FME). The process included the extraction of the themed features, and the translation of the data into a schema created by the Built Environment & Exposure Section, National Location Information Branch, Geoscience Australia (GA). In 2023 further FME processing was completed where the dataset was address matched using the original address provided and compared with the Geocoded National Address File (G-NAF) data. If no address match occurred GIS specialists attempted to find a relevant corresponding G-NAF address to join to, where possible. Data dictionary

    Attribute name Description

    OBJECTID Automatically generated system ID

    FEATURETYPE A singled feature type “Emergency Facility” is the collective name of the different facility subtypes identified in the CLASS field.

    DESCRIPTION Brief description of the feature type

    CLASS The feature type subtypes: Ambulance Station Emergency Management Facility Metro Fire Facility Police Station Rural/Country Fire Service Facility SES Facility

    FACILITY_NAME The station/facility name of each individual feature

    FACILITY_OPERATIONALSTATUS A description of the facility status Operational (functioning as an Emergency Services facility, does not indicate opening hours or if the facility is staffed) Non-operational (no longer operational as an Emergency Services facility)

    FACILITY_ADDRESS The address of this feature, as supplied by the data source

    ABS_SUBURB The ABS suburb where this feature is located

    FACILITY_STATE The state where this feature is located, as supplied by the data source

    ABS_POSTCODE The ABS postcode where this feature is located

    FACILITY_ATTRIBUTE_DATE Date of the source material used.

    FACILITY_DATE Date of the source material used to capture this feature

    FACILITY_SPATIAL_CONFIDENCE Confidence rating of the accuracy of the feature’s spatial location (5 high – 1 low)

    FACILITY_REVISED The date the feature was last revised

    COMMENT A free text field for adding general comments about this feature to external users

    FACILITY_LAT A numerical way to measure the North South position of the feature

    FACILITY_LONG A numerical way to measure the East West position of the feature

    VALIDATED Additional confirmation of the features accuracy

    GNAF_BUILDING_NAME The GNAF station/facility name of each individual feature

    GNAF_ADDRESS_DETAIL_PID The unique ID defined within the G-NAF address data

    GNAF_FORMATTED_ADDRESS The GNAF address where this feature is located

    GNAF_CONFIDENCE 2 - This reflects that all three contributors have supplied an identical address. 1 - This reflects that a match has been achieved between only two contributors. 0 - This reflects that a single contributor holds this address and no match has been achieved with either or the other two contributors. -1 - No match has been achieved but an entry exists

    GNAF_POSTCODE The GNAF postcode where this feature is located

    GNAF_SUBURB The GNAF suburb where this feature is located

    DISTANCE_TO_GNAF Distance of the GNAF from the Emergency management location point in metres

    GNAF_LAT A numerical way to measure the North South position of the GNAF feature

    GNAF_LONG A numerical way to measure the East West position of the GNAF feature

    Contact Geoscience Australia, clientservices@ga.gov.au

  12. Stanford Open Policing Project - Ohio

    • kaggle.com
    zip
    Updated Jul 24, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Stanford Open Policing Project (2017). Stanford Open Policing Project - Ohio [Dataset]. https://www.kaggle.com/datasets/stanford-open-policing/stanford-open-policing-project-ohio
    Explore at:
    zip(185573983 bytes)Available download formats
    Dataset updated
    Jul 24, 2017
    Dataset authored and provided by
    Stanford Open Policing Project
    Area covered
    Ohio
    Description

    Context:

    On a typical day in the United States, police officers make more than 50,000 traffic stops. The Stanford Open Policing Project team is gathering, analyzing, and releasing records from millions of traffic stops by law enforcement agencies across the country. Their goal is to help researchers, journalists, and policymakers investigate and improve interactions between police and the public.

    If you'd like to see data regarding other states, please go to https://www.kaggle.com/stanford-open-policing.

    Content:

    This dataset includes over 1 gb of stop data from Ohio. Please see the data readme for the full details of the available fields.

    Acknowledgements:

    This dataset was kindly made available by the Stanford Open Policing Project. If you use it for a research publication, please cite their working paper: E. Pierson, C. Simoiu, J. Overgoor, S. Corbett-Davies, V. Ramachandran, C. Phillips, S. Goel. (2017) “A large-scale analysis of racial disparities in police stops across the United States”.

    Inspiration:

    • How predictable are the stop rates? Are there times and places that reliably generate stops?
    • Concerns have been raised about jurisdictions using civil forfeiture as a funding mechanism rather than to properly fight drug trafficking. Can you identify any jurisdictions that may be exhibiting this behavior?
  13. d

    Civilian Complaint Review Board: Allegations Against Police Officers

    • catalog.data.gov
    • data.cityofnewyork.us
    Updated Jun 29, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.cityofnewyork.us (2025). Civilian Complaint Review Board: Allegations Against Police Officers [Dataset]. https://catalog.data.gov/dataset/civilian-complaint-review-board-allegations-against-police-officers
    Explore at:
    Dataset updated
    Jun 29, 2025
    Dataset provided by
    data.cityofnewyork.us
    Description

    A list of all closed allegations made against uniformed members of the New York Police Department since the year 2000. A single complaint may include multiple allegations between multiple victims / alleged victims and multiple officers. A single allegation is between one complainant and one officer. The term "Victim / Alleged Victim" refers to the person claiming harm by at least one or more allegation(s) of police misconduct. The dataset is part of a database of all public police misconduct records the Civilian Complaint Review Board (CCRB) maintains on complaints against New York Police Department uniformed members of service received in CCRB's jurisdiction since the year 2000, when CCRB's database was first built. This data is published as four tables: Civilian Complaint Review Board: Police Officers Civilian Complaint Review Board: Complaints Against Police Officers Civilian Complaint Review Board: Allegations Against Police Officers Civilian Complaint Review Board: Penalties A single complaint can include multiple allegations, and those allegations may include multiple subject officers and multiple complainants. Public records exclude complaints and allegations that were closed as Mediated, Mediation Attempted, Administrative Closure, Conciliated (for some complaints prior to the year 2000), or closed as Other Possible Misconduct Noted. This database is inclusive of prior datasets held on Open Data (previously maintained as "Civilian Complaint Review Board (CCRB) - Complaints Received," "Civilian Complaint Review Board (CCRB) - Complaints Closed," and "Civilian Complaint Review Board (CCRB) - Allegations Closed") but includes information and records made public by the June 2020 repeal of New York Civil Rights law 50-a, which precipitated a full revision of what CCRB data could be considered public.

  14. u

    New Hampshire Law Enforcement

    • nhgeodata.unh.edu
    • hub.arcgis.com
    • +2more
    Updated Dec 30, 2009
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    New Hampshire GRANIT GIS Clearinghouse (2009). New Hampshire Law Enforcement [Dataset]. https://www.nhgeodata.unh.edu/datasets/new-hampshire-law-enforcement/api
    Explore at:
    Dataset updated
    Dec 30, 2009
    Dataset authored and provided by
    New Hampshire GRANIT GIS Clearinghouse
    Area covered
    Description

    Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 04/26/2006 and the newest record dates from 10/19/2009

  15. a

    Local Law Enforcement Locations

    • disasters.amerigeoss.org
    • data.amerigeoss.org
    • +9more
    Updated Jun 27, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    GeoPlatform ArcGIS Online (2019). Local Law Enforcement Locations [Dataset]. https://disasters.amerigeoss.org/datasets/0d79b978d71b4654bddb6ca0f4b7f830
    Explore at:
    Dataset updated
    Jun 27, 2019
    Dataset authored and provided by
    GeoPlatform ArcGIS Online
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    The local law enforcement locations feature class/ shapefile contains point location and tabular information pertaining to a wide range of law enforcement entities in the United States. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Census of State and Local Law Enforcement Agencies (CSLLEA). Unlike the previous version of this dataset, published in 2009, federal level law enforcement agencies are excluded from this effort. Data fusion techniques are utilized to synchronize overlapping yet disparate source data. The primary sources for this effort are the DOJ-BJS CSLLEA from 2008 and the previously mentioned 2009 feature class from Homeland Security Infrastructure Foundation-Level Data (HIFLD). This feature class contains data for agencies across all 50 U.S. states, Washington D.C. and Puerto Rico.

  16. Sworn Law Enforcement Officer Locations

    • hub.arcgis.com
    Updated May 23, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    CA Governor's Office of Emergency Services (2019). Sworn Law Enforcement Officer Locations [Dataset]. https://hub.arcgis.com/maps/CalEMA::sworn-law-enforcement-officer-locations
    Explore at:
    Dataset updated
    May 23, 2019
    Dataset provided by
    California Governor's Office of Emergency Services
    Authors
    CA Governor's Office of Emergency Services
    Area covered
    Description

    Feature layer showing the locations of Sworn Law Enforcement Officer Locations in California.This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. This also applies to mounted police in New Mexico. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection in the United States and its territories. This dataset is comprised completely of license free data. At the request of NGA, FBI entities are intended to be excluded from this dataset, but a few may be included. The HSIP Freedom Law Enforcement dataset and the HSIP Freedom Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. Please see the process description for the breakdown of how the records were merged. With the merge of the Law Enforcement and the Correctional Institutions datasets, the HSIP Themes and NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard HSIP fields that TGS populated. Double spaces were replaced by single spaces in these same fields. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 12/07/2004 and the newest record dates from 09/10/2009.Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.1. An assessment of whether or not the total police capability in a given area is adequate. 2. A list of resources to draw upon in surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can help to determine those entities who are able to respond the quickest. 3. A resource for emergency management planning purposes. 4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster. 5. A resource for situational awareness planning and response for federal government events.

  17. UCI Communities and Crime Unnormalized Data Set

    • kaggle.com
    Updated Feb 21, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Kavitha (2018). UCI Communities and Crime Unnormalized Data Set [Dataset]. https://www.kaggle.com/datasets/kkanda/communities%20and%20crime%20unnormalized%20data%20set/discussion?sort=undefined
    Explore at:
    CroissantCroissant is a format for machine-learning datasets. Learn more about this at mlcommons.org/croissant.
    Dataset updated
    Feb 21, 2018
    Dataset provided by
    Kagglehttp://kaggle.com/
    Authors
    Kavitha
    License

    Attribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0)https://creativecommons.org/licenses/by-nc-sa/4.0/
    License information was derived automatically

    Description

    Context

    Introduction: The dataset used for this experiment is real and authentic. The dataset is acquired from UCI machine learning repository website [13]. The title of the dataset is ‘Crime and Communities’. It is prepared using real data from socio-economic data from 1990 US Census, law enforcement data from the 1990 US LEMAS survey, and crimedata from the 1995 FBI UCR [13]. This dataset contains a total number of 147 attributes and 2216 instances.

    The per capita crimes variables were calculated using population values included in the 1995 FBI data (which differ from the 1990 Census values).

    Content

    The variables included in the dataset involve the community, such as the percent of the population considered urban, and the median family income, and involving law enforcement, such as per capita number of police officers, and percent of officers assigned to drug units. The crime attributes (N=18) that could be predicted are the 8 crimes considered 'Index Crimes' by the FBI)(Murders, Rape, Robbery, .... ), per capita (actually per 100,000 population) versions of each, and Per Capita Violent Crimes and Per Capita Nonviolent Crimes)

    predictive variables : 125 non-predictive variables : 4 potential goal/response variables : 18

    Acknowledgements

    http://archive.ics.uci.edu/ml/datasets/Communities%20and%20Crime%20Unnormalized

    U. S. Department of Commerce, Bureau of the Census, Census Of Population And Housing 1990 United States: Summary Tape File 1a & 3a (Computer Files),

    U.S. Department Of Commerce, Bureau Of The Census Producer, Washington, DC and Inter-university Consortium for Political and Social Research Ann Arbor, Michigan. (1992)

    U.S. Department of Justice, Bureau of Justice Statistics, Law Enforcement Management And Administrative Statistics (Computer File) U.S. Department Of Commerce, Bureau Of The Census Producer, Washington, DC and Inter-university Consortium for Political and Social Research Ann Arbor, Michigan. (1992)

    U.S. Department of Justice, Federal Bureau of Investigation, Crime in the United States (Computer File) (1995)

    Inspiration

    Your data will be in front of the world's largest data science community. What questions do you want to see answered?

    Data available in the dataset may not act as a complete source of information for identifying factors that contribute to more violent and non-violent crimes as many relevant factors may still be missing.

    However, I would like to try and answer the following questions answered.

    1. Analyze if number of vacant and occupied houses and the period of time the houses were vacant had contributed to any significant change in violent and non-violent crime rates in communities

    2. How has unemployment changed crime rate(violent and non-violent) in the communities?

    3. Were people from a particular age group more vulnerable to crime?

    4. Does ethnicity play a role in crime rate?

    5. Has education played a role in bringing down the crime rate?

  18. g

    GRID3 NGA - Other POI: Police Stations

    • data.grid3.org
    • africageoportal.com
    • +2more
    Updated Oct 28, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    GRID3 (2020). GRID3 NGA - Other POI: Police Stations [Dataset]. https://data.grid3.org/datasets/grid3-nga-other-poi-police-stations/about
    Explore at:
    Dataset updated
    Oct 28, 2020
    Dataset authored and provided by
    GRID3
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    Police station locations and names in Nigeria. Released in September 2020. Dataset is incomplete for the country.

  19. Understanding Arrest Data in the National Incident-based Reporting System...

    • icpsr.umich.edu
    • catalog.data.gov
    Updated May 24, 2018
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Cross, Theodore (2018). Understanding Arrest Data in the National Incident-based Reporting System (NIBRS), Massachusetts, 2011-2013 [Dataset]. http://doi.org/10.3886/ICPSR36858.v1
    Explore at:
    Dataset updated
    May 24, 2018
    Dataset provided by
    Inter-university Consortium for Political and Social Researchhttps://www.icpsr.umich.edu/web/pages/
    Authors
    Cross, Theodore
    License

    https://www.icpsr.umich.edu/web/ICPSR/studies/36858/termshttps://www.icpsr.umich.edu/web/ICPSR/studies/36858/terms

    Time period covered
    2011 - 2013
    Area covered
    Massachusetts, United States
    Description

    These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. This research examined the reliability of the Federal Bureau of Investigation's National Incident-Based Reporting System (NIBRS) arrests data. Data on crime incidents, including data on whether an arrest was made or a summons issued, are collected from hundreds of law enforcement agencies (LEAs) across the country and then combined by the FBI into a national data set that is frequently used by researchers. This study compared arrest data in a sample of cases from NIBRS data files with arrest and summons data collected on the same cases directly from LEAs. The dataset consists of information collected from the Massachusetts NIBRS database combined with data from LEAs through a survey and includes data on arrests, summons, exceptional clearances, applicable statutes and offense names, arrest dates, and arrestees' sex, race, ethnicity and age for a sample of assault incidents between 2011 and 2013 from the NIBRS. The collection contains one SPSS data file (n=480; 32 variables). Qualitative data are not available as part of this collection.

  20. N

    NYC crime

    • data.cityofnewyork.us
    • data.wu.ac.at
    Updated May 7, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Police Department (NYPD) (2017). NYC crime [Dataset]. https://data.cityofnewyork.us/Public-Safety/NYC-crime/qb7u-rbmr
    Explore at:
    xml, csv, application/rdfxml, tsv, application/rssxml, kml, application/geo+json, kmzAvailable download formats
    Dataset updated
    May 7, 2017
    Authors
    Police Department (NYPD)
    Area covered
    New York
    Description

    This dataset includes all valid felony, misdemeanor, and violation crimes reported to the New York City Police Department (NYPD) for all complete quarters so far this year (2017). For additional details, please see the attached data dictionary in the ‘About’ section.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
(2025). Law Enforcement Facilities [Dataset]. https://data.oregon.gov/dataset/Law-Enforcement-Facilities/fhzx-esp8

Law Enforcement Facilities

Explore at:
application/rdfxml, json, csv, tsv, application/rssxml, xmlAvailable download formats
Dataset updated
Jan 29, 2025
Description

Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 06/27/2006 and the newest record dates from 10/22/2009

Search
Clear search
Close search
Google apps
Main menu