AndreaBozzo/ceres-open-data-index huggingface dataset:
DPD Initiated CAD Records 2018

This dataset is for DPD initiated CAD records for 2018. For the comprehensive dataset which includes all records please refer to the [DPD CAD Initiated Records] dataset. This dataset contains DPD initiated CAD (Computer Aided Dispatch) records in the City of Detroit in the 2018 calendar year. This compliments the [Police Serviced 911 Calls] dataset that is an internally generated equivalent to events reported by civilians that lead to a police response. Examples of records can include activities in which a law enforcement unit or officer initiates contact with the public. This can be to resolve, correct, or assist in a particular situation like helping a motorist, interviewing a witness, conducting a traffic stop, and engaging in foot pursuit. Each row in the dataset represents a DPD initiated record. These records detail when the call was entered, its nature, assigned priority level and DPD responding precinct/unit. When applicable, it also includes dispatch time, travel time, and total response times. Locations of the officer-initiated calls are reported based on the nearest intersection to protect the privacy of individuals. Records in this dataset that are of a more general nature may not have an associated location. Some records in the dataset with a Code Description of “Start of Shift Information” serve as routine informational purposes within DPD. Two other values that appear in the Code Description field frequently are Special Attention and Bus Boarding. Explanations of these values can be seen below. “Special Attention” records may be created for several reasons. Examples include check-ins with Project Green Light (PGL) partners, response to citizen requests such as people request notifying police when they are going out of town, wellness checks, when there has been a series of break-ins or other crimes in an area, or other concerns that prompt DPD to pay special attention to a location. Records may also be initiated by DPD for purposes related to the community. "Bus Boarding" records are entered into the system when the Transit Division of DPD boards a DDOT bus, as part of routine responsibilities. Typically, the officer’s partner trails the bus in their vehicle and picks up the other officer when the ride is over. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or DPDinformatics@detroitmi.gov. A DPD webpage provides [recommendations for reporting different types of crime.]
DPD Initiated CAD Records 2020

This dataset is for DPD initiated CAD records for 2020. For the comprehensive dataset which includes all records please refer to the [DPD CAD Initiated Records] dataset. This dataset contains DPD initiated CAD (Computer Aided Dispatch) records in the City of Detroit in the 2020 calendar year. This compliments the [Police Serviced 911 Calls] dataset that is an internally generated equivalent to events reported by civilians that lead to a police response. Examples of records can include activities in which a law enforcement unit or officer initiates contact with the public. This can be to resolve, correct, or assist in a particular situation like helping a motorist, interviewing a witness, conducting a traffic stop, and engaging in foot pursuit. Each row in the dataset represents a DPD initiated record. These records detail when the call was entered, its nature, assigned priority level and DPD responding precinct/unit. When applicable, it also includes dispatch time, travel time, and total response times. Locations of the officer-initiated calls are reported based on the nearest intersection to protect the privacy of individuals. Records in this dataset that are of a more general nature may not have an associated location. Some records in the dataset with a Code Description of “Start of Shift Information” serve as routine informational purposes within DPD. Two other values that appear in the Code Description field frequently are Special Attention and Bus Boarding. Explanations of these values can be seen below. “Special Attention” records may be created for several reasons. Examples include check-ins with Project Green Light (PGL) partners, response to citizen requests such as people request notifying police when they are going out of town, wellness checks, when there has been a series of break-ins or other crimes in an area, or other concerns that prompt DPD to pay special attention to a location. Records may also be initiated by DPD for purposes related to the community. "Bus Boarding" records are entered into the system when the Transit Division of DPD boards a DDOT bus, as part of routine responsibilities. Typically, the officer’s partner trails the bus in their vehicle and picks up the other officer when the ride is over. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or DPDinformatics@detroitmi.gov. A DPD webpage provides [recommendations for reporting different types of crime.]
DPD Initiated CAD Records 2017

