VITAL SIGNS INDICATOR Population (LU1)

FULL MEASURE NAME Population estimates

LAST UPDATED October 2019

DESCRIPTION Population is a measurement of the number of residents that live in a given geographical area, be it a neighborhood, city, county or region.

DATA SOURCES U.S Census Bureau: Decennial Census No link available (1960-1990) http://factfinder.census.gov (2000-2010)

California Department of Finance: Population and Housing Estimates Table E-6: County Population Estimates (1961-1969) Table E-4: Population Estimates for Counties and State (1971-1989) Table E-8: Historical Population and Housing Estimates (2001-2018) Table E-5: Population and Housing Estimates (2011-2019) http://www.dof.ca.gov/Forecasting/Demographics/Estimates/

U.S. Census Bureau: Decennial Census - via Longitudinal Tract Database Spatial Structures in the Social Sciences, Brown University Population Estimates (1970 - 2010) http://www.s4.brown.edu/us2010/index.htm

U.S. Census Bureau: American Community Survey 5-Year Population Estimates (2011-2017) http://factfinder.census.gov

U.S. Census Bureau: Intercensal Estimates Estimates of the Intercensal Population of Counties (1970-1979) Intercensal Estimates of the Resident Population (1980-1989) Population Estimates (1990-1999) Annual Estimates of the Population (2000-2009) Annual Estimates of the Population (2010-2017) No link available (1970-1989) http://www.census.gov/popest/data/metro/totals/1990s/tables/MA-99-03b.txt http://www.census.gov/popest/data/historical/2000s/vintage_2009/metro.html https://www.census.gov/data/datasets/time-series/demo/popest/2010s-total-metro-and-micro-statistical-areas.html

CONTACT INFORMATION vitalsigns.info@bayareametro.gov

METHODOLOGY NOTES (across all datasets for this indicator) All legal boundaries and names for Census geography (metropolitan statistical area, county, city, and tract) are as of January 1, 2010, released beginning November 30, 2010, by the U.S. Census Bureau. A Priority Development Area (PDA) is a locally-designated area with frequent transit service, where a jurisdiction has decided to concentrate most of its housing and jobs growth for development in the foreseeable future. PDA boundaries are current as of August 2019. For more information on PDA designation see http://gis.abag.ca.gov/website/PDAShowcase/.

Population estimates for Bay Area counties and cities are from the California Department of Finance, which are as of January 1st of each year. Population estimates for non-Bay Area regions are from the U.S. Census Bureau. Decennial Census years reflect population as of April 1st of each year whereas population estimates for intercensal estimates are as of July 1st of each year. Population estimates for Bay Area tracts are from the decennial Census (1970 -2010) and the American Community Survey (2008-2012 5-year rolling average; 2010-2014 5-year rolling average; 2013-2017 5-year rolling average). Estimates of population density for tracts use gross acres as the denominator.

Population estimates for Bay Area PDAs are from the decennial Census (1970 - 2010) and the American Community Survey (2006-2010 5 year rolling average; 2010-2014 5-year rolling average; 2013-2017 5-year rolling average). Population estimates for PDAs are derived from Census population counts at the tract level for 1970-1990 and at the block group level for 2000-2017. Population from either tracts or block groups are allocated to a PDA using an area ratio. For example, if a quarter of a Census block group lies with in a PDA, a quarter of its population will be allocated to that PDA. Tract-to-PDA and block group-to-PDA area ratios are calculated using gross acres. Estimates of population density for PDAs use gross acres as the denominator.

Annual population estimates for metropolitan areas outside the Bay Area are from the Census and are benchmarked to each decennial Census. The annual estimates in the 1990s were not updated to match the 2000 benchmark.

The following is a list of cities and towns by geographical area: Big Three: San Jose, San Francisco, Oakland Bayside: Alameda, Albany, Atherton, Belmont, Belvedere, Berkeley, Brisbane, Burlingame, Campbell, Colma, Corte Madera, Cupertino, Daly City, East Palo Alto, El Cerrito, Emeryville, Fairfax, Foster City, Fremont, Hayward, Hercules, Hillsborough, Larkspur, Los Altos, Los Altos Hills, Los Gatos, Menlo Park, Mill Valley, Millbrae, Milpitas, Monte Sereno, Mountain View, Newark, Pacifica, Palo Alto, Piedmont, Pinole, Portola Valley, Redwood City, Richmond, Ross, San Anselmo, San Bruno, San Carlos, San Leandro, San Mateo, San Pablo, San Rafael, Santa Clara, Saratoga, Sausalito, South San Francisco, Sunnyvale, Tiburon, Union City, Vallejo, Woodside Inland, Delta and Coastal: American Canyon, Antioch, Benicia, Brentwood, Calistoga, Clayton, Cloverdale, Concord, Cotati, Danville, Dixon, Dublin, Fairfield, Gilroy, Half Moon Bay, Healdsburg, Lafayette, Livermore, Martinez, Moraga, Morgan Hill, Napa, Novato, Oakley, Orinda, Petaluma, Pittsburg, Pleasant Hill, Pleasanton, Rio Vista, Rohnert Park, San Ramon, Santa Rosa, Sebastopol, Sonoma, St. Helena, Suisun City, Vacaville, Walnut Creek, Windsor, Yountville Unincorporated: all unincorporated towns

Abstract

A crosswalk matching US ZIP codes to corresponding CBSA (core-based statistical area)

Documentation

The denominators used to calculate the address ratios are the ZIP code totals. When a ZIP is split by any of the other geographies, that ZIP code is duplicated in the crosswalk file.

