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) 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. The TIGER/Line shapefiles 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 boundaries of most incorporated places in this shapefile are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2023 BAS as well.

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) 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. Public Use Microdata Areas (PUMAs) are decennial census areas that permit the tabulation and dissemination of Public Use Microdata Sample (PUMS) data, American Community Survey (ACS) data, and data from other census and surveys. For the 2020 Census, the State Data Centers (SDCs) in each state, the District of Columbia, and the Commonwealth of Puerto Rico had the opportunity to delineate PUMAS within their state or statistically equivalent entity. All PUMAs must nest within states and have a minimum population threshold of 100,000 persons. 2020 PUMAs consist of census tracts and cover the entirety of the United States, Puerto Rico and Guam. American Samoa, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands do not contain any 2020 PUMAs because the population is less than the minimum population requirement. Each PUMA is identified by a 5-character numeric census code that may contain leading zeros and a descriptive name.

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.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

place IN ('isolated_dwelling','town','village','hamlet','city')

Features may have these attributes:

• name
• is_in
• place
• population
• source

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

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. Voting district is the generic name for geographic entities such as precincts, wards, and election districts established by State governments for the purpose of conducting elections. States participating in the 2010 Census Redistricting Data Program as part of Public Law 94-171 (1975) provided the Census Bureau with boundaries, codes, and names for their VTDs. Each VTD is identified by a 1- to 6-character alphanumeric census code that is unique within county. For the 2010 Census, Kentucky and Rhode Island are the only States that did not provide voting district boundaries as part of Phase 2 (the Voting District Project) of the Redistricting Data Program and no VTDs exist for these States in the 2020 Census data products. Note that only Montana and Oregon do not have complete coverage of VTDs for the 2020 Census.

This map includes shoreline change data for the state of Massachusetts hosted by the Massachusetts Office of Coastal Zone Management.The active data layer in this map is Massachusetts Shoreline Change Transect (1970-2014) with short-term shoreline change rates. To view long-term rates, open map in Map Viewer to turn on layer.The Massachusetts Office of Coastal Zone Management launched the Shoreline Change Project in 1989 to identify erosion-prone areas of the coast. The shoreline position and change rate are used to inform management decisions regarding the erosion of coastal resources. In 2001, a shoreline from 1994 was added to calculate both long- and short-term shoreline change rates along ocean-facing sections of the Massachusetts coast. In 2013, two oceanfront shorelines for Massachusetts were added using 2008-9 color aerial orthoimagery and 2007 topographic lidar datasets obtained from the National Oceanic and Atmospheric Administration's Ocean Service, Coastal Services Center. In 2018 two new mean high water (MHW) shorelines for Massachusetts were extracted from lidar collected between 2010 and 2014 (described below). 2018 addition shoreline 1The North Shore and South Coast uses 2010 lidar data collected by the U.S. Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise. The South Shore and Outer Cape uses 2011 lidar data collected by the U.S. Geological Survey's (USGS) National Geospatial Program Office. Nantucket and Martha’s Vineyard uses 2012 lidar data collected by the USACE (post Sandy)from a 2012 USACE Post Sandy Topographic lidar survey. 2018 addition shoreline 2The North Shore, Boston, South Shore, Cape Cod Bay, Outer Cape, South Cape, Nantucket, Martha’s Vineyard, and the South Coast (around Buzzards Bay to the Rhode Island Border) is from 2013-14 lidar data collected by the (USGS) Coastal and Marine Geology Program. This 2018 update of the rate of shoreline change in Massachusetts includes two types of rates. Some of the rates include a proxy-datum bias correction, this is indicated in the filename with “PDB”. The rates that do not account for this correction have “NB” in their file names. The proxy-datum bias is applied because in some areas a proxy shoreline (like a High Water Line shoreline) has a bias when compared to a datum shoreline (like a Mean High Water shoreline). In areas where it exists, this bias should be accounted for when calculating rates using a mix of proxy and datum shorelines. This issue is explained further in Ruggiero and List (2009) and in the process steps of the metadata associated with the rates. This release includes both long-term (~150 years) and short term (~30 years) rates. Files associated with the long-term rates have “LT” in their names, files associated with short-term rates have “ST” in their names.

