U.S. Historical Counties

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: Peter Siczewicz, Digital Compiler
Originator: Emily Kelley, Digital Compiler
Originator: John H. Long, Editor, Atlas of Historical County Boundaries
Publication_Date: 20111001
Title: U.S. Historical Counties
Edition: 2.0
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: Atlas of Historical County Boundaries-Digital (Shapefiles)
Issue_Identification: 2010
Publication_Information:
Publication_Place: Newberry Library, Chicago, Illinois, USA
Publisher: Atlas of Historical County Boundaries
Online_Linkage: <http://publications.newberry.org/ahcbp>
Description:
Abstract:
This document serves as the metadata for the U.S. Historical Counties shapefile for use in a geographic information system (GIS). This file may be downloaded without charge from this Web site (<http://publications.newberry.org/ahcbp>); see also Distribution_Information (below).
This dataset was derived from the individual state datasets published by the Atlas of Historical County Boundaries project. A number of adjustments were made to the individual state files to produce the full United States dataset, as detailed in the Process_Step discussion (below).
The U.S. Historical Counties shapefile holds the polygons, metadata, and attribute data for every different configuration of every county or county equivalent in the area that became the fifty United States, dated to the day, from 4 March 1629 through 31 December 2000. This dataset enables users easily to employ a geographic information system for the analysis and display of county-related historical data. This downloadable dataset is provided in shapefile format in a geographic coordinate system (unprojected), so that it would be as accessible as possible to various GIS software.
Purpose:
This dataset provides a synthesis in shapefile format of the individual state files created by the Atlas of Historical County Boundaries project. The metadata for the individual state files provide a detailed description of the methodology used to research, plot, and digitize the historical county boundaries.
Supplemental_Information:
The Atlas aims to be absolutely comprehensive and, with a few exceptions (see next paragraph), to leave no "holes" in its historical and geographic coverage of a state. Each non-county area, whether an accidental gore or a region purposely set aside for future settlement, is represented by a polygon, the polygon is named (often merely as a non-county area with a number, such as NCA1), and a full set of data about it is entered in the database and the attribute file.
The exceptions to the "no-holes" policy described above are the large non-county areas in western Virginia, New York, and the New England states during much of the seventeenth century. In London and the other European capitals, officials had access to so little accurate information about inland territory that imperial claims and land grants, including colonial charters, often were incomplete or imprecise or asserted limits (e.g., the Pacific Ocean or "South Sea") that were so extreme as to be impractical to plot. Compilers treated those large, indefinitely bounded, and inadequately described, non-county areas as empty territory and made no attempt to represent them as coherent, historically complete polygons. In other cases the compilers supplied estimated boundary lines to close polygons representing indefinitely extensive frontier counties and noted their action in the CHANGE field.
Some changes have not been mapped because the change is too small to map, or the location is unknown, or both; for example, a law that transferred ten acres belonging to farmer Smith from one county to another would be unmappable because the parcel is too small to be mapped at the standard compilation scale or because the location of Smith's farm cannot be discovered. In some cases, information as to the location and date of changes too small to map is available with the individual state datasets.
State exceptions: In the case of South Carolina there were three overlapping layers of county-level jurisdiction; counties (10 May 1682 - 28 Jul 1769, and 12 Mar 1785 - 31 Dec 2000), parishes (30 Nov 1706 - 26 Sep 1865), and judicial districts (29 Jul 1769 - 15 Apr 1868). Louisiana also had two overlapping layers of jurisdiction; counties (10 Apr 1805 - 24 Jan 1846), and parishes (14 Apr 1807 - 31 Dec 2000). Polygons for all of these overlapping jurisdictions are included in the dataset, with the layer specified by the CNTY_TYPE field value. In addition, all changes for Alaska are by either the end of the particular census year, or by the official date of the census (when known). Alaska boroughs and census areas are treated as county equivalents in the dataset.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 16290304
Ending_Date: 20001231
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -179.147355
East_Bounding_Coordinate: -66.949425
North_Bounding_Coordinate: 71.389612
South_Bounding_Coordinate: 18.910845
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: polygon
Theme_Keyword: historical county boundaries
Place:
Place_Keyword_Thesaurus: none
Place_Keyword: United States
Temporal:
Temporal_Keyword_Thesaurus: none
Temporal_Keyword: 4 March 1629 to 31 December 2000
Access_Constraints:
Free access for use under an Attribution-NonCommercial-ShareAlike Creative Commons License
Use_Constraints:
Free for use under an Attribution-NonCommercial-ShareAlike Creative Commons License
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Dr. William M. Scholl Center for American History and Culture, The Newberry Library
Contact_Position:
Director, Dr. William M. Scholl Center for American History and Culture
Contact_Address:
Address_Type: mailing and physical address
Address: 60 W. Walton Street
City: Chicago
State_or_Province: Illinois
Postal_Code: 60610
Country: USA
Contact_Voice_Telephone: 312-943-9090
Contact_Electronic_Mail_Address: scholl@newberry.org
Hours_of_Service: 8:00 am - 5:00 pm M-F, CT
Data_Set_Credit:
Principal financial support for the Atlas of Historical County Boundaries project was provided by the Reference Materials Program of the National Endowment for the Humanities, an independent federal agency; additional support came from the Newberry Library, Chicago, the project's headquarters, and from a number of corporations, foundations, and individuals.
Security_Information:
Security_Classification_System: none
Security_Classification: Unclassified
Security_Handling_Description: none
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.3000
Cross_Reference:
Citation_Information:
Originator: John H. Long, Editor, Historical Compiler
Originator: Peggy Tuck Sinko, Assoc. Editor, Historical Compiler
Originator: Douglas Knox, Book Digitizing Director, GIS Compiler
Originator: Gordon DenBoer, Historical Compiler
Originator: Kathryn Ford Thorne, Historical Compiler
Originator: George E. Goodridge, Jr., Historical Compiler
Originator: Emily Kelley, Historical Compiler, GIS Compiler
Originator: Laura Rico-Beck, GIS Specialist, GIS Compiler
Originator: Peter Siczewicz, GIS Consultant
Originator: Robert Will, Cartographic Assistant
Originator: John Ford, Cartographic Assistant
Publication_Date: 20100701
Title: Atlas of Historical County Boundaries
Geospatial_Data_Presentation_Form: book and vector digital data
Publication_Information:
Publication_Place: New York
Publisher: Charles Scribner's Sons
Other_Citation_Details:
19 book vols. (1993-2000), online publication (2000-2011). Books published by Simon and Schuster, Charles Scribner's Sons.
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
This dataset provides a synthesis in shapefile format of the individual state datasets created by the Atlas of Historical County Boundaries project. The Atlas aims to achieve high accuracy through the use of the most authoritative and reliable sources, analysis of those sources by tested procedures, and careful proofreading of the results. Because counties are created and changed by their states, the state session laws are the primary, authoritative sources for the county lines, names, organization, and attachments. The initial plots of the boundaries are direct conversions of the legal boundary descriptions in the laws into linework on the plotting sheets. They are performed with copies of the legal descriptions at hand, and those same laws also are at hand for the GIS compiler when digitizing boundaries. All other sources, including old maps, are derived from those legal descriptions. The historical compiler searches the state session laws and, when necessary, related material (e.g., court decisions, executive proclamations) for information about the courses of the boundaries. Secondary texts, maps, and local experts are consulted as needed (e.g., when recovering a long-lost landmark that figured in an early boundary description). Dates of changes are also taken from the laws. Some laws specify when the change will go into effect, but others (mostly those passed before the twentieth century) do not; if no official effective date is provided, the historical compiler uses the date when the law was passed or approved.
The locations of places and landmarks cited in the boundary descriptions are gathered from the modern, federal base maps or from secondary publications (e.g., gazetteers, county histories, articles in historical journals), old maps, or local experts.
Details regarding the steps taken to insure the accuracy of the boundaries as they are plotted and digitized are available in the metadata for the individual state datasets.
Logical_Consistency_Report:
The dataset was initially created as a time-coded polygon feature class within an ESRI ArcGIS personal geodatabase, and ArcGIS tools were used to validate the polygon geometry. The procedures used to create the data ensure that the subset of polygons in effect at any given date from 4 March 1629 - 31 December 2000 is topologically correct, with no unexpected polygon gaps or overlaps. There are a number of known polygon overlaps, however, due to legislative or surveying errors, overlapping jurisdictions, and to conflicting territorial claims. As a final step, the polygon feature class was converted to a shapefile.
Completeness_Report:
The dataset is complete. All changes are dated to the day. If there is a difference between the effective date of change and the date when a law was passed, the effective date of change is used. Boundary changes too small to map are excluded from the shapefile. As a rule, boundary changes occurring entirely on water were not mapped. Exceptions to this rule might include county boundaries which run through large inland water bodies like Lake Okeechobee, Lake Pontchartrain, Great Salt Lake, etc.
No regular or systematic updating of the pre-2001 data is anticipated because (a) the historical data cannot change and (b) the compilers believe their methods and materials are sufficient to produce data that are complete and correct. (That is not to say no error can slip through. Suggestions for ad hoc changes or additions to the historical data, together with an explanation of why the change should be made and supporting evidence, should be directed to scholl@newberry.org or Dr. William M. Scholl Center for American History and Culture, The Newberry Library, 60 W. Walton St., Chicago, IL 60610). County boundary changes that occur after 31 December 2000 will routinely be digitized by the various states and the federal government and, therefore, will be available from agencies of those governments in separate files in the indefinite future.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report: Accurate to matching USGS 1:500,000 scale State Base maps.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Environmental Systems Research Institute, Inc. (ESRI)
Publication_Date: 20001101
Title: ESRI Data Maps
Edition: 2000
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 100,000
Type_of_Source_Media: CD-ROM
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2000
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: BASE1
Source_Contribution:
The ESRI detailed county, river, glocale, gsummit, highway, mjwater, and rail100K data were used as a modern base map, a reference for drawing historical county boundaries.
Source_Information:
Source_Citation:
Citation_Information:
Originator: Atlas of Historical County Boundaries
Publication_Date: 20100701
Title: State Historical County Boundaries
Edition: 2010
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Newberry Library, Chicago, Illinois, USA
Publisher: Atlas of Historical County Boundaries
Source_Scale_Denominator: 100,000
Type_of_Source_Media: shapefiles
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1629
Ending_Date: 2000
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: BASE2
Source_Contribution:
The individual state historical county boundary shapefiles were used to produce the full U.S. Historical Counties boundary file.
Process_Step:
Process_Description:
The U.S. Historical County dataset was derived from the individual state datasets published by the Atlas of Historical County Boundaries project. The individual state datasets were first combined, and then a number of adjustments were made to produce the full United States dataset.
First, duplicate copies of counties were removed. These generally were early versions of counties that crossed several modern state borders, and were therefore included in several state files. The attribute values of the retained copies were revised as appropriate for the United States dataset.
Proposed counties were removed, as were counties from the extralegal Territory of Jefferson. Polygons representing overlap areas between counties or disputed areas were also removed.
County boundary changes occurring after 31 December 2000 were eliminated from the dataset. This removed Broomfield, Colorado, which was created on 15 November 2001.
Areas under the jurisdiction of foreign governments after the colonial period were excluded. These included Spanish areas in Texas and Florida, British areas in Florida, Mexican municipalities established in Texas, as well as several counties established in New Mexico before that area became part of the United States.
Partial counties within separate state files were combined as necessary to form complete versions of various counties or territories, such as the Unorganized Federal Territory and the Northwest Territory.
In some cases new polygons were added to the dataset, generally for early territorial areas such as the Louisiana Purchase and Department of Alaska which were not included in the individual state shapefiles.
Additional county polygons were added to the United States dataset when there was a jurisdictional change without a county boundary change; for example, when an area changed from Wyoming Territory to the state of Wyoming. With these additional polygons it became possible to assign a unique jurisdiction code to each individual county version (the STATE_TERR field). This code supports the display of various U.S. state and territorial jurisdictions at any date, and allows the production of a state/territory jurisdiction shapefile. The information necessary to code the jurisdictional changes was obtained from the attribute tables and county chronologies provided with the individual state historical county boundary files. In a few instances a single county version fell into two jurisdictions, in which case the county polygon was divided into separate polygons for each jurisdiction.
Source_Used_Citation_Abbreviation: BASE1, BASE2
Process_Date: 2010
Source_Produced_Citation_Abbreviation: BASE3
Process_Step:
Process_Description:
Topology Check. A multi-step process was applied to ensure that historical county polygons fit together precisely at all dates. The first step was to convert the United States dataset (BASE3) to a polygon feature class in an ESRI geodatabase. ArcMap tools were then used to planarize the polygon boundary lines in the historical county feature class, and to create polygons from these lines. This resulted in a new feature class consisting of non-overlapping component polygons. The ESRI topology functionality was applied to the component polygons to detect overlaps and gaps, and to snap vertices to the ESRI modern county polygon feature class.
Based on the original historical county data, a table was created to specify, for each component polygon, the different counties to which it belonged and the time frames. The table was programmatically checked to verify that each component polygon was correctly assigned to historical counties throughout its life, with no unexpected gaps or overlaps.
The component polygons were then reassembled back into the historical counties, and converted to a shapefile. The resulting historical county shapefile consists of a large number of overlapping polygons; however, as a result of the topology check process, the subset of counties in effect at any selected date is topologically correct, with no unexpected gaps or overlaps. There are a number of known gaps and overlaps, however, due to legislative or surveying errors, overlapping jurisdictions, and conflicting territorial claims.
Source_Used_Citation_Abbreviation: BASE3
Process_Date: 2011
Source_Produced_Citation_Abbreviation: USB1
Process_Step:
Process_Description:
Dataset projected from GCS_North_American_1983 to GCS_WGS_1984, using NAD_1983_To_WGS_1984_5 Geographic Transformation.
Process_Date: 20110911
Process_Time: 12510400
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 17727
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.000002
Longitude_Resolution: 0.000002
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: D_WGS_1984
Ellipsoid_Name: WGS_1984
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257224
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: U.S. Historical Counties
Entity_Type_Definition: county and county equivalents
Entity_Type_Definition_Source: USA Laws
Attribute:
Attribute_Label: FID
Attribute_Definition:
Internal feature number. The FID number is the unique identifier (a primary key in database terms) for each polygon within the shapefile; its application is limited to its single shapefile.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: ID_NUM
Attribute_Definition: Numeric ID assigned to each polygon in the dataset.
Attribute_Definition_Source: compiler
Attribute_Domain_Values:
Unrepresentable_Domain: numeric field
Attribute:
Attribute_Label: NAME
Attribute_Definition:
Name or other identification of county or equivalent, limited to 20 characters.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: ID
Attribute_Definition:
Whereas the ID_NUM values (see above) uniquely identify the different polygons, the ID code identifies unique geographical institutions, i.e., states, counties, and other administrative entities. The ID code is stable across the entire dataset; it does not change when there is a change in the county's name, shape, size, location, or parent state or equivalent. Each county's unique identifier is set in terms of its current or most recent state affiliation. Hence, "mes_York" is the identifier for modern York County, Maine, and all its earlier versions, even though it was created as part of colonial Massachusetts.
Attribute_Definition_Source: project standards
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: STATE_TERR
Attribute_Definition:
Name of the county's state, colonial, or territorial affiliation during the county version's time frame. This differs from the STATE values included in the individual state datasets, which were based primarily on the modern jurisdiction. Except for the creation of West Virginia, the STATE_TERR values do not include any jurisdictional changes related to the Confederate States of America and the secession of southern states.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
FIPS codes are provided for the convenience of researchers working with data that has already been labeled with numbers from that coding system. FIPS is the abbreviation of Federal Information Processing Standard. FIPS codes were created in the first half of the twentieth century and are meant to facilitate efficiency and clarity in data handling. The system provides a two-digit code for each state or equivalent and a three-digit code for each county or equivalent. (Sometimes those codes are combined into five-digit numbers that start with the two digits for the state, as in this attribute table). The FIPS codes for states and counties in existence at the end of 2000 were taken from the federal government's FIPS PUB 6-4 (created 1996, last modified 10 May 2002), and the codes for extinct counties were taken from earlier lists. Some counties or other administrative entities may have no FIPS codes. In some cases they represent historical counties that became extinct before the introduction of FIPS codes; in other cases they represent temporary non-county areas. In the attribute table the FIPS field for those areas and extinct counties has been left blank because there is no standard system for pre-FIPS colonies, territories, and counties and no coding system includes non-county areas. Of course, users may supply a FIPS substitute of their own creation or, for extinct early counties, adopt an existing, alternative coding scheme, such as the one employed by Richard L. Forstall in his compilation, "Population of States and Counties of the United States: 1790-1990" (U.S. Bureau of the Census, 1996). In addition, as described above under Attribute Label: ID, the Atlas developed a parallel system of non-FIPS Identifiers to encode all states, counties, and equivalents; it is more flexible and working with it is easier than using the FIPS codes.
Attribute_Definition_Source: FIPS PUB 6-4
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Federal Information Processing Standards
Codeset_Source: FIPS PUB 6-4
Attribute:
Attribute_Label: VERSION
Attribute_Definition:
Sequential and chronological change in county name, configuration, or state/territorial jurisdiction. The versions in the U.S. Historical County dataset differ from the numbers in the individual state datasets, as the state datasets do not include new polygon versions for jurisdiction-only changes.
Attribute_Definition_Source: compiler
Attribute_Domain_Values:
Unrepresentable_Domain: numeric field
Attribute:
Attribute_Label: START_DATE
Attribute_Definition:
First date for a particular county version or event, arranged as mm/dd/yyyy.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 16290304
Range_Domain_Maximum: 20000401
Beginning_Date_of_Attribute_Values: 16290304
Ending_Date_of_Attribute_Values: 20000401
Attribute:
Attribute_Label: END_DATE
Attribute_Definition:
Last date for a particular county version or event, arranged as mm/dd/yyyy.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 16361230
Range_Domain_Maximum: 20001231
Beginning_Date_of_Attribute_Values: 16361230
Ending_Date_of_Attribute_Values: 20001231
Attribute:
Attribute_Label: CHANGE
Attribute_Definition:
Creation, change, or other event for each county on the given date.
Attribute_Definition_Source: colonial, territorial, state, and federal laws, compiler
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: CITATION
Attribute_Definition:
Reference to the source of data for the event described under CHANGE.
Attribute_Definition_Source:
colonial, territorial, state, and federal laws, any other texts, maps, or interviews employed to gather data
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: START_N
Attribute_Definition:
First date for a particular county version or event, arranged as yyyymmdd.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 16290304
Range_Domain_Maximum: 20000401
Beginning_Date_of_Attribute_Values: 16290304
Ending_Date_of_Attribute_Values: 20000401
Attribute:
Attribute_Label: END_N
Attribute_Definition:
Last date for a particular county version or event, arranged as yyyymmdd.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 16361230
Range_Domain_Maximum: 20001231
Beginning_Date_of_Attribute_Values: 16361230
Ending_Date_of_Attribute_Values: 20001231
Attribute:
Attribute_Label: AREA_SQMI
Attribute_Definition:
Area of a county or equivalent in square miles, calculated from the polygon by means of ArcMap facility. Calculations were based on the appropriate Albers Equal Area projection for (1) contiguous U.S., (2) Alaska, and (3) Hawaii.
Attribute_Definition_Source: compiler
Attribute_Domain_Values:
Unrepresentable_Domain: numeric field
Attribute:
Attribute_Label: CNTY_TYPE
Attribute_Definition:
This field classifies each county and equivalent into one of several categories: (1) District; judicial districts, a county equivalent which at one time served as a basic unit of government in South Carolina, (2) Parish; a county equivalent which at one time served as a basic unit of government in South Carolina, and which is currently the primary unit of government in Louisiana, (3) County; all remaining counties and county equivalents included in this dataset.
Attribute_Definition_Source: project standards
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: FULL_NAME
Attribute_Definition: Name or other identification of county or equivalent.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: CROSS_REF
Attribute_Definition:
Values to link United States county polygons with the original counties included in the state datasets of the Atlas of Historical County Boundaries. The values in the CROSS_REF field generally follow the ID_Version_Dataset format. For example, the entry "ils_cook_4_IL_Historical_Counties" indicates that the polygon was based on the county in the Atlas state files with ID = ils_cook, Version = 4, Dataset = IL_Historical_Counties. Only one county is referenced, though there may have been identical copies of the same county in several state datasets. Entries such as "Jurisdiction Change" or "New" are used in cases where the United States dataset contains a polygon not found in the original state files.
Attribute_Definition_Source: compiler
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: NAME_START
Attribute_Definition:
Combination of values from the NAME and the START_DATE fields, formatted for use in feature labeling applications.
Attribute_Definition_Source: compiler
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Dr. William M. Scholl Center for American History and Culture, The Newberry Library
Contact_Position:
Director, Dr. William M. Scholl Center for American History and Culture
Contact_Address:
Address_Type: mailing and physical address
Address: 60 W. Walton Street
City: Chicago
State_or_Province: Illinois
Postal_Code: 60610
Country: USA
Contact_Voice_Telephone: 312-943-9090
Contact_Electronic_Mail_Address: scholl@newberry.org
Hours_of_Service: 8:00 am - 5:00 pm, M-F, CT
Resource_Description: Downloadable Data
Distribution_Liability:
No liability is assumed by the Atlas of Historical County Boundaries project or the Newberry Library.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: SHP
File_Decompression_Technique: Zipped file
Transfer_Size: 751.427
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://publications.newberry.org/ahcbp>
Fees: None
Technical_Prerequisites:
To use this data requires software that supports ESRI GIS shapefiles.
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20110901
Metadata_Reference_Information:
Metadata_Date: 20110930
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Dr. William M. Scholl Center for American History and Culture, The Newberry Library
Contact_Person:
Director, Dr. William M. Scholl Center for American History and Culture
Contact_Position:
Director, Dr. William M. Scholl Center for American History and Culture
Contact_Address:
Address_Type: mailing and physical address
Address: 60 W. Walton Street
City: Chicago
State_or_Province: Illinois
Postal_Code: 60610
Country: USA
Contact_Voice_Telephone: 312-943-9090
Contact_Electronic_Mail_Address: scholl@newberry.org
Hours_of_Service: 8:00 am - 5:00 pm, M-F, CT
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.6 on Thu Dec 15 16:33:46 2011