This data layer is an element of the Oregon GIS Framework. 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.

The Consumer Demographic database is comprised of over 80 sources and includes over 400 different data points for each individual in a household with complete PII including name, address, email, phone, and IP addresses.

Data SourcesAmerican Community Survey (ACS):Conducted by: U.S. Census BureauDescription: The ACS is an ongoing survey that provides detailed demographic and socio-economic data on the population and housing characteristics of the United States.Content: The survey collects information on various topics such as income, education, employment, health insurance coverage, and housing costs and conditions.Frequency: The ACS offers more frequent and up-to-date information compared to the decennial census, with annual estimates produced based on a rolling sample of households.Purpose: ACS data is essential for policymakers, researchers, and communities to make informed decisions and address the evolving needs of the population.CDC/ATSDR Social Vulnerability Index (SVI):Created by: ATSDR’s Geospatial Research, Analysis & Services Program (GRASP)Utilized by: CDCDescription: The SVI is designed to identify and map communities that are most likely to need support before, during, and after hazardous events.Content: SVI ranks U.S. Census tracts based on 15 social factors, including unemployment, minority status, and disability, and groups them into four related themes. Each tract receives rankings for each Census variable and for each theme, as well as an overall ranking, indicating its relative vulnerability.Purpose: SVI data provides insights into the social vulnerability of communities at both the tract and zip code levels, helping public health officials and emergency response planners allocate resources effectively.Utilization and IntegrationBy integrating data from both the ACS and the SVI, this dataset enables an in-depth analysis and understanding of various socio-economic and demographic indicators at the census tract level. This integrated data is valuable for research, policymaking, and community planning purposes, allowing for a comprehensive understanding of social and economic dynamics across different geographical areas in the United States.ApplicationsTargeted Interventions: Facilitates the development of targeted interventions to address the needs of vulnerable populations within specific zip codes.Resource Allocation: Assists emergency response planners in allocating resources more effectively based on community vulnerability at the zip code level.Research: Provides a rich dataset for academic and applied research in socio-economic and demographic studies at a granular zip code level.Community Planning: Supports the planning and development of community programs and initiatives aimed at improving living conditions and reducing vulnerabilities within specific zip code areas.Note: Due to limitations in the data environment, variable names may be truncated. Refer to the provided table for a clear understanding of the variables. CSV Variable NameShapefile Variable NameDescriptionStateNameStateNameName of the stateStateFipsStateFipsState-level FIPS codeState nameStateNameName of the stateCountyNameCountyNameName of the countyCensusFipsCensusFipsCounty-level FIPS codeState abbreviationStateFipsState abbreviationCountyFipsCountyFipsCounty-level FIPS codeCensusFipsCensusFipsCounty-level FIPS codeCounty nameCountyNameName of the countyAREA_SQMIAREA_SQMITract area in square milesE_TOTPOPE_TOTPOPPopulation estimates, 2013-2017 ACSEP_POVEP_POVPercentage of persons below poverty estimateEP_UNEMPEP_UNEMPUnemployment Rate estimateEP_HBURDEP_HBURDHousing cost burdened occupied housing units with annual income less than $75,000EP_UNINSUREP_UNINSURUninsured in the total civilian noninstitutionalized population estimate, 2013-2017 ACSEP_PCIEP_PCIPer capita income estimate, 2013-2017 ACSEP_DISABLEP_DISABLPercentage of civilian noninstitutionalized population with a disability estimate, 2013-2017 ACSEP_SNGPNTEP_SNGPNTPercentage of single parent households with children under 18 estimate, 2013-2017 ACSEP_MINRTYEP_MINRTYPercentage minority (all persons except white, non-Hispanic) estimate, 2013-2017 ACSEP_LIMENGEP_LIMENGPercentage of persons (age 5+) who speak English "less than well" estimate, 2013-2017 ACSEP_MUNITEP_MUNITPercentage of housing in structures with 10 or more units estimateEP_MOBILEEP_MOBILEPercentage of mobile homes estimateEP_CROWDEP_CROWDPercentage of occupied housing units with more people than rooms estimateEP_NOVEHEP_NOVEHPercentage of households with no vehicle available estimateEP_GROUPQEP_GROUPQPercentage of persons in group quarters estimate, 2014-2018 ACSBelow_5_yrBelow_5_yrUnder 5 years: Percentage of Total populationBelow_18_yrBelow_18_yrUnder 18 years: Percentage of Total population18-39_yr18_39_yr18-39 years: Percentage of Total population40-64_yr40_64_yr40-64 years: Percentage of Total populationAbove_65_yrAbove_65_yrAbove 65 years: Percentage of Total populationPop_malePop_malePercentage of total population malePop_femalePop_femalePercentage of total population femaleWhitewhitePercentage population of white aloneBlackblackPercentage population of black or African American aloneAmerican_indianamerican_iPercentage population of American Indian and Alaska native aloneAsianasianPercentage population of Asian aloneHawaiian_pacific_islanderhawaiian_pPercentage population of Native Hawaiian and Other Pacific Islander aloneSome_othersome_otherPercentage population of some other race aloneMedian_tot_householdsmedian_totMedian household income in the past 12 months (in 2019 inflation-adjusted dollars) by household size – total householdsLess_than_high_schoolLess_than_Percentage of Educational attainment for the population less than 9th grades and 9th to 12th grade, no diploma estimateHigh_schoolHigh_schooPercentage of Educational attainment for the population of High school graduate (includes equivalency)Some_collegeSome_collePercentage of Educational attainment for the population of Some college, no degreeAssociates_degreeAssociatesPercentage of Educational attainment for the population of associate degreeBachelor’s_degreeBachelor_sPercentage of Educational attainment for the population of Bachelor’s degreeMaster’s_degreeMaster_s_dPercentage of Educational attainment for the population of Graduate or professional degreecomp_devicescomp_devicPercentage of Household having one or more types of computing devicesInternetInternetPercentage of Household with an Internet subscriptionBroadbandBroadbandPercentage of Household having Broadband of any typeSatelite_internetSatelite_iPercentage of Household having Satellite Internet serviceNo_internetNo_internePercentage of Household having No Internet accessNo_computerNo_computePercentage of Household having No computerThis table provides a mapping between the CSV variable names and the shapefile variable names, along with a brief description of each variable.

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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2020 Census.