Updated Continually

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 filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

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.

The TIGER/Line shapefiles 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 boundaries of most incorporated places in this shapefile are as of January 1, 2021, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

highway IS NOT NULL

Features may have these attributes:

• surface
• bridge
• lanes
• smoothness
• width
• highway
• oneway
• source
• name
• layer

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

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 filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

The mission of the USGS Gap Analysis Program (GAP) is providing state, regional and national assessments of the conservation status of native vertebrate species and natural land cover types and facilitating the application of this information to land management activities. The PAD-US geodatabase is required to organize and assess the management status (i.e. apply GAP Status Codes) of elements of biodiversity protection. The goal of GAP is to 'keep common species common' by identifying species and plant communities not adequately represented in existing conservation lands. Common species are those not currently threatened with extinction. By identifying their habitats, gap analysis gives land managers and policy makers the information they need to make better-informed decisions when identifying priority areas for conservation. In cooperation with UNEP-World Conservation Monitoring Centre, GAP ensures PAD-US also supports global analyses to inform policy decisions by maintaining World Database for Protected Areas (WDPA) Site Codes and data for International Union for the Conservation of Nature (IUCN) categorized protected areas in the United States. GAP seeks to increase the efficiency and accuracy of PAD-US updates by leveraging resources in protected areas data aggregation and maintenance as described in "A Map of the Future", published following the PAD-US Design Project (July, 2009). While PAD-US was originally developed to support the GAP Mission stated above, the dataset is robust and has been expanded to support the conservation, recreation and public health communities as well. Additional applications become apparent over time.