**Example: **ZIP code 03870 is split by two different Census tracts, 33015066000 and 33015071000, which appear in the tract column. The ratio of residential addresses in the first ZIP-Tract record to the total number of residential addresses in the ZIP code is .0042 (.42%). The remaining residential addresses in that ZIP (99.58%) fall into the second ZIP-Tract record.

So, for example, if one wanted to allocate data from ZIP code 03870 to each Census tract located in that ZIP code, one would multiply the number of observations in the ZIP code by the residential ratio for each tract associated with that ZIP code.

https://redivis.com/fileUploads/4ecb405e-f533-4a5b-8286-11e56bb93368%3E" alt="">(Note that the sum of each ratio column for each distinct ZIP code may not always equal 1.00 (or 100%) due to rounding issues.)

CBSA definition

A core-based statistical area (CBSA) is a U.S. geographic area defined by the Office of Management and Budget (OMB) that consists of one or more counties (or equivalents) anchored by an urban center of at least 10,000 people plus adjacent counties that are socioeconomically tied to the urban center by commuting. Areas defined on the basis of these standards applied to Census 2000 data were announced by OMB in June 2003. These standards are used to replace the definitions of metropolitan areas that were defined in 1990. The OMB released new standards based on the 2010 Census on July 15, 2015.

Further reading

The following article demonstrates how to more effectively use the U.S. Department of Housing and Urban Development (HUD) United States Postal Service ZIP Code Crosswalk Files when working with disparate geographies.

Wilson, Ron and Din, Alexander, 2018. “Understanding and Enhancing the U.S. Department of Housing and Urban Development’s ZIP Code Crosswalk Files,” Cityscape: A Journal of Policy Development and Research, Volume 20 Number 2, 277 – 294. URL: https://www.huduser.gov/portal/periodicals/cityscpe/vol20num2/ch16.pdf

Contact authors

Questions regarding these crosswalk files can be directed to Alex Din with the subject line HUD-Crosswalks.

Acknowledgement

This dataset is taken from the U.S. Department of Housing and Urban Development (HUD) office: https://www.huduser.gov/portal/datasets/usps_crosswalk.html#codebook

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.

The datasets are split by census block, cities, counties, districts, provinces, and states. The typical dataset includes the below fields.

Column numbers, Data attribute, Description 1, device_id, hashed anonymized unique id per moving device 2, origin_geoid, geohash id of the origin grid cell 3, destination_geoid, geohash id of the destination grid cell 4, origin_lat, origin latitude with 4-to-5 decimal precision 5, origin_long, origin longitude with 4-to-5 decimal precision 6, destination_lat, destination latitude with 5-to-6 decimal precision 7, destination_lon, destination longitude with 5-to-6 decimal precision 8, start_timestamp, start timestamp / local time 9, end_timestamp, end timestamp / local time 10, origin_shape_zone, customer provided origin shape id, zone or census block id 11, destination_shape_zone, customer provided destination shape id, zone or census block id 12, trip_distance, inferred distance traveled in meters, as the crow flies 13, trip_duration, inferred duration of the trip in seconds 14, trip_speed, inferred speed of the trip in meters per second 15, hour_of_day, hour of day of trip start (0-23) 16, time_period, time period of trip start (morning, afternoon, evening, night) 17, day_of_week, day of week of trip start(mon, tue, wed, thu, fri, sat, sun) 18, year, year of trip start 19, iso_week, iso week of the trip 20, iso_week_start_date, start date of the iso week 21, iso_week_end_date, end date of the iso week 22, travel_mode, mode of travel (walking, driving, bicycling, etc) 23, trip_event, trip or segment events (start, route, end, start-end) 24, trip_id, trip identifier (unique for each batch of results) 25, origin_city_block_id, census block id for the trip origin point 26, destination_city_block_id, census block id for the trip destination point 27, origin_city_block_name, census block name for the trip origin point 28, destination_city_block_name, census block name for the trip destination point 29, trip_scaled_ratio, ratio used to scale up each trip, for example, a trip_scaled_ratio value of 10 means that 1 original trip was scaled up to 10 trips 30, route_geojson, geojson line representing trip route trajectory or geometry

The datasets can be processed and enhanced to also include places, POI visitation patterns, hour-of-day patterns, weekday patterns, weekend patterns, dwell time inferences, and macro movement trends.

The dataset is delivered as gzipped CSV archive files that are uploaded to your AWS s3 bucket upon request.

The datasets are split by census block, cities, counties, districts, provinces, and states. The typical dataset includes the below fields.

Column numbers, Data attribute, Description 1, device_id, hashed anonymized unique id per moving device 2, origin_geoid, geohash id of the origin grid cell 3, destination_geoid, geohash id of the destination grid cell 4, origin_lat, origin latitude with 4-to-5 decimal precision 5, origin_long, origin longitude with 4-to-5 decimal precision 6, destination_lat, destination latitude with 5-to-6 decimal precision 7, destination_lon, destination longitude with 5-to-6 decimal precision 8, start_timestamp, start timestamp / local time 9, end_timestamp, end timestamp / local time 10, origin_shape_zone, customer provided origin shape id, zone or census block id 11, destination_shape_zone, customer provided destination shape id, zone or census block id 12, trip_distance, inferred distance traveled in meters, as the crow flies 13, trip_duration, inferred duration of the trip in seconds 14, trip_speed, inferred speed of the trip in meters per second 15, hour_of_day, hour of day of trip start (0-23) 16, time_period, time period of trip start (morning, afternoon, evening, night) 17, day_of_week, day of week of trip start(mon, tue, wed, thu, fri, sat, sun) 18, year, year of trip start 19, iso_week, iso week of the trip 20, iso_week_start_date, start date of the iso week 21, iso_week_end_date, end date of the iso week 22, travel_mode, mode of travel (walking, driving, bicycling, etc) 23, trip_event, trip or segment events (start, route, end, start-end) 24, trip_id, trip identifier (unique for each batch of results) 25, origin_city_block_id, census block id for the trip origin point 26, destination_city_block_id, census block id for the trip destination point 27, origin_city_block_name, census block name for the trip origin point 28, destination_city_block_name, census block name for the trip destination point 29, trip_scaled_ratio, ratio used to scale up each trip, for example, a trip_scaled_ratio value of 10 means that 1 original trip was scaled up to 10 trips 30, route_geojson, geojson line representing trip route trajectory or geometry