The Bureau of the Census has released Census 2000 Summary File 1 (SF1) 100-Percent data. The file includes the following population items: sex, age, race, Hispanic or Latino origin, household relationship, and household and family characteristics. Housing items include occupancy status and tenure (whether the unit is owner or renter occupied). SF1 does not include information on incomes, poverty status, overcrowded housing or age of housing. These topics will be covered in Summary File 3. Data are available for states, counties, county subdivisions, places, census tracts, block groups, and, where applicable, American Indian and Alaskan Native Areas and Hawaiian Home Lands. The SF1 data are available on the Bureau's web site and may be retrieved from American FactFinder as tables, lists, or maps. Users may also download a set of compressed ASCII files for each state via the Bureau's FTP server. There are over 8000 data items available for each geographic area. The full listing of these data items is available here as a downloadable compressed data base file named TABLES.ZIP. The uncompressed is in FoxPro data base file (dbf) format and may be imported to ACCESS, EXCEL, and other software formats. While all of this information is useful, the Office of Community Planning and Development has downloaded selected information for all states and areas and is making this information available on the CPD web pages. The tables and data items selected are those items used in the CDBG and HOME allocation formulas plus topics most pertinent to the Comprehensive Housing Affordability Strategy (CHAS), the Consolidated Plan, and similar overall economic and community development plans. The information is contained in five compressed (zipped) dbf tables for each state. When uncompressed the tables are ready for use with FoxPro and they can be imported into ACCESS, EXCEL, and other spreadsheet, GIS and database software. The data are at the block group summary level. The first two characters of the file name are the state abbreviation. The next two letters are BG for block group. Each record is labeled with the code and name of the city and county in which it is located so that the data can be summarized to higher-level geography. The last part of the file name describes the contents . The GEO file contains standard Census Bureau geographic identifiers for each block group, such as the metropolitan area code and congressional district code. The only data included in this table is total population and total housing units. POP1 and POP2 contain selected population variables and selected housing items are in the HU file. The MA05 table data is only for use by State CDBG grantees for the reporting of the racial composition of beneficiaries of Area Benefit activities. The complete package for a state consists of the dictionary file named TABLES, and the five data files for the state. The logical record number (LOGRECNO) links the records across tables.

