This dataset is a compilation of address point data for the City of Tempe. The dataset contains a point location, the official address (as defined by The Building Safety Division of Community Development) for all occupiable units and any other official addresses in the City. There are several additional attributes that may be populated for an address, but they may not be populated for every address. Contact: Lynn Flaaen-Hanna, Development Services Specialist Contact E-mail Link: Map that Lets You Explore and Export Address Data Data Source: The initial dataset was created by combining several datasets and then reviewing the information to remove duplicates and identify errors. This published dataset is the system of record for Tempe addresses going forward, with the address information being created and maintained by The Building Safety Division of Community Development.Data Source Type: ESRI ArcGIS Enterprise GeodatabasePreparation Method: N/APublish Frequency: WeeklyPublish Method: AutomaticData Dictionary

These datasets contain measures of socioeconomic and demographic characteristics by U.S. census tract for the years 1990-2022 and ZIP code tabulation area (ZCTA) for the years 2008-2022. Example measures include population density; population distribution by race, ethnicity, age, and income; income inequality by race and ethnicity; and proportion of population living below the poverty level, receiving public assistance, and female-headed or single parent families with kids. The datasets also contain a set of theoretically derived measures capturing neighborhood socioeconomic disadvantage and affluence, as well as a neighborhood index of Hispanic, foreign born, and limited English. The disadvantage variable was incorrectly calculated for the following datasets: DS7 Socioeconomic Status and Demographic Characteristics of Census Tracts (2020 Census), United States, 2018-2022 Data DS8 Socioeconomic Status and Demographic Characteristics of ZIP Code Tabulation Areas (2020 Census), United States, 2018-2022 Data Please refrain from downloading these datasets. The updated datasets are forthcoming and will be made available soon. Users needing these datasets can reach out to nanda-admin@umich.edu.

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

Description and PurposeThese data include the individual responses for the City of Tempe Annual Community Survey conducted by ETC Institute. These data help determine priorities for the community as part of the City's on-going strategic planning process. Averaged Community Survey results are used as indicators for several city performance measures. The summary data for each performance measure is provided as an open dataset for that measure (separate from this dataset). The performance measures with indicators from the survey include the following (as of 2022):1. Safe and Secure Communities1.04 Fire Services Satisfaction1.06 Crime Reporting1.07 Police Services Satisfaction1.09 Victim of Crime1.10 Worry About Being a Victim1.11 Feeling Safe in City Facilities1.23 Feeling of Safety in Parks2. Strong Community Connections2.02 Customer Service Satisfaction2.04 City Website Satisfaction2.05 Online Services Satisfaction Rate2.15 Feeling Invited to Participate in City Decisions2.21 Satisfaction with Availability of City Information3. Quality of Life3.16 City Recreation, Arts, and Cultural Centers3.17 Community Services Programs3.19 Value of Special Events3.23 Right of Way Landscape Maintenance3.36 Quality of City Services4. Sustainable Growth & DevelopmentNo Performance Measures in this category presently relate directly to the Community Survey5. Financial Stability & VitalityNo Performance Measures in this category presently relate directly to the Community SurveyMethodsThe survey is mailed to a random sample of households in the City of Tempe. Follow up emails and texts are also sent to encourage participation. A link to the survey is provided with each communication. To prevent people who do not live in Tempe or who were not selected as part of the random sample from completing the survey, everyone who completed the survey was required to provide their address. These addresses were then matched to those used for the random representative sample. If the respondent’s address did not match, the response was not used. To better understand how services are being delivered across the city, individual results were mapped to determine overall distribution across the city. Additionally, demographic data were used to monitor the distribution of responses to ensure the responding population of each survey is representative of city population. Processing and LimitationsThe location data in this dataset is generalized to the block level to protect privacy. This means that only the first two digits of an address are used to map the location. When they data are shared with the city only the latitude/longitude of the block level address points are provided. This results in points that overlap. In order to better visualize the data, overlapping points were randomly dispersed to remove overlap. The result of these two adjustments ensure that they are not related to a specific address, but are still close enough to allow insights about service delivery in different areas of the city. This data is the weighted data provided by the ETC Institute, which is used in the final published PDF report.The 2022 Annual Community Survey report is available on data.tempe.gov. The individual survey questions as well as the definition of the response scale (for example, 1 means “very dissatisfied” and 5 means “very satisfied”) are provided in the data dictionary.Additional InformationSource: Community Attitude SurveyContact (author): Wydale HolmesContact E-Mail (author): wydale_holmes@tempe.govContact (maintainer): Wydale HolmesContact E-Mail (maintainer): wydale_holmes@tempe.govData Source Type: Excel tablePreparation Method: Data received from vendor after report is completedPublish Frequency: AnnualPublish Method: ManualData Dictionary

