Description: The neighborhoods shown in this dataset are derived from a larger dataset drawn and maintained by the Data Desk, a team of Times reporters and Web developers in downtown L.A. The boundaries have expanded and shifted over time and now cover all of Los Angeles County broken down into 272 neighborhoods.This version of the LA Times boundaries only includes neighborhoods fully or partially within the City of Los Angeles. Neighborhoods that extend into other cities have been clipped to only show the portion(s) of the neighborhoods that are within the City of Los Angeles.Data Source: Los Angeles Times' Mapping LA project.Last Updated: October 7, 2016Refresh Rate: Never - Historical data (Note: should the LA Times update their Mapping LA project with new boundaries in the future, a new LA-specific layer will be added to the GeoHub as well.)

The Census Bureau does not recognize or release data for Boston neighborhoods. However, Census block groups can be aggregated to approximate Boston neighborhood boundaries to allow for reporting and visualization of Census data at the neighborhood level. Census block groups are created by the U.S. Census Bureau as statistical geographic subdivisions of a census tract defined for the tabulation and presentation of data from the decennial census and the American Community Survey. The 2020 Census block group boundary files for Boston can be found here. These block group-approximated neighborhood boundaries are used for work with Census data. Work that does not rely on Census data generally uses the Boston neighborhood boundaries found here.

This web service depicts nearly 17,000 neighborhood boundaries in over 650 U.S. cities. Zillow created the neighborhood boundaries and is sharing them with the public under a Creative Commons license. Users of the data must credit Zillow as the data source. Additional information regarding this dataset can be found at https://www.zillow.com/howto/api/neighborhood-boundaries.htm. Note that neighborhood boundaries are not formal geographic boundaries for legal or jurisdictional purposes and should not be interpreted as such.

Neighborhood Map Atlas neighborhoods are derived from the Seattle City Clerk's Office Geographic Indexing Atlas. These are the smallest neighborhood areas and have been supplemented with alternate names from other sources in 2020. They roll up to the district areas. The sub-neighborhood field contains the most common name and the alternate name field is a comma delimited list of all the alternate names.The original atlas is designed for subject indexing of legislation, photographs, and other documents and is an unofficial delineation of neighborhood boundaries used by the City Clerks Office. Sources for this atlas and the neighborhood names used in it include a 1980 neighborhood map produced by the Department of Community Development, Seattle Public Library indexes, a 1984-1986 Neighborhood Profiles feature series in the Seattle Post-Intelligencer, numerous parks, land use and transportation planning studies, and records in the Seattle Municipal Archives. Many of the neighborhood names are traditional names whose meaning has changed over the years, and others derive from subdivision names or elementary school attendance areas.Disclaimer: The Seattle City Clerk's Office Geographic Indexing Atlas is designed for subject indexing of legislation, photographs, and other records in the City Clerk's Office and Seattle Municipal Archives according to geographic area. Neighborhoods are named and delineated in this collection of maps in order to provide consistency in the way geographic names are used in describing records of the Archives and City Clerk, thus allowing precise retrieval of records. The neighborhood names and boundaries are not intended to represent any "official" City of Seattle neighborhood map.

The Office of the City Clerk makes no claims as to the completeness, accuracy, or content of any data contained in the Geographic Indexing Atlas; nor does it make any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the representations furnished herein. The maps are subject to change for administrative purposes of the Office of the City Clerk. Information contained in the site, if used for any purpose other than as an indexing and search aid for the databases of the Office of the City Clerk, is being used at one's own risk.

KML file of neighborhood boundaries in Chicago, as developed by the Office of Tourism. These boundaries are approximate and names are not official. To view or use these files, special GIS software, such as Google Earth, is required.

This data set describes Neighborhood Clusters that have been used for community planning and related purposes in the District of Columbia for many years. It does not represent boundaries of District of Columbia neighborhoods. Cluster boundaries were established in the early 2000s based on the professional judgment of the staff of the Office of Planning as reasonably descriptive units of the City for planning purposes. Once created, these boundaries have been maintained unchanged to facilitate comparisons over time, and have been used by many city agencies and outside analysts for this purpose. (The exception is that 7 “additional” areas were added to fill the gaps in the original dataset, which omitted areas without significant neighborhood character such as Rock Creek Park, the National Mall, and the Naval Observatory.) The District of Columbia does not have official neighborhood boundaries. The Office of Planning provides a separate data layer containing Neighborhood Labels that it uses to place neighborhood names on its maps. No formal set of standards describes which neighborhoods are included in that dataset.Whereas neighborhood boundaries can be subjective and fluid over time, these Neighborhood Clusters represent a stable set of boundaries that can be used to describe conditions within the District of Columbia over time.