Welcome to Apiscrapy, your ultimate destination for comprehensive location-based intelligence. As an AI-driven web scraping and automation platform, Apiscrapy excels in converting raw web data into polished, ready-to-use data APIs. With a unique capability to collect Google Address Data, Google Address API, Google Location API, Google Map, and Google Location Data with 100% accuracy, we redefine possibilities in location intelligence.

Key Features:

Unparalleled Data Variety: Apiscrapy offers a diverse range of address-related datasets, including Google Address Data and Google Location Data. Whether you seek B2B address data or detailed insights for various industries, we cover it all.

Integration with Google Address API: Seamlessly integrate our datasets with the powerful Google Address API. This collaboration ensures not just accessibility but a robust combination that amplifies the precision of your location-based insights.

Business Location Precision: Experience a new level of precision in business decision-making with our address data. Apiscrapy delivers accurate and up-to-date business locations, enhancing your strategic planning and expansion efforts.

Tailored B2B Marketing: Customize your B2B marketing strategies with precision using our detailed B2B address data. Target specific geographic areas, refine your approach, and maximize the impact of your marketing efforts.

Use Cases:

Location-Based Services: Companies use Google Address Data to provide location-based services such as navigation, local search, and location-aware advertisements.

Logistics and Transportation: Logistics companies utilize Google Address Data for route optimization, fleet management, and delivery tracking.

E-commerce: Online retailers integrate address autocomplete features powered by Google Address Data to simplify the checkout process and ensure accurate delivery addresses.

Real Estate: Real estate agents and property websites leverage Google Address Data to provide accurate property listings, neighborhood information, and proximity to amenities.

Urban Planning and Development: City planners and developers utilize Google Address Data to analyze population density, traffic patterns, and infrastructure needs for urban planning and development projects.

Market Analysis: Businesses use Google Address Data for market analysis, including identifying target demographics, analyzing competitor locations, and selecting optimal locations for new stores or offices.

Geographic Information Systems (GIS): GIS professionals use Google Address Data as a foundational layer for mapping and spatial analysis in fields such as environmental science, public health, and natural resource management.

Government Services: Government agencies utilize Google Address Data for census enumeration, voter registration, tax assessment, and planning public infrastructure projects.

Tourism and Hospitality: Travel agencies, hotels, and tourism websites incorporate Google Address Data to provide location-based recommendations, itinerary planning, and booking services for travelers.

Discover the difference with Apiscrapy – where accuracy meets diversity in address-related datasets, including Google Address Data, Google Address API, Google Location API, and more. Redefine your approach to location intelligence and make data-driven decisions with confidence. Revolutionize your business strategies today!