This dataset is for DPD initiated CAD records for 2017. For the comprehensive dataset which includes all records please refer to the [DPD CAD Initiated Records] dataset. This dataset contains DPD initiated CAD (Computer Aided Dispatch) records in the City of Detroit in the 2017 calendar year. This compliments the [Police Serviced 911 Calls] dataset that is an internally generated equivalent to events reported by civilians that lead to a police response. Examples of records can include activities in which a law enforcement unit or officer initiates contact with the public. This can be to resolve, correct, or assist in a particular situation like helping a motorist, interviewing a witness, conducting a traffic stop, and engaging in foot pursuit. Each row in the dataset represents a DPD initiated record. These records detail when the call was entered, its nature, assigned priority level and DPD responding precinct/unit. When applicable, it also includes dispatch time, travel time, and total response times. Locations of the officer-initiated calls are reported based on the nearest intersection to protect the privacy of individuals. Records in this dataset that are of a more general nature may not have an associated location. Some records in the dataset with a Code Description of “Start of Shift Information” serve as routine informational purposes within DPD. Two other values that appear in the Code Description field frequently are Special Attention and Bus Boarding. Explanations of these values can be seen below. “Special Attention” records may be created for several reasons. Examples include check-ins with Project Green Light (PGL) partners, response to citizen requests such as people request notifying police when they are going out of town, wellness checks, when there has been a series of break-ins or other crimes in an area, or other concerns that prompt DPD to pay special attention to a location. Records may also be initiated by DPD for purposes related to the community. "Bus Boarding" records are entered into the system when the Transit Division of DPD boards a DDOT bus, as part of routine responsibilities. Typically, the officer’s partner trails the bus in their vehicle and picks up the other officer when the ride is over. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or DPDinformatics@detroitmi.gov. A DPD webpage provides [recommendations for reporting different types of crime.]
DPD Initiated CAD Records 2026

This dataset is for DPD initiated CAD records for 2026. For the comprehensive dataset which includes all records please refer to the [DPD CAD Initiated Records] dataset. This dataset contains DPD initiated CAD (Computer Aided Dispatch) records in the City of Detroit since January 1st, 2026. This compliments the [Police Serviced 911 Calls] dataset that is an internally generated equivalent to events reported by civilians that lead to a police response. Examples of records can include activities in which a law enforcement unit or officer initiates contact with the public. This can be to resolve, correct, or assist in a particular situation like helping a motorist, interviewing a witness, conducting a traffic stop, and engaging in foot pursuit. Each row in the dataset represents a DPD initiated record. These records detail when the call was entered, its nature, assigned priority level and DPD responding precinct/unit. When applicable, it also includes dispatch time, travel time, and total response times. Locations of the officer-initiated calls are reported based on the nearest intersection to protect the privacy of individuals. Records in this dataset that are of a more general nature may not have an associated location. Some records in the dataset with a Code Description of “Start of Shift Information” serve as routine informational purposes within DPD. Two other values that appear in the Code Description field frequently are Special Attention and Bus Boarding. Explanations of these values can be seen below. “Special Attention” records may be created for several reasons. Examples include check-ins with Project Green Light (PGL) partners, response to citizen requests such as people request notifying police when they are going out of town, wellness checks, when there has been a series of break-ins or other crimes in an area, or other concerns that prompt DPD to pay special attention to a location. Records may also be initiated by DPD for purposes related to the community. "Bus Boarding" records are entered into the system when the Transit Division of DPD boards a DDOT bus, as part of routine responsibilities. Typically, the officer’s partner trails the bus in their vehicle and picks up the other officer when the ride is over. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or DPDinformatics@detroitmi.gov. A DPD webpage provides [recommendations for reporting different types of crime.]
Police Serviced 911 Calls 2026

This dataset is for Police Serviced 911 calls from January 1st, 2026 to present day, or until the end of the calendar year 2026 - whatever comes first. For the comprehensive dataset which includes all records please refer to the [Police Serviced 911 Calls] dataset. Emergency response calls are the result of people calling 911 to request police services, calls reported through the non-emergency DPD Telephone Crime Reporting (TCR) line that require emergency response, and ShotSpotter incidents. This dataset does not include requests for emergency response that occur through other channels (e.g. walk-ins, officer-initiated items). A DPD webpage provides [recommendations for reporting different types of crime]. Each row in the dataset represents a call for service and includes details such as when the call was received, its nature and assigned priority level, DPD response precinct or detail, and dispatch, travel, and total response times. Locations of incidents associated with each call are reported based on the nearest intersection to protect the privacy of individuals. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or CrimeIntelligenceBureau@detroitmi.gov.
RMS Crime Incidents 2026

