analyze the survey of income and program participation (sipp) with r if the census bureau's budget was gutted and only one complex sample survey survived, pray it's the survey of income and program participation (sipp). it's giant. it's rich with variables. it's monthly. it follows households over three, four, now five year panels. the congressional budget office uses it for their health insurance simulation . analysts read that sipp has person-month files, get scurred, and retreat to inferior options. the american community survey may be the mount everest of survey data, but sipp is most certainly the amazon. questions swing wild and free through the jungle canopy i mean core data dictionary. legend has it that there are still species of topical module variables that scientists like you have yet to analyze. ponce de león would've loved it here. ponce. what a name. what a guy. the sipp 2008 panel data started from a sample of 105,663 individuals in 42,030 households. once the sample gets drawn, the census bureau surveys one-fourth of the respondents every four months, over f our or five years (panel durations vary). you absolutely must read and understand pdf pages 3, 4, and 5 of this document before starting any analysis (start at the header 'waves and rotation groups'). if you don't comprehend what's going on, try their survey design tutorial. since sipp collects information from respondents regarding every month over the duration of the panel, you'll need to be hyper-aware of whether you want your results to be point-in-time, annualized, or specific to some other period. the analysis scripts below provide examples of each. at every four-month interview point, every respondent answers every core question for the previous four months. after that, wave-specific addenda (called topical modules) get asked, but generally only regarding a single prior month. to repeat: core wave files contain four records per person, topical modules contain one. if you stacked every core wave, you would have one record per person per month for the duration o f the panel. mmmassive. ~100,000 respondents x 12 months x ~4 years. have an analysis plan before you start writing code so you extract exactly what you need, nothing more. better yet, modify something of mine. cool? this new github repository contains eight, you read me, eight scripts: 1996 panel - download and create database.R 2001 panel - download and create database.R 2004 panel - download and create database.R 2008 panel - download and create database.R since some variables are character strings in one file and integers in anoth er, initiate an r function to harmonize variable class inconsistencies in the sas importation scripts properly handle the parentheses seen in a few of the sas importation scripts, because the SAScii package currently does not create an rsqlite database, initiate a variant of the read.SAScii function that imports ascii data directly into a sql database (.db) download each microdata file - weights, topical modules, everything - then read 'em into sql 2008 panel - full year analysis examples.R< br /> define which waves and specific variables to pull into ram, based on the year chosen loop through each of twelve months, constructing a single-year temporary table inside the database read that twelve-month file into working memory, then save it for faster loading later if you like read the main and replicate weights columns into working memory too, merge everything construct a few annualized and demographic columns using all twelve months' worth of information construct a replicate-weighted complex sample design with a fay's adjustment factor of one-half, again save it for faster loading later, only if you're so inclined reproduce census-publish ed statistics, not precisely (due to topcoding described here on pdf page 19) 2008 panel - point-in-time analysis examples.R define which wave(s) and specific variables to pull into ram, based on the calendar month chosen read that interview point (srefmon)- or calendar month (rhcalmn)-based file into working memory read the topical module and replicate weights files into working memory too, merge it like you mean it construct a few new, exciting variables using both core and topical module questions construct a replicate-weighted complex sample design with a fay's adjustment factor of one-half reproduce census-published statistics, not exactly cuz the authors of this brief used the generalized variance formula (gvf) to calculate the margin of error - see pdf page 4 for more detail - the friendly statisticians at census recommend using the replicate weights whenever possible. oh hayy, now it is. 2008 panel - median value of household assets.R define which wave(s) and spe cific variables to pull into ram, based on the topical module chosen read the topical module and replicate weights files into working memory too, merge once again construct a replicate-weighted complex sample design with a...