This TNC Lands spatial dataset represents the lands and waters in which The Nature Conservancy (TNC) currently has, or historically had, an interest, legal or otherwise in Massachusetts. The system of record for TNC Lands is the Legal Records Management (LRM) system, which is TNC’s database for all TNC land transactions.TNC properties should not be considered open to the public unless specifically designated as being so. TNC may change the access status at any time at its sole discretion. It's recommended to visit preserve-specific websites or contact the organization operating the preserve before any planned visit for the latest conditions, notices, and closures. TNC prohibits redistribution or display of the data in maps or online in any way that misleadingly implies such lands are universally open to the public.The types of current land interests represented in the TNC Lands data include: Fields and Attributes included in the public dataset:Field NameField DefinitionAttributesAttribute Definitions Public NameThe name of the tract that The Nature Conservancy (TNC) Business Unit (BU) uses for public audiences.Public name of tract if applicableN/A TNC Primary InterestThe primary interest held by The Nature Conservancy (TNC) on the tractFee OwnershipProperties where TNC currently holds fee-title or exclusive rights and control over real estate. Fee Ownership can include TNC Nature Preserves, managed areas, and properties that are held for future transfer. Conservation EasementProperties on which TNC holds a conservation easement, which is a legally binding agreement restricting the use of real property for conservation purposes (e.g., no development). The easement may additionally provide the holder (TNC) with affirmative rights, such as the rights to monitor species or to manage the land. It may run forever or for an expressed term of years. Deed RestrictionProperties where TNC holds a deed restriction, which is a provision placed in a deed restricting or limiting the use of the property in some manner (e.g., if a property goes up for sale, TNC gets the first option). TransferProperties where TNC historically had a legal interest (fee or easement), then subsequently transferred the interest to a conservation partner. AssistProperties where TNC assisted another agency/entity in protecting. Management Lease or AgreementAn agreement between two parties whereby one party allows the other to use their property for a certain period of time in exchange for a periodic fee. Grazing Lease or PermitA grazing lease or permit held by The Nature Conservancy Right of WayAn access easement or agreement held by The Nature Conservancy. OtherAnother real estate interest or legal agreement held by The Nature Conservancy Fee OwnerThe name of the organization serving as fee owner of the tract, or "Private Land Owner" if the owner is a private party. If The Nature Conservancy (TNC) primary interest is a "Transfer" or "Assist", then this is the fee owner at the time of the transaction.Fee Owner NameN/A Fee Org TypeThe type of organization(s) that hold(s) fee ownership. Chosen from a list of accepted values.Organization Types for Fee OwnershipFED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest HolderThe name of the organization(s) that hold(s) a different interest in the tract, besides fee ownership or TNC Primary Interest. This may include TNC if the Other Interest is held or co-held by TNC. Multiple interest holders should be separated by a semicolon (;).Other Interest Holder NameN/A Other Interest Org TypeThe type of organization(s) that hold(s) a different interest in the tract, besides fee ownership. This may include TNC if the Other Interest is held or co-held by TNC. Chosen from a list of accepted values.Organization Types for interest holders:FED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest TypeThe other interest type held on the tract. Chosen from a list of accepted values.​Access Right of Way; Conservation Easement; Co-held Conservation Easement; Deed Restriction; Co-held Deed Restriction; Fee Ownership; Co-held Fee Ownership; Grazing Lease or Permit; Life Estate; Management Lease or Agreement; Timber Lease or Agreement; OtherN/A Preserve NameThe name of The Nature Conservancy (TNC) preserve that the tract is a part of, this may be the same name as the as the "Public Name" for the tract.Preserve Name if applicableN/APublic AccessThe level of public access allowed on the tract.Open AccessAccess is encouraged on the tract, trails are maintained, signage is abundant, and parking is available. The tract may include regular hours of availability.Open with Limited AccessThere are no special requirements for public access to the tract, the tract may include regular hours of availability with limited amenities.Restricted AccessThe tract requires a special permit from the owner for access, a registration permit on public land, or has highly variable times or conditions to use.Closed AccessNo public access is allowed on the tract.UnknownAccess information for the tract is not currently available.Gap CategoryThe Gap Analysis Project (GAP) code for the tract. Gap Analysis is the science of determining how well we are protecting common plants and animals. Developing the data and tools to support that science is the mission of the Gap Analysis Project (GAP) at the US Geological Survey. See their website for more information, linked in the field name.1 - Permanent Protection for BiodiversityPermanent Protection for Biodiversity2 - Permanent Protection to Maintain a Primarily Natural StatePermanent Protection to Maintain a Primarily Natural State3 - Permanently Secured for Multiple Uses and in natural coverPermanently Secured for Multiple Uses and in natural cover39 - Permanently Secured and in agriculture or maintained grass coverPermanently Secured and in agriculture or maintained grass cover4 - UnsecuredUnsecured (temporary easements lands and/or municipal lands that are already developed (schools, golf course, soccer fields, ball fields)9 - UnknownUnknownProtected AcresThe planar area of the tract polygon in acres, calculated by the TNC Lands geographic information system (GIS).Total geodesic area of polygon in acresProjection: WGS 1984 Web Mercator Auxiliary SphereOriginal Protection DateThe original protection date for the tract, from the Land Resource Management (LRM) system record.Original protection dateN/AStateThe state within the United States of America or the Canadian province where the tract is located.Chosen from a list of state names.N/ACountryThe name of the country where the tract is located.Chosen from a list of countries.N/ADivisionThe name of the TNC North America Region Division where the tract is located. Chosen from a list of TNC North America DivisionsN/A

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

railway IN ('rail','station')

Features may have these attributes:

• layer
• name
• railway
• ele
• operator:type
• source
• addr:full
• addr:city

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This polygon layer contains the six elective districts for state legislators who represent Cambridge in the Massachusetts House of Representatives.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription DISTRICT type: Stringwidth: 30precision: 0 State Representative district name

REP type: Stringwidth: 50precision: 0 Name of current state representative for the district

Party type: Stringwidth: 8precision: 0 Party affiliation of current representative

EditDate type: Stringwidth: 4precision: 0

created_date type: Datewidth: 8precision: 0

last_edited_date type: Datewidth: 8precision: 0

We offer a simple API for searching and retrieving corporations data which you may use in your applications and web sites. Results can be returned in JSON with padding (JSONP) and XML formats. You do not need to apply for a special key to retrieve the information.

Getting Started