This layer contains a geographic identifier (GEO_ID_GRP) for each block group that is the key field for the data from censuses and surveys such as Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program. Data from many of the Census Bureau’s surveys and censuses, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). All original TIGER/Line shapefiles and geodatabases with demographic data are available atThe TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) Database (MTDB). The shapefiles include information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The shapefiles include polygon boundaries of geographic areas and features, linear features including roads and hydrography, and point features. These shapefiles do not contain any sensitive data or confidential data protected by Title 13 of the U.S.C.Standard block groups are clusters of blocks within the same census tract that have the same first digit of their 4-character census block number (e.g., Blocks 3001, 3002, 3003 to 3999 in census tract 1210.02 belong to block group 3). Current block groups do not always maintain these same block number to block group relationships due to boundary and feature changes that occur throughout the decade. For example, block 3001 might move due to a change in the census tract boundary. Block groups delineated for the 2020 Census generally contain 600 to 3,000 people and a block group usually covers a contiguous area. Each census tract contains one or more block groups and block groups have unique numbers within census tract. Within the standard census geographic hierarchy, block groups never cross county or census tract boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and AIANNH areas.Block groups have a valid range of zero (0) through nine (9). Block groups beginning with a zero generally are in coastal and Great Lakes water and territorial seas. Rather than extending a census tract boundary into the Great Lakes or out to the 3-mile territorial sea limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. Full documentation: https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2020/TGRSHP2020_TechDoc.pdf

This polygon shapefile contains 5-year American Community Survey (ACS) estimates of demographic variables at the tract level. 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 Bureaus 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.The American Community Survey (ACS) 5 Year 2008-2012 demographic information is a subset of information available for download. Downloaded tables include: B01001 - Sex By Age, B03002 - Hispanic Or Latino Origin By Race, B11001 - Household Type (Including Living Alone), B11005 - Households By Presence Of People Under 18 Years By Household Type, B11006 - Households By Presence Of People 60 Years And Over By Household Type, B16005 - Nativity By Language Spoken At Home By Ability To Speak English For The Population 5 Years And Over, B25010 - Average Household Size Of Occupied Housing Units By Tenure and B15001 - Sex by Educational Attainment for the Population 18 Years and Over.

This layer contains a unique geographic identifier (GEO_ID_TRT) for each tract group that is the key field for the data from censuses and surveys such as Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program. Data from many of the Census Bureau’s surveys and censuses, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). All original TIGER/Line shapefiles and geodatabases with demographic data are available atThe TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) Database (MTDB). The shapefiles include information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The shapefiles include polygon boundaries of geographic areas and features, linear features including roads and hydrography, and point features. These shapefiles do not contain any sensitive data or confidential data protected by Title 13 of the U.S.C.Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and are reviewed and updated by local participants prior to each decennial census. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. Census tracts generally have a population size of 1,200 to 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Ideally, census tract boundaries remain stable over time to facilitate statistical comparisons from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, significant changes in population may result in splitting or combining census tracts. Census tract boundaries generally follow visible and identifiable features. Census tract boundaries may follow legal boundaries. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. Census Tract Codes and Numbers—Census tract numbers have up to a 4-character basic number and may have an optional 2-character suffix, for example, 1457.02. The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Full documentation: https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2020/TGRSHP2020_TechDoc.pdf

USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS). The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). Census Designated Places (CDPs) are the statistical counterparts of incorporated places, and 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 usually are defined in cooperation with local or tribal officials and generally updated prior to each decennial census. These boundaries, which usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity boundary, have no legal status, nor do these places have officials elected to serve traditional municipal functions. CDP boundaries may change from one decennial census to the next with changes in the settlement pattern; a CDP with the same name as in an earlier census does not necessarily have the same boundary. CDPs must be contained within a single state and may not extend into an incorporated place. There are no population size requirements for CDPs, but they must include some residential population or housing. Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/PLACE/ on June 22, 2023

