MonroeWorkToday_Counties_centroids

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: auut studio is author of this derived CSV table
Publication_Date: 20171210
Title: MonroeWorkToday_Counties_centroids
Edition: 1.0
Geospatial_Data_Presentation_Form: non-spatial table of values
Series_Information:
Series_Name: MonroeWorkToday_Counties
Issue_Identification: 2017
Publication_Information:
Publication_Place: San Francisco, California, USA
Publisher: auut studio
Online_Linkage: <http://www.monroeworktoday.org/download.html>
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 data table MonroeWorkToday_Counties_centroids, which is a direct derivation of 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://www.monroeworktoday.org/download.html>), and the original U.S. Historical Counties file may be downloaded without charge from this Web site (<http://publications.newberry.org/ahcbp>); see also Distribution_Information (below).
This dataset contains centroids of polygons for a specific subset of that original shapefile, limited to only those county entities which are applicable to the MonroeWorkToday.org project.
The original U.S. Historical Counties shapefile from the Newberry Library 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. That dataset enables users easily to employ a geographic information system for the analysis and display of county-related historical data. That 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 file provides a convenient table for choosing a centroid point (lat,lng) to represent each county that appears in the Monroe Work Today Compiled Dataset.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 16361231
Ending_Date: 20031231
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: None planned for MonroeWorkToday_Counties_centroids.csv
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -125.634078929
East_Bounding_Coordinate: -67.6367633208
North_Bounding_Coordinate: 51.5822575771
South_Bounding_Coordinate: 25.4399986216
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: historical county boundaries
Place:
Place_Keyword_Thesaurus: none
Place_Keyword: United States
Temporal:
Temporal_Keyword_Thesaurus: none
Temporal_Keyword: none
Access_Constraints:
Free access for use under an Attribution-NonCommercial-ShareAlike Creative Commons License < https://creativecommons.org/licenses/by-nc-sa/4.0/ >
Use_Constraints:
Free for use under an Attribution-NonCommercial-ShareAlike Creative Commons License < https://creativecommons.org/licenses/by-nc-sa/4.0/ >
Point_of_Contact:
Contact_Information_Secondary:
Contact_Organization_Secondary:
Contact_Organization:
auut studio
Contact_Position:
Research Director, auut studio
Contact_Electronic_Mail_Address: info@findauut.com
Contact_Information_Primary:
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:
There is no canonical method for defining a centroid point of a polygon; therefore it is impossible to evaluate the "accuracy" of the coordinate given in this dataset for a county's central point.
The original 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.
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
Source_Information:
Source_Citation:
Citation_Information:
Originator: auut studio
Publication_Date: 20171215
Title: Monroe Work Today County Centroids
Edition: 2017
Geospatial_Data_Presentation_Form: tabular data
Publication_Information:
Publication_Place: San Francisco, CA, USA
Publisher: auut studio
Source_Scale_Denominator: 100,000
Type_of_Source_Media: comma delimited table
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: BASE4
Source_Contribution:
The full U.S. Historical Counties boundary file (USB1) was used to produce a table of centroid coordinates for each version of each county.
Process_Step:
Process_Description:
Dataset projected from GCS_North_American_1983 to GCS_WGS_1984, using NAD_1983_To_WGS_1984_5 Geographic Transformation in ArcGIS.
Source_Used_Citation_Abbreviation: USB1
Process_Date: 20110911
Source_Produced_Citation_Abbreviation: USB2
Process_Step:
Process_Description:
Dataset was reduced by auut studio to a subset of polygon data that is applicable to the MonroeWorkToday.org project: generally those U.S. counties in existence at or after 1834.
A new attribute was created called keyid which was populated by concatenating the attribute county_id + "." + county_ver.
Source_Used_Citation_Abbreviation: USB2
Process_Date: 20150110
Source_Produced_Citation_Abbreviation: USB3
Process_Step:
Process_Description:
Polygons were analyzed by auut studio in a geoprocessing tool "Calculate Geometry > Spherical Centroid X and Y Coordinates" that calculated the coordinates of the polygon center of mass. The tool calculated a point not on a planimetric basis but rather assuming that the polygon lies on a sphere. [Tool is authored by Jenness, J. 2011. Tools for Graphics and Shapes: Extension for ArcGIS. Jenness Enterprises. Available at: http://www.jennessent.com/arcgis/shapes_graphics.htm]
Source_Used_Citation_Abbreviation: USB3
Process_Date: 20150110
Source_Produced_Citation_Abbreviation: USB4
Process_Step:
Process_Description:
Attribute table was exported to CSV format.
Source_Used_Citation_Abbreviation: USB4
Process_Date: 20160807
Source_Produced_Citation_Abbreviation: USB5
Process_Step:
Process_Description:
Two attributes were created in the CSV table using Apple Numbers spreadsheet software: (1) a new column called lng_rounded was derived from lng_centroid when rounded to 4 decimal places; (2) a new column called lat_rounded was derived from lat_centroid when rounded to 4 decimal places.
Source_Used_Citation_Abbreviation: USB5
Process_Date: 20160807
Source_Produced_Citation_Abbreviation: USB6
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: none
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: keyid
Attribute_Definition:
Primary key. This string is a unique identifier for each centroid point in the table. This was constructed by concatenating the county_id attribute (which is not unique, and may repeat several times in the table) and the county_ver attribute.
Attribute_Definition_Source: auut studio
Attribute_Domain_Values:
Unrepresentable_Domain: character field
String values that were automatically generated from other attributes.
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: STATE
Attribute_Definition:
Name of the county's state, colonial, or territorial affiliation during the county version's time frame.
Attribute_Definition_Source: colonial, territorial, state, and federal laws
Attribute_Domain_Values:
Unrepresentable_Domain: character field
Attribute:
Attribute_Label: county_id
Attribute_Definition:
The county_id code identifies unique geographical institutions, i.e., states, counties, and other administrative entities. The county_id code (called 'ID' in the originating Atlas of Historical County Boundaries) 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" refers to Maine (ME) as a state (s) followed by an identifying name (_York), which 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: county_ver
Attribute_Definition:
Sequential and chronological change in county name, configuration, or state/territorial jurisdiction.
Attribute_Definition_Source: compiler
Attribute_Domain_Values:
Unrepresentable_Domain: numeric field
Attribute:
Attribute_Label: START_N
Attribute_Definition:
First date for a particular county version or event to have been in jurisdictional force, 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
Attribute:
Attribute_Label: END_N
Attribute_Definition:
Last date for a particular county version or event to have been in jurisdictional force,, 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
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: lng_centroid
Attribute_Definition:
Decimal degrees of longitude of the central point of the county, as calculated by a geoprocessing tool.
Attribute:
Attribute_Label: lat_centroid
Attribute_Definition:
Decimal degrees of latitude of the central point of the county, as calculated by a geoprocessing tool.
Attribute:
Attribute_Label: lng_rounded
Attribute_Definition:
Decimal degrees of longitude of the central point of the county, as calculated by a geoprocessing tool and rounded to four decimal places.
Attribute:
Attribute_Label: lat_rounded
Attribute_Definition:
Decimal degrees of latitude of the central point of the county, as calculated by a geoprocessing tool and rounded to four decimal places.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
auut studio
Contact_Position:
Research Director
Contact_Address:
Address_Type:
Address:
City: San Francisco
State_or_Province: California
Postal_Code:
Country: USA
Contact_Voice_Telephone:
Contact_Electronic_Mail_Address: info@findauut.com
Hours_of_Service:
Resource_Description: Downloadable Data
Distribution_Liability:
No liability is assumed by auut studio, nor the authors of the originating dataset from the Atlas of Historical County Boundaries project, nor the Newberry Library.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: CSV
File_Decompression_Technique: Zipped file
Transfer_Size: 0.411
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.monroeworktoday.org/download.html>
Fees: None
Technical_Prerequisites:
To use this data requires software that can perform a JOIN of one table to another by matching a primary key.
Metadata_Reference_Information:
Metadata_Date: 20171210
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
auut studio
Contact_Person:
Research Director
Contact_Position:
Research Director
Contact_Address:
Address_Type:
Address:
City: San Francisco
State_or_Province: California
Postal_Code:
Country: USA
Contact_Voice_Telephone:
Contact_Electronic_Mail_Address: info@findauut.com
Hours_of_Service:
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time