The easiest way to retrieve results is to use our web site to search for the information you need, using the parameters you plan to use in your application. On the results screen for both the results and the details of a corporation/entity, append the query string with "format=xml" or "format=json", respectively. This will give you an example of what will be returned. You can then use the final URL and modify the values as you deem necessary.

Searching

A maximum of 20 results are returned with each query.

URL: http://www.sos.wa.gov/corps/search_results.aspx

Query String Parameters:

name (required) - words or partial words to be found within a corporations name
name_type - "starts_with", "contains", or "ends_with", specifies how the values for the name parameter should function
criteria - "all", "any", "exact" , in multi-word searches, this specifies how the words can or cannot appear in a corporations name
category - category of the corporation.
  "na" - All
  "BNK" - Bank
  "COP" - Cooperative
  "SOL" - Corporation Sole
  "CRU" - Credit Union
  "FMA" - Fish Marketing Act
  "RFN" - Foreign Registration
  "FBS" - Fraternal Building Society
  "FRA" - Fraternal Society
  "GRG" - Grange
  "INS" - Insurance
  "LLP" - Limited Liability Partnership
  "PLC" - Limited Liability Professional
  "LLC" - Limited Liability Regular
  "LTD" - Limited Partnership
  "MAS" - Massachusetts Trust
  "MIL" - Military
  "MMC" - Miscellaneous and Mutual
  "PRO" - Professional Service
  "PBC" - Public Benefit Corporation
  "PUB" - Public Utilities
  "REG" - Regular Corporation
  "RES" - Reservation of Name
  "SAL" - Savings and Loan
  "CAS" - Special Cooperative
active - status of the corporation. "A" for active, "T" for inactive, "NA" for either
agent_name - name or partial name of registered agent
city - city of registered agent's address
zip - zip of regisetered agent's address
date1 - begining date of date range for date of incorporation (format: MM-DD-YYYY)
date2 - ending date of date range for date of incorporation (format: MM-DD-YYYY)
start - number in the results set to begin the search. For example, if a query returns 1000 results, specifying a start of 80 would return results 80 through 99 in the list.
format - "json" or "xml"
callback - for json format, this value must be supplied for cross-site scripting access. Use "?" with jquery.

Examples:

JSON

http://www.sos.wa.gov/corps/search_results.aspx?name_type=starts_with&name=Seattle+Sounders&format=json

XML

http://www.sos.wa.gov/corps/search_results.aspx?name_type=starts_with&name=Seattle+Sounders&format=xml

Corporation Details A new version has been released to address the multiple titles for a governing person. Please append "&version=2" to the query string to retrieve a node for each title (XML) or an array of strings (JSON).

URL: http://www.sos.wa.gov/corps/search_detail.aspx

Query String Parameters:

ubi - UBI of the corporation/entity
format - "json" or "xml"
callback - for json format, this value must be supplied for cross-site scripting access. Use "?" with jquery.

Examples:

JSON

http://www.sos.wa.gov/corps/search_detail.aspx?ubi=601810719&format=json&version=2&callback=?

XML

http://www.sos.wa.gov/corps/search_detail.aspx?ubi=601810719&format=xml&version=2

Support and Feedback

We are happy to answer general questions regarding the API. Due to limited resources we cannot offer specific help with the programming or the integration of the output into your application or system. Please send questions and comments to matthew.edwards@sos.wa.gov .

The 2023 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, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated or updated as part of the the 2023 BAS or the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The 2020 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, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This layer contains block level 2020 Decennial Census redistricting data as reported by the U.S. Census Bureau for the state of Massachusetts. The attributes come from the 2020 Public Law 94-171 (P.L. 94-171) tables.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block level, since this data has been protected using differential privacy.**To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual blocks will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized. The pop-up on this layer uses Arcade to display aggregated values for the surrounding area rather than values for the block itself.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

The Brand Name Pharmaceutical Manufacturing industry in Massachusetts is expected to grow an annualized x.x% to $x.x billion over the five years to 2025, while the national industry will likely grow at x.x% during the same period. Industry establishments increased an annualized x.x% to xx locations. Industry employment has increased an annualized x.x% to x,xxx workers, while industry wages have increased an annualized x.x% to $x.x billion.