Boundary for the City of Detroit. Obtained from Data Driven Detroit's SDE for the Kresge Early Childhood online mapping tool on July 25, 2017.

A boundary file for the city of Detroit - this is not clipped to the coastline.

Following each census, Detroit City Council is required by the 2012 Detroit City Charter to redraw the boundaries of the City's seven non at-large districts to be "as nearly of equal population as practicable, contiguous, compact and in accordance with any other criteria permitted by law" (Sec. 3-108). After considering six district boundary proposals meant to meet these criteria, City Council selected the boundaries described in this document by an 8-1 vote on February 6, 2024. These boundaries will be used to determine resident districts when voting in 2025 municipal elections, and will officially take effect January 1, 2026.

Current (non-historic) neighborhood boundaries as compiled by Department of Neighborhoods staff in concert with community groups.

Note: This council district layer goes into effect on January 1, 2026. The council district layer in effect until December 31st, 2025 can be found hereThis Council Districts map is for illustrative purposes only and the City of Detroit makes no representations as to its accuracy. For the official geographic boundaries, please refer to the geographical boundaries formally approved by the Detroit City Council on February 6, 2024. For convenience, a link to the formally approved boundaries may be found here. The reapportioned City Council District boundaries take effect on January 1, 2026.Following each census, Detroit City Council is required by the 2012 Detroit City Charter to redraw the boundaries of the City's seven non at-large districts to be "as nearly of equal population as practicable, contiguous, compact and in accordance with any other criteria permitted by law" (Sec. 3-108).City Council selected the boundaries illustrated here by an 8-1 vote on February 6, 2024. These boundaries will be used to determine resident districts when voting in 2025 municipal elections, and will officially take effect January 1, 2026.

Map of all local historic districts in the City of Detroit that is updated regularly and intended to be used for reference purposes only. Each local historic district is enacted by an ordinance containing a legal boundary description and elements of design. To obtain a copy of an ordinance, please consult Chapter 21 of the Detroit City Code or contact the Clerk's Office. Please note that all work conducted within a local historic district (construction, alteration, demolition, site work, etc.) requires review and approval by the Historic District Commission.For more information about final reports or proposed local historic districts currently under study, please visit the Historic Designation Advisory Board webpage or contact staff at (313) 224-3487.Column DefinitionsOBJECTID: Unique identifier for each record within this dataset.Name: Name of the Local Historic DistrictSection: The corresponding section within Chapter 21 of the City's Code of Ordinances.Year_Enacted: The day and year that the Local Historic District designation was enacted by the Detroit City Council for this area. Note: the time of day is not precise.Report_Link: Link to a report written by the Historic Designation Advisory Board that defines the boundaries of the area and describes the area's history. Historic districts enacted prior to 1976 do not have corresponding final reports.GlobalID: Unique identifier for each record within this dataset across geodatabases.Interior Designation: This field indicates if any interior alterations also require review and approval by the Historic District Commission. If it is blank, then only exterior alterations are reviewed.

Location of different zoning codes in the city of Detroit, Michigan. Parcels sharing the same zoning code have been dissolved together, but remain separated by street boundaries. A comprehensive list of zoning code descriptions is contained in the attribute table. Data are from 2010 and may not reflect changes in the zoning code of parcels.Click here for metadata.

Note: This layer is the current City Council district boundaries in effect until December 31, 2025. Starting on January 1, 2026 the new City Council boundaries will be in effect and can be found here. The boundaries are for the seven single-member City Council districts and were implemented for the 2013 election after a 2009 voter referendum.

While there is no one accepted complete neighborhood boundaries in the city of Detroit, this file is a commonly used and agreed upon set of boundaries. It is published through Cityscape Detroit and has been picked up for google, bing and other online mapping services to approximate Detroit's neighborhoods.

Detroit Fire Department Battalion Boundaries. The Detroit Fire Department uses the battalion boundaries layer to manage the multiple fire stations across the city. The cities of Highland Park and Hamtramck Fire Departments are also included in this map to differentiate agency jurisdictions.

The Citizen Radio Patrol Boundaries dataset describes areas with active citizen radio patrols. The Citizen Radio Patrol program was established in 1967 by a Detroit City Council Resolution and has become an essential part of the strength and safety of Detroit's neighborhoods. Community volunteers who participate in this program receive training from DPD and volunteer a small portion of their time each month to patrol their own neighborhood. Volunteers may serve as a patrol base operator, driver, or observer, roles that work together to observe and report any suspicious activity to the police. For more information on joining or creating a Radio Patrol area, please contact Myra Gracey at the office of Workplace & Community Resilience, Detroit Police Department 313-596-2520.

City of Detroit renewed five Neighborhood Revitalization Strategy Areas (NRSA) in 2020, as defined by the Department of Housing and Urban Development (HUD) Notice CPD‐16‐16. The intent of the NRSAs is to target Community Development Block Grant (CDBG) resources and leverage them with additional resources to further comprehensive community revitalization efforts. Click here for further information.

Planning areas layer managed by PDD for any boundary update or new designation. Last updated 09/05/2024 - AN

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The QLINE is a transit line that operates along the Woodward corridor within the city limits of Detroit. It has 20 stations across a total of 12 stops from Downtown Detroit to Grand Boulevard.The dataset includes the location of all the QLINE stations. In this dataset, "station" is defined as the designated place where the streetcar loads and unloads passengers. A "stop" is defined as the location where passengers can embark and disembark. In general, each stop has a station, but there are QLINE stops that have two stations - a northbound station and a southbound station.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined because of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division or incorporated place boundaries in some states and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard Census Bureau geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.

Feature layer (hosted) containing Speed Limit & LRS Information.

The 2014 precinct data provides a comprehensive map of the City of Detroit’s Police Department precincts. The precincts were created by building from the squad car areas dataset published on the City of Detroit’s open data portal in 2014. However, D3 staff revised the precinct geographies to reflect the maps displayed on the police department’s website since the Scout Car Areas didn't line up consistently. It is possible to view each individual precinct boundary and squad car area on the City of Detroit Police Department’s website. This map was created in order to layout the boundaries of each precinct on one map, providing a complete map of all twelve police precincts. This map was created using ArcMap by Alexis Farmer and D3 staff on July 7, 2015.