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. Block groups are clusters of blocks within the same census tract. Each census tract contains at least one block group, and are uniquely numbered within census tracts. Block groups have a valid code range of 0 through 9. They also have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within block group 3 within that census tract. Block groups coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A block group usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The block group boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

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 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 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 Shootings dashboard contains information on shooting incidents where a victim was struck by a bullet, either fatally or non-fatally; that occurred in the City of Boston and fall under Boston Police Department jurisdiction. The dashboard does not contain records for self-inflicted gunshot wounds or shootings determined to be justifiable. Information on the incident, and the demographics of victims are included. This information is updated based on analysis conducted by the Boston Regional Intelligence Center under the Boston Police Department Bureau of Intelligence and Analysis. The data is for 2015 forward, with a 7 day rolling delay to allow for analysis and data entry to occur.

Building permits help to establish compliance of construction work with the minimum standards of safety established by the State Building Code to ensure public health and safety for everyone. A building permit is required before beginning most construction, demolition, modification and repair work. The Inspectional Services Department offers permitting processes tailored for a wide variety of projects, from home repairs to building demolition.

For more information on the permitting process, visit our Inspectional Services Department Permitting Process page. To apply for a new building permit or check the status of your pending permit application, go to our City of Boston Permits and Licenses Application page.

WHAT IS THE DATASET FOR?

This dataset includes information about building permits issued by the City of Boston from 2009 to the present. Permits that are being processed or have been denied, deleted, void or revoked are not included in the dataset.

WHAT PERMIT TYPES ARE PRESENT IN THE DATASET?

This dataset includes information about the following types of building permits:

• Short Form Building Permit
• Electrical Permit
• Plumbing Permit
• Gas Permit
• Electrical Low Voltage
• Long Form/Alteration Permit
• Electrical Fire Alarms
• Certificate of Occupancy
• Electrical Temporary Service
• Amendment to a Long Form
• Erect/New Construction
• Use of Premises
• Foundation Permit

For more information on these permits and their application process, visit our Building Permits information page.

WHAT DOES EACH PERMIT APPLICATION STATUS MEAN?

• Issued: indicates that the permit has been issued on date specified as issued_date.

• Open: indicates that the permit has been issued and is still valid for the applicant (i.e. not expired yet).

• Closed: indicates that the permit was successfully issued but is not valid anymore (i.e. has expired).

• Stop work: indicates the permit was successfully issued but it stopped working due to non-compliance or other issues before the expiration date.

The 2022 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The cartographic boundary files include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The generalized boundaries of most incorporated places in this file are based on those as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The 2023 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. 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 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 and beyond, 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 TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File 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.

DPH note about change from 7-day to 14-day metrics: As of 10/15/2020, this dataset is no longer being updated. Starting on 10/15/2020, these metrics will be calculated using a 14-day average rather than a 7-day average. The new dataset using 14-day averages can be accessed here: https://data.ct.gov/Health-and-Human-Services/COVID-19-case-rate-per-100-000-population-and-perc/hree-nys2

As you know, we are learning more about COVID-19 all the time, including the best ways to measure COVID-19 activity in our communities. CT DPH has decided to shift to 14-day rates because these are more stable, particularly at the town level, as compared to 7-day rates. In addition, since the school indicators were initially published by DPH last summer, CDC has recommended 14-day rates and other states (e.g., Massachusetts) have started to implement 14-day metrics for monitoring COVID transmission as well.

With respect to geography, we also have learned that many people are looking at the town-level data to inform decision making, despite emphasis on the county-level metrics in the published addenda. This is understandable as there has been variation within counties in COVID-19 activity (for example, rates that are higher in one town than in most other towns in the county).

This dataset includes a weekly count and weekly rate per 100,000 population for COVID-19 cases, a weekly count of COVID-19 PCR diagnostic tests, and a weekly percent positivity rate for tests among people living in community settings. Dates are based on date of specimen collection (cases and positivity).

A person is considered a new case only upon their first COVID-19 testing result because a case is defined as an instance or bout of illness. If they are tested again subsequently and are still positive, it still counts toward the test positivity metric but they are not considered another case.

These case and test counts do not include cases or tests among people residing in congregate settings, such as nursing homes, assisted living facilities, or correctional facilities.