Although the American Community Survey (ACS) produces population, demographic and housing unit estimates, it is the Census Bureau's Population Estimates Program that produces and disseminates the official estimates of the population for the nation, states, counties, cities, and towns and estimates of housing units for states and counties..Supporting documentation on code lists, subject definitions, data accuracy, and statistical testing can be found on the American Community Survey website in the Technical Documentation section.Sample size and data quality measures (including coverage rates, allocation rates, and response rates) can be found on the American Community Survey website in the Methodology section..Source: U.S. Census Bureau, 2017-2021 American Community Survey 5-Year Estimates.Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted roughly as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see ACS Technical Documentation). The effect of nonsampling error is not represented in these tables..Foreign born excludes people born outside the United States to a parent who is a U.S. citizen..Tables for Workplace Geography are only available for States; Counties; Places; County Subdivisions in selected states (CT, ME, MA, MI, MN, NH, NJ, NY, PA, RI, VT, WI); Combined Statistical Areas; Metropolitan and Micropolitan Statistical Areas, and their associated Metropolitan Divisions and Principal Cities; Combined New England City and Town Areas; New England City and Town Areas, and their associated Divisions and Principal Cities. Tables B08601, B08602, B08603, and B08604 are also available for Place parts and County Subdivision parts for the 5-year ACS datasets..Workers include members of the Armed Forces and civilians who were at work last week..Industry titles and their 4-digit codes are based on the North American Industry Classification System (NAICS). The Census industry codes for 2018 and later years are based on the 2017 revision of the NAICS. To allow for the creation of multiyear tables, industry data in the multiyear files (prior to data year 2018) were recoded to the 2017 Census industry codes. We recommend using caution when comparing data coded using 2017 Census industry codes with data coded using Census industry codes prior to data year 2018. For more information on the Census industry code changes, please visit our website at https://www.census.gov/topics/employment/industry-occupation/guidance/code-lists.html..When information is missing or inconsistent, the Census Bureau logically assigns an acceptable value using the response to a related question or questions. If a logical assignment is not possible, data are filled using a statistical process called allocation, which uses a similar individual or household to provide a donor value. The "Allocated" section is the number of respondents who received an allocated value for a particular subject..Several means of transportation to work categories were updated in 2019. For more information, see: Change to Means of Transportation..Occupation titles and their 4-digit codes are based on the Standard Occupational Classification (SOC). The Census occupation codes for 2018 and later years are based on the 2018 revision of the SOC. To allow for the creation of the multiyear tables, occupation data in the multiyear files (prior to data year 2018) were recoded to the 2018 Census occupation codes. We recommend using caution when comparing data coded using 2018 Census occupation codes with data coded using Census occupation codes prior to data year 2018. For more information on the Census occupation code changes, please visit our website at https://www.census.gov/topics/employment /industry-occupation/guidance/code-lists.html..In 2019, methodological changes were made to the class of worker question. These changes involved modifications to the question wording, the category wording, and the visual format of the categories on the questionnaire. The format for the class of worker categories are now listed under the headings "Private Sector Employee," "Government Employee," and "Self-Employed or Other." Additionally, the category of Active Duty was added as one of the response categories under the "Government Employee" section for the mail questionnaire. For more detailed information about the 2019 changes, see the 2016 American Community Survey Content Test Report for Class of Worker located at http://www.census.gov/library/working-pap...

Census Tracts from 2020. The TIGER/Line shapefiles 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 2020 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 2010 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.

Although the American Community Survey (ACS) produces population, demographic and housing unit estimates, the decennial census is the official source of population totals for April 1st of each decennial year. In between censuses, the Census Bureau's Population Estimates Program produces and disseminates the official estimates of the population for the nation, states, counties, cities, and towns and estimates of housing units for states and counties..Information about the American Community Survey (ACS) can be found on the ACS website. Supporting documentation including code lists, subject definitions, data accuracy, and statistical testing, and a full list of ACS tables and table shells (without estimates) can be found on the Technical Documentation section of the ACS website.Sample size and data quality measures (including coverage rates, allocation rates, and response rates) can be found on the American Community Survey website in the Methodology section..Source: U.S. Census Bureau, 2022 American Community Survey 1-Year Estimates.Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted roughly as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see ACS Technical Documentation). The effect of nonsampling error is not represented in these tables..Foreign born excludes people born outside the United States to a parent who is a U.S. citizen..Tables for Workplace Geography are only available for States; Counties; Places; County Subdivisions in selected states (CT, ME, MA, MI, MN, NH, NJ, NY, PA, RI, VT, WI); Combined Statistical Areas; Metropolitan and Micropolitan Statistical Areas, and their associated Metropolitan Divisions and Principal Cities; Combined New England City and Town Areas; New England City and Town Areas, and their associated Divisions and Principal Cities. Tables B08601, B08602, B08603, and B08604 are also available for Place parts and County Subdivision parts for the 5-year ACS datasets..Workers include members of the Armed Forces and civilians who were at work last week..Industry titles and their 4-digit codes are based on the 2017 North American Industry Classification System. The Industry categories adhere to the guidelines issued in Clarification Memorandum No. 2, "NAICS Alternate Aggregation Structure for Use By U.S. Statistical Agencies," issued by the Office of Management and Budget..Occupation titles and their 4-digit codes are based on the 2018 Standard Occupational Classification..When information is missing or inconsistent, the Census Bureau logically assigns an acceptable value using the response to a related question or questions. If a logical assignment is not possible, data are filled using a statistical process called allocation, which uses a similar individual or household to provide a donor value. The "Allocated" section is the number of respondents who received an allocated value for a particular subject..In 2019, methodological changes were made to the class of worker question. These changes involved modifications to the question wording, the category wording, and the visual format of the categories on the questionnaire. The format for the class of worker categories are now listed under the headings "Private Sector Employee," "Government Employee," and "Self-Employed or Other." Additionally, the category of Active Duty was added as one of the response categories under the "Government Employee" section for the mail questionnaire. For more detailed information about the 2019 changes, see the 2016 American Community Survey Content Test Report for Class of Worker located at http://www.census.gov/library/working-papers/2017/acs/2017_Martinez_01.html..The 2022 American Community Survey (ACS) data generally reflect the March 2020 Office of Management and Budget (OMB) delineations of metropolitan and micropolitan statistical areas. In certain instances the names, codes, and boundaries of the principal cities shown in ACS tables may differ from the OMB delineations due to differences in the effective dates of the geographic entities..Estimates of urban and rural populations, housing units, and characteristics reflect boundaries of urban areas defined based on 2020 Census data. As a result, data for urban and rural areas from the ACS do not necessarily reflect the results of ongoing urbanization..Explanation of Symbols:- The estimate could not be computed because there were an insufficient number of sample observations. For a ratio of medians estimate, one o...

