Minnesota Population Center vector digital data Minneapolis, Minnesota Minnesota Population Center http://www.nhgis.org US_county_1860 2013 This 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 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 for the 1790 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. This shapefile represents the output from NSF Grant BCS0648045. This grant supports the re-alignment, or conflation, of the historical census tract and county boundaries in NHGIS with the Census Bureau's more accurate TIGER features, created through the MAF/TIGER Accuracy Improvement Project. This project greatly improved the spatial accuracy of the TIGER features, but at the cost of no longer aligning with the NHGIS boundaries. We used ESEA's MapMerger extension to ArcGIS to align the historical census tract and county boundaries with features from the 2008 TIGER/Line shapefiles. 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. en 1860 1860 1860 1860 1860 1860 1860 1860 1860 1860 publication date In work As work is completed None historical census of population and housing counties county equivalents census boundaries census geography census data population housing county borough independent city census area parish None None All 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: Minnesota Population Center. National Historical Geographic Information System: Version 2.0. Minneaoplis, MN: University of Minnesota 2011. 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 55455 David Van Riper Minnesota Population Center Research Fellow physical address

50 Willey Hall

225 19th Avenue South

Minneapolis Minnesota 55455 USA 612-625-7375 nhgis@umn.edu National Science Foundation Grant No. BCS0094908 and BCS0648045 ESRI ArcCatalog 9.2.0.1324 -2356113.743199 2258224.796357 -1337508.077280 1565781.659379 -127.887285 -65.345793 51.604785 22.871934 Shapefile All 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. Additionally, some records in the aggregate data files could not be mapped because they represent point features (e.g., military forts) - NHGIS boundary files are only composed of polygon features. 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 2008 shapefiles) can be found at http://www.census.gov/geo/www/tiger/tgrshp2008/tgrshp2008acc.html. When there was no 2008 TIGER feature to conflate to, we rubbersheeted the end points of the source line to a 2008 TIGER feature. These 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. ArcInfo 8.3 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. ArcInfo 8.3 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. ArcCatalog 9.0 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. ArcCatalog 9.0 Registered every state's featured data as versioned so that NHGIS staff could edit the feature classes. ArcCatalog 9.0 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. withheld withheld withheld ArcMap 9.0 After 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. ArcCatalog 9.0 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. ArcMap 9.0 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. withheld ArcCatalog 9.0 Using 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. ArcMap 9.0 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. ArcCatalog 9.0 and ArcMap 9.0 Checked the accuracy of historical county boundaries by comparing them to maps in Thorndale and Dollarhide (1987) or various John H. Long volumes. withheld withheld William Thorndale and William Dollarhide 1987 Baltimore, MD Genealogical Publishing Co., Inc. map Genealogical Publishing Co., Inc. various paper Thorndale and Dollarhide 1987 Depicts county boundaries used in 1790-1920 census Richard Forstall 1966 Washington, DC U.S. Department of Commerce, Bureau of the Census, Population Division U.S. Department of Commerce, Bureau of the Census, Population Division paper Forstall 1996 Lists population for each county enumerated U.S. Census Bureau 2001 Washington, DC U.S. Department of Commerce, Bureau of the Census, Geography Division vector digital file http://www.census.gov/geo/www/tiger/index.html U.S. Department of Commerce, Bureau of the Census, Geography Division 100000 online U.S. Census Bureau 2001b Base linework for the historic counties John S. Adams, William C. Block, Mark Lindberg, Robert McMaster, Steven Ruggles, and Wendy Thomas 2004 Minneapolis, MN Minnesota Population Center, University of Minnesota vector digital file http://www.nhgis.org Minnesota Population Center, University of Minnesota 100000 online Adams, et al. 2004 Peggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.) 2004 Chicago The Newberry Library map http://www.newberry.org/ahcbp/ie/index.html The Newberry Library various online Sinko, Rico and Long 2004e Gordon DenBoer (comp.) and John H. Long (ed.) 1995 map New York Charles Scribner's Sons various paper DenBoer and Long 1995 Gordon DenBoer (comp.) and John H. Long (ed.) 2000 map New York Charles Scribner's Sons various paper DenBoer and Long 2000 Gordon DenBoer (comp.) and John H. Long (ed.) map New York Charles Scribner's Sons 1998 various paper DenBoer and Long 1998b Gordon DenBoer (comp.) and John H. Long (ed.) map New York Charles Scribner's Sons 1996 various paper DenBoer and Long 1996 Gordon DenBoer (comp.) and John H. Long (ed.) map New York Charles Scribner's Sons 1997 various paper DenBoer and Long 1997b Gordon DenBoer (comp.), John H. Long (comp.) and John H. Long (ed.) 1994 map New York Simon and Schuster various paper DenBoer, Long and Long 1994 Gordon DenBoer (comp.), Kathryn Ford Thorne (comp.), and John H. Long (ed.) map New York Simon and Schuster 1993 various paper DenBoer, Thorne, and Long 1993 Gordon DenBoer (comp.), George E. Goodridge, Jr. (comp.) and John H. Long (ed.) 1993 map New York Simon and Schuster various paper DenBoer, Goodridge Jr., and Long 1993 John H. Long (comp. and ed.) 1996 map New York Charles Scribner's Sons various paper Long 1996 Peggy Tuck Sinko (comp.) and John H. Long (ed.) 1996 map New York Charles Scribner's Sons various paper Sinko and Long 1996a Peggy Tuck Sinko (comp.) and John H. Long (ed.) 1996 map New York Charles Scribner's Sons various paper Sinko and Long 1996b Peggy Tuck Sinko (comp.) and John H. Long (ed.) 1997 map New York Charles Scribner's Sons various paper Sinko and Long 1997 Peggy Tuck Sinko (comp.) and John H. Long (ed.) 1993 map New York Simon and Schuster various paper Sinko and Long 1993 Peggy Tuck Sinko (comp.) and John H. Long (ed.) 1998 map New York Charles Scribner's Sons various paper Sinko and Long 1998 various paper Sinko and Long 2000 Peggy Tuck Sinko (comp.) and John H. Long (ed.) 2000 map New York Charles Scribner's Sons Peggy Tuck Sinko (comp.), Kathryn Ford Thorne (comp.), and John H. Long (ed.) 1997 map New York Charles Scribner's Sons various paper Sinko, Thorne and Long 1997 Kathryn Ford Thorne (comp.) and John H. Long (ed.) 1993 map New York Simon and Schuster various paper Thorne and Long 1993 Gordon DenBoer (comp.) and John H. Long (ed.) 1997 map New York Charles Scribner's Sons various paper DenBoer and Long 1997a Gordon DenBoer (comp.) and John H. Long (ed.) 1998 map New York Charles Scribner's Sons various paper DenBoer and Long 1998a Peggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.) 2004 map Chicago The Newberry Library http://www.newberry.org/ahcbp/ie/index.html various online Sinko, Rico and Long 2004b Peggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.) 2004 map Chicago The Newberry Library http://www.newberry.org/ahcbp/ie/index.html various online Sinko, Rico and Long 2004d Peggy Tuck Sinko (comp.), Laura Rico (comp.) and John H. Long (ed.) 2004 map Chicago The Newberry Library http://www.newberry.org/ahcbp/ie/index.html various online Sinko, Rico and Long 2004c Sylvia Nimmo 1978 map Papillion, NE Sylvia Nimmo various paper Nimmo 1978 John H. Long (ed.) and Stephen L. Hansen (comp.) 1984 map Boston G.K. Hall & Co. various paper Long and Hansen 1984 John H. Long (ed. and comp.) and Hugo P. Leaming (comp.) 1984 map Boston G.K. Hall & Co. various paper Long and Leaming 1984 John H. Long (ed.), Mark P. Donovan (comp.), and Jeffrey D. Siebert (comp.) 1984 map Boston G.K. Hall & Co. various paper Long, Donovan and Siebert 1984 U.S. Census Bureau 1932 map Washington, D.C. U.S. Government Printing Office various paper U.S. Census Bureau 1932 U.S. Census Bureau 1943 map Washington, D.C. U.S. Government Printing Office various paper U.S. Census Bureau 1943 U.S. Census Bureau 1952 map Washington, D.C. U.S. Government Printing Office various paper U.S. Census Bureau 1952c U.S. Census Bureau 1963 map Washington, D.C. U.S. Government Printing Office various paper U.S. Census Bureau 1963 U.S. Census Bureau 1973 map Washington, D.C. U.S. Government Printing Office various paper U.S. Census Bureau 1973 U.S. Census Bureau 1981 map Washington, D.C. U.S. Government Printing Office various paper U.S. Census Bureau 1981 John H. Long (ed. and comp.) and Adele Hast (comp.) 1984 map Boston G.K. Hall & Co. various paper Long and Hast 1984 John H. Long (ed.and comp.) 1984 map Boston G.K. Hall & Co. various paper Long 1984 Michael Haines 2001 Ann Arbor, MI Inter-University Consortium for Political and Social Research Haines 2001 Projected 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. ArcCatalog 9.0 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. ArcCatalog 9.0 Using a custom Python script, extracted counties for each decade from the contiguous 48 states. ArcCatalog 9.0 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. ArcCatalog 9.0 and ArcMap 9.0 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. ArcCatalog 9.0 Attached FGDC-compliant metadata to every nationwide feature class and converted the feature classes to shapefiles for distribution on the NHGIS data access site. ArcCatalog 9.0 Metadata imported. withheld 20060911 08132600 Dataset copied. withheld 20061206 10060300 Vector Simple FALSE 0 TRUE FALSE North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983 USA_Contiguous_Albers_Equal_Area_Conic coordinate pair meters 0.000000 0.000000 Explicit elevation coordinate included with horizontal coordinates 1.000000 Counties Feature Class 0 Shape_Area OBJECTID OID 4 0 0 Area of feature in internal units squared. Esri Positive real numbers that are automatically generated. Shape GISJOIN String 8 Feature geometry. ESRI Coordinates defining the features. 0 0 GISJOIN DECADE String 4 0 0 Attribute used to join GIS data to aggregate data tables NHGIS DECADE NHGISNAM String 50 0 0 Census decade NHGIS NHGISNAM NHGISST String 3 NHGIS county name NHGIS 0 0 NHGISST NHGISCTY String 4 NHGIS state code NHGIS 0 0 NHGISCTY ICPSRST String 3 NHGIS county code NHGIS 0 0 ICPSRST ICPSRCTY String 4 ICPSR state code Historical, Demographic, Economic, and Social Data: The United States, 1790-2000 (Haines 2001) 0 0 ICPSRCTY ICPSRNAM String 35 ICPSR county code Historical, Demographic, Economic, and Social Data: The United States, 1790-2000 (Haines 2004) 0 0 ICPSRNAM STATENAM String 25 ICPSR county name Historical, Demographic, Economic, and Social Data: The United States, 1790-2000 (Haines 2004) 0 0 STATENAM ICPSRSTI Integer 4 State or territory name NHGIS 0 0 ICPSRSTI ICPSRCTYI Integer 4 0 0 ICPSRCTYI ICPSRFIP Double 8 0 0 ICPSRFIP STATE String 3 0 0 STATE COUNTY String 4 0 0 COUNTY PID Double 8 0 0 PID X_CENTROID Double 8 0 0 X_CENTROID GISJOIN2 String 7 0 0 GISJOIN2 Y_CENTROID Double 8 Alternate attribute used to join GIS data to aggregate data tables NHGIS 0 0 Y_CENTROID Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. SHAPE Area Integer 4 Feature geometry. ESRI Coordinates defining the features. 0 0 Area Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. Shape_Length Shape_Area Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. 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 - this attribute is an alternative linking attribute and 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 Center physical address