The datasets can be processed and enhanced to also include places, POI visitation patterns, hour-of-day patterns, weekday patterns, weekend patterns, dwell time inferences, and macro movement trends.

The dataset is delivered as gzipped CSV archive files that are uploaded to your AWS s3 bucket upon request.

This data collection contains information from samples of housing units in 11 Metropolitan Statistical Areas (MSAs). Data include year the structure was built, type and number of living quarters, occupancy status, presence of commercial or medical establishments on the property, and property value. Additional data focus on kitchen and plumbing facilities, type of heating fuel used, source of water, sewage disposal, and heating and air-conditioning equipment. Questions concerning quality of housing include condition of walls and floors, adequacy of heat in winter, availability of electrical outlets, basement and roof water leakage, and exterminator service for mice or rats. Data on housing expenses include amount of mortgage or rent payments and costs of utilities, fuel, garbage collection, property insurance, and real estate taxes. Respondents who had moved recently were questioned about characteristics of the previous residence and reasons for moving. Residents were also asked to evaluate the quality of their neighborhoods with respect to issues such as crime, street noise, quality of roads, commercial activities, presence of trash, litter, abandoned structures, or offensive odors, and adequacy of services such as police protection, shopping facilities, and schools. In addition to housing characteristics, some demographic information is provided on household members, such as age, sex, race, marital status, income, and relationship to householder. Additional data are available on the householder, including years of school completed, Spanish origin, and length of residence. (Source: downloaded from ICPSR 7/13/10)

Please Note: This dataset is part of the historical CISER Data Archive Collection and is also available at ICPSR at https://doi.org/10.3886/ICPSR09853.v1. We highly recommend using the ICPSR version as they may make this dataset available in multiple data formats in the future.

Abstract (en): The Public Use Microdata Samples (PUMS) contain person- and household-level information from the "long-form" questionnaires distributed to a sample of the population enumerated in the 1980 Census. The B Sample containing 1-percent data, consists of a file for each state and an additional file for households and persons residing in metropolitan areas that are too small to be separately identified and/or that cross state boundaries. The B Sample defines Standard Metropolitan Statistical Areas (SMSAs) and county groups differently than in the A Sample [CENSUS OF POPULATION AND HOUSING, 1980 [UNITED STATES]: PUBLIC USE MICRODATA SAMPLE (A SAMPLE): 5-PERCENT SAMPLE (ICPSR 8101)]. Most states cannot be identified in their entirety. Household-level variables include housing tenure, year structure was built, number and types of rooms in dwelling, plumbing facilities, heating equipment, taxes and mortgage costs, number of children, and household and family income. The person record, in addition to containing demographic items such as sex, age, marital status, race, Spanish origin, income, occupation, transportation to work, and education. All persons and housing units in the United States. The B Sample is a stratified sample of households that received the "long-form" questionnaire in the 1980 Census. It comprises 1 percent of all households enumerated in the Census. 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.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. The household and person records in each data file have a logical record length of 193 characters, but the number of records varies with each file.