Presents the number of cases and individuals for each shelter case type by borough and community district

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.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RandD@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data is updated daily Tuesday through Sunday. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

Our Communities: The 2025 Data Book provides insights into the communities that comprise Cuyahoga County. It is intended to be used by local governments, community organizations, and others interested in learning more about our communities. It can also be used as a resource in preparing grant applications, understanding community changes, and identifying issues to address.The Data Book series was conceived and developed for the following purposes:Assist communities in understanding their Indicators: Provide communities with the data that helps them make funding and programming decisions.Provide recent data in an accessible format: Share data as quickly as possible in ways that are easy to understand and visualize for anyone in a community. Update the data regularly: Select data that can be updated on an annual basis easily and quickly so that communities can see how national, regional, or local polices are affecting them. Vintage of boundaries: 2024Vintage of data: VariesGeography: Municipalities (Census Subdivisions)Coverage: Cuyahoga CountyData Sources: U.S. Census Bureau 2020 Census, U.S. Census Bureau Population Estimates, U.S. Census bureau 5-Year American Community Survey (ACS), Longitudinal Employer-Household Dynamics (LEHD), Northeast Ohio Metropolitan Data Resources (NEOMDR), Northeast Ohio Community and Neighborhood Data for Organizing (NEOCANDO), Urban Tree Canopy Assessment (UTC), Cuyahoga County Fiscal Office, County Planning Information and Research, Transportation Information and Mapping Systems (TIMS), Center for Disease Control and Prevention (CDC) Data downloaded from: Various SourcesDate the Data was Downloaded: Varies

These data include the individual responses for the City of Tempe Annual Community Survey conducted by ETC Institute. This dataset has two layers and includes both the weighted data and unweighted data. Weighting data is a statistical method in which datasets are adjusted through calculations in order to more accurately represent the population being studied. The weighted data are used in the final published PDF report.These data help determine priorities for the community as part of the City's on-going strategic planning process. Averaged Community Survey results are used as indicators for several city performance measures. The summary data for each performance measure is provided as an open dataset for that measure (separate from this dataset). The performance measures with indicators from the survey include the following (as of 2023):1. Safe and Secure Communities1.04 Fire Services Satisfaction1.06 Crime Reporting1.07 Police Services Satisfaction1.09 Victim of Crime1.10 Worry About Being a Victim1.11 Feeling Safe in City Facilities1.23 Feeling of Safety in Parks2. Strong Community Connections2.02 Customer Service Satisfaction2.04 City Website Satisfaction2.05 Online Services Satisfaction Rate2.15 Feeling Invited to Participate in City Decisions2.21 Satisfaction with Availability of City Information3. Quality of Life3.16 City Recreation, Arts, and Cultural Centers3.17 Community Services Programs3.19 Value of Special Events3.23 Right of Way Landscape Maintenance3.36 Quality of City Services4. Sustainable Growth & DevelopmentNo Performance Measures in this category presently relate directly to the Community Survey5. Financial Stability & VitalityNo Performance Measures in this category presently relate directly to the Community SurveyMethods:The survey is mailed to a random sample of households in the City of Tempe. Follow up emails and texts are also sent to encourage participation. A link to the survey is provided with each communication. To prevent people who do not live in Tempe or who were not selected as part of the random sample from completing the survey, everyone who completed the survey was required to provide their address. These addresses were then matched to those used for the random representative sample. If the respondent’s address did not match, the response was not used. To better understand how services are being delivered across the city, individual results were mapped to determine overall distribution across the city. Additionally, demographic data were used to monitor the distribution of responses to ensure the responding population of each survey is representative of city population. Processing and Limitations:The location data in this dataset is generalized to the block level to protect privacy. This means that only the first two digits of an address are used to map the location. When they data are shared with the city only the latitude/longitude of the block level address points are provided. This results in points that overlap. In order to better visualize the data, overlapping points were randomly dispersed to remove overlap. The result of these two adjustments ensure that they are not related to a specific address, but are still close enough to allow insights about service delivery in different areas of the city. The weighted data are used by the ETC Institute, in the final published PDF report.The 2023 Annual Community Survey report is available on data.tempe.gov or by visiting https://www.tempe.gov/government/strategic-management-and-innovation/signature-surveys-research-and-dataThe individual survey questions as well as the definition of the response scale (for example, 1 means “very dissatisfied” and 5 means “very satisfied”) are provided in the data dictionary.Additional InformationSource: Community Attitude SurveyContact (author): Adam SamuelsContact E-Mail (author): Adam_Samuels@tempe.govContact (maintainer): Contact E-Mail (maintainer): Data Source Type: Excel tablePreparation Method: Data received from vendor after report is completedPublish Frequency: AnnualPublish Method: ManualData Dictionary