About this dataset

Context

The dataset tabulates the United States population distribution across 18 age groups. It lists the population in each age group along with the percentage population relative of the total population for United States. The dataset can be utilized to understand the population distribution of United States by age. For example, using this dataset, we can identify the largest age group in United States.

Key observations

The largest age group in United States was for the group of age 25-29 years with a population of 22,854,328 (6.93%), according to the 2021 American Community Survey. At the same time, the smallest age group in United States was the 80-84 years with a population of 5,932,196 (1.80%). Source: U.S. Census Bureau American Community Survey (ACS) 2017-2021 5-Year Estimates.

Content

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

Age groups:

• Under 5 years
• 5 to 9 years
• 10 to 14 years
• 15 to 19 years
• 20 to 24 years
• 25 to 29 years
• 30 to 34 years
• 35 to 39 years
• 40 to 44 years
• 45 to 49 years
• 50 to 54 years
• 55 to 59 years
• 60 to 64 years
• 65 to 69 years
• 70 to 74 years
• 75 to 79 years
• 80 to 84 years
• 85 years and over

Variables / Data Columns

• Age Group: This column displays the age group in consideration
• Population: The population for the specific age group in the United States is shown in this column.
• % of Total Population: This column displays the population of each age group as a proportion of United States total population. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

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

Custom data

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

Inspiration

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

Recommended for further research

This dataset is a part of the main dataset for United States Population by Age. You can refer the same here

Abstract (en): The Public Use Microdata Sample (PUMS) 1-Percent Sample contains household and person records for a sample of housing units that received the "long form" of the 1990 Census questionnaire. Data items include the full range of population and housing information collected in the 1990 Census, including 500 occupation categories, age by single years up to 90, and wages in dollars up to $140,000. Each person identified in the sample has an associated household record, containing information on household characteristics such as type of household and family income. All persons and housing units in the United States. A stratified sample, consisting of a subsample of the household units that received the 1990 Census "long-form" questionnaire (approximately 15.9 percent of all housing units). 2006-01-12 All files were removed from dataset 85 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 83 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 82 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 81 and flagged as study-level files, so that they will accompany all downloads.2006-01-12 All files were removed from dataset 80 and flagged as study-level files, so that they will accompany all downloads.1998-08-28 The following data files were replaced by the Census Bureau: the state files (Parts 1-56), Puerto Rico (Part 72), Geographic Equivalency File (Part 84), and Public Use Microdata Areas (PUMAS) Crossing State Lines (Part 99). These files now incorporate revised group quarters data. Parts 201-256, which were separate revised group quarters files for each state, have been removed from the collection. The data fields affected by the group quarters data revisions were POWSTATE, POWPUMA, MIGSTATE and MIGPUMA. As a result of the revisions, the Maine file (Part 23) gained 763 records and Part 99 lost 763 records. In addition, the following files have been added to the collection: Ancestry Code List, Place of Birth Code List, Industry Code List, Language Code List, Occupation Code List, and Race Code List (Parts 86-91). Also, the codebook is now available as a PDF file. (1) Although all records are 231 characters in length, each file is hierarchical in structure, containing a housing unit record followed by a variable number of person records. Both record types contain approximately 120 variables. Two improvements over the 1980 PUMS files have been incorporated. First, the housing unit serial number is identified on both the housing unit record and on the person record, allowing the file to be processed as a rectangular file. In addition, each person record is assigned an individual weight, allowing users to more closely approximate published reports. Unlike previous years, the 1990 PUMS 1-Percent and 5-Percent Samples have not been released in separate geographic series (known as "A," "B," etc. records). Instead, each sample has its own set of geographies, known as "Public Use Microdata Areas" (PUMAs), established by the Census Bureau with assistance from each State Data Center. The PUMAs in the 1-Percent Sample are based on a distinction between metropolitan and nonmetropolitan areas. Metropolitan areas encompass whole central cities, Primary Metropolitan Statistical Areas (PMSAs), Metropolitan Statistical Areas (MSAs), or groups thereof, except where the city or metropolitan area contains more than 200,000 inhabitants. In that case, the city or metropolitan area is divided into several PUMAs. Nonmetropolitan PUMAs are based on areas or groups of areas outside the central city, PMSA, or MSA. PUMAs in this 1-Percent Sample may cross state lines. (2) The codebook is provided as a Portable Document Format (PDF) file. The PDF file format was developed by Adobe Systems Incorporated and can be accessed using PDF reader software, such as the Adobe Acrobat Reader. Information on how to obtain a copy of the Acrobat Reader is provided through the ICPSR Website on the Internet.

About this dataset

Context

The dataset tabulates the Non-Hispanic population of Beatrice by race. It includes the distribution of the Non-Hispanic population of Beatrice across various race categories as identified by the Census Bureau. The dataset can be utilized to understand the Non-Hispanic population distribution of Beatrice across relevant racial categories.

Key observations

Of the Non-Hispanic population in Beatrice, the largest racial group is White alone with a population of 11,272 (95.38% of the total Non-Hispanic population).

Content

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

Racial categories include:

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

Variables / Data Columns

• Race: This column displays the racial categories (for Non-Hispanic) for the Beatrice
• Population: The population of the racial category (for Non-Hispanic) in the Beatrice is shown in this column.
• % of Total Population: This column displays the percentage distribution of each race as a proportion of Beatrice total Non-Hispanic population. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

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