The 2020 TIGER/Line Shapefiles contain current geographic extent and boundaries of both legal and statistical entities (which have no governmental standing) for the United States, the District of Columbia, Puerto Rico, and the Island areas. This vintage includes boundaries of governmental units that match the data from the surveys that use 2020 geography (e.g., 2020 Population Estimates and the 2020 American Community Survey). In addition to geographic boundaries, the 2020 TIGER/Line Shapefiles also include geographic feature shapefiles and relationship files. Feature shapefiles represent the point, line and polygon features in the MTDB (e.g., roads and rivers). Relationship files contain additional attribute information users can join to the shapefiles. Both the feature shapefiles and relationship files reflect updates made in the database through September 2020. To see how the geographic entities, relate to one another, please see our geographic hierarchy diagrams here.Census Urbanized Areashttps://www2.census.gov/geo/tiger/TIGER2020/UACCensus Urban/Rural Census Block Shapefileshttps://www.census.gov/cgi-bin/geo/shapefiles/index.php2020 TIGER/Line and Redistricting shapefiles:https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.2020.htmlTechnical documentation:https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2020/TGRSHP2020_TechDoc.pdfTIGERweb REST Services:https://tigerweb.geo.census.gov/tigerwebmain/TIGERweb_restmapservice.htmlTIGERweb WMS Services:https://tigerweb.geo.census.gov/tigerwebmain/TIGERweb_wms.htmlThe legal entities included in these shapefiles are:American Indian Off-Reservation Trust LandsAmerican Indian Reservations – FederalAmerican Indian Reservations – StateAmerican Indian Tribal Subdivisions (within legal American Indian areas)Alaska Native Regional CorporationsCongressional Districts – 116th CongressConsolidated CitiesCounties and Equivalent Entities (except census areas in Alaska)Estates (US Virgin Islands only)Hawaiian Home LandsIncorporated PlacesMinor Civil DivisionsSchool Districts – ElementarySchool Districts – SecondarySchool Districts – UnifiedStates and Equivalent EntitiesState Legislative Districts – UpperState Legislative Districts – LowerSubminor Civil Divisions (Subbarrios in Puerto Rico)The statistical entities included in these shapefiles are:Alaska Native Village Statistical AreasAmerican Indian/Alaska Native Statistical AreasAmerican Indian Tribal Subdivisions (within Oklahoma Tribal Statistical Areas)Block Groups3-5Census AreasCensus BlocksCensus County Divisions (Census Subareas in Alaska)Unorganized Territories (statistical county subdivisions)Census Designated Places (CDPs)Census TractsCombined New England City and Town AreasCombined Statistical AreasMetropolitan and Micropolitan Statistical Areas and related statistical areasMetropolitan DivisionsNew England City and Town AreasNew England City and Town Area DivisionsOklahoma Tribal Statistical AreasPublic Use Microdata Areas (PUMAs)State Designated Tribal Statistical AreasTribal Designated Statistical AreasUrban AreasZIP Code Tabulation Areas (ZCTAs)Shapefiles - Features:Address Range-FeatureAll Lines (called Edges)All RoadsArea HydrographyArea LandmarkCoastlineLinear HydrographyMilitary InstallationPoint LandmarkPrimary RoadsPrimary and Secondary RoadsTopological Faces (polygons with all geocodes)Relationship Files:Address Range-Feature NameAddress RangesFeature NamesTopological Faces – Area LandmarkTopological Faces – Area HydrographyTopological Faces – Military Installations

This layer is intended for researchers, students, policy makers, and the general public for reference and mapping purposes, and may be used for basic applications such as viewing, querying, and map output production. This layer will provide a basemap for layers related to socio-political analysis, statistical enumeration and analysis, or to support graphical overlays and analysis with other spatial data. More advanced user applications may focus on demographics, urban and rural land use planning, socio-economic analysis and related areas (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output.)

Abstract

Dataset quality **: Medium/high quality dataset, not quality checked or modified by the EIDC team

Census data plays a pivotal role in academic data research, particularly when exploring relationships between different demographic characteristics. The significance of this particular dataset lies in its ability to facilitate the merging of various datasets with basic census information, thereby streamlining the research process and eliminating the need for separate API calls.

The American Community Survey is an ongoing survey conducted by the U.S. Census Bureau, which provides detailed social, economic, and demographic data about the United States population. The ACS collects data continuously throughout the decade, gathering information from a sample of households across the country, covering a wide range of topics

Methodology

The Census Data Application Programming Interface (API) is an API that gives the public access to raw statistical data from various Census Bureau data programs.

We used this API to collect various demographic and socioeconomic variables from both the ACS and the Deccenial survey on different geographical levels:

ZCTAs:

ZIP Code Tabulation Areas (ZCTAs) are generalized areal representations of United States Postal Service (USPS) ZIP Code service areas. The USPS ZIP Codes identify the individual post office or metropolitan area delivery station associated with mailing addresses. USPS ZIP Codes are not areal features but a collection of mail delivery routes.

Census Tract:

Census Tracts are small, relatively permanent statistical subdivisions of a county or statistically equivalent entity that can be updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP).

Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. A census tract usually covers a contiguous area; however, the spatial size of census tracts varies widely depending on the density of settlement. Census tract boundaries are delineated with the intention of being maintained over a long time so that statistical comparisons can be made from census to census.

Block Groups:

Block groups (BGs) are the next level above census blocks in the geographic hierarchy (see Figure 2-1 in Chapter 2). A BG is a combination of census blocks that is a subdivision of a census tract or block numbering area (BNA). (A county or its statistically equivalent entity contains either census tracts or BNAs; it can not contain both.) A BG consists of all census blocks whose numbers begin with the same digit in a given census tract or BNA; for example, BG 3 includes all census blocks numbered in the 300s. The BG is the smallest geographic entity for which the decennial census tabulates and publishes sample data.

Census Blocks:

Census blocks, the smallest geographic area for which the Bureau of the Census collects and tabulates decennial census data, are formed by streets, roads, railroads, streams and other bodies of water, other visible physical and cultural features, and the legal boundaries shown on Census Bureau maps.

The Decennial Census provides population estimates and demographic information on residents of the United States.

The Census Summary Files contain detailed tables on responses to the decennial census. Data tables in Summary File 1 provide information on population and housing characteristics, including cross-tabulations of age, sex, households, families, relationship to householder, housing units, detailed race and Hispanic or Latino origin groups, and group quarters for the total population. Summary File 2 contains data tables on population and housing characteristics as reported by housing unit.

Researchers at NYU Langone Health can find guidance for the use and analysis of Census Bureau data on the Population Health Data Hub (listed under "Other Resources"), which is accessible only through the intranet portal with a valid Kerberos ID (KID).

description: 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. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may 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. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.; abstract: 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. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may 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. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

Premium B2C Consumer Database - 269+ Million US Records

Supercharge your B2C marketing campaigns with comprehensive consumer database, featuring over 269 million verified US consumer records. Our 20+ year data expertise delivers higher quality and more extensive coverage than competitors.

Core Database Statistics

Consumer Records: Over 269 million

Email Addresses: Over 160 million (verified and deliverable)

Phone Numbers: Over 76 million (mobile and landline)

Mailing Addresses: Over 116,000,000 (NCOA processed)

Geographic Coverage: Complete US (all 50 states)

Compliance Status: CCPA compliant with consent management

Targeting Categories Available

Demographics: Age ranges, education levels, occupation types, household composition, marital status, presence of children, income brackets, and gender (where legally permitted)

Geographic: Nationwide, state-level, MSA (Metropolitan Service Area), zip code radius, city, county, and SCF range targeting options

Property & Dwelling: Home ownership status, estimated home value, years in residence, property type (single-family, condo, apartment), and dwelling characteristics

Financial Indicators: Income levels, investment activity, mortgage information, credit indicators, and wealth markers for premium audience targeting

Lifestyle & Interests: Purchase history, donation patterns, political preferences, health interests, recreational activities, and hobby-based targeting

Behavioral Data: Shopping preferences, brand affinities, online activity patterns, and purchase timing behaviors

Multi-Channel Campaign Applications

Deploy across all major marketing channels:

Email marketing and automation

Social media advertising

Search and display advertising (Google, YouTube)

Direct mail and print campaigns

Telemarketing and SMS campaigns

Programmatic advertising platforms

Data Quality & Sources

Our consumer data aggregates from multiple verified sources:

Public records and government databases

Opt-in subscription services and registrations

Purchase transaction data from retail partners

Survey participation and research studies

Online behavioral data (privacy compliant)

Technical Delivery Options

File Formats: CSV, Excel, JSON, XML formats available