The Census Bureau does not recognize or release data for Boston neighborhoods. However, Census tracts can be aggregated to approximate Boston neighborhood boundaries to allow for reporting and visualization of Census data at the neighborhood level. Census tracts are created by the U.S. Census Bureau as statistical geographic subdivisions of a county defined for the tabulation and presentation of data from the decennial census and the American Community Survey. The 2020 Census tract boundary files for Boston can be found here. These tract-approximated neighborhood boundaries are used for work with Census data. Work that does not rely on Census data generally uses the Boston neighborhood boundaries found here.

Neighbourhood Boundaries in the City of Victoria. Data gets updated on an as-needed basis.The "Last Updated" date shown on our Open Data Portal refers to the last time the data schema was modified in the portal, or any changes were made to this description. We update our data through scripts which does not trigger the "last updated" date to change.Note: Attributes represent each field in a dataset, and some fields will contain information such as ID numbers. As a result some visualizations on the tabs on our Open Data page will not be relevant.

The attribute information for this layer includes links to the respective neighborhood associations. If there are questions regrading this data layer, you can either contact the City of Minneapolis Neighborhood & Community Relations office, or Minneapolis GIS.

A. SUMMARY The Department of Public Health and the Mayor’s Office of Housing and Community Development, with support from the Planning Department, created these 41 neighborhoods by grouping 2010 Census tracts, using common real estate and residents’ definitions for the purpose of providing consistency in the analysis and reporting of socio-economic, demographic, and environmental data, and data on City-funded programs and services. These neighborhoods are not codified in Planning Code nor Administrative Code, although this map is referenced in Planning Code Section 415 as the “American Community Survey Neighborhood Profile Boundaries Map. Note: These are NOT statistical boundaries as they are not controlled for population size. This is also NOT an official map of neighborhood boundaries in SF but an aggregation of Census tracts and should be used in conjunction with other spatial boundaries for decision making. B. HOW THE DATASET IS CREATED This dataset is produced by assigning Census tracts to neighborhoods based on existing neighborhood definitions used by Planning and MOHCD. A qualitative assessment is made to identify the appropriate neighborhood for a given tract based on understanding of population distribution and significant landmarks. Once all tracts have been assigned a neighborhood, the tracts are dissolved to produce this dataset, Analysis Neighborhoods. C. UPDATE PROCESS This dataset is static. Changes to the analysis neighborhood boundaries will be evaluated as needed by the Analysis Neighborhood working group led by DataSF and the Planning department and includes staff from various other city departments. Contact us for any questions. D. HOW TO USE THIS DATASET Downloading this dataset and opening it in Excel may cause some of the data values to be lost or not display properly (particularly the Analysis Neighborhood column). For a simple list of Analysis Neighborhoods without geographic coordinates, click here: https://data.sfgov.org/resource/xfcw-9evu.csv?$select=nhood E. RELATED DATASETS 2020 Census tracts assigned a neighborhood 2010 Census tracts assigned a neighborhood

Neighborhood boundaries for the City of Providence

Neighborhoods within Baltimore City limits. This dataset was sourced from Baltimore Neighborhood Indicators Alliance (BNIA). No additional

   metadata was provided with the dataset.


   This is part of a collection of Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

This dataset was created by the DC Office of Planning and provides a simplified representation of the neighborhoods of the District of Columbia. These boundaries are used by the Office of Planning to determine appropriate locations for placement of neighborhood names on maps. They do not reflect detailed boundary information, do not necessarily include all commonly-used neighborhood designations, do not match planimetric centerlines, and do not necessarily match Neighborhood Cluster boundaries. There is no formal set of standards that describes which neighborhoods are represented or where boundaries are placed. These informal boundaries are not appropriate for display, calculation, or reporting. Their only appropriate use is to guide the placement of text labels for DC's neighborhoods. This is an informal product used for internal mapping purposes only. It should be considered draft, will be subject to change on an irregular basis, and is not intended for publication.