Custom data

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

Inspiration

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

Recommended for further research

This dataset is a part of the main dataset for Beatrice Population by Race & Ethnicity. You can refer the same here

Source

This dataset is a modified version of the California Housing dataset available from Luís Torgo's page (University of Porto). Luís Torgo obtained it from the StatLib repository (which is closed now). The dataset may also be downloaded from StatLib mirrors.

This dataset appeared in a 1997 paper titled Sparse Spatial Autoregressions by Pace, R. Kelley and Ronald Barry, published in the Statistics and Probability Letters journal. They built it using the 1990 California census data. It contains one row per census block group. A block group is the smallest geographical unit for which the U.S. Census Bureau publishes sample data (a block group typically has a population of 600 to 3,000 people)

Tweaks

The dataset in this directory is almost identical to the original, with two differences:

207 values were randomly removed from the total_bedrooms column, so we can discuss what to do with missing data. An additional categorical attribute called ocean_proximity was added, indicating (very roughly) whether each block group is near the ocean, near the Bay area, inland or on an island. This allows discussing what to do with categorical data. Note that the block groups are called "districts" in the Jupyter notebooks, simply because in some contexts the name "block group" was confusing.

Important Dataset Update 6/24/2020:Summit and Wasatch Counties updated.Important Dataset Update 6/12/2020:MAG area updated.Important Dataset Update 7/15/2019: This dataset now includes projections for all populated statewide traffic analysis zones (TAZs). Projections within the Wasatch Front urban area ( SUBAREAID = 1) were produced with using the Real Estate Market Model as described below. Socioeconomic forecasts produced for Cache MPO (Cache County, SUBAREAID = 2), Dixie MPO (Washington County, SUBAREAID = 3), Summit County (SUBAREAID = 4), and UDOT (other areas of the state, SUBAREAID = 0) all adhere to the University of Utah Gardner Policy Institute's county-level projection controls, but other modeling methods are used to arrive at the TAZ-level forecasts for these areas.As with any dataset that presents projections into the future, it is important to have a full understanding of the data before using it. Before using this data, you are strongly encouraged to read the metadata description below and direct any questions or feedback about this data to analytics@wfrc.org. Every four years, the Wasatch Front’s two metropolitan planning organizations (MPOs), Wasatch Front Regional Council (WFRC) and Mountainland Association of Governments (MAG), collaborate to update a set of annual small area -- traffic analysis zone and ‘city area’, see descriptions below) -- population and employment projections for the Salt Lake City-West Valley City (WFRC), Ogden-Layton (WFRC), and Provo-Orem (MAG) urbanized areas. These projections are primarily developed for the purpose of informing long-range transportation infrastructure and services planning done as part of the 4 year Regional Transportation Plan update cycle, as well as Utah’s Unified Transportation Plan, 2019-2050. Accordingly, the foundation for these projections is largely data describing existing conditions for a 2015 base year, the first year of the latest RTP process. The projections are included in the official travel models, which are publicly released at the conclusion of the RTP process. As these projections may be a valuable input to other analyses, this dataset is made available at http://data.wfrc.org/search?q=projections as a public service for informational purposes only. It is solely the responsibility of the end user to determine the appropriate use of this dataset for other purposes. Wasatch Front Real Estate Market Model (REMM) ProjectionsWFRC and MAG have developed a spatial statistical model using the UrbanSim modeling platform to assist in producing these annual projections. This model is called the Real Estate Market Model, or REMM for short. REMM is used for the urban portion of Weber, Davis, Salt Lake, and Utah counties. REMM relies on extensive inputs to simulate future development activity across the greater urbanized region. Key inputs to REMM include:Demographic data from the decennial census;County-level population and employment projections -- used as REMM control totals -- are produced by the University of Utah’s Kem C. Gardner Policy Institute (GPI) funded by the Utah State Legislature;Current employment locational patterns derived from the Utah Department of Workforce Services; Land use visioning exercises and feedback, especially in regard to planned urban and local center development, with city and county elected officials and staff;Current land use and valuation GIS-based parcel data stewarded by County Assessors;Traffic patterns and transit service from the regional Travel Demand Model that together form the landscape of regional accessibility to workplaces and other destinations; andCalibration of model variables to balance the fit of current conditions and dynamics at the county and regional level.‘Traffic Analysis Zone’ ProjectionsThe annual projections are forecasted for each of the Wasatch Front’s 2,800+ Traffic Analysis Zone (TAZ) geographic units. TAZ boundaries are set along roads, streams, and other physical features and average about 600 acres (0.94 square miles). TAZ sizes vary, with some TAZs in the densest areas representing only a single city block (25 acres). ‘City Area’ ProjectionsThe TAZ-level output from the model is also available for ‘city areas’ that sum the projections for the TAZ geographies that roughly align with each city’s current boundary. As TAZs do not align perfectly with current city boundaries, the ‘city area’ summaries are not projections specific to a current or future city boundary, but the ‘city area’ summaries may be suitable surrogates or starting points upon which to base city-specific projections.Summary Variables in the DatasetsAnnual projection counts are available for the following variables (please read Key Exclusions note below):DemographicsHousehold Population Count (excludes persons living in group quarters)Household Count (excludes group quarters)EmploymentTypical Job Count (includes job types that exhibit typical commuting and other travel/vehicle use patterns)Retail Job Count (retail, food service, hotels, etc)Office Job Count (office, health care, government, education, etc)Industrial Job Count (manufacturing, wholesale, transport, etc)Non-Typical Job Count* (includes agriculture, construction, mining, and home-based jobs) This can be calculated by subtracting Typical Job Count from All Employment Count.All Employment Count* (all jobs, this sums jobs from typical and non-typical sectors).* These variable includes REMM’s attempt to estimate construction jobs in areas that experience new and re-development activity. Areas may see short-term fluctuations in Non-Typical and All Employment counts due to the temporary location of construction jobs.Population and employment projections for the Wasatch Front area can be combined with those developed by Dixie MPO (St. George area), Cache MPO (Logan area), and the Utah Department of Transportation (for the remainder of the state) into one database for use in the Utah Statewide Travel Model (USTM). While projections for the areas outside of the Wasatch Front use different forecasting methods, they contain the same summary-level population and employment projections making similar TAZ and ‘City Area’ data available statewide. WFRC plans, in the near future, to add additional areas to these projections datasets by including the projections from the USTM model.Key Exclusions from TAZ and ‘City Area’ ProjectionsAs the primary purpose for the development of these population and employment projections is to model future travel in the region, REMM-based projections do not include population or households that reside in group quarters (prisons, senior centers, dormitories, etc), as residents of these facilities typically have a very low impact on regional travel. USTM-based projections also excludes group quarter populations. Group quarters population estimates are available at the county-level from GPI and at various sub-county geographies from the Census Bureau.