Zoom and pan to a neighborhood location of interest, or enter an address to locate, then click on the map to see a pop-up showing the neighborhood association at that location along with contact information for the City of Rockville neighborhood resources coordinator.

All BPD data on Open Baltimore is preliminary data and subject to change. The information presented through Open Baltimore represents Part I victim based crime data. The data do not represent statistics submitted to the FBI's Uniform Crime Report (UCR); therefore any comparisons are strictly prohibited. For further clarification of UCR data, please visit http://www.fbi.gov/about-us/cjis/ucr/ucr. Please note that this data is preliminary and subject to change. Prior month data is likely to show changes when it is refreshed on a monthly basis. All data is geocoded to the approximate latitude/longitude location of the incident and excludes those records for which an address could not be geocoded. Any attempt to match the approximate location of the incident to an exact address is strictly prohibited.

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.

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.

Using the My Neighborhood tool on Boston.gov, residents can search an address and find city resources closest to them, including City Councilor information, the nearest public library and park, early voting information, and more. This is the underlying dataset for the My Neighborhood tool. It is the result of joining datasets from multiple departments based on address and location information in the Street Address Management (SAM) system that is administered by the City. Each row in this dataset represents an address in the city and the resources associated with it.

This dataset contains measures of the number and per capita density of all eating and drinking places plus select subtypes – fast food restaurants, coffee shops, and bars – per United States census tract from 2006 through 2015. Establishment data was taken from the National Establishment Time Series (NETS) database which classifies establishments by North American Industry Classification System (NAICS) code and provides detailed address history.

This dataset and map service provides information on the U.S. Housing and Urban Development's (HUD) low to moderate income areas. The term Low to Moderate Income, often referred to as low-mod, has a specific programmatic context within the Community Development Block Grant (CDBG) program. Over a 1, 2, or 3-year period, as selected by the grantee, not less than 70 percent of CDBG funds must be used for activities that benefit low- and moderate-income persons. HUD uses special tabulations of Census data to determine areas where at least 51% of households have incomes at or below 80% of the area median income (AMI). This dataset and map service contains the following layer.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RandD@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data is updated daily Tuesday through Sunday. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

This dataset contains measures of the number and per capita density of personal service establishments – such as hairdressers, barber shops, nail salons, laundromats, and dry cleaners – per United States census tract from 2006 through 2015. Establishment data was taken from the National Establishment Time Series (NETS) database which classifies establishments by North American Industry Classification System (NAICS) code and provides detailed address history.