Key Table Information.Table Title.Nonemployer Statistics by Demographics series (NES-D): Statistics for Employer and Nonemployer Firms by Industry and Sex for the U.S., States, Metro Areas, Counties, and Places: 2022.Table ID.ABSNESD2022.AB00MYNESD01A.Survey/Program.Economic Surveys.Year.2022.Dataset.ECNSVY Nonemployer Statistics by Demographics Company Summary.Source.U.S. Census Bureau, 2022 Economic Surveys, Nonemployer Statistics by Demographics.Release Date.2025-05-08.Release Schedule.The Nonemployer Statistics by Demographics (NES-D) is released yearly, beginning in 2017..Sponsor.National Center for Science and Engineering Statistics, U.S. National Science Foundation.Table Universe.Data in this table combines estimates from the Annual Business Survey (employer firms) and the Nonemployer Statistics by Demographics (nonemployer firms).Includes U.S. firms with no paid employment or payroll, annual receipts of $1,000 or more ($1 or more in the construction industries) and filing Internal Revenue Service (IRS) tax forms for sole proprietorships (Form 1040, Schedule C), partnerships (Form 1065), or corporations (the Form 1120 series).Includes U.S. employer firms estimates of business ownership by sex, ethnicity, race, and veteran status from the 2023 Annual Business Survey (ABS) collection. The employer business dataset universe consists of employer firms that are in operation for at least some part of the reference year, are located in one of the 50 U.S. states, associated offshore areas, or the District of Columbia, have paid employees and annual receipts of $1,000 or more, and are classified in one of nineteen in-scope sectors defined by the 2022 North American Industry Classification System (NAICS), except for NAICS 111, 112, 482, 491, 521, 525, 813, 814, and 92 which are not covered.Data are also obtained from administrative records, the 2022 Economic Census, and other economic surveys. Note: For employer data only, the collection year is the year in which the data are collected. A reference year is the year that is referenced in the questions on the survey and in which the statistics are tabulated. For example, the 2023 ABS collection year produces statistics for the 2022 reference year. The "Year" column in the table is the reference year..Methodology.Data Items and Other Identifying Records.Total number of employer and nonemployer firmsTotal sales, value of shipments, or revenue of employer and nonemployer firms ($1,000)Number of nonemployer firmsSales, value of shipments, or revenue of nonemployer firms ($1,000)Number of employer firmsSales, value of shipments, or revenue of employer firms ($1,000)Number of employeesAnnual payroll ($1,000)These data are aggregated by the following demographic classifications of firm for:All firms Classifiable (firms classifiable by sex, ethnicity, race, and veteran status) Sex Female Male Equally male-owned and female-owned Unclassifiable (firms not classifiable by sex, ethnicity, race, and veteran status) Definitions can be found by clicking on the column header in the table or by accessing the Economic Census Glossary..Unit(s) of Observation.The reporting units for the NES-D and the ABS are companies or firms rather than establishments. A company or firm is comprised of one or more in-scope establishments that operate under the ownership or control of a single organization..Geography Coverage.The 2022 data are shown for the total of all sectors (00) and the 2- to 6-digit NAICS code levels for:United StatesStates and the District of ColumbiaIn addition, the total of all sectors (00) NAICS and the 2-digit NAICS code levels for:Metropolitan Statistical AreasMicropolitan Statistical AreasMetropolitan DivisionsCombined Statistical AreasCountiesEconomic PlacesFor information about geographies, see Geographies..Industry Coverage.The data are shown for the total of all sectors ("00"), and at the 2- through 6-digit NAICS code levels depending on geography. Sector "00" is not an official NAICS sector but is rather a way to indicate a total for multiple sectors. Note: Other programs outside of ABS may use sector 00 to indicate when multiple NAICS sectors are being displayed within the same table and/or dataset.The following are excluded from the total of all sectors:Crop and Animal Production (NAICS 111 and 112)Rail Transportation (NAICS 482)Postal Service (NAICS 491)Monetary Authorities-Central Bank (NAICS 521)Funds, Trusts, and Other Financial Vehicles (NAICS 525)Office of Notaries (NAICS 541120)Religious, Grantmaking, Civic, Professional, and Similar Organizations (NAICS 813)Private Households (NAICS 814)Public Administration (NAICS 92)For information about NAICS, see North American Industry Classification System..Sampling.NES-D nonemployer data are not conducted through sampling. Nonemployer Statistics (NES) data originate from statistical information obtained through business income tax records that the Internal Revenue Service (IRS) provides to the Census Bureau. ...

This dataset is imported from the US Department of Commerce, National Telecommunications and Information Administration (NTIA) and its "Data Explorer" site. The underlying data comes from the US Census

1. dataset: Specifies the month and year of the survey as a string, in "Mon YYYY" format. The CPS is a monthly survey, and NTIA periodically sponsors Supplements to that survey.

2. variable: Contains the standardized name of the variable being measured. NTIA identified the availability of similar data across Supplements, and assigned variable names to ease time-series comparisons.

3. description: Provides a concise description of the variable.

4. universe: Specifies the variable representing the universe of persons or households included in the variable's statistics. The specified variable is always included in the file. The only variables lacking universes are isPerson and isHouseholder, as they are themselves the broadest universes measured in the CPS.

5. A large number of *Prop, *PropSE, *Count, and *CountSE columns comprise the remainder of the columns. For each demographic being measured (see below), four statistics are produced, including the estimated proportion of the group for which the variable is true (*Prop), the standard error of that proportion (*PropSE), the estimated number of persons or households in that group for which the variable is true (*Count), and the standard error of that count (*CountSE).

DEMOGRAPHIC CATEGORIES

1. us: The usProp, usPropSE, usCount, and usCountSE columns contain statistics about all persons and households in the universe (which represents the population of the fifty states and the District and Columbia). For example, to see how the prevelance of Internet use by Americans has changed over time, look at the usProp column for each survey's internetUser variable.

2. age: The age category is divided into five ranges: ages 3-14, 15-24, 25-44, 45-64, and 65+. The CPS only includes data on Americans ages 3 and older. Also note that household reference persons must be at least 15 years old, so the age314* columns are blank for household-based variables. Those columns are also blank for person-based variables where the universe is "isAdult" (or a sub-universe of "isAdult"), as the CPS defines adults as persons ages 15 or older. Finally, note that some variables where children are technically in the univese will show zero values for the age314* columns. This occurs in cases where a variable simply cannot be true of a child (e.g. the workInternetUser variable, as the CPS presumes children under 15 are not eligible to work), but the topic of interest is relevant to children (e.g. locations of Internet use).

3. work: Employment status is divided into "Employed," "Unemployed," and "NILF" (Not in the Labor Force). These three categories reflect the official BLS definitions used in official labor force statistics. Note that employment status is only recorded in the CPS for individuals ages 15 and older. As a result, children are excluded from the universe when calculating statistics by work status, even if they are otherwise considered part of the universe for the variable of interest.

4. income: The income category represents annual family income, rather than just an individual person's income. It is divided into five ranges: below $25K, $25K-49,999, $50K-74,999, $75K-99,999, and $100K or more. Statistics by income group are only available in this file for Supplements beginning in 2010; prior to 2010, family income range is available in public use datasets, but is not directly comparable to newer datasets due to the 2010 introduction of the practice of allocating "don't know," "refused," and other responses that result in missing data. Prior to 2010, family income is unkown for approximately 20 percent of persons, while in 2010 the Census Bureau began imputing likely income ranges to replace missing data.