The American Community Survey (ACS) is a nationwide survey conducted by the U.S. Census Bureau that is designed to provide communities a fresh look at how they are changing. It is a critical element in the Census Bureau's reengineered decennial census program, incorporating the detailed socioeconomic and housing questions that were previously asked on the decennial census long form into the ACS questionnaire. The ACS now collects and produces this detailed population and housing information every year instead of every ten years. Data are collected on an on-going basis throughout the year and are released each year for large geographic areas, those with 65,000 persons or more. However, sample sizes are not large enough for annual releases that cover smaller areas, those with less than 65,000 persons. Data that are suitable for areas with 20,000 to 65,000 persons are accumulated over three years and termed a three-year period estimate, the first of which was for the 2005-2007 period. Data that are suitable for areas with less than 20,000 persons are accumulated over five years and termed a five-year period estimate, the first of which was for the 2005-2009 period. The data in this series of RGIS Clearinghouse tables are for all New Mexico counties and are based on the 2005-2009 ACS Five-Year Period Estimates collected between January 2005 and December 2009. These data tables are a summary of all major economic topics published through the ACS, providing statistics on employment status, commuting to work, occupation, industry, class of worker, household income distributions, household income by type, family income distributions, nonfamily household income, incomes of individuals, and family and person poverty rates. Percentages are shown along with numeric estimates for most data items. Because the data are based on a sample the Census Bureau also provides information about the magnitude of sampling error. Consequently, the estimated margin of error (MOE) is shown next to each data item. Each economic topic is covered in a separate file in both Excel and CSV formats. These files, along with file-specific descriptions (in Word and text formats) are available in a single zip file.

What you get:

Upvote! The database contains +40,000 records on US Gross Rent & Geo Locations. The field description of the database is documented in the attached pdf file. To access, all 325,272 records on a scale roughly equivalent to a neighborhood (census tract) see link below and make sure to upvote. Upvote right now, please. Enjoy!

Get the full free database with coupon code: FreeDatabase, See directions at the bottom of the description... And make sure to upvote :) coupon ends at 2:00 pm 8-23-2017

Gross Rent & Geographic Statistics:

• Mean Gross Rent (double)
• Median Gross Rent (double)
• Standard Deviation of Gross Rent (double)
• Number of Samples (double)
• Square area of land at location (double)
• Square area of water at location (double)

Geographic Location:

• Longitude (double)
• Latitude (double)
• State Name (character)
• State abbreviated (character)
• State_Code (character)
• County Name (character)
• City Name (character)
• Name of city, town, village or CPD (character)
• Primary, Defines if the location is a track and block group.
• Zip Code (character)
• Area Code (character)

Abstract

The data set originally developed for real estate and business investment research. Income is a vital element when determining both quality and socioeconomic features of a given geographic location. The following data was derived from over +36,000 files and covers 348,893 location records.

License

Only proper citing is required please see the documentation for details. Have Fun!!!

Golden Oak Research Group, LLC. “U.S. Income Database Kaggle”. Publication: 5, August 2017. Accessed, day, month year.

For any questions, you may reach us at research_development@goldenoakresearch.com. For immediate assistance, you may reach me on at 585-626-2965

please note: it is my personal number and email is preferred

Check our data's accuracy: Census Fact Checker

Access all 325,272 location for Free Database Coupon Code:

Don't settle. Go big and win big. Optimize your potential**. Access all gross rent records and more on a scale roughly equivalent to a neighborhood, see link below:

• Website: Golden Oak Research make sure to upvote

