Crime Incidents in 2026

The dataset contains locations and attributes of blocks, created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and participating DC government agencies. The blocks used street centerlines information from DDOT. Blocks include named alleys in DC (such as 'WALTER ALLEY NE'). A block represents a street segment which usually has two bordering streets. The coordinates for the blocks are located at the midpoint of the street segment. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the BlocksPt is called BLOCKS_PT and is primarily based off of street data from DC Department of Transportation's Roads & Highways database, it also features additional useful information such as created date, last edited date, begin date, and more.

This dataset represents arrests made by the Baltimore Police Department. Data are updated weekly. To leave feedback or ask a question about this dataset, please fill out the following form: BPD Arrests feedback form.

The dataset contains locations and attributes of building construction and alteration permits applied for and approved by the District of Columbia Department of Buildings. These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC.

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.   Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred). Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained. Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.com Data Dictionary: Field Name Field Description Incident Number the number associated with either the incident or used as reference to store the items in our evidence rooms Date Reported the date the incident was reported to LMPD Date Occurred the date the incident actually occurred Badge ID Badge ID of responding Officer Offense Classification NIBRS Reporting category for the criminal act committed Offense Code Name NIBRS Reporting code for the criminal act committed NIBRS_CODE the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/view NIBRS Group hierarchy that follows the guidelines of the FBI National Incident Based Reporting System Was Offense Completed Status indicating whether the incident was an attempted crime or a completed crime. LMPD Division the LMPD division in which the incident actually occurred LMPD Beat the LMPD beat in which the incident actually occurred Location Category the type of location in which the incident occurred (e.g. Restaurant) Block Address the location the incident occurred City the city associated to the incident block location Zip Code the zip code associated to the incident block location Contact: LMPD Open Records    lmpdopenrecords@louisvilleky.gov

Please note that the responseDate is shown in UTC time, not local time. The data set is refreshed on a daily basis by 9:30 AM.

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at 311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC) oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Map which allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.