5. education: Educational attainment is divided into "No Diploma," "High School Grad," "Some College," and "College Grad." High school graduates are considered to include GED completers, and those with some college include community college attendees (and graduates) and those who have attended certain postsecondary vocational or technical schools--in other words, it signifies additional education beyond high school, but short of attaining a bachelor's degree or equivilent. Note that educational attainment is only recorded in the CPS for individuals ages 15 and older. As a result, children are excluded from the universe when calculating statistics by education, even if they are otherwise considered part of the universe for the variable of interest.

6. sex: "Male" and "Female" are the two groups in this category. The CPS does not currently provide response options for intersex individuals.

7. race: This category includes "White," "Black," "Hispanic," "Asian," "Am Indian," and "Other" groups. The CPS asks about Hispanic origin separately from racial identification; as a result, all persons identifying as Hispanic are in the Hispanic group, regardless of how else they identify. Furthermore, all non-Hispanic persons identifying with two or more races are tallied in the "Other" group (along with other less-prevelant responses). The Am Indian group includes both American Indians and Alaska Natives.

8. disability: Disability status is divided into "No" and "Yes" groups, indicating whether the person was identified as having a disability. Disabilities screened for in the CPS include hearing impairment, vision impairment (not sufficiently correctable by glasses), cognitive difficulties arising from physical, mental, or emotional conditions, serious difficulty walking or climbing stairs, difficulty dressing or bathing, and difficulties performing errands due to physical, mental, or emotional conditions. The Census Bureau began collecting data on disability status in June 2008; accordingly, this category is unavailable in Supplements prior to that date. Note that disability status is only recorded in the CPS for individuals ages 15 and older. As a result, children are excluded from the universe when calculating statistics by disability status, even if they are otherwise considered part of the universe for the variable of interest.

9. metro: Metropolitan status is divided into "No," "Yes," and "Unkown," reflecting information in the dataset about the household's location. A household located within a metropolitan statistical area is assigned to the Yes group, and those outside such areas are assigned to No. However, due to the risk of de-anonymization, the metropolitan area status of certain households is unidentified in public use datasets. In those cases, the Census Bureau has determined that revealing this geographic information poses a disclosure risk. Such households are tallied in the Unknown group.

10. scChldHome:

The Low Income Housing Tax Credit (LIHTC) is a tax incentive intended to increase the availability of low income housing. Section 42 provides an income tax credit to owners of newly constructed or substantially rehabilitated low-income rental housing projects. The dollar amount of the LIHTC available for allocation by each state (the "credit ceiling") is limited by population. Each state is allocated credit based on $1.25 per resident. States may carry forward unused or returned credit derived from the credit ceiling for one year; if not used by then, credit goes into a national pool to be allocated to states as additional credit. State and local housing agencies allocate the state's credit ceiling among low-income housing buildings whose owners have applied for the credit. The LIHTC reduces income tax liability. It is taken annually for a term of ten years and is intended to yield a present value of either (1) 70 percent of the "qualified basis" for new construction or rehabilitation that are not federally subsidized (i.e., financed with tax-exempt bonds or below-market federal loans), or (2) 30 percent of the qualified basis for the cost of acquiring certain existing projects or projects that are federally subsidized. The actual credit rates are adjusted monthly for projects placed in service after 1987. The qualified basis represents the product of the "applicable fraction" of the building and the "eligible basis" of the building. The applicable fraction is based on the number of low income units in the building as a percentage of the total number of units, or based on the floor space of low income units as a percentage of the total floor space of residential units in the building. The eligible basis is the adjusted basis attributable to acquisition, rehabilitation, or new construction costs (depending on the type of LIHTC involved). In the case of buildings located in designated Qualified Census Tracts or designated Difficult Development Areas (DDA), eligible basis can be increased up to 130 percent of what it would otherwise be. This means that the available credit also can be increased by up to 30 percent. For example, if the 70 percent credit is available, it effectively could be increased up to 91 percent. There is a limit on the number of Qualified Census Tracts in any Metropolitan Statistical Area (MSA) or Primary Metropolitan Statistical Area (PMSA) that may be designated to receive an increase in eligible basis: all of the designated census tracts within a given MSA/PMSA may not together contain more than 20 percent of the total population of the MSA/PMSA. For purposes of HUD designations of Qualified Census Tracts, all non-metropolitan areas in a state are treated as if they constituted a single metropolitan area.To learn more, go to: https://www.huduser.org/portal/datasets/qct.htmlPurposeTo be used on the City of Tucson - Water Department's 2022 QCT Dashboard.Dataset ClassificationLevel 1 - Public, Not Proactively Released Known UsesCity of Tucson - Water Department's 2022 QCT DashboardKnown ErrorsUnknownContactInformation Technology DepartmentIT_GIS@tucsonaz.govUpdate FrequencyAnnually

The datasets are split by census block, cities, counties, districts, provinces, and states. The typical dataset includes the below fields.

Column numbers, Data attribute, Description 1, device_id, hashed anonymized unique id per moving device 2, origin_geoid, geohash id of the origin grid cell 3, destination_geoid, geohash id of the destination grid cell 4, origin_lat, origin latitude with 4-to-5 decimal precision 5, origin_long, origin longitude with 4-to-5 decimal precision 6, destination_lat, destination latitude with 5-to-6 decimal precision 7, destination_lon, destination longitude with 5-to-6 decimal precision 8, start_timestamp, start timestamp / local time 9, end_timestamp, end timestamp / local time 10, origin_shape_zone, customer provided origin shape id, zone or census block id 11, destination_shape_zone, customer provided destination shape id, zone or census block id 12, trip_distance, inferred distance traveled in meters, as the crow flies 13, trip_duration, inferred duration of the trip in seconds 14, trip_speed, inferred speed of the trip in meters per second 15, hour_of_day, hour of day of trip start (0-23) 16, time_period, time period of trip start (morning, afternoon, evening, night) 17, day_of_week, day of week of trip start(mon, tue, wed, thu, fri, sat, sun) 18, year, year of trip start 19, iso_week, iso week of the trip 20, iso_week_start_date, start date of the iso week 21, iso_week_end_date, end date of the iso week 22, travel_mode, mode of travel (walking, driving, bicycling, etc) 23, trip_event, trip or segment events (start, route, end, start-end) 24, trip_id, trip identifier (unique for each batch of results) 25, origin_city_block_id, census block id for the trip origin point 26, destination_city_block_id, census block id for the trip destination point 27, origin_city_block_name, census block name for the trip origin point 28, destination_city_block_name, census block name for the trip destination point 29, trip_scaled_ratio, ratio used to scale up each trip, for example, a trip_scaled_ratio value of 10 means that 1 original trip was scaled up to 10 trips 30, route_geojson, geojson line representing trip route trajectory or geometry

