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.

The Mayor’s Office utilizes the most recent data to inform decisions about COVID-19 response and policies. The Los Angeles COVID-19 Neighborhood Map visualizes the cases and deaths across 139 neighborhoods in the city. It includes the same data used by the office to spot changes in infection trends in the city, and identify areas where testing resources should be deployed.Data Source:Data are provided on a weekly basis by the LA County Department of Public Health and prepared by the LA Mayor's Office Innovation Team. The data included in this map are on a one-week lag. That means the data shown here are reporting statistics gathered from one week ago. This map will be updated weekly on Mondays. Click on the maps to zoom in, get more details, and see the legends.

The Mayor’s Office utilizes the most recent data to inform decisions about COVID-19 response and policies. The Los Angeles COVID-19 Neighborhood Map visualizes the cases and deaths across 139 neighborhoods in the city. It includes the same data used by the office to spot changes in infection trends in the city, and identify areas where testing resources should be deployed.Data Source:Data are provided on a weekly basis by the LA County Department of Public Health and prepared by the LA Mayor's Office Innovation Team. The data included in this map are on a one-week lag. That means the data shown here are reporting statistics gathered from one week ago. This map will be updated weekly on Mondays. Click on the maps to zoom in, get more details, and see the legends.

Neighborhood map atlas district areas are derived from the Seattle City Clerk's Office Geographic Indexing Atlas. These are the largest neighborhood areas and have been supplemented with alternate names from other sources in 2020. They are subdivided further into the neighborhood map atlas sub-areas called neighborhoods. The sub-neighborhoods field contains a comma delimited list of all the sub-areas and their 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.

"Neighborhood Financial Health (NFH) Digital Mapping and Data Tool provides neighborhood financial health indicator data for every neighborhood in New York City. DCWP's Office of Financial Empowerment (OFE) also developed NFH Indexes to present patterns in the data within and across neighborhoods. NFH Index scores describe relative differences between neighborhoods across the same indicators; they do not evaluate neighborhoods against fixed standards. OFE intends for the NFH Indexes to provide an easy reference tool for comparing neighborhoods, and to establish patterns in the relationship of NFH indicators to economic and demographic factors, such as race and income. Understanding these connections is potentially useful for uncovering systems that perpetuate the racial wealth gap, an issue with direct implications for OFE’s mission to expand asset building opportunities for New Yorkers with low and moderate incomes. This data tool was borne out of the Collaborative for Neighborhood Financial Health, a community-led initiative designed to better understand how neighborhoods influence the financial health of their residents.

This map symbolizes the relative population counts for the City's 12 Data Divisions, aggregating the tract-level estimates from the the Census Bureau's American Community Survey 2021 five-year samples. Please refer to the map's legend for context to the color shading -- darker hues indicate more population.If you click on each Data Division, you can view other Census demographic information about that Data Division in addition to the population count.About the Census Data:The data comes from the U.S. Census Bureau's American Community Survey's 2017-2021 five-year samples. The American Community Survey (ACS) is an ongoing survey conducted by the federal government that provides vital information annually about America and its population. Information from the survey generates data that help determine how more than $675 billion in federal and state funds are distributed each year.For more information about the Census Bureau's ACS data and process of constructing the survey, visit the ACS's About page.About the City's Data Divisions:As a planning analytic tool, an interdepartmental working group divided Rochester into 12 “data divisions.” These divisions are well-defined and static so they are positioned to be used by the City of Rochester for statistical and planning purposes. Census data is tied to these divisions and serves as the basis for analyses over time. As such, the data divisions are designed to follow census boundaries, while also recognizing natural and human-made boundaries, such as the River, rail lines, and highways. Historical neighborhood boundaries, while informative in the division process, did not drive the boundaries. Data divisions are distinct from the numerous neighborhoods in Rochester. Neighborhood boundaries, like quadrant boundaries, police precincts, and legislative districts often change, which makes statistical analysis challenging when looking at data over time. The data division boundaries, however, are intended to remain unchanged. It is hoped that over time, all City data analysts will adopt the data divisions for the purpose of measuring change over time throughout the city.

City map with neighborhoods boundaries

Analysis of ‘Planning Neighborhood Groups Map’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/43f70602-710e-44e3-a7cd-91a8df265003 on 26 January 2022.

--- Dataset description provided by original source is as follows ---

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/d/5gzd-g9ns

--- Original source retains full ownership of the source dataset ---

This feature class represents the boundaries of the City of Austin Neighborhood Planning Areas (NPA). The status of these areas, as directed by City Council, can either be plan approved, planning underway/set to begin, future planning area, or non-neighborhood planning area. Future planning area boundaries may change before they are set by the City Council to begin. See https://www.austintexas.gov/department/planning-and-zoning/plans for more information.

Terms of Use This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries. This product has been produced by the City of Austin for the sole purpose of geographic reference. No warranty is made by the City of Austin regarding specific accuracy or completeness.

This feature class represents the boundaries of the City of Austin Neighborhood Planning Areas (NPA). The status of these areas, as directed by City Council, can either be plan approved, planning underway/set to begin, future planning area, or non-neighborhood planning area. Future planning area boundaries may change before they are set by the City Council to begin. See https://www.austintexas.gov/department/planning-and-zoning/plans for more information. Terms of Use This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries. This product has been produced by the City of Austin for the sole purpose of geographic reference. No warranty is made by the City of Austin regarding specific accuracy or completeness.

A. SUMMARY This dataset includes COVID-19 tests by resident neighborhood and specimen collection date (the day the test was collected). Specifically, this dataset includes tests of San Francisco residents who listed a San Francisco home address at the time of testing. These resident addresses were then geo-located and mapped to neighborhoods. The resident address associated with each test is hand-entered and susceptible to errors, therefore neighborhood data should be interpreted as an approximation, not a precise nor comprehensive total.