A small startup with big dreams, giving the every day, up and coming data scientist professional grade data at affordable prices It's what we do.

This web map displays data from the voter registration database as the percent of registered voters by census tract in King County, Washington. The data for this web map is compiled from King County Elections voter registration data for the years 2013-2019. The total number of registered voters is based on the geo-location of the voter's registered address at the time of the general election for each year. The eligible voting population, age 18 and over, is based on the estimated population increase from the US Census Bureau and the Washington Office of Financial Management and was calculated as a projected 6 percent population increase for the years 2010-2013, 7 percent population increase for the years 2010-2014, 9 percent population increase for the years 2010-2015, 11 percent population increase for the years 2010-2016 & 2017, 14 percent population increase for the years 2010-2018 and 17 percent population increase for the years 2010-2019. The total population 18 and over in 2010 was 1,517,747 in King County, Washington. The percentage of registered voters represents the number of people who are registered to vote as compared to the eligible voting population, age 18 and over. The voter registration data by census tract was grouped into six percentage range estimates: 50% or below, 51-60%, 61-70%, 71-80%, 81-90% and 91% or above with an overall 84 percent registration rate. In the map the lighter colors represent a relatively low percentage range of voter registration and the darker colors represent a relatively high percentage range of voter registration. PDF maps of these data can be viewed at King County Elections downloadable voter registration maps. The 2019 General Election Voter Turnout layer is voter turnout data by historical precinct boundaries for the corresponding year. The data is grouped into six percentage ranges: 0-30%, 31-40%, 41-50% 51-60%, 61-70%, and 71-100%. The lighter colors represent lower turnout and the darker colors represent higher turnout. The King County Demographics Layer is census data for language, income, poverty, race and ethnicity at the census tract level and is based on the 2010-2014 American Community Survey 5 year Average provided by the United States Census Bureau. Since the data is based on a survey, they are considered to be estimates and should be used with that understanding. The demographic data sets were developed and are maintained by King County Staff to support the King County Equity and Social Justice program. Other data for this map is located in the King County GIS Spatial Data Catalog, where data is managed by the King County GIS Center, a multi-department enterprise GIS in King County, Washington. King County has nearly 1.3 million registered voters and is the largest jurisdiction in the United States to conduct all elections by mail. In the map you can view the percent of registered voters by census tract, compare registration within political districts, compare registration and demographic data, verify your voter registration or register to vote through a link to the VoteWA, Washington State Online Voter Registration web page.

The Census Bureau’s urban-rural classification is fundamentally a delineation of geographical areas, identifying both individual urban areas and the rural areas of the nation. The Census Bureau’s urban areas represent densely developed territory, and encompass residential, commercial, and other non-residential urban land uses. To qualify as an urban area, the territory identified according to criteria must have at least 5,000 people or 2,000 housing units. The 2020 Census changed how urban areas are determined from the 2010 criteria. The population requirement was increased to 5,000 people from 2,500 in 2010. This value is now determined by housing unit density instead of population density. Urban areas can now also be defined by the number of housing units present. Finally, the 2020 Census does not distinguish different types of urban areas. Areas are simply urban or rural.This layer was originally downloaded from the US Census Bureau website and clipped to the Stark County boundary. For more information on urban and rural classification and criteria, visit Redefining Urban Areas following the 2020 Census.

IPUMS-International is an effort to inventory, preserve, harmonize, and disseminate census microdata from around the world. The project has collected the world's largest archive of publicly available census samples. The data are coded and documented consistently across countries and over time to facillitate comparative research. IPUMS-International makes these data available to qualified researchers free of charge through a web dissemination system. The IPUMS project is a collaboration of the Minnesota Population Center, National Statistical Offices, and international data archives. Major funding is provided by the U.S. National Science Foundation and the Demographic and Behavioral Sciences Branch of the National Institute of Child Health and Human Development. Additional support is provided by the University of Minnesota Office of the Vice President for Research, the Minnesota Population Center, and Sun Microsystems. The American Community Survey (ACS) is a relatively new survey conducted by the U.S. Census Bureau. It uses a series of monthly samples to produce annually updated estimates for the same small areas (census tracts and block groups) formerly surveyed via the decennial census long-form sample. Initially, five years of samples were required to produce these small-area data. Once the Census Bureau, released its first 5-year estimates in December 2010; new small-area statistics now are produced annually. The Census Bureau also will produce 3-year and 1-year data products for larger geographic areas. The ACS includes people living in both housing units (HUs) and group quarters (GQs). The ACS is conducted throughout the United States and in Puerto Rico, where it is called the Puerto Rico Community Survey (PRCS).