The datasets can be processed and enhanced to also include places, POI visitation patterns, hour-of-day patterns, weekday patterns, weekend patterns, dwell time inferences, and macro movement trends.

The dataset is delivered as gzipped CSV archive files that are uploaded to your AWS s3 bucket upon request.

Related article: Bergroth, C., Järv, O., Tenkanen, H., Manninen, M., Toivonen, T., 2022. A 24-hour population distribution dataset based on mobile phone data from Helsinki Metropolitan Area, Finland. Scientific Data 9, 39.

In this dataset:

We present temporally dynamic population distribution data from the Helsinki Metropolitan Area, Finland, at the level of 250 m by 250 m statistical grid cells. Three hourly population distribution datasets are provided for regular workdays (Mon – Thu), Saturdays and Sundays. The data are based on aggregated mobile phone data collected by the biggest mobile network operator in Finland. Mobile phone data are assigned to statistical grid cells using an advanced dasymetric interpolation method based on ancillary data about land cover, buildings and a time use survey. The data were validated by comparing population register data from Statistics Finland for night-time hours and a daytime workplace registry. The resulting 24-hour population data can be used to reveal the temporal dynamics of the city and examine population variations relevant to for instance spatial accessibility analyses, crisis management and planning.

Please cite this dataset as:

Bergroth, C., Järv, O., Tenkanen, H., Manninen, M., Toivonen, T., 2022. A 24-hour population distribution dataset based on mobile phone data from Helsinki Metropolitan Area, Finland. Scientific Data 9, 39. https://doi.org/10.1038/s41597-021-01113-4

Organization of data

The dataset is packaged into a single Zipfile Helsinki_dynpop_matrix.zip which contains following files:

HMA_Dynamic_population_24H_workdays.csv represents the dynamic population for average workday in the study area.

HMA_Dynamic_population_24H_sat.csv represents the dynamic population for average saturday in the study area.

HMA_Dynamic_population_24H_sun.csv represents the dynamic population for average sunday in the study area.

target_zones_grid250m_EPSG3067.geojson represents the statistical grid in ETRS89/ETRS-TM35FIN projection that can be used to visualize the data on a map using e.g. QGIS.

Column names

YKR_ID : a unique identifier for each statistical grid cell (n=13,231). The identifier is compatible with the statistical YKR grid cell data by Statistics Finland and Finnish Environment Institute.

H0, H1 ... H23 : Each field represents the proportional distribution of the total population in the study area between grid cells during a one-hour period. In total, 24 fields are formatted as “Hx”, where x stands for the hour of the day (values ranging from 0-23). For example, H0 stands for the first hour of the day: 00:00 - 00:59. The sum of all cell values for each field equals to 100 (i.e. 100% of total population for each one-hour period)

In order to visualize the data on a map, the result tables can be joined with the target_zones_grid250m_EPSG3067.geojson data. The data can be joined by using the field YKR_ID as a common key between the datasets.

License Creative Commons Attribution 4.0 International.

Related datasets

Järv, Olle; Tenkanen, Henrikki & Toivonen, Tuuli. (2017). Multi-temporal function-based dasymetric interpolation tool for mobile phone data. Zenodo. https://doi.org/10.5281/zenodo.252612

Tenkanen, Henrikki, & Toivonen, Tuuli. (2019). Helsinki Region Travel Time Matrix [Data set]. Zenodo. http://doi.org/10.5281/zenodo.3247564

The datasets are split by census block, cities, counties, districts, provinces, and states. The typical dataset includes the below fields.

Column numbers, Data attribute, Description 1, device_id, hashed anonymized unique id per moving device 2, origin_geoid, geohash id of the origin grid cell 3, destination_geoid, geohash id of the destination grid cell 4, origin_lat, origin latitude with 4-to-5 decimal precision 5, origin_long, origin longitude with 4-to-5 decimal precision 6, destination_lat, destination latitude with 5-to-6 decimal precision 7, destination_lon, destination longitude with 5-to-6 decimal precision 8, start_timestamp, start timestamp / local time 9, end_timestamp, end timestamp / local time 10, origin_shape_zone, customer provided origin shape id, zone or census block id 11, destination_shape_zone, customer provided destination shape id, zone or census block id 12, trip_distance, inferred distance traveled in meters, as the crow flies 13, trip_duration, inferred duration of the trip in seconds 14, trip_speed, inferred speed of the trip in meters per second 15, hour_of_day, hour of day of trip start (0-23) 16, time_period, time period of trip start (morning, afternoon, evening, night) 17, day_of_week, day of week of trip start(mon, tue, wed, thu, fri, sat, sun) 18, year, year of trip start 19, iso_week, iso week of the trip 20, iso_week_start_date, start date of the iso week 21, iso_week_end_date, end date of the iso week 22, travel_mode, mode of travel (walking, driving, bicycling, etc) 23, trip_event, trip or segment events (start, route, end, start-end) 24, trip_id, trip identifier (unique for each batch of results) 25, origin_city_block_id, census block id for the trip origin point 26, destination_city_block_id, census block id for the trip destination point 27, origin_city_block_name, census block name for the trip origin point 28, destination_city_block_name, census block name for the trip destination point 29, trip_scaled_ratio, ratio used to scale up each trip, for example, a trip_scaled_ratio value of 10 means that 1 original trip was scaled up to 10 trips 30, route_geojson, geojson line representing trip route trajectory or geometry