This dataset is for RMS Crime Incidents for 2026. For the comprehensive dataset which includes all records please refer to the [RMS Crime Incidents] dataset. The RMS Crime Incidents dataset consists of crime reports from the Detroit Police Department Records Management System (RMS). This data reflects criminal offenses reported in the City of Detroit that DPD was involved in the 2026 calendar year. Incident data is typically entered into mobile devices by the officer in the field when responding to an incident. Incidents that occurred in Detroit but in a location that is under the jurisdiction of the Michigan State Police (MSP) or Wayne State University Police Department (WSUPD), such as on an expressway, Belle Isle, or around Wayne State University, are included only if the incident is handled by DPD. Such records are reviewed in a monthly audit to ensure that the incidents are counted by one and only one agency (MSP or DPD). This data is updated daily. For each crime incident, one or more offense charges are recorded, and each row in the dataset corresponds with one of these charges. An example could be a domestic assault where property was also vandalized. Offense charges that occurred at the same crime incident share a common incident number. For each offense charge record (rows) details include when and where the incident occurred, the nature of the offense, DPD precinct or detail, and the case investigation status. Locations of incidents associated with each call are reported based on the nearest intersection to protect the privacy of individuals. RMS Crime Incident data complies with Michigan Incident Crime Reporting (MICR) standards. More information about MICR standards is available via the [MICR Website]. The Manual and Arrest Charge Code Card may be especially helpful. There may be small differences between RMS Crime Incident data shared here and data shared through MICR given data presented here is updated here more frequently which results in a difference in a cadence of status updates. Additionally, this dataset includes crime incidents that following an investigation are coded with a case status of ‘Unfounded’. In most cases, this means that the incident occurred outside the jurisdiction of DPD or otherwise was reported in error. The State of Michigan, through the MICR program, reports data to the National Incident-Based Reporting System ([NIBRS]). [Yearly Datasets] for RMS Crime Incidents have been added to the ODP. This is to improve the user's experience in handling the large file size of the records in the comprehensive dataset. You may download each year separately, which significantly reduces the size and records for each file. In addition to the past years, we have also included a year-to-date dataset. This captures all RMS Crime Incidents from January 1, 2025, to present. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or CrimeIntelligenceBureau@detroitmi.gov.
DPD ShotSpotter Incident Records

This dataset contains DPD (Detroit Police Department) Computer Aided Dispatch (CAD) records initiated by the Gunshot Detection System (ShotSpotter) from March 15, 2023, the date ShotSpotter was integrated into the CAD system, to the present. CAD records created in response to ShotSpotter alerts from March 15, 2021 to March 15, 2023 were initiated by 911 call center staff, and are therefore included in the [Police Serviced 911 Calls] dataset. Please note that there are some ShotSpotter records in the Police Serviced 911 calls and [DPD CAD Initiated Records] datasets after March 15,2023. DPD implemented the Detroit ShotSpotter program on March 15, 2021. ShotSpotter audio sensor devices, which are produced by SoundThinking, Inc., are used to detect gunshots and estimate their locations. ShotSpotter currently covers approximately 39 square miles of Detroit. When a sound that meets the parameters established to identify a potential gunshot is detected, an event record in the ShotSpotter system is created and proceeds through the shot detection workflow. If the sound is determined to be a gunshot or probable gunshot rather than fireworks, a car backfiring and so on, a record is created in the DPD CAD system. The ShotSpotter system uses triangulation to estimate where a gunshot sound originated and uses this location estimate to identify the nearest street address, which is then recorded as the event location. The process from gunshot to alert typically takes less than 60 seconds. A DPD dispatcher will then assign a unit to investigate the incident. For more information, please refer to this [document], which DPD presented to the BOPC (Board of Police Commissioners) in March of 2025. Each row in the dataset represents a ShotSpotter incident record that details when the call was entered, its nature, assigned priority level, DPD responding precinct or detail, and when applicable dispatch, travel, and total response times. Locations of the ShotSpotter incident are based on the nearest intersection to protect the privacy of individuals. There are several nature codes that appear frequently in the dataset. A short description of these can be found below: * SST345 – Single Gunshot * SST346 – Multiple Gunshots * SST342 – Probable Gunfire Please note that there are records that have a negative dispatch time. This occurred when the multiple systems within the ShotSpotter – CAD integration workflow were running on slightly different system times. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or DPDinformatics@detroitmi.gov. A DPD webpage provides [recommendations for reporting different types of crime.]
DPD Initiated CAD Records 2016

