Minnesota Population Center2006/10/05Historic US Census Tract Boundaries, Hawaii Territory, 1940vector digital dataMinneapolis, MinnesotaMinnesota Population Center\\thalia.socsci.umn.edu\popgis\labpcs\conflation\shapefiles\packing\gisjoin_gisjoin2_feature_class\tract\us_tract_1940\HI_tract_1940.shpHI_tract_1940This boundary file contains historic census tract boundaries for which the U.S. Census Bureau tabulated data and was produced by the Minnesota Population Center as part of the National Historical Geographic Information System (NHGIS) project. The NHGIS is an National Science Foundation-sponsored project (Grant No. BCS0094908) to create a digital spatial-temporal database of all available historical US aggregate census materials. The available shapefiles on the NHGIS site represent version 1.0 of historical US census tract boundary files for the 1910-2000 censuses. These electronic census tract boundary files were created by referencing publicly available, printed U.S. Census Bureau maps and considerable care was taken during their production. TIGER/Line spatial features that corresponded to boundaries on these maps were used to construct proper historic boundaries. When a TIGER/Line features was not available, we digitized the historic boundary from a geo-referenced, scanned census map. The boundary files have been checked against currently available historical census aggregate data.These data are based upon work supported by the National Science Foundation under Grant No. BCS0094908 - in infrastructure grant provided for the social sciences. Its purpose is twofold. First, the NHGIS created and freely distributes a database incorporating all available aggregate census information for the United States between 1790 and 2000. The database contains information for a wide variety of statistical (blocks, block groups, census tracts, metropolitan statistical areas) and administrative units (places, minor civil divisions, counties, states). Second, the NHGIS produced and freely distributes boundary files for small areas (census tracts and counties) in the United States. Boundary files for tracts are available for the 1910-2000 censuses, and boundary files for counties are available for the 1790-2000 censuses.Census tracts are small, relatively permanent geographic entities within counties and contain between 2,500 and 8,000 residents. The Census Bureau helped create and tabulate aggregate data for census tracts for ten cities in 1910. The creation of the census tract was a joint effort between federal and local entities to create a set of small geographic entities based on both population and housing characteristics. It was the localities, not the federal government, that requested the special tabulations and used the data. Additional cities were tracted by the Bureau in later decades and in 1940 the Census Bureau adopted the census tract as an official enumeration unit. The US first experienced complete coverage of census tracts in 2000.
Prior to the year 2000, Block Numbering Areas (BNAs) were used for areas that did not meet the tract eligibility criteria for the Census Bureau. At the time of their official recognition in 1940, BNAs and census tracts did not have similar attribute information available. In 1990, however, the Census Bureau delineated the same basic attributes for both the census tract and the BNA. For this reason, BNAs are represented as census tracts in the datasets for 1990. Prior to 1990 only census tracts are represented.
Crews-on-vessels refer to military or merchant ship populations, not inhabitants of houseboats or marinas. In 1990 the Census Bureau chose to represent crews-on-vessels in their electronic boundary files. This decision differed from previous and later decades where the crews-on-vessels population was added to the nearby land census tracts with which the vessels was associated. In an attempt to provide consistency over time, crews-on-vessels were removed from all of the tract boundary files. Separate statewide point shapefiles have been created for 1970, 1980 and 1990 representing crews-on-vessels within the county in which the crews-on-vessels were located in that census year.enREQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.publication dateAs work is completed-178.341454-154.71974829.24303718.134225-2162877.975576230564.227708656110.4085071780356.806159Nonehistoricalcensus of population and housingtractscensus boundariescensus geographycensus datapopulationhousingNoneNoneAll persons are granted a limited license to use and distribute this documentation and the available data, subject to the use constraints listed below.This dataset was produced with an intended application at the city, county, metropolitan, or state/territory level. Appropriate uses include thematic mapping of census data and spatial analysis of census data. These unaltered data may be redistributed by a third party. If these data are altered or incorporated into another dataset, they are not to be redistributed without also: altering the name of the dataset, including a Content Standars for Digital Geospatial Metadata (FGDC-STD-001-1998) compliant metadata file that describes the dataset and reflects the alteration steps that makes the new dataset different from this one, and citing this dataset in the metadata as a source for the altered dataset using the source citation specified below. If these digital data are used in the production of a report or in the compilation of a standalone printed map, then this dataset is to be cited in the report or on the map using the source citation specified below. The following source citation should be used when citing this dataset: John S. Adams, William C. Block, Mark Lindberg, Robert McMaster, Steven Ruggles, and Wendy Thomas, National Historical Geographic Information System: Pre-release Version 0.1, Minneapolis: Minnesota Population Center, University of Minnesota, 2004. No fee may be charged for use or distribution. Publications and research reports based on the database must cite it appropriately. Users are requested to send a copy of any publications, research reports, or educational material making use of the data or documentation. Printed matter should be sent to: NHGIS Minnesota Population Center University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455Petra NobleMinnesota Population CenterResearch Fellowphysical address
50 Willey Hall
225 19th Ave S
MinneapolisMinnesota55455USA612-625-7375nhgis@pop.umn.eduMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.0.1324ShapefileAll attributes in this boundary file were checked against attributes in the available aggregate data to ensure accuracy and consistency. The boundary file may contain more or fewer tracts than the aggregate data file. Sources for the boundary files sometimes depicted tracts that were not listed in the aggregate data file. Sometimes, the aggregate data files contains records for tracts that are not mappable (e.g. crews-on-vessels tracts are denoted as points, tracts for which paper maps not longer exist).All spatial data have been reviewed to assure topological consistency and completeness. All polygons close and do not overlap. No voids exist within polygons. ArcGIS topology features classes were used to identify and fix topological errors (e.g., overlaps, voids, missing polygons) in the tract boundary datasets. The ArcGIS topology rules used to ensure logical consistency were 'Must not overlap' and 'Area Boundary must be Covered by Boundary of'.Version 1.0 of the tract boundary files contains census tracts. Most tracts, although not all, have a matching record in the aggregate data files. Tracts without a matching record contain"nodata" in its GISJOIN attribute. We will made those tracts because we had a geographic representation of it. Additionally, some records in the aggregate data files could not be mapped because they were not depicted on the paper maps or they represent crews-on-vessels tracts, which the Census Bureau denoted as points - NHGIS boundary files are only composed of polygon features. Version 1.0 boundary files have not been generalized, and tracts containing parts of the following bodies of water do not have historically accurate coastlines: the Great Lakes, Atlantic Ocean, Pacific Ocean, and the Gulf of Mexico. No tracts overlap, no voids exist between tracts, and any polygon belongs to one and only one tract. Every tract has a FIPS-like code (GISJOIN) that uniquely identifies it. The aggregate data file contains a matching code (GISJOIN) so that the files can be easily joined together.
This is a work in progress. A more detailed report will be provided with the final release. The beta version of the files are not generalized. Most counties that were tracted, in whole or in part, between 1910 and 2000 are available in beta format. Counties that include part of the following bodies of water: the Great Lakes, Atlantic Ocean, Gulf of Mexico, and the Pacific Ocean do not have accurate, historical coastlines.The horizontal positional accuracy of the source data (U.S. Census Bureau TIGER/Line 2000 files) can be found at http://www.census.gov/geo/www/tlmetadata/tl2kmeta.txt. To create historic county boundaries, we used existing TIGER lines whereever possible. When no TIGER line existed, we digitized new linework from scanned and rectified U.S. Census Bureau tract maps.U.S. Census Bureau19421940 census tracts [city, state]Washington D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau1952U.S. Census of population. Volume II Characteristics of populationWashington D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau1960U.S. Censuses of population and housing: 1960 census tracts. Final reportWashington D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau1972U.S. Census of population and housing: 1970 census tracts. Final reportWashington D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau19831980 Census of population and housing census tracts. Final report PHCWashington D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau19931990 census of population and housing. Population and housing characteristics for census tracts and block numbering areas. Final reportWashington D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau1994TIGER/Line 1992: the coast-to-coast digital map databaseWashington D.C.U.S. Census Bureau, Data User Services DivisionvariousdigitalU.S. Census Bureau2000Census 2000 TIGER/Line files [machine-readable data files].Washington D.C.U.S. Government Printing OfficevariousonlineU.S. Census Bureau20012000 Summary File 1 (SF1)Washington D.C.U.S. Government Printing Officehttp://factfinder.census.govdigital tape mediaCities Census Committee, Inc.1932Population of the City of New York, 1890-1930New YorkCities Census Committee, Inc.paperHoward Whipple Green1927An analysis of population data by census tracts with location index, Cleveland and vicinityCleveland, OHCleveland Health CouncilpaperU.S. Bureau of the Census1971U.S. Census of Housing: 1970. Block StatisticsWashington, D.C.U.S. Government Printing OfficepaperU.S. Bureau of the Census1961U.S. Census of Housing: 1960. Volume III, City Blocks. Series HC(3)Washington, D.C.U.S. Government Printing OfficepaperU.S. Bureau of the Census1952U.S. Census fo Housing: 1950. Volume V, Block StatisticsWashington, D.C.U.S. Government Printing OfficepaperU.S. Bureau of the Census19821980 Census of Population and Housing. Block StatisticsWashington, D.C.U.S. Government Printing OfficemicroficheThe U.S. Census Bureau's Census 2000 TIGER/Line files were downloaded from the Internet (http://www.census.gov/geo/www/tiger/tiger2k/tgr2000.html).Obtained 1992 TIGER/Line files on CD-ROM.Using a custom Arc Macro Language (AML) script, staff converted the TIGER/Line files into Arc/Info coverages. The AML then projected the coverages into the proper UTM zone, created regions for the 1990 and 2000 census tracts and water, and extracted the 1980 census tracts from the 1992 TIGER/Line files. The end product, for editing purposes, was a polygon base map consisting of the boundary of a single county, the 1990 and 2000 tract boundaries for that county, and a coverage containing the 1980 census tracts from the 1992 TIGER/Line files.Arc/Info 8.3Paper census tract maps were scanned and the resultant image geo-referenced to the TIGER/Line tract boundaries.Arc/Info 8.3Starting with the 1990 TIGER-derived base map, editors worked on a county-by-county basis, backwards in time, decade by decade. A duplicate copy of the completed 1980 tract map became the edit map for the 1970 census tract map, and so on. A primary goal was to make tract borders match, where unchanged, from census year to census year. By reusing borders across different years, the NHGIS boundary files maximize the geographic correspondance between the datasets and avoid the problem of map conflation.Arc/Info 8.3With the scanned, geo-referenced tract map in the background, editors modified tract boundaries to match boundaries on the paper map. TIGER/Line features were used to verify tract borders by feature name (e.g., street, river, railroad) and was the first choice for obtaining additional line work. For example, if a tract border changed from a railroad line to a street and if the street still existed in the TIGER/Line file, the appropriate line from the TIGER/Line file was incorporated into the census tract boundaries. In cases where a new border was required that was not found in the TIGER/Line files, editors drew from a variety of ancillary data, including block maps and comparability tables from printed census documents. Usually, the editor digitized the new boundary using the scanned tract map as a guide.Arc/Info 8.3After making a new census tract, the editor calculated that tract's ID equal to the value denoted on the scanned map.Arc/Info 8.3The most common editing procedure required to make new census tracts were merge, split, swap, and calculate. For merge, an editor merged together two or more tracts to make a new tract. For split, an editor split one tract into two or more tracts. For swap, editors swapped polygons between two or more tracts but didn't create and destroy any tracts. For calculate, the editors simply calculated the tract's ID to the new value denoted on the scanned map.Arc/Info 8.3When staff finished editing all counties, a custom AML script appended all tracts and water in a given state to create a statewide coverage. Besides appending all tracts together, the AML also projected the coverages from UTM to Lambert Conformal Conic.Arc/Info 8.3To remove water from tracts along the coasts, staff edited the water regions for all coastal states and then used a custom AML to remove water from the coastal census tracts.Arc/Info 8.3NHGIS staff undertook an extensive review process after finishing tract editing. Staff examined coverages for topological errors, and they compared tract IDs with IDs found on the historical aggregate data files. The ID comparison process highlighted tracts that were missed during editing, extra tracts, and mistakes in the tract IDs.Arc/Info 8.3Converted the statewide tract coverages to ArcSDE feature classes using a custom C# program.ArcObjects and Visual Studio .NETProjected feature classes from Lambert Conformal Conic to the Contiguous US Albers Equal Area Conic projection.ArcCatalog 9.0Appended all statewide tract feature classes together to make a seamless, nationwide feature class containing all tracts for a given decade.ArcCatalog 9.0ArcGIS topology rules were used to check for topology errors in the nationwide feature classes. All errors were fixed using ArcMap 9.0.ArcCatalog 9.0 and ArcMap 9.0Census tracts were checked against aggregate data files again to ensure that no census tracts were lost during the coverage-to-feature class conversion processArcCatalog 9.0Used ArcCatalog's metadata tools to write FGDC-compliant metadata.ArcCatalog 9.0Converted tracts from feature classes to shapefiles for Internet dissemination.ArcCatalog 9.0Metadata imported.G:\conflation\shapefiles\metadata_templates\feature_class\metadata_originals\HI_tract_1940.xml20080425VectorG-polygon0GT-polygon composed of chains1338SimplePolygonFALSE0FALSEFALSEcoordinate pairmeters0.0000000.000000Albers Conical Equal Area8.00000018.000000-157.00000013.0000000.0000000.000000North American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983Hawaii_Albers_Equal_Area_ConicExplicit elevation coordinate included with horizontal coordinates1.000000GISJOINGISJOINString15STATESTATEString300COUNTYCOUNTYString3PREFIXPREFIXString4TRACTTRACTString4SUFFIXSUFFIXNumber6POPULATIONPOPULATIONString4AGGPREFIXAGGPREFIXNumber9NHGISCTYNHGISCTYString3ShapeFeature geometryESRICoordinates defining the featuresString10HI_tract_1940Feature Class0NHGISSTNHGISSTString3AGGTRACTAGGTRACTString2SHAPEShapeString3Feature geometry.ESRICoordinates defining the features.FIDFIDString4Internal feature number.ESRISequential unique whole numbers that are automatically generated.GISJOIN2GISJOIN2String16AGGSUFFIXAGGSUFFIXString15AGGTRACT80AGGTRACT80Float1911SHAPE_AREASHAPE_AREAFloat19Area of feature in internal units squared.ESRIPositive real numbers that are automatically generated.11SHAPE_LENSHAPE_LENDouble1900The most important attribute in this shapefile is GISJOIN because it provides the link between the shapefile and the aggregate data files. Any aggregate data file obtained through the NHGIS data acces system will contain a GISJOIN attribute. Use this attribute to link the data with the shapefile for mapping purposes. Please note that values in GISJOIN begin with "G" in order to retain leading zeros. This update took effect on May 7, 2008.
GISJOIN2 is an alternative linking attribute. GISJOIN2 is similar to GISJOIN except that its values do not begin with "G". GISJOIN2 may be used when linking to an aggregate data file extracted before May 7, 2008.
Other attributes in the shapefile include area (in square meters), perimeter (in meters), FID (a ArcGIS-generated unique identifier for each record), NHGISST (the NHGIS state code, derived from FIPS codes), and NHGISCTY (the NHGIS county code, also derived from FIPS codes).This shapefile contains census tracts for the Census of Population and Housing.200804252006/10/01As necessaryMinnesota Population CenterPetra Noble
50 Willey Hall
225 19th Avenue South
MinneapolisMinnesota55455USAREQUIRED: The mailing and/or physical address for the organization or individual.612-625-7375nhgis@pop.umn.eduFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998enlocal timehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile20080425135357002008042513535700{526845F7-F17A-4D8D-8E55-D62AEFE1FDF6}2008042511044100FALSECopyFeatures "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.hi\POPGIS.hi_t1940" G:\conflation\shapefiles\packing\gisjoin_gisjoin2_feature_class\tract\us_tract_1940\HI_tract_1940.shp # 0 0 020080425Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.0.1324HI_tract_1940-2162877.975576230564.2277081780356.806159656110.4085071-178.341454-154.71974829.24303718.1342251ISO 19115 Geographic Information - MetadataDIS_ESRI1.0datasetDownloadable Data0.0000.000002file://\\thalia.socsci.umn.edu\popgis\labpcs\conflation\shapefiles\packing\gisjoin_gisjoin2_feature_class\tract\us_tract_1940\HI_tract_1940.shpLocal Area Network0.000ShapefileHawaii_Albers_Equal_Area_Conic0