This dataset contains point locations for all publicly identified sites and office locations including headquarters, station, field office and investigative unit locations. This dataset was created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO), MPD and participating D.C. government agencies. Facilities and offices were obtained from MPD's Office of Corporate Communications, through interviews with MPD's Criminal Intelligence, and Tactical Crime Analysis Unit and through site surveys conducted by DC GIS staff.

The Regional Crime Analysis GIS (RCAGIS) is an Environmental Systems Research Institute (ESRI) MapObjects-based system that was developed by the United States Department of Justice Criminal Division Geographic Information Systems (GIS) Staff, in conjunction with the Baltimore County Police Department and the Regional Crime Analysis System (RCAS) group, to facilitate the analysis of crime on a regional basis. The RCAGIS system was designed specifically to assist in the analysis of crime incident data across jurisdictional boundaries. Features of the system include: (1) three modes, each designed for a specific level of analysis (simple queries, crime analysis, or reports), (2) wizard-driven (guided) incident database queries, (3) graphical tools for the creation, saving, and printing of map layout files, (4) an interface with CrimeStat spatial statistics software developed by Ned Levine and Associates for advanced analysis tools such as hot spot surfaces and ellipses, (5) tools for graphically viewing and analyzing historical crime trends in specific areas, and (6) linkage tools for drawing connections between vehicle theft and recovery locations, incident locations and suspects' homes, and between attributes in any two loaded shapefiles. RCAGIS also supports digital imagery, such as orthophotos and other raster data sources, and geographic source data in multiple projections. RCAGIS can be configured to support multiple incident database backends and varying database schemas using a field mapping utility.

This dataset is the City of Bend Police Department Case Offenses GIS layer curated for public use. Data is exported nightly from County E911 and ingested into City databases for both internal and external use. The data is then geocoded and generalized to the block level for confidentiality purposes. Cases with the following crime codes are excluded from both the public GIS and tabular data:RAPE - Forcible RapeASSAULT - StalkerASSAULT - Restraining Order ViolationSEX CRIME - Pornography/Obscene MaterialSEX CRIME - Non-Force RapeSEX CRIME - Contribute to Sex DelinquencySEX CRIME - Physical MolestSEX CRIME - IncestSEX CRIME - ExposerSEX CRIME - Forcible SodomySEX CRIME - Non-Force SodomySEX CRIME - All Other Sex CrimesSEX CRIME - Sexual Assault with an ObjectSEX CRIMES - Invasion of Personal PrivacyFAMILY - Child AbandonmentFAMILY - Child NeglectFAMILY - Non-SupportFAMILY - Criminal MistreatmentPlease note data is updated nightly and reflects cases received as of 6 PM the previous day.For questions regarding individual cases or incidents, you can request records from the Bend Police Department here: https://www.bendoregon.gov/government/departments/police/records-division or you can send an email to police@bendoregon.gov Attribute Information: See Table Field Name Description

OBJECTID For internal use.

CaseNumber A unique identifier that corresponds to a call for service number. Case numbers with a “91” after the dash indicate they originated as an online report submitted via bendpolicereports.com (i.e. 2021-91001234). The first four numbers of a case number are the year the case was created.

ReportedDate This is the date and time the incident was reported to Deschutes County 911 or initiated by a Bend Police officer.

Day of Week Day of the week the case was reported.

CrimeCode Description of an offense as assigned by Oregon National Incident-Based Reporting System (O-NIBRS). One or more offense codes may be applied to each case report to identify which offenses occurred during the incident. In some instances, no codes are applied to a case report if the intent is to only document information; such instances will appear as “Case Report Only / No Crime Codes” in any tables.

CrimeCodeDesc Crime code description, based on the grouping of statutes as defined by Oregon Criminal Justice Information Services (CJIS) Division and National Incident-Base Reporting System (NIBRS). Full definitions available on the State of Oregon CJIS Uniform Crime Reporting Reference Materials website.

Statute Oregon Revised Statutes (ORS) applied to the case report. ORS are the codified laws of the State of Oregon. Full statute definitions are available on the State of Oregon website.

