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

This data layer is an element of the Oregon GIS Framework. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

Address ranges describe a label given to a unique collection of addresses that fall along a road or path. Address ranges provide a way of locating homes and businesses based on their street addresses when no other location information is available.Using a house number, street name, street side and ZIP code, address ranges can locate the address to the geographic area associated to that side of the street. Once geocoded, the U.S. Census Bureau can assign the address to a field assignment area or tabulate the data for that address. In addition, academics, researchers, professionals and government agencies outside of the Census Bureau use MAF/TIGER address ranges to transform tabular addresses into geographical datasets for decision-making and analytical purposes.Address ranges must be unique to geocode addresses to the correct location and avoid geocoding conflicts. Multiple elements in MAF/TIGER are required to make an address range unique including street names, address house numbers and street feature geometries, such as street centerlines. The address range data model is designed to maximize geocoding matches with their correct geographic areas in MAF/TIGER by allowing an unlimited number of address range-to-street feature relationships.The Census Bureau’s Geography Division devises numerous operations and processes to build and maintain high quality address ranges so that:Address ranges accurately describe the location of addresses on the ground.Address All possible city-style addresses are geocoded.Address ranges can handle all known address and street name variations.Address ranges conform with current U.S. Postal Service ZIP codes.Address ranges are reliable and free from conflicts.Automated software continually updates existing address ranges, builds new address ranges and corrects errors. An automated operation links address location points and tabular address information to street feature edges with matching street names in the same block to build and modify address ranges.Many business rules and legal value checks ensure quality address range data in MAF/TIGER. For example, business rules prevent adding or modifying address ranges that overlap another house number range with the same street name and ZIP code. Legal value checks verify that address ranges include mandatory attribute information, valid data types and valid character values.Some of the TIGER/Line products for the public include address ranges and give the public the ability to geocode addresses to MAF/TIGER address ranges for the user’s own purpose. The address range files are available for the nation, Puerto Rico and the U.S. Island Areas at the county level. TIGER/Line files require geographic information system (GIS) software to use.The Census Bureau Geocoder Service is a web service provided to the public. The service accepts up to 1,000 input addresses and, based on Census address ranges, returns the interpolated geocoded location and census geographies. Users can access the service a web interface or a representational state transfer (REST) application program interface (API) web service. See the Census Geocoder for more information on this process. Directions on how to use the Census Geocoder available: Geocoding Services Web Application Programming Interface (API)Download: https://www2.census.gov/geo/tiger/TGRGDB24/tlgdb_2024_a_us_addr.gdb.zip

Context

There are a number of Kaggle datasets that provide spatial data around New York City. For many of these, it may be quite interesting to relate the data to the demographic and economic characteristics of nearby neighborhoods. I hope this data set will allow for making these comparisons without too much difficulty.

Exploring the data and making maps could be quite interesting as well.

Content

This dataset contains two CSV files:

1. nyc_census_tracts.csv

   This file contains a selection of census data taken from the ACS DP03 and DP05 tables. Things like total population, racial/ethnic demographic information, employment and commuting characteristics, and more are contained here. There is a great deal of additional data in the raw tables retrieved from the US Census Bureau website, so I could easily add more fields if there is enough interest.

   I obtained data for individual census tracts, which typically contain several thousand residents.

2. census_block_loc.csv

   For this file, I used an online FCC census block lookup tool to retrieve the census block code for a 200 x 200 grid containing New York City and a bit of the surrounding area. This file contains the coordinates and associated census block codes along
   with the state and county names to make things a bit more readable to users.

   Each census tract is split into a number of blocks, so one must extract the census tract code from the block code.

Acknowledgements