The datasets can be processed and enhanced to also include places, POI visitation patterns, hour-of-day patterns, weekday patterns, weekend patterns, dwell time inferences, and macro movement trends.

The dataset is delivered as gzipped CSV archive files that are uploaded to your AWS s3 bucket upon request.

The NHGIS is a National Institutes of Health and National Science Foundation-sponsored project to create a digital spatial-temporal database of all available historical US aggregate census materials. The available shapefiles on the NHGIS site represent version 2.0 of historical US state/territory boundary files for the 1790 to 2010 decennial censuses and American Community Survey releases. 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 Census 2000 blocks nest within every other Census 2000 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 data set contains vector polygons depicting locations for aquaculture, essential habitats, and water intakes; and vector points depicting locations for aquaculture, artificial reefs, recreational fishing, repeated measurement sites, and water intakes found i in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions. Polygons in the SOCECON feature data set may overlap where an area is associated with more than one agency or feature type. As an example, multiple parks may fall within a county boundary, which may itself fall within a larger polygon depicting the jurisdiction of an Army Corps of Engineers region. As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. The entirety of the NY/NJ Metro Area, Hudson River, and South Long Island Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE Points, Lines; POLITICAL-JURISDICTIONAL Polygons, Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Polygons, Points, Lines; and NATURAL HAZARD Polygons.

2023 Functional Urban Area update

For the 2023 FUA, there have been minor updates from the 2018 FUAs to align with changes to urban rural (UR) boundaries and statistical area 1 (SA1) composition. FUA 2023 is still based on the analysis of 2018 Census of Population and Dwellings commuting data. The Wanaka urban area, whose population has grown to be more than 10,000 based on population estimates, has been reclassified to a medium urban area in the 2023 UR and a medium regional centre in the FUA type.

Description

This dataset is the definitive version of the Functional Urban Area boundaries as at 1 January 2023, as defined by Stats NZ.

The functional urban area (FUA) classification identifies small urban areas and rural areas that are integrated with major, large, and medium urban areas to create FUAs. In 2023, there are 53 FUAs,excluding ‘land area outside functional urban area’ (9001) and ‘water area outside functional urban area’ (9002). The FUA classificationuses the urban rural (UR) geography to demarcate urban areas, and statistical area 1 areas(SA1s) to demarcate surrounding hinterland (the commuting zone) within FUAs, and rural and water areas outside FUAs.

FUAs represent a populated urban core/s and its commuting zone. Workplace address and usual residence address data from the 2018 Census of Population and Dwellings were used to identify satellite urban areas (1,000–4,999 residents), rural settlements and other rural SA1s from which at least 40 percent of workers commuted to urban areas with more than 5,000 residents.

FUA numbering and naming

The FUA classification identifies FUAs by the name of the most highly populated urban area it contains, for example, the Christchurch FUA includes the Christchurch urban core and Rangiora, Kaiapoi, and Rolleston secondary urban cores. There is one exception to the naming rule. The Paraparaumu-Waikanae-Paekakariki conurbation and surrounding hinterland is named Kapiti Coast.

The FUA classification has a two-level hierarchical structure, joined together to create each FUA code. Level 1 is classified by FUA type (TFUA) a one-digit code and level 2, which has three-digit codes numbered approximately north to south. Some examples are: 1001 Auckland, 2001 Whangārei, 3001 Cambridge, and 4001 Kaitāia.

FUA type (TFUA)

FUAs are further categorised by population size. The urban core’s population rather than the entire FUA’s population is used to maintain consistency between the descriptions of UR urban area and FUA type. The categories are, by code:

1 Metropolitan area – more than 100,000 residents living in the urban core,

2 Large regional centre – urban core population 30,000–99,999,

3 Medium regional centre – urban core population 10,000–29,999,

4 Small regional centre – urban core population 5,000–9,999, and,

9 Area outside functional urban area.

The Greymouth urban area population is less than 10,000 but is classified as a medium regional centre, consistent with its treatment as a medium urban area in the UA classification.

To differentiate from the UR classification, when referring to FUAs by name, their FUA type should also be mentioned, for example, Christchurch metropolitan area, Whangarei regional centre.

FUA indicator (IFUA)

The IFUA classifies UR2023 urban areas and rural SA1s according to their character within their FUA. The indicators, with their codes in brackets, are:

• urban area within functional urban area – urban core (101), secondary urban core (102), satellite urban area (103),

• rural area within functional urban area – hinterland (201),

• area outside functional urban area – land area outside functional urban area (901), water area outside functional urban area (902).

​

Further information on the urban rural indicator is available on the Stats NZ classification tool Ariā.

For more information please refer to the Statistical standard for geographic areas 2023.

​

Generalised version

This generalised version has been simplified for rapid drawing and is designed for thematic or web mapping purposes.

​

Macrons

Names are provided with and without tohutō/macrons. The column name for those without macrons is suffixed ‘ascii’.

​

Digital data