All BPD data on Open Baltimore is preliminary data and subject to change. The information presented through Open Baltimore represents Part I victim based crime data. The data do not represent statistics submitted to the FBI's Uniform Crime Report (UCR); therefore any comparisons are strictly prohibited. For further clarification of UCR data, please visit http://www.fbi.gov/about-us/cjis/ucr/ucr. Please note that this data is preliminary and subject to change. Prior month data is likely to show changes when it is refreshed on a monthly basis. All data is geocoded to the approximate latitude/longitude location of the incident and excludes those records for which an address could not be geocoded. Any attempt to match the approximate location of the incident to an exact address is strictly prohibited.

Disclaimer: These data are updated by the author and are not an official product of the Federal Reserve Bank of Cleveland.This project provides two sets of migration estimates for the major US metro areas. The first series measures net migration of people to and from the urban neighborhoods of the metro areas. The second series covers all neighborhoods but breaks down net migration to other regions by four region types: (1) high-cost metros, (2) affordable, large metros, (3) midsized metros, and (4) small metros and rural areas. These series were introduced in a Cleveland Fed District Data Brief entitled “Urban and Regional Migration Estimates: Will Your City Recover from the Pandemic?"The migration estimates in this project are created with data from the Federal Reserve Bank of New York/Equifax Consumer Credit Panel (CCP). The CCP is a 5 percent random sample of the credit histories maintained by Equifax. The CCP reports the census block of residence for over 10 million individuals each quarter. Each month, Equifax receives individuals’ addresses, along with reports of debt balances and payments, from creditors (mortgage lenders, credit card issuers, student loan servicers, etc.). An algorithm maintained by Equifax considers all of the addresses reported for an individual and identifies the individual’s most likely current address. Equifax anonymizes the data before they are added to the CCP, removing names, addresses, and Social Security numbers (SSNs). In lieu of mailing addresses, the census block of the address is added to the CCP. Equifax creates a unique, anonymous identifier to enable researchers to build individuals’ panels. The panel nature of the data allows us to observe when someone has migrated and is living in a census block different from the one they lived in at the end of the preceding quarter. For more details about the CCP and its use in measuring migration, see Lee and Van der Klaauw (2010) and DeWaard, Johnson and Whitaker (2019). DefinitionsMetropolitan areaThe metropolitan areas in these data are combined statistical areas. This is the most aggregate definition of metro areas, and it combines Washington DC with Baltimore, San Jose with San Francisco, Akron with Cleveland, etc. Metro areas are combinations of counties that are tightly linked by worker commutes and other economic activity. All counties outside of metropolitan areas are tracked as parts of a rural commuting zone (CZ). CZs are also groups of counties linked by commuting, but CZ definitions cover all counties, both metropolitan and non-metropolitan. High-cost metropolitan areasHigh-cost metro areas are those where the median list price for a house was more than $200 per square foot on average between April 2017 and April 2022. These areas include San Francisco-San Jose, New York, San Diego, Los Angeles, Seattle, Boston, Miami, Sacramento, Denver, Salt Lake City, Portland, and Washington-Baltimore. Other Types of RegionsMetro areas with populations above 2 million and house price averages below $200 per square foot are categorized as affordable, large metros. Metro areas with populations between 500,000 and 2 million are categorized as mid-sized metros, regardless of house prices. All remaining counties are in the small metro and rural category.To obtain a metro area's total net migration, sum the four net migration values for the the four types of regions.Urban neighborhoodCensus tracts are designated as urban if they have a population density above 7,000 people per square mile. High density neighborhoods can support walkable retail districts and high-frequency public transportation. They are more likely to have the “street life” that people associate with living in an urban rather than a suburban area. The threshold of 7,000 people per square mile was selected because it was the average density in the largest US cities in the 1930 census. Before World War II, workplaces, shopping, schools and parks had to be accessible on foot. Tracts are also designated as urban if more than half of their housing units were built before WWII and they have a population density above 2,000 people per square mile. The lower population density threshold for the pre-war neighborhoods recognizes that many urban tracts have lost population since the 1960s. While the street grids usually remain, the area also needs su