The data here was taken from the American Community Survey 2015 5-year estimates (https://factfinder.census.gov/faces/nav/jsf/pages/index.xhtml).

The census block coordinate data was taken from the FCC Census Block Conversions API (https://www.fcc.gov/general/census-block-conversions-api)

As public data from the US government, this is not subject to copyright within the US and should be considered public domain.

Census Year 1930 Census Tracts. The dataset contains polygons representing CY 1930 census tracts, created as part of the D.C. Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Census tracts were identified from maps provided by the U.S. Census Bureau and the D.C. Office of Planning. The tract polygons were created by selecting street arcs from the WGIS planimetric street centerlines. Where necessary, polygons were also heads-up digitized from 1995/1999 orthophotographs. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

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.

Census Tracts from the 2020 US Census for New York City clipped to the shoreline. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. Because some census tracts are under water not all census tracts are contained in this file, only census tracts that are partially or totally located on land have been mapped in this file.

All previously released versions of this data are available at the DCP Website: BYTES of the BIG APPLE.

Note: For information on data collection, confidentiality protection, nonsampling error, and definitions, see the 2020 Island Areas Censuses Technical Documentation..Due to operational changes for military installation enumeration, the 2020 Census of Guam data tables reporting housing, social, and economic characteristics do not include housing units or populations living on Guam's U.S. military installations in the table universe. As a result, impacted 2020 data tables should not be compared to 2010 and other past census data tables reporting the same characteristics. The Census Bureau advises data users to verify table universes are the same before comparing data across census years. For more information about operational changes and the impacts on Guam's data products, see the 2020 Island Areas Censuses Technical Documentation..Due to COVID-19 restrictions impacting data collection for the 2020 Census of Guam, data tables reporting social and economic characteristics do not include the group quarters population in the table universe. As a result, impacted 2020 data tables should not be compared to 2010 and other past census data tables reporting the same characteristics. The Census Bureau advises data users to verify table universes are the same before comparing data across census years. For more information about data collection limitations and the impacts on Guam's data products, see the 2020 Island Areas Censuses Technical Documentation..Note: Industry codes are based on 4-digit codes from the North American Industry Classification System 2017. 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..Explanation of Symbols: 1.An "-" means the statistic could not be computed because there were an insufficient number of observations. 2. An "-" following a median estimate means the median falls in the lowest interval of an open-ended distribution.3. An "+" following a median estimate means the median falls in the upper interval of an open-ended distribution.4. An "N" means data are not displayed for the selected geographic area due to concerns with statistical reliability or an insufficient number of cases.5. An "(X)" means not applicable..Source: U.S. Census Bureau, 2020 Census, Guam.

The U.S. Constitution mandates that the federal government count all persons living in the United States every ten years. The census is critical to states because its results are used to reapportion seats in the U.S. House of Representatives; guide redistricting; and form the basis for allocating federal funds, such as those used for schools, health services, child care, highways, and emergency services.

In response to long-standing concerns about the accuracy of census data and about a possible undercount, a group of researchers conducted the California Neighborhoods Count (CNC) — the first-ever independent, survey-based enumeration to directly evaluate the accuracy of the U.S. Census Bureau's population totals for a subset of California census blocks.

This 2020 research was intended to produce parallel estimates of the 2020 Census population and housing unit totals at the census block level, employing the same items as the census and using enhanced data collection strategies and exploration of imputation methods. Although the CNC was intended to largely replicate census data collection processes, there were a few methodological differences: For example, much of the address canvassing for the 2020 Census was done in-office, whereas the CNC team undertook a complete in-person address-listing operation that included interviews with residents and door-to-door verification of each structure.

In this report, the researchers detail their methodology and present the enumeration results. They compare the 2020 Census counts with the CNC estimates, describe limitations of their data collection effort, and offer considerations for future data collection.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2010 Census.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

From https://www.census.gov/hhes/commuting/data/jtw_workerflow.html as of March 29, 2017:These files were compiled from STF-S-5, Census of Population 1990: Number of Workers by County of Residence by County of Work [http://doi.org/10.3886/ICPSR06123.v1]. For the six New England States (CT, ME, MA, NH, RI, VT), data are provided for Minor Civil Divisions (MCDs) instead of for counties.For any State, or for the entire nation, there are four files to choose from, depending on the sort order and format you may find most useful.The sort order refers to whether the county of residence or the county of work is the main focus. If you are most interested in the number of people who live in a county, and want to know where they go to work, you should download one of the files sorted by county of residence. These files will show you all the work destinations for people who live in each county.On the other hand, if you are most interested in the people who work in a county, and want to know where they come from, you should download one of the files sorted by county of work. These files will show you all the origins for people who work in each county.The files have also been created in two formats: DBF and ASCII. The DBF files are directly accessible by a number of database, spreadsheet, and geographic information system programs. The ASCII files are more general purpose and may be imported into many software applications.Record Layouts Record Layout for ASCII (Plain Text) Files [TXT - 2K] coxcoasc.txtRecord Layout for DBF Files [TXT - 2K]coxcodbf.txtThe link to the FIPS Lookup File [ed.: absent when archived] can be used to access a list of FIPS State codes and the corresponding State names. In the county-to-county worker flow files, only the State codes are used. The files do not contain State names.United States county-to-county worker flow files: 1990 Residence County USresco.txt USresco.zip USresco.dbf USresco.dbf.zipWork County USwrkco.txt USwrkco.zip USwrkco.dbf USwrkco.dbf.zip [Ed.: the original site also had state files. These were not downloaded, as they simply split the United States file into smaller chunks.]

Abstract

The 2010 Population and Housing Census was Conducted between 11-17 November 2010. Over 750,000 household forms were completed by over 12,000 enumerators. More than 30,000 persons were directly involved in census conducting. The Population and Housing Census is the biggest event organized by the National Statistical Office. The unique feature of the Census is that it covers a wide range of entities starting from the primary unit of the local government up to the highest levels of the government as well as all citizens and conducted with the highest levels of organization. For the 2010 Population and Housing Census, the management team to coordinate the preparatory work was established, a detailed work plan was prepared and the plan was successfully implemented. The preliminary condition for the successful conduct of the Census was the development of a detailed plan. The well thought-out, step by step plan and carefully evidenced estimation of the expenditure and expected results were crucial for the successful Census. Every stage of the Census including preparation, training, enumeration, data processing, analysis, evaluation and dissemination of the results to users should be reflected in the Census Plan.

Geographic coverage

National

Analysis unit

• Household;
• Indivudual.

Kind of data

Census/enumeration data [cen]

Mode of data collection

Face-to-face [f2f]

Cleaning operations

Data Processing System

The introduction of internet technology and GIS in the 2010 Population and Housing Census has made the census more technically advanced than the previous ones. Compared to the data processing of the 2000 Population and Housing Census the techniques and technological abilities of the NSO have advanced. The central office - National Statistical Office has used an internal network with 1000 Mbps speed, an independent internet line with 2048 Kbps speed and server computers with special equipments to ensure the reliable function of internal and external networks and confidentiality. The Law on Statistics, the Law on Population and Housing Census, the guidelines of the safety of statistical information systems and policies, the provisional guidelines on the use of census and survey raw data by the users, the guidelines on receiving, entering and validating census data have created a legal basis for census data processing.

The data-entry network was set up separately from the network of the organization in order to ensure the safety and confidentiality of the data. The network was organized by using the windows platform and managed by a separate domain controller. Computers where the census data will be entered were linked to this server computer and a safety devise was set up to protect data loss and fixing. Data backup was done twice daily at 15:10 hour and 22:10 hour by auto archive and the full day archive was stored in tape at 23:00 hour everyday.

The essential resources of important equipments and tools were prepared in order to provide continuous function of all equipment, to be able to carry out urgent repairs when needed, and to return the equipment to normal function. The computer where the census data would be entered and other necessary equipment were purchased by the state budget. For the data processing, the latest packages of software programs (CSPro, SPSS) were used. Also, software programs for the computer assisted coding and checking were developed on NET within the network framework.

INTERNET CENSUS DATA PROCESSING

One of the specific features of the 2010 Population and Housing Census was e-enumeration of Mongolian citizens living abroad for longer period. The development of a web based software and a website, and other specific measures were taken in line with the coordination of the General Authority for State Registration, the National Data Centre, and the Central Intelligence Agency in relation to ensuring the confidentiality of data. Some difficulties were encountered in sharing information between government agencies and ensuring the safety and confidentiality of census data due to limited professional and organizational experience, also because it was the first attempt to enumerate its citizens online.

The main software to be used for online registration, getting permission to get login and filling in the census questionnaire online as well as receiving a reply was developed by the NSO using a symphony framework and the web service was provided by the National Data Centre. Due to the different technological conditions for citizens living and working abroad and the lack of certain levels of technological knowledge for some people the diplomatic representative offices from Mongolia in different countries printed out the online-census questionnaire and asked citizens to fill in and deliver them to the NSO in Mongolia. During the data processing stage these filled in questionnaires were key-entered into the system and checked against the main census database to avoid duplication.

CODING OF DATA, DATA-ENTRY AND VALIDATION

Additional 136 workers were contracted temporarily to complete the census data processing and disseminate the results to the users within a short period of time. Due to limited work spaces all of them were divided into six groups and worked in two shifts with equipments set up in three rooms and connected to the network. A total of six team leaders and 130 operators worked on data processing. The census questionnaires were checked by the ad hoc bureau staff at the respective levels and submitted to the NSO according to the intended schedule.

These organizational measures were taken to ensure continuity of the census data processing that included stages of receiving the census documents, coding the questionnaire, key-entering into the system and validating the data. Coding was started on December 13, 2010 and the data-entry on January 7, 2011. Data entering of the post-enumeration survey and verification were completed by April 16, 2011. Data checking and validation started on April 18, 2011 and was completed on May 5, 2011. The automatic editing and imputation based on scripts written by the PHCB staff was completed on May 10, 2011 and the results tabulation was started.

Note: For information on data collection, confidentiality protection, nonsampling error, and definitions, see the 2020 Island Areas Censuses Technical Documentation..Due to operational changes for military installation enumeration, the 2020 Census of Guam data tables reporting housing, social, and economic characteristics do not include housing units or populations living on Guam's U.S. military installations in the table universe. As a result, impacted 2020 data tables should not be compared to 2010 and other past census data tables reporting the same characteristics. The Census Bureau advises data users to verify table universes are the same before comparing data across census years. For more information about operational changes and the impacts on Guam's data products, see the 2020 Island Areas Censuses Technical Documentation..Due to COVID-19 restrictions impacting data collection for the 2020 Census of Guam, data tables reporting social and economic characteristics do not include the group quarters population in the table universe. As a result, impacted 2020 data tables should not be compared to 2010 and other past census data tables reporting the same characteristics. The Census Bureau advises data users to verify table universes are the same before comparing data across census years. For more information about data collection limitations and the impacts on Guam's data products, see the 2020 Island Areas Censuses Technical Documentation..Note: Industry codes are based on 4-digit codes from the North American Industry Classification System 2017. 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..Explanation of Symbols: 1.An "-" means the statistic could not be computed because there were an insufficient number of observations. 2. An "-" following a median estimate means the median falls in the lowest interval of an open-ended distribution.3. An "+" following a median estimate means the median falls in the upper interval of an open-ended distribution.4. An "N" means data are not displayed for the selected geographic area due to concerns with statistical reliability or an insufficient number of cases.5. An "(X)" means not applicable..Source: U.S. Census Bureau, 2020 Census, Guam.

This dataset represents all City of Bend permit applications from 1934 to present, including some historic permits prior to 1993. Data is derived from the City of Bend permitting software and includes all permit records available. Please note data is updated weekly and subject to change as applications are received and reviewed.Attribute Information: Field Name Description

ObjectID For internal use.

GNMasterProjectID For internal use.

GNCommonID For internal use.

PR_RecordID For internal use.

ApplicationNumber The tracking number for this application in The City of Bend permitting system.

ApplicationDate The date the application was submitted for review.

IssueDate The date the City of Bend issued the permit. If there is an Application Date but no Issue Date, this generally means the application is still under review.

DateFinaled The date the application had all its inspections completed. If there is an Issue Date but not a Date Finaled, this generally means the application is still under construction.

SQFT The estimate square footage of the work being proposed. The estimated square footage (if any) is supplied by the applicant and not verified by the City.

Units The number of housing units that will be constructed. Please note units are not verified until permit issuance. Data is subject to change.

Affordable Housing Identifier for permits related to affordable housing projects.

Expedited Identifier for permits under expedited review.

OnSewer Identifier for permits on properties served by City sewer.

ProjectValuation The estimated project cost of the work being proposed based on the fair market value. The estimate cost (if any) represents the best available information and is subject to change.

OldAppType For internal use.

ApplicationType The application type code by category, such as new construction, demolition, renovation, addition, etc.

TypeDesc The application type description by category, such as new construction, demolition, renovation, addition, etc.

ApplicationStatus The current status code for the application. Updated nightly.

StatusDesc The current status description for the application. Updated nightly.

ApplicationDescription The application description.

BldgUse The building use code by category, such as single family dwelling, duplex, multifamily, commercial or industrial, etc.

UseDesc The building use description by category, such as single family dwelling, duplex, multifamily, commercial or industrial, etc.

BuildingCategory A description of whether the permit is for a residential or non-residential project.

OregonBuildingCodeApplied For internal use.

Proposed Land Use The proposed land use classificaton assoicated with all proposed and existing structures.

DeptCode The lead department managing the application review.

Department The lead department managing the application review.

Owner The owner of the property associated with this permit at the time of application.

CensusStructureCode The census structure code. Permits for new housing units are classified into US Census Bureau-defined classifications.

CensusStructureDesc The census structure description. Permits for new housing units are classified into US Census Bureau-defined classifications.

Address The site address for the application. Please note if a project includes multiple addresses, only one is visible in this field.

LOCID For internal use.

SITADDID For internal use.

TAXLOT The tax lot for the application. Please note if a project includes multiple tax lots, only one is visible in this field.

CENTERLINID For internal use.

LocationFinaled For internal use.

GlobalID For internal use.

InfoFinaled For internal use.

OverallStatus For internal use. For questions regarding planning applications, please visit The City of Bend Online Permit Center or call 541-388-5580. For questions related to the data please email GIS@bendoregon.gov.

This dataset contains model-based census tract estimates. PLACES covers the entire United States—50 states and the District of Columbia—at county, place, census tract, and ZIP Code Tabulation Area levels. It provides information uniformly on this large scale for local areas at four geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. PLACES was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. The dataset includes estimates for 40 measures: 12 for health outcomes, 7 for preventive services use, 4 for chronic disease-related health risk behaviors, 7 for disabilities, 3 for health status, and 7 for health-related social needs. These estimates can be used to identify emerging health problems and to help develop and carry out effective, targeted public health prevention activities. Because the small area model cannot detect effects due to local interventions, users are cautioned against using these estimates for program or policy evaluations. Data sources used to generate these model-based estimates are Behavioral Risk Factor Surveillance System (BRFSS) 2022 or 2021 data, Census Bureau 2020 population data, and American Community Survey 2018–2022 estimates. The 2024 release uses 2022 BRFSS data for 36 measures and 2021 BRFSS data for 4 measures (high blood pressure, high cholesterol, cholesterol screening, and taking medicine for high blood pressure control among those with high blood pressure) that the survey collects data on every other year. More information about the methodology can be found at www.cdc.gov/places.

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.

This is a series-level metadata record. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding adn Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Voting district is the generic name for geographic entities such as precincts, wards, and election districts established by State governments for the purpose of conducting elections. States participating in the 2020 redistricting program as part of Public Law 94-171 (1975) provided the Census Bureau with boundaries, codes, and names for their VTDs. Voting districts do not exist for all states since some states did not participate in the program or chose not to submit boundaries for some of, or their entire, state. Each VTD is identified by a 1- to 6-character alphanumeric census code that is unique within county. The code "ZZZZZZ" identifies a portion of the county for which no VTDs were identified.

Nonemployer Statistics is an annual series that provides statistics on U.S. businesses with no paid employees or payroll, are subject to federal income taxes, and have receipts of $1,000 or more ($1 or more for the Construction sector). This program is authorized by the United States Code, Titles 13 and 26. Also, the collection provides data for approximately 450 North American Industry Classification System (NAICS) industries at the national, state, county, metropolitan statistical area, and combined statistical area geography levels. The majority of NAICS industries are included with some exceptions as follows: crop and animal production; investment funds, trusts, and other financial vehicles; management of companies and enterprises; and public administration. Data are also presented by Legal Form of Organization (LFO) (U.S. and state only) as filed with the Internal Revenue Service (IRS). Most nonemployers are self-employed individuals operating unincorporated businesses (known as sole proprietorships), which may or may not be the owner's principal source of income. Nonemployers Statistics features nonemployers in several arts-related industries and occupations, including the following: Arts, entertainment, and recreation (NAICS Code 71) Performing arts companies Spectator sports Promoters of performing arts, sports, and similar events Independent artists, writers, and performers Museums, historical sites, and similar institutions Amusement parks and arcades Professional, scientific, and technical services (NAICS Code 54) Architectural services Landscape architectural services Photographic services Retail trade (NAICS Code 44-45) Sporting goods, hobby, and musical instrument stores Sewing, needlework, and piece goods stores Book stores Art dealers Nonemployer Statistics data originate from statistical information obtained through business income tax records that the Internal Revenue Service (IRS) provides to the Census Bureau. The data are processed through various automated and analytical review to eliminate employers from the tabulation, correct and complete data items, remove anomalies, and validate geography coding and industry classification. Prior to publication, the noise infusion method is applied to protect individual businesses from disclosure. Noise infusion was first applied to Nonemployer Statistics in 2005. Prior to 2005, data were suppressed using the complementary cell suppression method. For more information on the coverage and methods used in Nonemployer Statistics, refer to NES Methodology. The majority of all business establishments in the United States are nonemployers, yet these firms average less than 4 percent of all sales and receipts nationally. Due to their small economic impact, these firms are excluded from most other Census Bureau business statistics (the primary exception being the Survey of Business Owners). The Nonemployers Statistics series is the primary resource available to study the scope and activities of nonemployers at a detailed geographic level. For complementary statistics on the firms that do have paid employees, refer to the County Business Patterns. Additional sources of data on small businesses include the Economic Census, and the Statistics of U.S. Businesses. The annual Nonemployer Statistics data are available approximately 18 months after each reference year. Data for years since 2002 are published via comma-delimited format (csv) for spreadsheet or database use, and in the American FactFinder (AFF). For help accessing the data, please refer to the Data User Guide.