These data are updated weekly; the previous week period for each dataset is the previous Sunday-Saturday, known as an MMWR week (https://wwwn.cdc.gov/nndss/document/MMWR_week_overview.pdf). The date listed is the date the dataset was last updated and corresponds to a reporting period of the previous MMWR week. For instance, the data for 8/20/2020 corresponds to a reporting period of 8/9/2020-8/15/2020.

Notes: 9/25/2020: Data for Mansfield and Middletown for the week of Sept 13-19 were unavailable at the time of reporting due to delays in lab reporting.

Crime incident reports are provided by Boston Police Department (BPD) to document the initial details surrounding an incident to which BPD officers respond. This is a dataset containing records from the new crime incident report system, which includes a reduced set of fields focused on capturing the type of incident as well as when and where it occurred. Records in the new system begin in June of 2015.

The Analyze Boston Data Exports posted now are the updated incident data from the Mark43 RMS Database which launched in September of 2019 and is complete through present with the exclusion of data that falls under MGL ch.41 s.98f. The 2019 data that was originally posted contained combined exports from the Intergraph RMS and the Mark43 RMS during 2019 but the Extract/Transfer/Load process was not updated during the transition.

Vision Zero Boston is our commitment to focus the city’s resources on proven strategies to eliminate fatal and serious traffic crashes in the city by 2030. We are inspired by the belief that even one fatality is too many. Learn more about about the Vision Zero Boston program at https://www.boston.gov/departments/transportation/vision-zero.

This dataset, provided as part of the Vision Zero Boston program, contains records of the date, time, location, and type of crash for incidents requiring public safety response which may involve injuries or fatalities. All records are compiled by the Department of Innovation and Technology from the City's Computer-Aided Dispatch (911) system and verified as having required a response from a public safety agency. To protect the privacy of individuals involved in these incidents, we do not indicate the severity of specific crashes or whether medical care was provided in any specific case.

Additional notes:

• Each incident is included only once regardless of the number of individuals involved.
• The date and time of an incident reflects when public safety response was dispatched to the location, not the crash itself.
• Records are typically updated on a monthly basis, but because the verification process involves manual confirmation of incidents, exact posting schedules may vary.
• Records may be updated after their initial posting if new information becomes available.
• Motor Vehicle Accidents (MVAs) provided in this data set are Boston EMS incidents with a documented patient encounter that were identified as an MVA during the 9-1-1 call taking process, by crews on scene, or incidents where the injury cause is documented as related to an MVA. Roadway incidents determined to involve a pedestrian or bicycle are excluded, as they are captured separately in those data sets. Please note, in June of 2024, Boston EMS transitioned to a new patient record system. During this transition, a more refined approach to identifying roadway incidents was established, allowing for additional cases to be captured. Differences in MVA rates before and after June 2024 are reflective of this new reporting methodology and should not be interpreted as a change in motor vehicle incidents. Boston EMS is actively working to further improve this dataset. Once this process is complete, historic records will be updated to reflect the new methodology. If using this data for research, please reach out to Boston EMS directly at emailems@bostonems.org if you have any questions.
• Data is now available through May 31, 2025.

After over two years of public reporting, the State Profile Report will no longer be produced and distributed after February 2023. The final release was on February 23, 2023. We want to thank everyone who contributed to the design, production, and review of this report and we hope that it provided insight into the data trends throughout the COVID-19 pandemic. Data about COVID-19 will continue to be updated at CDC’s COVID Data Tracker. The State Profile Report (SPR) is generated by the Data Strategy and Execution Workgroup in the Joint Coordination Cell, in collaboration with the White House. It is managed by an interagency team with representatives from multiple agencies and offices (including the United States Department of Health and Human Services (HHS), the Centers for Disease Control and Prevention, the HHS Assistant Secretary for Preparedness and Response, and the Indian Health Service). The SPR provides easily interpretable information on key indicators for each state, down to the county level. It is a weekly snapshot in time that: Focuses on recent outcomes in the last seven days and changes relative to the month prior Provides additional contextual information at the county level for each state, and includes national level information Supports rapid visual interpretation of results with color thresholds

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 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. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

The City of Boston reports on our contract awards as part of our commitment to transparency and to growing pathways to equitable procurement for diverse suppliers. This dataset reports on our procurement contracts and other agreements, such as grants, from Fiscal Year 2019 through Fiscal Year 2025, Quarter 3.

A contract is an agreement between the City of Boston and a supplier to acquire supplies and services over $10,000. Contracts have an award value. This is the maximum dollar amount that a business can be paid, in total, over the life of the contract.

You can view an interactive dashboard of our procurement contract award at https://www.boston.gov/equitable-procurement. This dashboard does not report on non-procurement contracts or agreement types.

To learn more about the City's procurement and supplier diversity efforts, visit:

• https://www.boston.gov/procurement
• https://www.boston.gov/supplier-diversity

** Notes on the Data **

• In some circumstances, the City department name was not recorded on the electronic contract record.
• There are some instances where the description of the contract only references City identifiers, such as a bid or purchase order number.
• Some electronic contract records do not have information recorded in our administrative systems in order to accurately categorize them as a Procurement Contract. We have included these contracts as "Other Contracts".
• In the event of a discrepancy between the electronic contract record and the signed contract document, the signed contract document is the record of truth. There are some instances where these two may differ.

** Contract Categorization **

The City categorizes agreements into Procurement Contracts and Other Contracts to distinguish contracts entered through a procurement process from other types of agreements.

• Procurement Contract: An agreement between the City of Boston and a supplier to acquire supplies and services over $10,000. Procurement contracts are awarded through competitive or limited competition procurements.

  • Competitive Procurement: A City contract is awarded after a competitive evaluation of quotes, bids, or proposals. The City can either publicly invite suppliers or selectively invite several suppliers to submit a response.
  • Limited Competition Procurement: A City contract for an item or service that is not subject to all of the requirements outlined in Massachusetts public procurement laws. This includes exempt, sole source, and emergency procurements.

• Other Contract: Other types of contracts include Government-to-Government Agreements, Grants to Nonprofits, Loans, Revenue Contracts, Trusts or Gift Agreements, Special Education, Health Insurance, and Employment Agreements.

If you have questions about this data or would like to provide feedback, please use this form: https://docs.google.com/forms/d/10_VGn3OEaa-JA5VJynZ9JKw-I3t0BAzw3ckv8rxVMLc/viewform?edit_requested=true

The Health Division of the Department of Inspectional Services ensures that all food establishments in the City of Boston meet relevant sanitary codes and standards. Businesses that serve food are inspected at least once a year, and follow-up inspections are performed on high risk establishments. Health inspections are also conducted in response to complaints of unsanitary conditions or illness. This is a legacy dataset containing records of individual inspections and results.

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 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 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 and beyond, 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.

About this dataset

Context

The dataset presents the median household incomes over the past decade across various racial categories identified by the U.S. Census Bureau in New Boston. It portrays the median household income of the head of household across racial categories (excluding ethnicity) as identified by the Census Bureau. It also showcases the annual income trends, between 2013 and 2023, providing insights into the economic shifts within diverse racial communities.The dataset can be utilized to gain insights into income disparities and variations across racial categories, aiding in data analysis and decision-making..

Key observations

• White: In New Boston, the median household income for the households where the householder is White increased by $10,767(21.22%), between 2013 and 2023. The median household income, in 2023 inflation-adjusted dollars, was $50,743 in 2013 and $61,510 in 2023.
• Black or African American: As per the U.S. Census Bureau population data, in New Boston, there are no households where the householder is Black or African American; hence, the median household income for the Black or African American population is not applicable.
• Refer to the research insights for more key observations on American Indian and Alaska Native, Asian, Native Hawaiian and Other Pacific Islander, Some other race and Two or more races (multiracial) households

Content

When available, the data consists of estimates from the U.S. Census Bureau American Community Survey (ACS) 2019-2023 5-Year Estimates.

Racial categories include:

• White
• Black or African American
• American Indian and Alaska Native
• Asian
• Native Hawaiian and Other Pacific Islander
• Some other race
• Two or more races (multiracial)

Variables / Data Columns

• Race of the head of household: This column presents the self-identified race of the household head, encompassing all relevant racial categories (excluding ethnicity) applicable in New Boston.
• 2010: 2010 median household income
• 2011: 2011 median household income
• 2012: 2012 median household income
• 2013: 2013 median household income
• 2014: 2014 median household income
• 2015: 2015 median household income
• 2016: 2016 median household income
• 2017: 2017 median household income
• 2018: 2018 median household income
• 2019: 2019 median household income
• 2020: 2020 median household income
• 2021: 2021 median household income
• 2022: 2022 median household income
• 2023: 2023 median household income
• Please note: All incomes have been adjusted for inflation and are presented in 2023-inflation-adjusted dollars.

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

Recommended for further research

This dataset is a part of the main dataset for New Boston median household income by race. You can refer the same here