Delivery Methods: Secure FTP, API integration, direct download

Processing: Real-time NCOA, email validation, phone verification

Custom Selections: 1,000+ selectable demographic and behavioral attributes

Minimum Orders: Flexible based on targeting complexity

Unique Value Propositions

Dual Spouse Targeting: Reach both household decision-makers for maximum impact

Cross-Platform Integration: Seamless deployment to major ad platforms

Real-Time Updates: Monthly data refreshes ensure maximum accuracy

Advanced Segmentation: Combine multiple targeting criteria for precision campaigns

Compliance Management: Built-in opt-out and suppression list management

Ideal Customer Profiles

E-commerce retailers seeking customer acquisition

Financial services companies targeting specific demographics

Healthcare organizations with compliant marketing needs

Automotive dealers and service providers

Home improvement and real estate professionals

Insurance companies and agents

Subscription services and SaaS providers

Performance Optimization Features

Lookalike Modeling: Create audiences similar to your best customers

Predictive Scoring: Identify high-value prospects using AI algorithms

Campaign Attribution: Track performance across multiple touchpoints

A/B Testing Support: Split audiences for campaign optimization

Suppression Management: Automatic opt-out and DNC compliance

Pricing & Volume Options

Flexible pricing structures accommodate businesses of all sizes:

Pay-per-record for small campaigns

Volume discounts for large deployments

Subscription models for ongoing campaigns

Custom enterprise pricing for high-volume users

Data Compliance & Privacy

VIA.tools maintains industry-leading compliance standards:

CCPA (California Consumer Privacy Act) compliant

CAN-SPAM Act adherence for email marketing

TCPA compliance for phone and SMS campaigns

Regular privacy audits and data governance reviews

Transparent opt-out and data deletion processes

Getting Started

Our data specialists work with you to:

1. Define your target audience criteria

2. Recommend optimal data selections

3. Provide sample data for testing

4. Configure delivery methods and formats

5. Implement ongoing campaign optimization

Why We Lead the Industry

With over two decades of data industry experience, we combine extensive database coverage with advanced targeting capabilities. Our commitment to data quality, compliance, and customer success has made us the preferred choice for businesses seeking superior B2C marketing performance.

Contact our team to discuss your specific targeting requirements and receive custom pricing for your marketing objectives.

description: 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. This census data layer has been imported into the Miami-Dade County ArcSDE infrastructure and re-projected to: Projected Coordinate System: NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet Projection: Transverse_Mercator False_Easting: 656166.66666667 False_Northing: 0.00000000 Central_Meridian: -81.00000000 Scale_Factor: 0.99994118 Latitude_Of_Origin: 24.33333333 Linear Unit: Foot_US The boundaries have been aligned to Miami-Dade County base data where they have been found to NOT be within +/- 10 ft Population figures have been appended to the end of the feature classes attribute table: Pop2010, HU2010, HISPAN, WHITENH, BLACKNH, AMERINDIANNH, ASIANNH, HAWIANNH, OTHERNH, and MULTIRACE. Definitions can be found in the census documentation.; abstract: 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. This census data layer has been imported into the Miami-Dade County ArcSDE infrastructure and re-projected to: Projected Coordinate System: NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet Projection: Transverse_Mercator False_Easting: 656166.66666667 False_Northing: 0.00000000 Central_Meridian: -81.00000000 Scale_Factor: 0.99994118 Latitude_Of_Origin: 24.33333333 Linear Unit: Foot_US The boundaries have been aligned to Miami-Dade County base data where they have been found to NOT be within +/- 10 ft Population figures have been appended to the end of the feature classes attribute table: Pop2010, HU2010, HISPAN, WHITENH, BLACKNH, AMERINDIANNH, ASIANNH, HAWIANNH, OTHERNH, and MULTIRACE. Definitions can be found in the census documentation.

Our consumer data is gathered and aggregated via surveys, digital services, and public data sources. We use powerful profiling algorithms to collect and ingest only fresh and reliable data points.

