Minnesota Population Center2006/10/05Historic US County Boundaries to be used with 1960 census tracts, 1960, to be used with 1960 census tractsvector digital dataMinneapolis, MinnesotaMinnesota Population Centerhttp://www.nhgis.orgUS_tractcounty_1960This boundary file contains historic county 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 project has created two sets of county boundary files. This set, which comes bundled with the tract boundary files, is to be used in conjunction with the historic census tract boundary files, which are available for the 1910-2000 censuses. For decades when states do not contain census tracts, we have not included those states' counties in the boundary file. The other set contains all county boundaries for every census decade, 1790-2000. 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 county boundary files, to be used with the historic census tract boundary files, for the 1910 to 2000 censuses. These electronic county boundary files were created by referencing a wide variety of sources and considerable care was taken during their production. U.S. Census Bureau TIGER/Line Census 2000 files provided the 1990 and 2000 county boundaries and the roads, hydrography, and public land survey lines required to construct historic county boundaries. Locations of historic county boundaries were derived from William Thorndale and William Dollarhide's Map Guide to the U.S. Federal Censuses (1987), various volumes of John H. Long's Atlas of Historical County Boundaries, the Atlas of Historical County Boundaries website (http://www.newberry.org/ahcbp/), and other state-specific sources. TIGER/Line spatial features that corresponded to boundaries in these sources were used to construct the proper historic boundaries. When a TIGER/Line feature was not available, we digitized the historic boundary from one of the map sources. Aggregate data from Michael Haines' Historical Demographic, Economic and Social Data: The United States, 1790-1970 (2001) and Richard Forstall's Population of States and Counties of the United States: 1790 to 1990 (1996) were used to determine whether a county was enumerated during a given census. If a county was not enumerated, notes from those sources were used to attach the county in question to the county with which it was enumerated. If a county was not enumerated and the notes provide no details, the county was considered 'unattached' and it was merged with other unattached land within the state or territory.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. The boundaries contained in this file do not necessarily represent legal county boundaries. Instead, they represent the county boundaries over which the U.S. Census Bureau tabulated and published data.Counties are the primary legal subdivisions of most states and territories. Louisiana uses the term parish when referring to counties. Alaska has no counties; instead, the equivalents to counties are census areas, boroughs, city and boroughs, and municipalities. The U.S. Census Bureau and the state of Alaska jointly delineate the state's county equivalents. The District of Columbia has to legal subdivisions; thus, the Census Bureau treats the entire entity as a county. Four states (Maryland, Missouri, Nevada, and Virginia) have independent cities. These cities are independent of any county and thus serve as county equivalents in their respective states. The NHGIS assigned a four-digit code to every county and county equivalent within a state or territory. The codes are assigned in alphabetical order, except for independent cities, which are assigned codes higher than counties. FIPS codes were used to uniquely identify a county within a state or territory, except for historical counties that were never assigned FIPS codes. For those historical counties, the NHGIS assigned a new code based on the alphabetical order of all counties a state or territory ever contained.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-127.887285-65.34579351.60478522.871934-2356113.7457572258224.799287-1337508.0767191565781.660886Nonehistoricalcensus of population and housingcountiescounty equivalentscensus boundariescensus geographycensus datapopulationhousingcountyboroughindependent citycensus areaparishNoneNoneAll 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 state/territory, regional or national 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 Avenue South
MinneapolisMinnesota55455USA612-625-7375nhgis@pop.umn.eduNational Science Foundation Grant No. BCS0094908Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.0.1324ShapefileAll county codes were checked against codes in the available aggregate data to ensure accuracy and consistency. The boundary file may contain more or fewer counties than the aggregate data file. Sources for the boundary files sometimes depicted counties that contained no population; thus, they have no record in the aggregate data file. Sometimes, the aggregate data files contain records for county equivalents that are not mappable (e.g., military forts). Also, the boundary file sometimes contains an "unattached" county. This section of the state was not counted by the U.S. Census Bureau, but it has been included in order to depict the correct state/territory outline.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 county boundary datasets. The ArcGIS topology rules used to ensure logical consistency were 'Must not overlap' and 'Must be covered by'.Version 1.0 of the county boundary files contains counties and county equivalents. Most counties, although not all, have a matching record in the aggregate data files. Counties without a matching record were denoted on source materials as having "no population". We still made those counties because we had a geographic representation of it. Version 1.0 boundary files have not been generalized, and counties 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 counties overlap, no voids exist within counties, and any polygon belongs to one and only one county. Every county has a FIPS-like code (GISJOIN) that uniquely identifies it. The aggregate data contains a matching code (GISJOIN) so that the files can be easily joined together.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 Thorndale and Dollarhide (1987) maps for John H. Long (various) maps. These historic county boundaries do not represent legal boundaries and should only be used for thematic mapping and statistical analysis.William Thorndale and William Dollarhide1987Map Guide to the U.S. Federal Censuses, 1790-1920mapBaltimore, MDGenealogical Publishing Co., Inc.variouspaperThorndale and Dollarhide 1987Depicts county boundaries used in 1790-1920 censusRichard Forstall1966Population of States and Counties of the United States: 1790 to 1990Washington, DCU.S. Department of Commerce, Bureau of the Census, Population DivisionpaperForstall 1996Lists population for each county enumeratedU.S. Census Bureau2001Census 2000 TIGER/Line files [machine-readable data file]vector digital fileWashington, DCU.S. Department of Commerce, Bureau of the Census, Geography Divisionhttp://www.census.gov/geo/www/tiger/index.html100000onlineU.S. Census Bureau 2001bBase linework for the historic countiesJohn S. Adams, William C. Block, Mark Lindberg, Robert McMaster, Steven Ruggles, and Wendy Thomas2004National Historical Geographic Information System: Pre-release Version 0.1vector digital fileMinneapolis, MNMinnesota Population Center, University of Minnesotahttp://www.nhgis.org100000onlineAdams, et al. 2004Peggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.)2004Wyoming Historical CountiesmapChicagoThe Newberry Libraryhttp://www.newberry.org/ahcbp/ie/index.htmlvariousonlineSinko, Rico and Long 2004eGordon DenBoer (comp.) and John H. Long (ed.)1995Atlas of Historical County Boundaries: KentuckymapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 1995Gordon DenBoer (comp.) and John H. Long (ed.)2000Atlas of Historical County Boundaries: MinnesotamapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 2000Gordon DenBoer (comp.) and John H. Long (ed.)1998Atlas of Historical County Boundaries: North CarolinamapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 1998bGordon DenBoer (comp.) and John H. Long (ed.)1996Atlas of Historical County Boundaries: PennsylvaniamapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 1996Gordon DenBoer (comp.) and John H. Long (ed.)1997Atlas of Historical County Boundaries: WisconsinmapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 1997bGordon DenBoer (comp.), John H. Long (comp.) and John H. Long (ed.)1994Atlas of Historical County Boundaries: Connecticut, Maine, Massachusette, Rhode IslandmapNew YorkSimon and SchustervariouspaperDenBoer, Long and Long 1994Gordon DenBoer (comp.), Kathryn Ford Thorne (comp.), and John H. Long (ed.)1993Atlas of Historical County Boundaries: South CarolinamapNew YorkSimon and SchustervariouspaperDenBoer, Thorne, and Long 1993Gordon DenBoer (comp.), George E. Goodridge, Jr. (comp.) and John H. Long (ed.)1993Atlas of Historical County Boundaries: New Hampshire, VermontmapNew YorkSimon and SchustervariouspaperDenBoer, Goodridge Jr., and Long 1993John H. Long (comp. and ed.)1996Atlas of Historical Boundaries: Delaware, Maryland, District of ColumbiamapNew YorkCharles Scribner's SonsvariouspaperLong 1996Peggy Tuck Sinko (comp.) and John H. Long (ed.)1996Atlas of Historical County Boundaries: AlabamamapNew YorkCharles Scribner's SonsvariouspaperSinko and Long 1996aPeggy Tuck Sinko (comp.) and John H. Long (ed.)1996Atlas of Historical County Boundaries: IndianamapNew YorkCharles Scribner's SonsvariouspaperSinko and Long 1996bPeggy Tuck Sinko (comp.) and John H. Long (ed.)1997Atlas of Historical County Boundaries: MichiganmapNew YorkCharles Scribner's SonsvariouspaperSinko and Long 1997Peggy Tuck Sinko (comp.) and John H. Long (ed.)1993Atlas of Historical County Boundaries: MississippimapNew YorkSimon and SchustervariouspaperSinko and Long 1993Peggy Tuck Sinko (comp.) and John H. Long (ed.)1998Atlas of Historical County Boundaries: OhiomapNew YorkCharles Scribner's SonsvariouspaperSinko and Long 1998Peggy Tuck Sinko (comp.) and John H. Long (ed.)2000Atlas of Historical County Boundaries: TennesseemapNew YorkCharles Scribner's SonsvariouspaperSinko and Long 2000Peggy Tuck Sinko (comp.), Kathryn Ford Thorne (comp.), and John H. Long (ed.)1997Atlas of Historical County Boundaries: FloridamapNew YorkCharles Scribner's SonsvariouspaperSinko, Thorne and Long 1997Kathryn Ford Thorne (comp.) and John H. Long (ed.)1993Atlas of Historical County Boundaries: New YorkmapNew YorkSimon and SchustervariouspaperThorne and Long 1993Gordon DenBoer (comp.) and John H. Long (ed.)1997Atlas of Historical County Boundaries: IllinoismapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 1997aGordon DenBoer (comp.) and John H. Long (ed.)1998Atlas of Historical County Boundaries: IowamapNew YorkCharles Scribner's SonsvariouspaperDenBoer and Long 1998aPeggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.)2004Virginia Historical CountiesmapChicagoThe Newberry Libraryhttp://www.newberry.org/ahcbp/ie/index.htmlvariousonlineSinko, Rico and Long 2004bPeggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.)2004Montana Historical CountiesmapChicagoThe Newberry Libraryhttp://www.newberry.org/ahcbp/ie/index.htmlvariousonlineSinko, Rico and Long 2004dPeggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.)2004West Virginia Historical CountiesmapChicagoThe Newberry Libraryhttp://www.newberry.org/ahcbp/ie/index.htmlvariousonlineSinko, Rico and Long 2004cSylvia Nimmo1978Maps Showing the County Boundaries of Nebraska, 1854-1925mapPapillion, NESylvia NimmovariouspaperNimmo 1978John H. Long (ed.) and Stephen L. Hansen (comp.)1984Historical Atlas and Chronology of County Boundaries, 1788-1980, Volume 2: Illinois, Indiana, OhiomapBostonG.K. Hall & Co.variouspaperLong and Hansen 1984John H. Long (ed. and comp.) and Hugo P. Leaming (comp.)1984Historical Atlas and Chronology of County Boundaries, 1788-1980, Volume 3: Michigan, WisconsinmapBostonG.K. Hall & Co.variouspaperLong and Leaming 1984John H. Long (ed.), Mark P. Donovan (comp.), and Jeffrey D. Siebert (comp.)1984Historical Atlas and Chronology of County Boundaries, 1788-1980, Volume 5: Minnesota, North Dakota, South DakotamapBostonG.K. Hall & Co.variouspaperLong, Donovan and Siebert 1984U.S. Census Bureau1932Fifteenth Census of the United States: 1930. Population. Volume IIImapWashington, D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau 1932U.S. Census Bureau1943Sixteenth Census of the United States: 1940. Population. Volume IImapWashington, D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau 1943U.S. Census Bureau1952Census of Population: 1950. Volume II. Characteristics of the PopulationmapWashington, D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau 1952cU.S. Census Bureau1963Census of Population: 1960. Volume I. Characteristics of the PopulationmapWashington, D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau 1963U.S. Census Bureau1973Census of Population: 1970. Volume I, Characteristics of the PopulationmapWashington, D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau 1973U.S. Census Bureau19811980 Census of Population: Volume I, Characteristics of the PopulationmapWashington, D.C.U.S. Government Printing OfficevariouspaperU.S. Census Bureau 1981John H. Long (ed. and comp.) and Adele Hast (comp.)1984Historical Atlas and Chronology of County Boundaries, 1788-1980, Volume 4: Iowa, MissourimapBostonG.K. Hall & Co.variouspaperLong and Hast 1984John H. Long (ed.and comp.)1984Historical Atlas and Chronology of County Boundaries, 1788-1980, Volume 1: Delaware, Maryland, New Jersey, PennsylvaniamapBostonG.K. Hall & Co.variouspaperLong 1984Michael Haines2001Historical Demographic, Economic and Social Data: The United States, 1790-1970Ann Arbor, MIInter-University Consortium for Political and Social ResearchHaines 2001These process steps describe, in general, the procedures used to construct the NHGIS' historical county boundaries. The production procedures vary depending on the available source materials. The base counties were derived from the U.S. Census Bureau's Census 2000 TIGER/Line files. Many historical boundaries were derived from linear features also available in the TIGER/Line files. Those boundaries not available in digital form were digitized from scanned, geo-referenced maps.Using a custom AML, generated a statewide polygon coverage containing a union of 1990 and 2000 counties from the statewide census tract coverage. The projection, units, and datum for this coverage were geographic (latitude/longitude), decimal degrees, and NAD 83.Using a custom AML, generated a statewide coverage containing two region subclasses. One subclass contained all linear hydrographic (water) features and the second contained all roads and non-visible boundaries. The projection, units, and datum for this coverage were geographic (latitude/longitude), decimal degrees, and NAD 83.Using ArcCatalog 9.0, created feature datasets for each state in an ArcSDE database. The projection, unit, and datum of the feature datasets were geographic (latitude/longitude), decimal degrees, and NAD 83. The feature dataset's geographic extent was derived from an existing feature dataset containing all the state's census tracts.Imported the county polygon coverage, the hydrographic lines, and the streets into the ArcSDE feature dataset as feature classes. ArcCatalog 9.0's import function was used.Registered every state's featured data as versioned so that NHGIS staff could edit the feature classes.The county polygon features classes were edited in ArcMap to create the historical county boundaries. Edits were based on the sources available for a given state. Long (various) and Thorndale and Dollarhide (1987) were the main sources for historical boundaries. Books depicting or describing historical county boundaries existed for some states, and these were used when available. First, the counties, water, and roads were loaded into ArcMap. Second, map topology was created for the county polygon feature class. Third, the roads or water features representing a historical boundary were selected. Fourth, the polygon or polygons that required editing were selected. Finally, the Construct Features option of the ArcMap topology toolbar was used to split the selected polygon(s) with the selected roads and/or water. If a historical county boundary followed a feature not in the roads or water feature classes, the feature was digitized into the proper feature class.Thorndale and Dollarhide 1987U.S. Census Bureau 2000various John H. Long volumesAfter all edits were complete, the state features datasets were copied from one ArcSDE instance to a second ArcSDE instance.A topology features class was created for each state. The county polygon feature class was the only feature class participating in the topology. The topology rules were "Must not overlap" and "Must not have gaps." ArcCatalog's Create New Topology was used.The topology feature class was used to find gaps and overlaps in the county polygon feature class. ArcMap's editing tools were then used to fix the errors.A unique ID was then assigned to every polygon in a county polygon feature class. The ID was a concatenation of the state FIPS code and the polygon OID. Using the state FIPS code in the ID guaranteed that every polygon had a unique ID, even when appended together to make the entire country.Using historical census data acquired from Michael Haines, a database table was created for every state and territory in Microsoft Excel. The table contained a COUNTYSHAPE_ID for every census in which a county had data tabulated for it. The COUNTYSHAPE_ID was a concatenation of the county FIPS code and the census decade. The database table was saved as a comma-delimited file and imported into the ArcSDE database using a custom VBA script.Haines 2001Using a custom VBA script in ArcMap, a many-to-many relationship was established between county polygons and the database table containing the COUNTYSHAPE_ID. The polygons comprising a historical county were selected and "associated" to a row in the database table.After finishing the many-to-many relationships for the COUNTYSHAPE_IDs for a state or territory, a custom Python script was run to generate the counties for every census. Topology rules were established to detect holes and overlaps in a census' counties. The topology feature class was used to locate holes and overlaps. Custom ArcMap VBA tools were used to fix the "associations" between a county and the polygons comprising the county. Individual polygons were deleted or added to an "association" in order to fix the topology error. This step was repeated until all the topology errors in a state were eliminated.Checked the accuracy of historical county boundaries by comparing them to maps in Thorndale and Dollarhide (1987) or various John H. Long volumes.Thorndale and Dollarhide 1987various John H. Long volumesProjected each state feature dataset to USA Contiguous Albers Equal Area Conic projection, in meters and NAD83. Alaska was projected to the Alaska Albers Equal Area Conic projection, and Hawaii was projected to the Hawaii Albers Equal Area Conic projection.Used the Integrate function (with a 2.0 meter cluster tolerance) in ArcCatalog to snap the state polygon feature classes to the state boundaries contained in a nationwide feature class. We did the Integrate so that we could append all states together to make a seamless nationwide feature class containing all counties.Using a custom Python script, extracted counties for each decade from the contiguous 48 states.Starting in 1790, we appended all extracted counties together to make a nationwide feature class, one for each decade (1790-2000). We also created a topology feature class with the Must Not Overlap and Must Not Have Gaps rules to check for errors introduced by the append. Any errors were corrected and then this step was repeated.For each decade, we joined the attributes from Haines 2001 to the corresponding nationwide county feature class. This will provide users with the state and county codes and county names in the Haines 2001 data along with the state and county codes and county names developed for the NHGIS.Attached FGDC-compliant metadata to every nationwide feature class and converted the feature classes to shapefiles for distribution on the NHGIS data access site.Metadata imported.C:\WorkSpace\county.xmlMetadata imported.C:\WorkSpace\metadata.xmlDataset copied.Server=sdenhgis.socsci.umn.edu; Service=5153; User=popgis; Version=VANRIPER.intAppendMetadata imported.C:\WorkSpace\tract_county.xml20070111VectorG-polygon0GT-polygon composed of chains11SimplePolygonFALSE0FALSEFALSE115.000000FALSE549550551coordinate pair0.0000000.000000metersAlbers Conical Equal Area29.50000045.500000-96.00000037.5000000.0000000.000000North American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983USA_Contiguous_Albers_Equal_Area_Conic1.000000Explicit elevation coordinate included with horizontal coordinatesUS_tractcounty_1960Feature Class0GISJOINGISJOINString700NHGISSTNHGISSTString300NHGISCTYNHGISCTYString3NHGISNAMNHGISNAMString4DECADEDECADEString50ICPSRSTICPSRSTString9ICPSRCTYICPSRCTYString15ICPSRNAMICPSRNAMString13ICPSRSTIICPSRSTIString50ICPSRUNIICPSRUNIString30ICPSRFIPICPSRFIPNumber10GISJOIN2GISJOIN2Number10FIDFIDString60Internal feature number.ESRISequential unique whole numbers that are automatically generated.STATENAMSTATENAMNumber175ShapeShapeString8Feature geometry.ESRICoordinates defining the features.ICPSRCTYIICPSRCTYIString7SHAPE_AREASHAPE_AREAFloat19Area of feature in internal units squared.ESRIPositive real numbers that are automatically generated.11SHAPE_LENSHAPE_LENFloat1911This dataset contains historic county boundaries to be used with census tract boundaries. This dataset is a shapefile containing polygon features. The features depict historic county boundaries for the Unites States. There are 13 attributes associated with each county:
OID - unique identifier calculate by ArcSDE
GISJOIN - this attribute is a concatenation of the NHGISST and NHGISCTY codes and is a unique identifier for a county in a given decade. Use this attribute to join the shapefile's attribute table to aggregate data tables downloaded from the NHGIS website. 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.
DECADE - this attribute is the census decade
NHGISST - this attribute is the NHGIS state code, which was adapted from the FIPS codes. NHGIS staff added a third character to the FIPS codes for territories.
NHGISCTY - this attribute is the NHGIS county code, which was adapted from the FIPS codes. NHGIS staff added a fourth character to the FIPS codes for historical counties (i.e., counties that no longer exist).
NHGISNAM - this attribute is the NHGIS county name. NHGIS staff adapted the county names from Thorndale and Dollarhide (1987), John Long (various), Haines (2004), and current-day FIPS codes.
ICPSRST - this attribute is the ICPSR state code, which came from the Historical, Demographic, Economic, and Social Data: The United States, 1790-2000 (Haines 2004, http://webapp.icpsr.umich.edu/cocoon/ICPSR-STUDY/02896.xml) dataset. Counties with no value in the ICPSRST column were not found in the ICPSR dataset.
ICPSRCTY - this attribute is the ICPSR county code, which came from the Historical, Demographic, Economic, and Social Data: The United States, 1790-2000 (Haines 2004, http://webapp.icpsr.umich.edu/cocoon/ICPSR-STUDY/02896.xml) dataset. Counties with no value in the ICPSRCTY column were not found in the ICPSR dataset.
ICPSRNAM - this attribute is the ICPSR county name, which came from the Historical, Demographic, Economic, and Social Data: The United States, 1790-2000 (Haines 2004, http://webapp.icpsr.umich.edu/cocoon/ICPSR-STUDY/02896.xml) dataset. Counties with no value in the ICPSRNAM column were not found in the ICPSR dataset.
STATENAM - this attribute is the NHGIS state/territory name. NHGIS staff adapted the county names from Thorndale and Dollarhide (1987), John Long (various), Haines (2004), and current-day FIPS codes.
SHAPE - this is the geometry attribute for the county. ESRI ArcSDE maintains this attribute.
SHAPE.AREA - this is the area of a county, in square meters.
SHAPE.LEN - this is the perimeter of a county, in meters.Minnesota Population Centerphysical address
50 Willey Hall
225 19th Ave S
MinneapolisMN55455Downloadable Data0.0260.00020080424As necessaryMinnesota Population CenterPetra NobleREQUIRED: The mailing and/or physical address for the organization or individual.
50 Willey Hall
225 19th Avenue South
MinneapolisMinnesota55455USA612-625-7375nhgis@pop.umn.eduFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profilehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profilehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profileenhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile2008042417441900{D1341856-8008-4CBE-82E1-1068D154ECC5}2007011108591000FALSE2008042417441900AddField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOINA TEXT # # 7 # NULLABLE NON_REQUIRED # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"CalculateField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOINA [GISJOIN] VB # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"DeleteField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"AddField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN TEXT # # 8 # NULLABLE NON_REQUIRED # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"DeleteField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"AddField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN TEXT # # 8 # NULLABLE NON_REQUIRED # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"CalculateField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN ""G" & [GISJOINA]" VB # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"AddField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN2 TEXT # # 7 # NULLABLE NON_REQUIRED # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"CalculateField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOIN2 [GISJOINA] VB # "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"DeleteField "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960" GISJOINA "Database Connections\sdenhgis.socsci.umn.edu (5153).sde\POPGIS.Contiguous_USA_TC\POPGIS.c1960"CopyFeatures cLayer G:\conflation\shapefiles\packing\gisjoin_gisjoin2_feature_class\tract\us_tract_1960\US_tractcounty_1960.shp # 0 0 020080424Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.0.1324US_tractcounty_1960-2356113.7457572258224.7992871565781.660886-1337508.0767191-127.887285-65.34579351.60478522.8719341ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\thalia.socsci.umn.edu\popgis\labpcs\conflation\shapefiles\packing\gisjoin_gisjoin2_feature_class\tract\us_tract_1960\US_tractcounty_1960.shpLocal Area Network0.000ShapefileUSA_Contiguous_Albers_Equal_Area_Conic0