- API data.detroitmi.gov | Last Updated 2019-09-30T07:12:02.000Z
Rental Registration is a certificate issued by BSEED that identifies a residential property as a rental property.
- API data.detroitmi.gov | Last Updated 2016-08-28T20:41:18.000Z
Location of all traffic signals
- API data.detroitmi.gov | Last Updated 2019-04-23T18:54:49.000Z
Vacant properties that have been issued a Certificate of Compliance per City Ordinance 18-03 by BSEED since January 1, 2017.
- API data.detroitmi.gov | Last Updated 2019-04-15T23:14:24.000Z
This dataset provides an estimate of the percent of Detroit residents who reported having health insurance at the time they completed the American Community Survey (ACS). The data is averaged over 5 years. This data can be also be accessed in Table S2701 on the American FactFinder website. Note that the data is provided by ZIP Code Tabulation Area (ZCTA), which may not exactly match USPS ZIP Code service areas. For more information: https://web.archive.org/web/20130617034846/http://www.census.gov/geo/reference/zctas.html We're excited to make health data more accessible. Let us know how you're using the data!
- API data.detroitmi.gov | Last Updated 2019-07-25T19:03:28.000Z
All food safety inspections that have been conducted by the Detroit Health Department since 8/1/2016, including the inspection date as well as the number of violations in each of the three violation categories: - PRIORITY VIOLATIONS are the most serious category and directly contribute to foodborne illness or food poisoning. Examples include food at unsafe temperature (warmer than 41 degrees F and colder than 135 degrees F) and employees failing to wash hands before handing food. - PRIORITY FOUNDATION VIOLATIONS (labeled Foundation in this dataset) are the second most serious and indirectly contribute to foodborne illness or food poisoning. Examples include not having a food product thermometer or no paper towel at the hand sink. - CORE VIOLATIONS are the least serious category and primarily relate to general cleanliness and facility maintenance. Examples include a dirty floor or a dirty dumpster area. For additional data about the violations cited during an inspection, go to: https://data.detroitmi.gov/d/6kry-5abc The see the Michigan Food Code, go to: https://www.michigan.gov/documents/mdard/MI_Modified_2009_Food_Code_396675_7.pdf
- API data.detroitmi.gov | Last Updated 2019-09-30T10:08:59.000Z
Parcel point file with ownership, assessment, and taxable value information. If you need the shapefiles, go to this dataset: <a href="https://data.detroitmi.gov/Property-Parcels/Parcel-Map/fxkw-udwf" target="_blank" rel="nofollow external">https://data.detroitmi.gov/Property-Parcels/Parcel-Map/fxkw-udwf</a>
- API data.detroitmi.gov | Last Updated 2019-09-30T08:19:04.000Z
Rental properties that have been registered or renewed their registration within the last 365 days. Learn more about rental properties at <a href="http://detroitmi.gov/rental" target="_blank" rel="nofollow external">http://detroitmi.gov/rental</a>.
- API data.detroitmi.gov | Last Updated 2019-09-27T14:28:04.000Z
This table shows all 911 police emergency response and officer-initiated calls for service in the City of Detroit beginning September 20, 2016. Emergency response calls are the result of people calling 911 to request police services. Officer-initiated calls include traffic stops, street investigations and other policing activities (such as observing crimes in progress) where police officers initiate the response. The table includes all calls taken, dispatch, travel, and total response times for those calls serviced by a police agency. The data also include the responding agency, unit, call type and category of each call. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Intelligence Unit at 313-596-2250, or CrimeIntelligenceBureau@detroitmi.gov.
- API data.detroitmi.gov | Last Updated 2019-09-27T14:33:32.000Z
Issues submitted through the Improve Detroit mobile app. Improve Detroit is a 311 ticketing system used by many City departments and agencies to manage resident requests to fill potholes, fix streetlights, clear blocked catch basins, and more. Learn more at: http://www.detroitmi.gov/How-Do-I/Mobile-Apps/ImproveDetroit
- API data.detroitmi.gov | Last Updated 2019-09-27T14:04:25.000Z
This data reflects reported criminal offenses that have occurred in the City of Detroit since December 6, 2016. Offense data was extracted from the Detroit Police Department's records management system. This data set contains the most recent data available and is updated anytime DPD sends official crime records contributing to the Michigan Incident Crime Reporting (MICR) or the National Incident Based Reporting systems (reflected by the IBR Date field). It should be noted that some incidents involve the commission of multiple offenses, such as a domestic assault where property was also vandalized. Accordingly, the data describe all offenses associated with all reported incidents. In order to protect the privacy of crime victims, addresses are shown at the block level only and the geographic coordinates (longitude and latitude) have been randomly offset by up to 180 feet along the street segment. See the Note on Anonymized Addresses below for more information. For data prior to December 6, 2016, go to https://data.detroitmi.gov/Public-Safety/DPD-All-Crime-Incidents-January-1-2009-December-6-/invm-th67. Please note that DPD launched a new system to collect crime reports on that date, and certain fields of information may not be appropriate to compare between the two systems. Both systems were used to enter reports on December 6, 2016, so neither dataset is inclusive alone of all reports entered on that day. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Intelligence Unit at 313-596-2250, or CrimeIntelligenceBureau@detroitmi.gov. Field Descriptions: Crime ID - text - Numeric offense identifier in Record Management System Report # - text - Unique ID in Record Management System (YYYYMMDD Report Number) Incident Address - text - Location of incident (see Note on Anonymized Addresses for more information) Offense Description - text - Detail about the offense reported Offense Category - text - Type of offense described in the report, categorized State Offense Code - text - Michigan State Police offense code Incident Date & Time - datetime - Date and time of incident Incident Time (24h) - text - Time of incident, based on 24-hour clock Day of Week (Sunday is 1) - number - Numeric code for the day of the week, where Sunday = 1, Monday = 2, etc. Hour of Day - number - Time of incident, based on the hour Year - number - Year of incident Scout Car Area - text - DPD Scout Car Area, a geography within a precinct Precinct Number - number - DPD Precinct IBR Report Date - datetime - The date and time that DPD sent official crime records to the Michigan Incident Crime Reporting (MICR) and the National Incident Based Reporting systems Location - location - Location field generated by Socrata Neighborhood - text - The neighborhood of the original XY coordinate, using the neighborhood file on the City’s Open Data Portal Census Block GEOID - text - The Census Block of the original XY coordinate, using the 2010 Census Blocks provided by the US Census Bureau Council District - text - The Detroit City Council District of the original XY coordinate Note on Anonymized Addresses: DPD works with the Department of Innovation and Technology (DoIT) to de-identify location information for both 911 calls and reported crimes to protect victim and caller information. Each record has two sets of location information - address and XY coordinates. The address field represents the location of the incident, and the XY coordinates are populated based on the geo-verified location of that address. The anonymization process systematically takes the point of the original XY coordinates and places them randomly within 180 feet along the street from the original point. If the point appears on either side of the street, it does so randomly, and it is not an indication of where the original event occurred. The XY coordinate fields provided in this dataset are t