This dataset is for DPD initiated CAD records from 9/20/2016 to 12/31/2016. For the comprehensive dataset which includes all records please refer to the [DPD CAD Initiated Records] dataset. This dataset contains DPD initiated CAD (Computer Aided Dispatch) records in the City of Detroit from September 20, 2016 to December 31, 2016. This compliments the [Police Serviced 911 Calls] dataset that is an internally generated equivalent to events reported by civilians that lead to a police response. Examples of records can include activities in which a law enforcement unit or officer initiates contact with the public. This can be to resolve, correct, or assist in a particular situation like helping a motorist, interviewing a witness, conducting a traffic stop, and engaging in foot pursuit. Each row in the dataset represents a DPD initiated record. These records detail when the call was entered, its nature, assigned priority level and DPD responding precinct/unit. When applicable, it also includes dispatch time, travel time, and total response times. Locations of the officer-initiated calls are reported based on the nearest intersection to protect the privacy of individuals. Records in this dataset that are of a more general nature may not have an associated location. Some records in the dataset with a Code Description of “Start of Shift Information” serve as routine informational purposes within DPD. Two other values that appear in the Code Description field frequently are Special Attention and Bus Boarding. Explanations of these values can be seen below. “Special Attention” records may be created for several reasons. Examples include check-ins with Project Green Light (PGL) partners, response to citizen requests such as people request notifying police when they are going out of town, wellness checks, when there has been a series of break-ins or other crimes in an area, or other concerns that prompt DPD to pay special attention to a location. Records may also be initiated by DPD for purposes related to the community. "Bus Boarding" records are entered into the system when the Transit Division of DPD boards a DDOT bus, as part of routine responsibilities. Typically, the officer’s partner trails the bus in their vehicle and picks up the other officer when the ride is over. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or DPDinformatics@detroitmi.gov. A DPD webpage provides [recommendations for reporting different types of crime.]
Current Master Plan Future General Land Use

The Master Plan of Policies Future General Land Use map sets forth a comprehensive long-range strategy for the City of Detroit. The plan is designed to change in response to new information and changing circumstances. It contains Future General Land Use maps for each neighborhood. In general, these do not address small-scale situations less than 10 acres, the specific characteristics of residential development, or the specific types of commercial and other nonresidential uses. City Planning Commission review and adoption are required by the State’s Municipal Planning Act (PA 285), and City Council approval via resolution is required by the City Charter. The Master Plan is amended 2-3 times/year on average. Reasons for amending include implementing neighborhood plans, changing conditions, and permitting the redevelopment of specific properties. The last time the layer has been amended on October 25, 2022, since it was adopted.
City Parks

This dataset includes the geographic boundaries of city-owned parks within the Detroit Parks and Recreation Division. This Division is within Detroit's General Services Department (GSD). The General Services Department helps to make the City of Detroit a clean, safe and vibrant place. GSD manages the City’s vehicle fleet, forestry services, vacant lot maintenance, and park and recreation center planning, design, improvements, and programming. Park boundary records define the physical extent of each park and are used for planning, operations, maintenance, and public information purposes. The dataset does not include privately owned open spaces, school playgrounds, or other non-Parks-and-Recreation City properties. For information on recreational programming, event permits, and reservations please refer to the [Detroit Parks and Recreation official website.] Each row in the dataset represents one park and includes details such as the park’s name, address, council district, type, and size. Park Type Definitions: Mini Parks: Parks under 1 acre in size that support active and passive recreation in dense residential and commercial areas where larger sites are not currently feasible. Neighborhood Parks: Parks between 1 and 10 acres in size that serve as the recreational and social activity point of a neighborhood. Community Parks: Parks between 10 and 50 acres in size that offer diverse amenities intended to meet the recreational needs of a larger community. Regional Parks: Parks over 50 acres in size that serve citywide recreational needs, function as destination parks, accommodate large-scale events, provide specialized amenities, and emphasize the preservation of natural areas. Riverfront Parks: Parks on the waterfront that provide access to the Detroit River for scenic viewing, relaxation, and a wide variety of recreational opportunities. Should you have questions about this dataset, you may contact the Public Space Planning Unit within the City of Detroit’s Parks and Recreation Division at [PSPU@detroitmi.gov].
2024 Targeted Multifamily Areas

Purpose: Prioritize investments to create walkable, urban nodes that provide services, transit, and access to employment, and strategies to preserve affordable housing units. Use: The City of Detroit requires that all Affordable projects funded by HRD Notice of Funding Availability be located in the target areas identified in the 2024 Targeted Multifamily Housing Area. Unless a waiver is granted at the sole discretion of the city In contrast, preservation (meaning preservation of affordable rents of an occupied structure) projects can be located throughout the City of Detroit.
Detroit Foursquare Places of Interest (POI)

Places of Interest (POI), within the City of Detroit, from [Foursquare's] open-source Places dataset. A bounding box of: west(xmin), south(ymin), east(xmax), north(ymax) = [-83.29, 42.25, -82.85, 42.45] was applied when querying the dataset, then the resultant layer was clipped to the City of Detroit boundary including: Hamtrammck & Highland Park. With Foursquare’s Open Source Places monthly data [releases], you can access free data to accelerate geospatial innovation and insights. [https://docs.foursquare.com/data-products/docs/access-fsq-os-places] CRS: EPSG:4326 (WGS 84) 04-15-2026