Digital boundary data became freely available on 1 July 2007.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable. For a deep dive into the data model including every specific metric, see the ACS 2017-2021 Data Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e21Estimate from 2017-21 ACS_m21Margin of Error from 2017-21 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_21Change, 2010-21 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLine (buffer)BeltLine Study (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Planning Unit STV (3 NPUs merged to a single geographic unit within City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)City of Atlanta Neighborhood Statistical Areas E02E06 (2 NSAs merged to single geographic unit within City of Atlanta)County (statewide)Georgia House (statewide)Georgia Senate (statewide)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)SPARCC = Strong, Prosperous And Resilient Communities ChallengeState of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)WFF = Westside Future Fund (subarea of City of Atlanta)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2017-2021). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2017-2021Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://garc.maps.arcgis.com/sharing/rest/content/items/34b9adfdcc294788ba9c70bf433bd4c1/data

Abstract

The Quarterly Labour Force Survey (QLFS) is a household-based sample survey conducted by Statistics South Africa (StatsSA). It collects data on the labour market activities of individuals aged 15 years or older who live in South Africa. Since 2008, StatsSA have produced an annual dataset based on the QLFS data, "Labour Market Dynamics in South Africa". The dataset is constructed using data from all four QLFS datasets in the year. The dataset also includes a number of variables (including income) that are not available in any of the QLFS datasets from 2010.

Geographic coverage

National coverage

Analysis unit

Individuals

Universe

The QLFS sample covers the non-institutional population except for those in workers' hostels. However, persons living in private dwelling units within institutions are enumerated. For example, within a school compound, one would enumerate the schoolmaster's house and teachers' accommodation because these are private dwellings. Students living in a dormitory on the school compound would, however, be excluded.

Kind of data

Sample survey data [ssd]

Sampling procedure

The Quarterly Labour Force Survey (QLFS) uses a master sample frame which has been developed as a general-purpose household survey frame that can be used by all other Stats SA household surveys that have reasonably compatible design requirement as the QLFS. The 2013 master sample is based on information collected during the 2011 population Census conducted by Stats SA. In preparation for Census 2011, the country was divided into 103 576 enumeration areas (EAs). The census EAs, together with the auxiliary information for the EAs were used as the frame units or building blocks for the formation of primary sampling units (PSUs) for the master sample since they covered the entire country and had other information that is crucial for stratification and creation of PSUs. There are 3 324 primary sampling units (PSUs) in the master sample with an expected sample of approximately 33 000 dwelling units (DUs). The number of PSUs in the current master sample (3 324) reflects an 8,0% increase in the size of the master sample compared to the previous (2007) master sample (which had 3 080 PSUs). The larger master sample of PSUs was selected to improve the precision (smaller CVs) of the QLFS estimates.

The master sample is designed to be representative at provincial level and within provinces at metro/non-metro levels. Within the metros, the sample is further distributed by geographical type. The three geography types area: urban, tribal and farms. This implies, for example, that within a metropolitan area, the sample is representative of the different geography types that may exist within that metro. It is divided equally into four sub-groups or panels called rotation groups. The rotation groups are designed in such a way that each of these groups has the same distribution pattern as that which is observed in the whole sample. They are numbered from one (1) to four (4) and these numbers also correspond to the quarters of the year in which the sample will be rotated for the particular group.

There are a number of aspects in which the 2013 version of the master sample differs from the 2007 version. In particular, the number of primary sample units increased. Mining strata were also introduced which serves to improve the efficiency of estimates relating to employment in mining. The number of geo-types was reduced from 4 to 3 while the new master sample allows for the publication of estimates of the labour market at metro level. The master sample was also adjusted Given the change in the provincial distribution of the South African population between 2001 and 2011. There was also an 8% increase in the sample size of the master sample of PSUs to improve the precision of the QLFS estimates. The sample size increased most notable in Gauteng, the Eastern Cape and KwaZulu-Natal. For more details on the differences between the two master samples please consult the section 8 (technical notes) of the QLFS 2015 Q3 release document (P0211).

From the master sample frame, the QLFS takes draws employing a stratified two-stage design with probability proportional to size (PPS) sampling of PSUs in the first stage, and sampling of dwelling units (DUs) with systematic sampling in the second stage. The primary stratification occurred at provincial, metro/non-metro, mining and geography type while the secondary strata were created within the primary strata based on the demographic and socio-economic characteristics of the population.

For each quarter of the QLFS, a ¼ of the sampled dwellings is rotated out of the sample. These dwellings are replaced by new dwellings from the same PSU or the next PSU on the list. Thus, sampled dwellings are expected to remain in the sample for four consecutive quarters. It should be noted that the sampling unit is the dwelling, and the unit of observation is the household. Therefore, if a household moves out of a dwelling after being in the sample for, two quarters and a new household moves in, the new household will be enumerated for the next two quarters. If no household moves into the sampled dwelling, the dwelling will be classified as vacant (or unoccupied).

Mode of data collection

Face-to-face [f2f]

This dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties will polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. The primary example of this is the condominium. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

Polygon and point counts for each county are as follows (based on the October 2008 dataset unless otherwise noted):

polygons / points
Anoka 129139 / 129138
Carver 38134 / 38133
Dakota 135925 / 150294
Hennepin 422976 / 446623
Ramsey 149169 / 168233
Scott 55191 / 55191
Washington 98915 / 103915

This is a MetroGIS Regionally Endorsed dataset.

Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset.

A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2008 document.

Additional information may be available in the individual metadata for each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata.

Anoka = http://www.anokacounty.us/315/GIS

Caver = http://www.co.carver.mn.us/GIS

Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx

Hennepin: http://www.hennepin.us/gisopendata

Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data

Scott = http://www.scottcountymn.gov/1183/GIS-Data-and-Maps

Washington = http://www.co.washington.mn.us/index.aspx?NID=1606