50 Willey Hall

225 19th Ave S

Minneapolis MN 55455 Downloadable Data 0.026 0.000 As necessary Minnesota Population Center David Van Riper

50 Willey Hall

225 19th Avenue South

Minneapolis Minnesota 55455 USA REQUIRED: The mailing and/or physical address for the organization or individual. 612-624-5818 nhgis@umn.edu FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile en 20080424 Esri ArcGIS 12.5.1.22081 Counties -2356113.743199 2258224.796357 1565781.659379 -1337508.07728 1 -127.887285 -65.345793 51.604785 22.871934 1 002 Counties Counties ISO 19115 Geographic Information - Metadata DIS_ESRI1.0 dataset 002 withheld Local Area Network 0.000 Shapefile File Geodatabase Feature Class 0.000 USA_Contiguous_Albers_Equal_Area_Conic Esri 4.0.0 0 20220405 12100500 20220405 12100500 20061206 10060300 FALSE Counties 002 0.000 Projected GCS_North_American_1983 USA_Contiguous_Albers_Equal_Area_Conic <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.5.0'><WKT>PROJCS[&quot;USA_Contiguous_Albers_Equal_Area_Conic&quot;,GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433]],PROJECTION[&quot;Albers&quot;],PARAMETER[&quot;False_Easting&quot;,0.0],PARAMETER[&quot;False_Northing&quot;,0.0],PARAMETER[&quot;Central_Meridian&quot;,-96.0],PARAMETER[&quot;Standard_Parallel_1&quot;,29.5],PARAMETER[&quot;Standard_Parallel_2&quot;,45.5],PARAMETER[&quot;Latitude_Of_Origin&quot;,37.5],UNIT[&quot;Meter&quot;,1.0],AUTHORITY[&quot;Esri&quot;,102003]]</WKT><XOrigin>-16901100</XOrigin><YOrigin>-8579000</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102003</WKID><LatestWKID>102003</LatestWKID></ProjectedCoordinateSystem> Linear Unit: Meter (1.000000) {E4422BC2-1808-4825-8E52-BABA4720A400} 20220405 /9j/4AAQSkZJRgABAQEAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCADIASwDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iii gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiii gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiii gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiii gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiii gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigD//2Q==