Important Dataset Update 6/24/2020:Summit and Wasatch Counties updated.Important Dataset Update 6/12/2020:MAG area updated.Important Dataset Update 7/15/2019:This dataset now includes projections for all populated statewide traffic analysis zones (TAZs).Projections within the Wasatch Front urban area ( SUBAREAID = 1) were produced with using the Real Estate Market Model as described below.Socioeconomic forecasts produced for Cache MPO (Cache County, SUBAREAID = 2), Dixie MPO (Washington County, SUBAREAID = 3), Summit County (SUBAREAID = 4), and UDOT (other areas of the state, SUBAREAID = 0) all adhere to the University of Utah Gardner Policy Institute's county-level projection controls, but other modeling methods are used to arrive at the TAZ-level forecasts for these areas.As with any dataset that presents projections into the future, it is important to have a full understanding of the data before using it. Before using this data, you are strongly encouraged to read the metadata description below and direct any questions or feedback about this data to analytics@wfrc.org.Every four years, the Wasatch Front’s two metropolitan planning organizations (MPOs), Wasatch Front Regional Council (WFRC) and Mountainland Association of Governments (MAG), collaborate to update a set of annual small area -- traffic analysis zone and ‘city area’, see descriptions below) -- population and employment projections for the Salt Lake City-West Valley City (WFRC), Ogden-Layton (WFRC), and Provo-Orem (MAG) urbanized areas.These projections are primarily developed for the purpose of informing long-range transportation infrastructure and services planning done as part of the 4 year Regional Transportation Plan update cycle, as well as Utah’s Unified Transportation Plan, 2019-2050. Accordingly, the foundation for these projections is largely data describing existing conditions for a 2015 base year, the first year of the latest RTP process. The projections are included in the official travel models, which are publicly released at the conclusion of the RTP process.As these projections may be a valuable input to other analyses, this dataset is made available at http://data.wfrc.org/search?q=projections as a public service for informational purposes only. It is solely the responsibility of the end user to determine the appropriate use of this dataset for other purposes.Wasatch Front Real Estate Market Model (REMM) ProjectionsWFRC and MAG have developed a spatial statistical model using the UrbanSim modeling platform to assist in producing these annual projections. This model is called the Real Estate Market Model, or REMM for short. REMM is used for the urban portion of Weber, Davis, Salt Lake, and Utah counties. REMM relies on extensive inputs to simulate future development activity across the greater urbanized region. Key inputs to REMM include:Demographic data from the decennial census;County-level population and employment projections -- used as REMM control totals -- are produced by the University of Utah’s Kem C. Gardner Policy Institute (GPI) funded by the Utah State Legislature;Current employment locational patterns derived from the Utah Department of Workforce Services;Land use visioning exercises and feedback, especially in regard to planned urban and local center development, with city and county elected officials and staff;Current land use and valuation GIS-based parcel data stewarded by County Assessors;Traffic patterns and transit service from the regional Travel Demand Model that together form the landscape of regional accessibility to workplaces and other destinations; andCalibration of model variables to balance the fit of current conditions and dynamics at the county and regional level.‘Traffic Analysis Zone’ ProjectionsThe annual projections are forecasted for each of the Wasatch Front’s 2,800+ Traffic Analysis Zone (TAZ) geographic units. TAZ boundaries are set along roads, streams, and other physical features and average about 600 acres (0.94 square miles). TAZ sizes vary, with some TAZs in the densest areas representing only a single city block (25 acres).‘City Area’ ProjectionsThe TAZ-level output from the model is also available for ‘city areas’ that sum the projections for the TAZ geographies that roughly align with each city’s current boundary. As TAZs do not align perfectly with current city boundaries, the ‘city area’ summaries are not projections specific to a current or future city boundary, but the ‘city area’ summaries may be suitable surrogates or starting points upon which to base city-specific projections.Summary Variables in the DatasetsAnnual projection counts are available for the following variables (please read Key Exclusions note below):DemographicsHousehold Population Count (excludes persons living in group quarters)Household Count (excludes group quarters)EmploymentTypical Job Count (includes job types that exhibit typical commuting and other travel/vehicle use patterns)Retail Job Count (retail, food service, hotels, etc)Office Job Count (office, health care, government, education, etc)Industrial Job Count (manufacturing, wholesale, transport, etc)Non-Typical Job Count* (includes agriculture, construction, mining, and home-based jobs) This can be calculated by subtracting Typical Job Count from All Employment Count.All Employment Count* (all jobs, this sums jobs from typical and non-typical sectors).* These variable includes REMM’s attempt to estimate construction jobs in areas that experience new and re-development activity. Areas may see short-term fluctuations in Non-Typical and All Employment counts due to the temporary location of construction jobs.Population and employment projections for the Wasatch Front area can be combined with those developed by Dixie MPO (St. George area), Cache MPO (Logan area), and the Utah Department of Transportation (for the remainder of the state) into one database for use in the Utah Statewide Travel Model (USTM). While projections for the areas outside of the Wasatch Front use different forecasting methods, they contain the same summary-level population and employment projections making similar TAZ and ‘City Area’ data available statewide. WFRC plans, in the near future, to add additional areas to these projections datasets by including the projections from the USTM model.Key Exclusions from TAZ and ‘City Area’ ProjectionsAs the primary purpose for the development of these population and employment projections is to model future travel in the region, REMM-based projections do not include population or households that reside in group quarters (prisons, senior centers, dormitories, etc), as residents of these facilities typically have a very low impact on regional travel. USTM-based projections also excludes group quarter populations. Group quarters population estimates are available at the county-level from GPI and at various sub-county geographies from the Census Bureau.

About this dataset

Context

The dataset tabulates the Non-Hispanic population of Saltville by race. It includes the distribution of the Non-Hispanic population of Saltville across various race categories as identified by the Census Bureau. The dataset can be utilized to understand the Non-Hispanic population distribution of Saltville across relevant racial categories.