Update frequency: Datasets are refreshed every night to ensure the most current information is available. Even if there are no changes, the data will be updated nightly.

Polygons representing City of Milwaukee neighborhoods as defined by the City of Milwaukee Department of City Development (DCD) through the "Milwaukee Neighborhood Identification Project" of 2000 - subdivisions, major streets, physical barriers, community group participation, housing styles, types, & ages, historic areas, and residents' opinions were among the factors used to define boundaries. Note: these boundaries are not intended to define or correspond to boundaries defined by individual neighborhood associations. The neighborhood boundaries identified through this initiative are not used for any official purposes by the City, and are not updated on an ongoing basis. They are not intended to define or correspond to boundaries defined by individual neighborhood organizations.

Shapefile is projected in Wisconsin State Plane South NAD27 (WKID 32054)

Portland Neighborhood association boundaries. BPS maintains GIS data under direction of ONI.-- Additional Information: Category: Boundary Purpose: Mapped by-law boundaries of Portland neighborhoods. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53509

This shapefile includes neighborhoods boundaries from Community Foundation, Innovate Memphis, neighborhood CDCs, and other civic groups for use on the map tools "Public Safety" and "Open311." It is not an exhaustive list. If you'd like add your group's boundaries, please contact Sarah Harris at sarah.harris@memphistn.gov.

Due to a limitation of the platform, community boundaries are split in to two groups to avoid overlapping boundaries.

Neighborhood notification boundaries created by the Department of City Planning. These boundaries are designed solely for the Planning Department's neighborhood notifications where neighborhood groups are notified about certain types of developments in their area. An Excel spreadsheet of Neighborhood Groups contact details can be downloaded from this page: http://sf-planning.org/index.aspx?page=1654 There are alternative neighborhood boundaries available (which include a larger number of neighborhoods) here (Mayors Office): https://data.sfgov.org/d/pty2-tcw4 and here (Realtors): https://data.sfgov.org/Geography/SF-Realtor-Neighborhoods/wwis-y924

NYC Neighborhoods polygons and correlated data with their respective Postal Codes, Assembly Districts, Community Districts, Congressional Districts, Council Districts and State Senate Districts created by Ontodia. There are hundreds of neighborhoods in New York City's five boroughs, each with unique characteristics and histories. Many historical neighborhood names are derived from the names of the previously independent villages, towns, and cities that were incorporated into into the City of New York in the consolidation of 1898. Other neighborhood names have been introduced by real estate developers and urban planners, sometimes contentiously. Boundaries of neighborhoods are notoriously fuzzy, although many boundaries are widely agreed upon. Complicating the definition of neighborhood further, boundaries may overlap, some neighborhoods may function as a micro-neighborhood within another neighborhood, or a larger district which can be made up of multiple neighborhoods. Names and boundaries of neighborhoods shift over time; they are determined by the collective conscious of the people who live, work, and play in these places. There is never an official version of neighborhoods, but the concept is deeply meaningful to many people. In many cases a New Yorker is just as proud to claim identity with a particular neighborhood, and visitors plan their trips around visits to specific neighborhoods. To display data about neighborhoods on NYCpedia we created our own neighborhood boundaries, 264 in all. In order to display a continuous map with no overlap some boundaries have been stretched or shrunk, and neighborhoods have been omitted in this version. We intend to expand our work developing neighborhood polygon files (all released with open source license) and also to collect and organize as many meaningful alternative versions of neighborhood boundaries as possible. If you are a map geek or software developer who builds apps about New York City you can find the shapefile and geoJSON of the NYCpedia neighborhoods on Data Wrangler. Drop us a line if you see any errors, or if you have suggestions for how to improve our conception of NYC geography.

Neighborhood boundaries that were defined in 2006 by the Mayor's Office of Neighborhood Services for use with the SF Find tool: https://sfplanninggis.org/sffind. All boundaries are for the purpose of defining general locations of neighborhoods for the SF FIND application only, and as such they are not "hard" lines of demarcation.