StatuteDesc Description of the listed ORS. Full statute definitions are available on the State of Oregon website.

Counts The number of offenses reported in an incident.

AttemptCode Indicates whether the reported offense was attempted or committed.

CaseAddress The address where the incident occurred, rounded to the hundred block for privacy. Occasionally, reporting parties or involved subjects may not be able to provide the exact location where the reported incident occurred, a non-verifiable address is provided, or the crime may have occurred in a location outside Deschutes County. In these instances, the location field will say “address not verified or outside jurisdiction.”

Neighborhood City of Bend neighborhood in which an offense occurred.

The dataset contains polygons representing of MPD Police Sectors, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. In 2017 the Metropolitan Police Department formed an additional operational geographic layer called Sector. The Sector model brings additional management accountability to districts and allows for faster dispatch, lower response times, and improved service to the community. Sectors are made up of multiple Police Service Areas (PSAs) and are headed by a Captain. Please note that PSA is still an active operational model used by MPD; Sector is an additional layer between the PSA and District levels.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, economic development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019.On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RandD@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data is updated daily Tuesday through Sunday. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

Chicago Police district station locations. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required. To download, right-click the "Download" link above and choose "Save link as."

This dataset contains polygons features representing individual Precinct boundaries for the Columbus Division of Police. The City of Columbus is broken down into five Police Zones (Zones 1 through 5). Each Police Zone is then split into four Precincts (Precincts 1 through 20). Each Precinct is then split into several Cruiser Districts, the smallest geographical area utilized by the Division of Police. Police Zones vary in size based on many different factors including but not limited to the following: Square Mileage, Population, Violent Crime, Number of Households, and Natural Boundaries.The Columbus Division of Police can be reached by calling 911 for emergencies or by calling 614-645-4545 to report a non-emergency.

The locations of the police stations within Fairfax County.

Please note data is updated nightly and reflects calls received as of 6 PM the previous day.For questions regarding individual cases or incidents, you can request records from the Bend Police Department here: https://www.bendoregon.gov/government/departments/police/records-division or you can send an email to police@bendoregon.gov Attribute Information: See Table Field Name Description

OBJECTID For internal use.

IncidentNumber A unique incident identifier that corresponds to a call for service number.

CreateDateTime Date and time that the call was received by Deschutes County 911 or initiated by a Bend Police officer.

Day_of_Week Day of the week the call was received.

Hour_of_Day Time the call was received.

CallType The specific nature of the call for service.

Source Where the call for service originated.

CallAddress The address of the call, generalized to the hundred block for privacy. Occasionally, reporting parties or involved subjects are unable to provide the exact location where the reported incident occurred, a non-verifiable address is provided, or the crime may have occurred in a location outside of Deschutes County. In these instances, the location field will say “address not verified or outside jurisdiction.”

Neighborhood The City of Bend neighborhood boundary in which a call for service originated.

Metropolitan Police Department (MPD) Police Service Areas (PSA). The dataset contains polygons representing of MPD PSA, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Police jurisdictions were initially created selecting street arcs from the planimetric street centerlines and street polygons, water polygons, real property boundaries and District of Columbia boundaries.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019. On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.

The Tempe Police Department prides itself in its continued efforts to reduce harm within the community and is providing this dataset on hate crime incidents that occur in Tempe.The Tempe Police Department documents the type of bias that motivated a hate crime according to those categories established by the FBI. These include crimes motivated by biases based on race and ethnicity, religion, sexual orientation, disability, gender and gender identity.The Bias Type categories provided in the data come from the Bias Motivation Categories as defined in the Federal Bureau of Investigation (FBI) National Incident-Based Reporting System (NIBRS) manual, version 2020.1 dated 4/15/2021. The FBI NIBRS manual can be found at https://www.fbi.gov/file-repository/ucr/ucr-2019-1-nibrs-user-manua-093020.pdf with the Bias Motivation Categories found on pages 78-79.Although data is updated monthly, there is a delay by one month to allow for data validation and submission.Information about Tempe Police Department's collection and reporting process for possible hate crimes is included in https://storymaps.arcgis.com/stories/a963e97ca3494bfc8cd66d593eebabaf.Additional InformationSource: Data are from the Law Enforcement Records Management System (RMS)Contact: Angelique BeltranContact E-Mail: angelique_beltran@tempe.govData Source Type: TabularPreparation Method: Data from the Law Enforcement Records Management System (RMS) are entered by the Tempe Police Department into a GIS mapping system, which automatically publishes to open data.Publish Frequency: MonthlyPublish Method: New data entries are automatically published to open data. Data Dictionary