Our comprehensive data enrichment solution includes a variety of data sets that can help you address gaps in your customer data, gain a deeper understanding of your customers, and power superior client experiences.

1. Geography - City, State, ZIP, County, CBSA, Census Tract, etc.
2. Demographics - Gender, Age Group, Marital Status, Language etc.
3. Financial - Income Range, Credit Rating Range, Credit Type, Net worth Range, etc
4. Persona - Consumer type, Communication preferences, Family type, etc
5. Interests - Content, Brands, Shopping, Hobbies, Lifestyle etc.
6. Household - Number of Children, Number of Adults, IP Address, etc.
7. Behaviours - Brand Affinity, App Usage, Web Browsing etc.
8. Firmographics - Industry, Company, Occupation, Revenue, etc
9. Retail Purchase - Store, Category, Brand, SKU, Quantity, Price etc.
10. Auto - Car Make, Model, Type, Year, etc.
11. Housing - Home type, Home value, Renter/Owner, Year Built etc.

Consumer Graph Schema & Reach: Our data reach represents the total number of counts available within various categories and comprises attributes such as country location, MAU, DAU & Monthly Location Pings:

Data Export Methodology: Since we collect data dynamically, we provide the most updated data and insights via a best-suited method on a suitable interval (daily/weekly/monthly).

Consumer Graph Use Cases:

360-Degree Customer View:Get a comprehensive image of customers by the means of internal and external data aggregation.

Data Enrichment:Leverage Online to offline consumer profiles to build holistic audience segments to improve campaign targeting using user data enrichment

Fraud Detection: Use multiple digital (web and mobile) identities to verify real users and detect anomalies or fraudulent activity.

Advertising & Marketing:Understand audience demographics, interests, lifestyle, hobbies, and behaviors to build targeted marketing campaigns.

Using Factori Consumer Data graph you can solve use cases like:

Acquisition Marketing Expand your reach to new users and customers using lookalike modeling with your first party audiences to extend to other potential consumers with similar traits and attributes.

Lookalike Modeling

Build lookalike audience segments using your first party audiences as a seed to extend your reach for running marketing campaigns to acquire new users or customers

And also, CRM Data Enrichment, Consumer Data Enrichment B2B Data Enrichment B2C Data Enrichment Customer Acquisition Audience Segmentation 360-Degree Customer View Consumer Profiling Consumer Behaviour Data

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces. This census data layer has been imported into the Miami-Dade County ArcSDE infrastructure and re-projected to: Projected Coordinate System: NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet Projection: Transverse_Mercator False_Easting: 656166.66666667 False_Northing: 0.00000000 Central_Meridian: -81.00000000 Scale_Factor: 0.99994118 Latitude_Of_Origin: 24.33333333 Linear Unit: Foot_US The boundaries have been aligned to Miami-Dade County base data where they have been found to NOT be within +/- 10 ft. Population figures have been appended to the end of the feature classes attribute table: Pop2010, HU2010, HISPAN, WHITENH, BLACKNH, AMERINDIANNH, ASIANNH, HAWIANNH, OTHERNH, and MULTIRACE. Definitions can be found in the census documentation.

2010 US Census block boundaries attributed with a subset of the PL94-171 demographic data released March 2011. Please contact the Hennepin GIS Office if you require additional PL94-171 fields. Downloaded the 2010 US Census block boundary shapefile from the US Census Bureau at the following address: http://www.census.gov/cgi-bin/geo/shapefiles2010/main Downloaded the PL94-171 demographic data from the following address: http://www.census.gov/rdo/data/2010_census_redistricting_data_pl_94-171_summary_files.html Post processed the demographic data per instructions. Stored in Access database. Set up SQL Query to create a subset of the data based on feedback from HSPHD and the GIS Office. Database documentation on file at the GIS Office. Imported the shapefile and demographic data into a File geodatabase. Joined and saved the data sets. Performed error checking by comparing against State and Maptitude versions. 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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/2010%20Census%20Blocks.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© Hennepin County GIS Office This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..