In recent months, about 5% of tests are missing addresses and therefore cannot be included in any neighborhood totals. In earlier months, more tests were missing address data. Because of this high percentage of tests missing resident address data, this neighborhood testing data for March, April, and May should be interpreted with caution (see below)

Percentage of tests missing address information, by month in 2020 Mar - 33.6% Apr - 25.9% May - 11.1% Jun - 7.2% Jul - 5.8% Aug - 5.4% Sep - 5.1% Oct (Oct 1-12) - 5.1%

To protect the privacy of residents, the City does not disclose the number of tests in neighborhoods with resident populations of fewer than 1,000 people. These neighborhoods are omitted from the data (they include Golden Gate Park, John McLaren Park, and Lands End).

Tests for residents that listed a Skilled Nursing Facility as their home address are not included in this neighborhood-level testing data. Skilled Nursing Facilities have required and repeated testing of residents, which would change neighborhood trends and not reflect the broader neighborhood's testing data.

This data was de-duplicated by individual and date, so if a person gets tested multiple times on different dates, all tests will be included in this dataset (on the day each test was collected).

The total number of positive test results is not equal to the total number of COVID-19 cases in San Francisco. During this investigation, some test results are found to be for persons living outside of San Francisco and some people in San Francisco may be tested multiple times (which is common). To see the number of new confirmed cases by neighborhood, reference this map: https://sf.gov/data/covid-19-case-maps#new-cases-maps

B. HOW THE DATASET IS CREATED COVID-19 laboratory test data is based on electronic laboratory test reports. Deduplication, quality assurance measures and other data verification processes maximize accuracy of laboratory test information. All testing data is then geo-coded by resident address. Then data is aggregated by analysis neighborhood and specimen collection date.

Data are prepared by close of business Monday through Saturday for public display.

C. UPDATE PROCESS Updates automatically at 05:00 Pacific Time each day. Redundant runs are scheduled at 07:00 and 09:00 in case of pipeline failure.

D. HOW TO USE THIS DATASET San Francisco population estimates for geographic regions can be found in a view based on the San Francisco Population and Demographic Census dataset. These population estimates are from the 2016-2020 5-year American Community Survey (ACS).

Due to the high degree of variation in the time needed to complete tests by different labs there is a delay in this reporting. On March 24 the Health Officer ordered all labs in the City to report complete COVID-19 testing information to the local and state health departments.

In order to track trends over time, a data user can analyze this data by "specimen_collection_date".

Calculating Percent Positivity: The positivity rate is the percentage of tests that return a positive result for COVID-19 (positive tests divided by the sum of positive and negative tests). Indeterminate results, which could not conclusively determine whether COVID-19 virus was present, are not included in the calculation of pe

In order to comply with the government's information disclosure policy and facilitate the use of geographical information in business operations, GIS layers have been established for the boundaries of the 12 administrative districts and 456 neighborhoods in this city for reference and use by various government agencies or relevant units. The coordinate system used for this data is TWD97.

Pittsburgh Neighborhoods

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.)

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.

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

City of Seattle neighborhood boundaries with American Community Survey (ACS) 5-year series data of frequently requested topics. Data is pulled from block group tables for the most recent ACS vintage and summarized to the neighborhoods based on block group assignment. Seattle neighborhood geography of Council Districts, Comprehensive Plan Growth Areas are included.The census block groups have been assigned to a neighborhood based on the distribution of the total population from the 2020 decennial census for the component census blocks. If the majority of the population in the block group were inside the boundaries of the neighborhood, the block group was assigned wholly to that neighborhood.Feature layer created for and used in the Neighborhood Profiles application.The attribute data associated with this map is updated annually to contain the most currently released American Community Survey (ACS) 5-year data and contains estimates and margins of error. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. <div style='font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next&qu

COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/ Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only. 2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan. Field descriptions Field descriptions for the "Plan_boundaries" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number ADOPT_DATE: Date of Plan adoption IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the City of Tucson's Open Data portal and not for regular use in ArcGIS Online, ArcGIS Enterprise or other web applications.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohn BeallCity of Tucson Development Services520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Please Note: Community Reporting Areas (CRA) have been updated to follow the 2020 census tract lines which resulted in minor changes to some boundary conditions. They have also been extended into water areas to allow the assignment of CRAs to overwater housing and businesses. To exclude the water polygons from a map choose the filter, water=0.Community reporting areas (CRAs) are designed to address a gap that existed in city geography. The task of reporting citywide information at a "community-like level" across all departments was either not undertaken or it was handled in inconsistent ways across departments. The CRA geography provides a "common language" for geographic description of the city for reporting purposes. Therefore, this geography may be used by departments for geographic reporting and tracking purposes, as appropriate. The U.S. Census Bureau census tract geography was chosen as the basis of the CRA geography due to their stability through time and link to widely-used demographic data.The following criteria for a CRA geography were defined for this effort:no overlapping areascomplete coverage of the citysuitable scale to represent neighborhood areas/conditionsreasonably stable over timeconsistent with census geographyrelatively easy to use in a data contextfamiliar system of common place namesrespects neighborhood district geography to the extent possibleThe following existing geographies were reviewed during this effort:neighborhood planning areas (DON)neighborhood districts (DON/CNC/Neighborhood District Councils)city sectors/neighborhood plan implementation areas (DON)urban centers/urban villages (DPD)population sub-areas (DPD)Neighborhood Map Atlas (City Clerk)Census tract geographytopographyvarious other geographic information sources related to neighborhood areas and common place namesThis is not an attempt to identify neighborhood boundaries as defined by neighborhoods themselves.