Key observations

Of the Non-Hispanic population in Saltville, the largest racial group is White alone with a population of 2,039 (99.32% of the total Non-Hispanic population).

Content

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

Racial categories include:

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

Variables / Data Columns

• Race: This column displays the racial categories (for Non-Hispanic) for the Saltville
• Population: The population of the racial category (for Non-Hispanic) in the Saltville is shown in this column.
• % of Total Population: This column displays the percentage distribution of each race as a proportion of Saltville total Non-Hispanic population. Please note that the sum of all percentages may not equal one due to rounding of values.

Good to know

Margin of Error

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

Custom data

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

Inspiration

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

Recommended for further research

This dataset is a part of the main dataset for Saltville Population by Race & Ethnicity. You can refer the same here

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

City boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to

Big “p” policy changes at the state and federal level are certainly important to health equity, such as eligibility for and generosity of Medicaid benefits. Medicaid expansion has significantly expanded the number of people who are eligible for Medicaid and the creation of the health insurance exchanges (Marketplace) under the Affordable Care Act created a very visible avenue through which people can learn that they are eligible. Although many applications are now submitted online, physical access to state, county, and tribal government Medicaid offices still plays a critical role in understanding eligibility, getting help in applying, and navigating required documentation for both initial enrollment and redetermination of eligibility. However, as more government functions have moved online, in-person office locations and/or staff may have been cut to reduce costs, and gentrification has shifted where minoritized, marginalized, and/or low-income populations live, it is unclear if this key local connection point between residents and Medicaid has been maintained. Our objective was to identify and geocode all Medicaid offices in the United States for pairing with other spatial data (e.g., demographics, Medicaid participation, health care use, health outcomes) to investigate policy-relevant research questions. Three coders identified Medicaid office addresses in all 50 states and the District of Columbia by searching state government websites (e.g., Department of Health and Human Services or analogous state agency) during late 2021 and early 2022 for the appropriate Medicaid agency and its office locations, which were then reviewed for accuracy by a fourth coder. Our corpus of Medicaid office addresses was then geocoded using the Census Geocoder from the US Census Bureau (https://geocoding.geo.census.gov/geocoder/) with unresolved addresses investigated and/or manually geocoded using Google Maps. The corpus was updated in August through December 2023 following the end of the COVID-19 public health emergency by a fifth coder as several states closed and/or combined offices during the pandemic. After deduplication (e.g., where multiple counties share a single office) and removal of mailing addresses (e.g., PO Boxes), our dataset includes 3,027 Medicaid office locations. 1 (December 19, 2023) – original version 2 (January 25, 2024) – added related publication (Data in Brief), corrected two records that were missing negative signs in longitude 3 (February 6, 2024) – corrected latitude and longitude for one office (1340 State Route 9, Lake George, NY 12845) 4 (March 4, 2024) – added one office for Vermont after contacting relevant state agency (280 State Road, Waterbury, VT 05671)

This is a lookup table containing various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them. These are termed Minor Civil Division (MCDs) by the Census Bureau. The table encompases the Twin Cities 7-county metropolitan area. It is intended to be a Council wide master lookup table for these entites. It contains official federal and state unique identifiers for CTUs and MCDs as well as identifiers created and used by other organizations. The table also contains historical MCDs dating back to the 1990s and a few other non-MCD records that are of importance to Met. Council use of this table.

The County CTU Lookup Table relates to the Counties and Cities & Townships, Twin Cities Metropolitan Area dataset here: https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-metro-counties-and-ctus

NOTES:

- On 5/28/2014 a new field was added to reflect the new community designations defined in the Council's Thrive MSP 2040 regional plan - COMDES2040

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lake St. Croix Beach was incorrect. It was changed from 2394379 to 2395599 to match GNIS.

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lilydale was incorrect. It was changed from 2394457 to 2395708 to match GNIS.

- On 11/9/2010 it was discovered that the CTU ID used for the City of Crystal was incorrect. It was changed from 2393541 to 2393683 to match GNIS.

- Effective April 2008, a change was made in GNIS to match the FIPS place codes to the "civil" feature for each city instead of the "populated place" feature. Both cities and townships are now "civil" features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed.

- As of January 1, 2006, the five digit FIPS 55-3 Place codes that were used as unique identifiers in this dataset (CTU_CODE and COCTU_CODE fields) were officially retired by the Federal governement. They are replaced by a set of integer codes from the Geographic Names Information System (GNIS_CODE field). Both codes will be kept in this database, but the GNIS_CODE is considered the official unique identifier from this point forward. The GNIS codes are also slated to become official ANSI codes for these geographic features. While GNIS treats these codes as 6 to 8 digit integer data types, the Census Bureau formats them as 8 digit text fields, right justified with leading zeros included.

- The Census Bureau will continue to create FIPS 55 Place codes for new cities and townships through the 2010 Census. After that, no new FIPS 55 codes will be created. Note that for townships that wholly incorporate into cities, the same FIPS 55 code will be used for the new city. (GNIS creates a new ID for the new city.)

- Cities and townships have also been referred to as ''MCDs'' (a Census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity.

- A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport).

- Some cities are split between two counties. Only those parts of cities within the 7-county area are included.

- Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change.