The land area of Detroit, MI was 139 in 2017.

Land Area

Water Area

Land area is a measurement providing the size, in square miles, of the land portions of geographic entities for which the Census Bureau tabulates and disseminates data. Area is calculated from the specific boundary recorded for each entity in the Census Bureau's geographic database. Land area is based on current information in the TIGER® data base, calculated for use with Census 2010.

Water Area figures include inland, coastal, Great Lakes, and territorial sea water. Inland water consists of any lake, reservoir, pond, or similar body of water that is recorded in the Census Bureau's geographic database. It also includes any river, creek, canal, stream, or similar feature that is recorded in that database as a two- dimensional feature (rather than as a single line). The portions of the oceans and related large embayments (such as Chesapeake Bay and Puget Sound), the Gulf of Mexico, and the Caribbean Sea that belong to the United States and its territories are classified as coastal and territorial waters; the Great Lakes are treated as a separate water entity. Rivers and bays that empty into these bodies of water are treated as inland water from the point beyond which they are narrower than 1 nautical mile across. Identification of land and inland, coastal, territorial, and Great Lakes waters is for data presentation purposes only and does not necessarily reflect their legal definitions.

Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to http://opendatanetwork.com. Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Geographic and Area Datasets Involving Detroit, MI

  • API

    DPD: All Crime Incidents, December 6, 2016 - Present

    data.detroitmi.gov | Last Updated 2019-09-23T19:07:09.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

  • API

    Liquor Licenses

    data.detroitmi.gov | Last Updated 2017-09-11T17:30:38.000Z

    Active Liquor License in Detroit city limits

  • API

    Restaurant Inspections - Establishments

    data.detroitmi.gov | Last Updated 2019-07-25T19:03:23.000Z

    Food service establishments that have been inspected by the Detroit Health Department since 8/1/2016. For more info about an establishment's inspections, check out these datasets: - Inspection dates and total number of violations: https://data.detroitmi.gov/d/kpnp-cx36 - Details of each violation cited: https://data.detroitmi.gov/d/6kry-5abc

  • API

    Restaurant Inspections - All Inspections

    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

    Federally Qualified Health Centers

    data.detroitmi.gov | Last Updated 2019-04-23T01:51:42.000Z

    All locations of Federally Qualified Health Centers (FQHCs) in the City of Detroit. FQHCs include all organizations receiving grants under Section 330 of the Public Health Service Act (PHS). FQHCs qualify for enhanced reimbursement from Medicare and Medicaid, as well as other benefits. FQHCs must serve an underserved area or population, offer a sliding fee scale, provide comprehensive services, have an ongoing quality assurance program, and have a governing board of directors.

  • API

    DivDat Payment Kiosks

    data.detroitmi.gov | Last Updated 2019-09-23T09:44:17.000Z

    Locations of DivDat Kiosks where customers can pay bills for Detroit Water and Sewerage, City of Detroit Property Tax, DTE Energy, and Wayne County Treasurer. Learn more at: http://detroitmi.gov/dwsdkiosk

  • API

    DPD: All Crime Incidents, January 1, 2009 - December 6, 2016

    data.detroitmi.gov | Last Updated 2019-04-23T01:53:14.000Z

    This data reflects reported criminal offenses that have occurred in the City of Detroit between January 1, 2009 and December 6, 2016. Offense data was extracted from the Detroit Police Department's records management system. 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. See the Note on Anonymized Addresses below for more information. For data after December 6, 2016, go to https://data.detroitmi.gov/Public-Safety/DPD-All-Crime-Incidents-December-6-2016-Present/6gdg-y3kf. 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 ROWNUM - text - Data set row number CASEID - text - Case ID identifier CRIMEID - text - Offense identifier CRNO - text - Unique ID in Record Management System (YYYYMMDD Report Number) ADDRESS - text - Location of incident (see Note on Anonymized Addresses for more information) CATEGORY - text - Type of offense described in the report, categorized OFFENSEDESCRIPTION - text - Detail about the offense reported STATEOFFENSECODE - text - Michigan State Police offense code INCIDENTDATE - date - Date of incident HOUR - number - Time of incident, based on the hour SCA - number - DPD Scout Car Area, a geography within a precinct PRECINCT - number - DPD Precinct COUNCIL - number - Detroit City Council district NEIGHBORHOOD - text - The neighborhood of the original XY coordinate CENSUSTRACT - number - The Census Tract of the original XY coordinate, using the 2010 Census Tracts provided by the US Census Bureau LON - longitude - Longitude WGS 1984 LAT - latitude - Latitude WGS 1984 LOCATION - location - Location field generated by Socrata Note on Anonymized Addresses: Please note that the anonymization process for this dataset is different than for the All Crime Incidents dataset that contains information for reported crimes after December 6, 2016. For more information about anonymization prior to that date, read the metadata here: https://data.detroitmi.gov/Public-Safety/DPD-All-Crime-Incidents-December-6-2016-Present/6gdg-y3kf. The anonymization process systematically takes the point of the original XY coordinates and places them randomly within a 100 buffer of the original point. The XY coordinate fields provided in this dataset are the new, anonymized location. To mask the address field where there is a street number provided by the caller, the last two digits of the address field are removed and replaced with “00.”

  • API

    Traffic Crashes

    data.detroitmi.gov | Last Updated 2019-04-23T01:49:51.000Z

    All reported traffic crashes in Detroit from 2011-2016.

  • API

    Education Dashboard

    midashboard.michigan.gov | Last Updated 2017-12-18T21:24:38.000Z

    Open Michigan (OpenMichigan@michigan.gov) is the official State of Michigan account. Any items created by other user accounts are not endorsed by the State of Michigan.

  • API

    Restaurant Inspections - Violations by Inspection

    data.detroitmi.gov | Last Updated 2019-07-25T19:12:01.000Z

    Food safety violations that have been cited during inspections conducted by the Detroit Health Department since 8/1/2016, including the inspection date, food code definition, and the correction status. There are three categories of violations: - 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. To see the entire Michigan Food Code, go to: https://www.michigan.gov/documents/mdard/MI_Modified_2009_Food_Code_396675_7.pdf