Current police beat boundaries in Chicago. The data can be viewed on the Chicago Data Portal with a web browser. However, to view or use the files outside of a web browser, you will need to use compression software and special GIS software, such as ESRI ArcGIS (shapefile) or Google Earth (KML or KMZ), is required.

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

CrimeMapTutorial is a step-by-step tutorial for learning crime mapping using ArcView GIS or MapInfo Professional GIS. It was designed to give users a thorough introduction to most of the knowledge and skills needed to produce daily maps and spatial data queries that uniformed officers and detectives find valuable for crime prevention and enforcement. The tutorials can be used either for self-learning or in a laboratory setting. The geographic information system (GIS) and police data were supplied by the Rochester, New York, Police Department. For each mapping software package, there are three PDF tutorial workbooks and one WinZip archive containing sample data and maps. Workbook 1 was designed for GIS users who want to learn how to use a crime-mapping GIS and how to generate maps and data queries. Workbook 2 was created to assist data preparers in processing police data for use in a GIS. This includes address-matching of police incidents to place them on pin maps and aggregating crime counts by areas (like car beats) to produce area or choropleth maps. Workbook 3 was designed for map makers who want to learn how to construct useful crime maps, given police data that have already been address-matched and preprocessed by data preparers. It is estimated that the three tutorials take approximately six hours to complete in total, including exercises.

Service for LPD data

Police facilities

DISCLAIMER In May of 2021 the department’s method of Uniform Crime Reporting (UCR) transitioned from the Summary Reporting System (SSR) to the federally mandated National Incident-Based Reporting System (NIBRS). When comparing SSR and NIBRS data, the user should be aware of the differences between the two reporting methodologies. This dataset reflects reported incidents of crime (with the exception of sexual assaults, which are excluded by statute) that occurred in the City of Hartford from January 1, 2005 to May 18, 2021. Should you have questions about this dataset, you may contact the Crime Analysis Division of the Hartford Police Department at 860.757.4020 or policechief@Hartford.gov. Disclaimer: These incidents are based on crimes verified by the Hartford Police Department's Crime Analysis Division. The crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Hartford Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Hartford Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. The Hartford Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Hartford or Hartford Police Department web page. The user specifically acknowledges that the Hartford Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Hartford Police Department", "Hartford Police", "HPD" or any colorable imitation of these words or the unauthorized use of the Hartford Police Department logo is unlawful. This web page does not, in any way, authorize such use.

Police station locations in Chicago

The Police Stations layer shows the point locations of law enforcement and sheriff offices in Massachusetts, covering local, county and state jurisdictions. The Massachusetts Emergency Management Agency (MEMA) GIS Program in cooperation with the Regional Planning Agencies and participating communities created the original data as part of the development of Homeland Security Data Layers. MassGIS has since incorporated updates into the data.The features represented include municipal police stations and Massachusetts State Police barracks. Although sheriffs are not technically charged with the same law enforcement tasks as local and state police, county sheriff headquarters are also included in this layer. The duties of the sheriffs include the management and operation of regional correctional systems and transportation of prisoners, service of judicial process and delivery of legal documents needed to support the operation of the courts, community policing, running various outreach services, and the enforcement of laws enacted for the public safety, health and welfare of the people. Not included in this layer are Environmental Police, campus police and various state and federal level law enforcement locations.Feature service also available.More details...