John H. Long, Historical Compiler Laura Rico-Beck, Digital Compiler John H. Long, Editor, Atlas of Historical County Boundaries 2/12/2010 vector digital data Atlas of Historical County Boundaries-Digital (Shapefiles) http://www.newberry.org/ahcbp This document serves as the metadata for the Massachusetts Historical Counties Dataset shapefile for use in a geographic information system (GIS). That file may be downloaded without charge from this Web site (www.newberry.org/ahcbp); see also Distribution_Information, below. In addition, an interactive map of Massachusetts's Historical Counties Dataset is available for operation and viewing through the Web site by means of ArcIMS, a program produced by Environmental Systems Research Institute (ESRI). ArcIMS draws its boundary data for the interactive map from the Massachusetts Historical Counties Dataset shapefile. The interactive map is projected while the downloadable shapefile is not. Here are descriptions of the sources and methods used to gather and process the information that appears in the shapefile and in the interactive map so that users can evaluate the quality and utility of the data. The comprehensive Massachusetts Historical Counties Dataset shapefile holds the polygons, metadata, and attribute data for every different configuration of every county or county equivalent in Massachusetts, dated to the day, from 4 March 1629 through 31 December 2000. The Historical Counties Dataset, together with a number of supplementary cartographic data files and text files, enable users easily to employ a geographic information system for the analysis and display of county-related historical data. First among the non-cartographic data files is the Massachusetts Comprehensive Database (a tab-delimited text file that can be imported into a database or spreadsheet program), which provides descriptions of all known changes in state and county boundaries, changes in county organization and attachments, and changes in status and name, together with citations to the sources. These data include unmappable boundary changes, which usually means changes too small to plot as polygons at compilation scale, changes whose shapes could not be plotted at compilation scale (e.g., shift of a boundary line from the centerline of a road to one shoulder or the other), and changes that could not be mapped for other reasons (e.g., the location of the change could not be determined). In the Comprehensive Database, there is a separate entry for each county involved in each event. That facilitates assembling all the events pertaining to a single county. In addition to the Comprehensive Database, there are five supplemental texts. These are: (1) a comprehensive County Index (includes proposed and extinct counties and non-county areas and provides cross references for name changes, with hyperlinks to corresponding individual county chronologies), (2) a Consolidated Chronology that organizes all the data by date, combining all the counties involved in an event into a single, composite entry, (3) a set of Individual County Chronologies, each one covering all the changes in a single county or equivalent, (4) a Bibliography that lists the primary and secondary sources found useful in the historical research, and (5) a Commentary on the research problems and materials that were remarkable or unusual in the process of historical compilation (Not every state requires a commentary.). A "Read Me" file introduces all these files and indicates how to get started with them. The Atlas is meant to be a resource for people (a) seeking records of past events, (b) trying to analyze, interpret, and display county-based historical data like returns of elections and censuses, and (c) working on state and local history. The special interests of those potential users range from history to demography, economics, genealogy, geography, law, and politics. Counties and their equivalents (e.g., parishes in Louisiana and independent cities in four other states) cover all the territory of the United States, function as repositories of valuable records, and long have been used as the geographic base units for the gathering of essential social, political, and economic data. The authority to create, change, or eliminate counties and to specify their functions lies with the states and their predecessors. In detail, the role of counties varies from state to state, but in every state they administer the judicial system and provide a great number of services. In the process, counties collect and preserve large quantities of information. For example: records of marriages, births, and deaths; probated wills; militia training; real-estate transfers; tax collections; welfare benefits; school programs; voter registrations; etc. Outside densely populated cities, counties have served as colonial, territorial, and state legislative districts and as the building blocks of congressional districts. In the nineteenth century they became the grassroots centers for the development of political parties. Moreover, counties have been the principal geographic units for the collection and aggregation of data from colonial/territorial, state, and federal censuses. Unfortunately for researchers, the average county has changed size, shape, or location between four and five times. Therefore, knowing the present county of the place where a past event occurred may not be sufficient to find its official records. If county boundaries changed in the meantime, it is necessary to learn what county had jurisdiction at the time of the event to identify the courthouse where the record is stored today. If the reported population of a county changed from one census to another, was that because of an increase or a decrease in the number of people, or an annexation or loss of populated territory, or a combination of both? Trying to analyze county-based historical data without controlling for boundary changes is almost certain to yield errors and lead to false conclusions. Method: Historical compilers plot county boundary changes in chronological order. Working directly from originals or photocopies of the verbal boundary descriptions in the state session laws, the ultimate authoritative source, the researcher plots the lines on a transparent compilation sheet laid over a modern base map of the state. As each change is plotted, the compiler writes a descriptive entry for the state's boundary chronology and a brief citation of the source of the information. The compiler creates the Comprehensive Database from this information. Plotting boundary changes of all counties together and in sequence, not merely reconstructing the counties at different points in time (e.g., dates of censuses) or concentrating on a single county at a time (thereby taking it out of the context of what happened to its neighbors), is an important aspect of the historical compilation process. Doing so gives the compiler valuable insight into how the counties developed and whether the intentions of legislators were realized in their enactments. For example, a law may say its purpose is to transfer territory from County A to County B, but the actual effect, visibly evident from the plot, may be to transfer territory from both A and C to B. When boundaries are plotted this way, gores (gaps between counties) and overlaps created accidentally by the legislature are readily apparent, and errors in plotting are discovered almost immediately. It is nearly impossible to detect such developments unless the counties are plotted together. Descriptive entries in the comprehensive database and in the chronologies reflect actual changes because they are written from the compilation plots, not from the laws alone or from secondary works. One additional benefit of this approach is that it provides an automatic checking mechanism. When the historical compiler reaches the end of the development of the county network, the final version should be identical with the boundaries of the present county. If there is a difference between the completed compilation and the standard, current map, the compiler knows there is a mistake somewhere. Such a discrepancy is rare, but when one is discovered, the compiler reviews the compilation to find the source of the problem. Usually it is a matter of the compiler erring in the plot of a boundary or accidentally omitting some change, either of which can easily be corrected, but occasionally the fault is found on the current, federal map. When the error appears on the federal map, the boundary is plotted accurately and a brief explanation of the difference is added to the supplemental Commentary. Problematic Data. Every so often, a state's law makers mistakenly overlapped the lines of two or more counties. Once such an overlap was detected, it seldom lasted long because dual jurisdictions generate only trouble, and states acted swiftly to eliminate them. This atlas treats areas of overlapping jurisdiction as distinct polygons and provides the usual data (e.g., start dates and end dates) for each one. Much more common than overlaps are non-county areas, that is, areas not within the jurisdiction of any county. Sometimes legal boundary descriptions left small areas, known as gores, outside the bounds of any county. Such inadvertent omissions errors most often occurred in the early days of a state's history when boundary makers lacked knowledge of the state's topography. Sometimes, legislators purposely did not extend county jurisdiction over all of their state's territory as early as possible, but waited until they had a better understanding of the lay of the land and until the prospect of European settlement was closer. Under those circumstances, they often provided a minimum of legal and administrative services for each non-county area by formally attaching it to a fully operational county; later, when the area was ready for settlement or was already under development, the state created one or more counties from the non-county area. This 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. In practice, each state compilation includes all the territory within its bounds in 2000, regardless of what authority created or altered a county there, plus all other territory that may have been within the state's jurisdiction at an earlier time. Also, there are no empty spaces, no areas outside a named polygon. 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. Because the ArcGIS program requires that all polygons be closed, 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. When the location of a change too small to map is known, the historical compiler marks the location and the digital compiler digitizes it as a point. All such tiny changes are collected in a separate shapefile, usually labeled [YEAR]_pt.shp. Using the historical compiler's plotting overlays and associated material (e.g., notes, copies of the laws), the GIS compiler draws the counties in digital form. For digitizing, the program is ArcGIS 9.1, and the electronic modern "base map" is from the Digital Chart of the World (DCW) provided with ArcGIS by Environmental Systems Research Institute (ESRI), plus, as needed, such other data (often from another source) as the grid of the Public Land Survey System (PLSS). By repeating much of the procedure of the historical compiler, the digital compiler implicitly checks the work of her predecessor and occasionally finds line segments that must be corrected. As digitizing proceeds, data from the comprehensive database are entered into the attribute table. After perfecting the boundary lines, the GIS digitizer assembles copies of all county polygons and attribute data into a single shapefile, the Historical Counties Dataset shapefile. 3/4/1629 12/31/2000 publication date Complete As needed -73.521416 -66.949426 47.459687 41.146249 none historical county boundaries none Massachusetts none 4 March 1629 to 31 December 2000 Free access for use under an Attribution-NonCommercial-ShareAlike Creative Commons License Free for use under an Attribution-NonCommercial-ShareAlike Creative Commons License Dr. William M. Scholl Center for American History and Culture, The Newberry Library Director, Dr. William M. Scholl Center for American History and Culture mailing and physical address

60 W. Walton Street

Chicago Illinois 60610 USA scholl@newberry.org 8:00 am - 5:00 pm M-F, CT Principal financial support for the 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. none Unclassified none ESRI ArcCatalog 9.1.0.780 John H. Long, Editor, Historical Compiler Peggy Tuck Sinko, Assoc. Editor, Historical Compiler Douglas Knox, Book Digitizing Director, GIS Compiler Gordon DenBoer, Historical Compiler Kathryn Ford Thorne, Historical Compiler George E. Goodridge, Jr., Historical Compiler Emily Kelley, Historical Compiler, GIS Compiler Laura Rico-Beck, GIS Specialist, GIS Compiler Peter Siczewicz, GIS Consultant Robert Will, Cartographic Assistant John Ford, Cartographic Assistant various book and vector digital data New York Simon and Schuster Charles Scribner's Sons 19 book vols. (1993-2000), online publication (2000-present) The Atlas of Historical County Boundaries Project 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. Several steps are taken to insure the accuracy of the boundaries as they are manually plotted, and to maintain the precision of those plots as they are manually digitized. The digitizing process involves faithfully drawing the sketched counties using landmarks such as rivers, roads, and places. These positional data were obtained from ESRI's Data and Maps collection (1:100,000 scale). Additionally, "Community Boundaries (Towns)," a collection of polygons representing Massachusetts's modern city and town boundaries (1:25,000 scale) were used to digitize boundaries in Massachusetts. These data were acquired from the Office of Geographic and Environmental Information (MassGIS), Commonwealth of Massachusetts. Once the initial digitizing is complete a master file is created and uploaded on IMS. When the digitizing is complete, the digitized polygons and their attribute data are once again checked for accuracy against the chronology for the state. The data set 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 included in the chronologies and in the Comprehensive Database. 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 both the state of MA and the federal government and, therefore, will be available from agencies of those governments in separate files in the indefinite future. Accurate to matching USGS 1:500,000 scale State Base maps. Massachusetts legislature 1869 to 1922 document Boston Commonwealth of Massachusetts paper 1692 1780 publication date Mass. Col. Acts These laws are the authority for the creation and change of each county; they contain the legal, verbal descriptions of the county boundaries, the effective dates of change, and related material. The historical compilers plot the lines described in the laws, converting them from words to lines on a map. Massachusetts legislature 1781 to 2000 document Boston Commonwealth of Massachusetts paper 10/1780 12/31/2000 publication date Mass. Acts These laws are the authority for the creation and change of each county; they contain the legal, verbal descriptions of the county boundaries, the effective dates of change, and related material. The historical compilers plot the lines described in the laws, converting them from words to lines on a map. Environmental Systems Research Institute, Inc. (ESRI) 11/01/2000 2000 vector digital data Redlands, California, USA Environmental Systems Research Institute, Inc. (ESRI) 100,000 CD-ROM 2000 publication date BASE1 For MA the ESRI detailed county, rivers, glocale, gsummit, highway, mjwater, and rail100K data were used as a modern base map, a reference for drawing historical county boundaries. Office of Geographic and Environmental Information (MassGIS) October 2002 vector digital data MassGIS, Commonwealth of Massachusetts http://www.mass.gov/mgis/towns.htm 25,000 online download towns The Community Boundaries (Towns) file is a collection of polygons representing Massachusetts's modern city and town political boundaries. Towns in Massachusetts, as in most of New England, are in many cases the basic building blocks of counties, and many county boundaries are described in the laws as a list of town names. Using the modern town network as a base layer was useful in reconstructing historical town boundaries and, consequently, historical county boundaries. various various various various various various paper, internet MA_BIB "Massachusetts: Bibliography and Sources," a partially annotated bibliography of textual and cartographic sources that yielded useful information in the compilation of the historical evolution of MA's counties, is a separate document that is a companion to this shapefile. Items in the bibliography are not equally important, yet each one was sufficiently valuable to the research and compilation of Massachusetts's historical county boundaries to merit listing. With the exception of the detailed citations above, no other sources are cited and described separately in the metadata and in the style set by the FGDC metadata standard; traditional bibliographic style is more compact and provides sufficient information for a user to find the item in any library. Historical Compilation. Working directly from originals or photocopies of the verbal boundary descriptions in the laws, the historical compiler plots the boundary lines of Historical Counties Dataset on a transparent compilation sheet laid over a base map of the state. Compilation proceeds from past to present. As each change is plotted the compiler writes a descriptive entry for the state's boundary chronology and a brief citation of the source of the information and enters it into the Comprehensive Database. (See also Supplemental_Information, Method, above.) The base map for this operation was the Massachusetts map from the U.S.G.S. State Base series at the scale of 1:500,000. (The 1:1,000,000 version of the map was employed whenever smaller scale was appropriate or needed to plot large or simple changes.) The original strategy for the Atlas was to publish all states in book form before venturing to digitize the data, and the 1:500,000 scale maps were used in making the books. Before switching to all digital products and methods, about 80% of the states had been researched and compiled using this series of base maps, including 24 states published in 19 printed volumes. It was not practical to re-compile those data at a larger scale like 1:100,000. (See below, the next two process steps.) withheld withheld withheld 1994 withheld Digital Base Map Creation. The GIS compiler creates a digital base map for the state (and any neighboring states that take part in its history) by editing the relevant portion of the Digital Chart of the World (DCW) supplied by ESRI in its ArcView package. This process consists chiefly in deleting elements (e.g., rivers) that are not related to the boundaries or do not serve a major reference function for potential readers and adding such other data as necessary. State Web sites commonly are the best sources for the grid of the Public Land Survey System (PLSS) in states west of the Appalachian Mountains and for the networks of town boundaries in the New England states. The main component of the customized base map is the set of detailed polygons of the modern counties. The GIS compiler projects the DCW so that the working version matches the projection of the paper base map used by the historical compiler. withheld 2008 withheld Digitizing Historical Counties. Using the historical compiler's base map, plotting overlays, the Comprehensive Database, and associated material (e.g., notes, copies of the laws), the GIS compiler manually digitizes the historical county polygons over the digital base map. By repeating much of the process of the historical compiler, the digital compiler implicitly checks the work of the historical compiler and occasionally finds line segments that are in error and must be corrected. As digitizing proceeds, data from the Comprehensive Database are entered into the attribute table. The process of entering attribute data entails an implicit review of the database and, if the greater map detail involved in working at digitization scale (see below) is different from the original descriptions, that may lead to updates of the database, including dates and version numbers and even descriptions of changes. The compiler works "heads up," facing the monitor and using the mouse to draw lines against a background of the digital base map. The historical compiler's plots are not scanned and overlaid on the digital base map, nor does the digital compiler trace the earlier work on a digitizing tablet, because neither technique is as efficient or accurate as drawing the lines anew. One reason is that the scale for most of the historical compilations is 1:500,000 and the scale for digitization is 1:100,000. It is most unusual to draw a map at a larger scale than its source or early version, but in this case it was unavoidable because digitization did not commence until after nearly all the states had already been compiled at the smaller scale. In effect, the historical plots are a preliminary stage, and the plots from that work become the chief sources or guides (supported by the historical notes and copies of the legal descriptions, and other material) for the digital compiler who renders the final, detailed version of the boundary lines. withheld 2008 withheld Create the comprehensive Historical Counties Dataset shapefile. After digitizing the historical counties, the GIS compiler creates a shapefile known as the comprehensive Historical Counties Dataset shapefile. It holds all versions of each county, plus unsuccessful proposals for changes and new counties, thus enabling a user to acquire maps of every version of every county. After the historical and IMS master files have been created, areas are calculated for all polygons. withheld 2008 withheld Final Proofing. Compilers proof the polygons of the master shapefile against the comprehensive database. After using ArcIMS to prepare an interactive, viewable cartographic shapefile, the compiler compares the entries in the database to the entries in the attribute table and checks the IMS image for the date and county names specified in the database entry. Discrepancies in the textual material (i.e., database) can be corrected on the spot; apparent errors in the polygons are noted for later correction by the GIS compiler. Later, after the GIS compiler corrects any faults in the line work, those corrections are reviewed again by the compilers and, if all polygons and text match properly, the shapefile is posted to the Web site. withheld 2009 withheld 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 historical county shapefile 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, and to conflicting territorial claims. withheld 2009 withheld Vector G-polygon 205 0.000000 0.000000 Decimal degrees North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 county county and county equivalents Mass. Acts FID Internal feature number. The FID number is the unique identifier (a primary key in database terms) for each polygon within a shapefile; its application is limited to its single shapefile. ESRI Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. NAME name or other identification of county or equivalent, limited to 20 characters colonial, territorial, state, and federal laws character field ID Whereas the FID numbers (see above) uniquely identify the different polygons in a single state's shapefile, the ID code identifies unique geographical institutions, i.e., states, counties, and other administrative entities. The ID code is stable across datasets (state shapefiles); 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 MA and is represented by polygons in the shapefiles of both MA and Maine. Because the FIPS system (see below) provides no codes for some extinct counties, no codes for non-county areas, and no codes for the colonies and territories that were predecessors of the states, it has been necessary to create a more comprehensive, alternative system of identifiers. The system adopted by the Atlas identifies each state and colony or territory with three letters, the first two based on the system of two-letter codes employed by the U.S. Post Office and the third indicating the status of the organization. (In most cases that is simply a C for colony, a T for territory, or an S for state.) For example, IAT stands for Iowa Territory and IAS for the state of Iowa. Some precursors of states need special ID codes, most of which are intuitively easy to read and to apply, especially in the context of a particular state's dataset. Examples are NWT (Northwest Territory, formally named Territory Northwest of the River Ohio), SWF (Spanish West Florida), FRS (State of Franklin), DKT (Dakota Territory), CRC (Colony of Carolina), and TXR (Republic of Texas). Counties are identified by appending their names to the state codes, as in "KYS_Adair" for Adair County in the state of Kentucky. Non-county areas are abbreviated NCA; within a specific state they are differentiated from each other by adding a numeral to the abbreviation, as in "MOS_NCA1" for non-county area number 1 in the state of Missouri. Occasionally special codes are needed to deal with unusual historical situations, as in Vermont where the original Washington County, identified as "VTS_Washington01," became extinct and later the name was applied to another county ("VTS_Washington") that continues today. The county identifiers also have been created with an eye towards users who may wish to download and work with more than one state file for regions and want a comprehensive way to sort and select shapefiles or to link the attribute table to the comprehensive database. project standards character field STATE name of the county's current or most recent state affiliation colonial, territorial, state, and federal laws character field FIPS 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. FIPS PUB 6-4 Federal Information Processing Standards FIPS PUB 6-4 VERSION sequential and chronological change in county name or configuration compiler character field START_DATE first date for a particular county version or event, arranged as mm/dd/yyyy colonial, territorial, state, and federal laws 16290304 20001231 3/4/1629 4/10/1947 END_DATE last date for a particular county version or event, arranged as mm/dd/yyyy colonial, territorial, state, and federal laws 16430509 20001231 5/09/1643 12/31/2000 CHANGE creation, change, or other event for each county on the given date colonial, territorial, state, and federal laws, compiler character field CITATION reference to the source of data for the event described under CHANGE colonial, territorial, state, and federal laws, any other texts, maps, or interviews employed to gather data character field START_N first date for a particular county version or event, arranged in the standard date format yyyymmdd colonial, territorial, state, and federal laws 16290304 19470410 END_N last date for a particular county version or event, arranged in the standard date format yyyymmdd colonial, territorial, state, and federal laws 16430509 20001231 AREA_SQMI area of a county or equivalent in square miles, calculated from polygon by means of ArcMap facility compiler numeric field DATASET The dataset field identifies the topical focus of the master shapefile. For every state the subject matter consists of all events affecting state and county jurisdiction within the borders of the modern state, regardless of the enabling authority, plus similar events involving the state outside its modern bounds, regardless of where or when. For example, polygons for Virginia's earliest western counties appear in the dataset for Kentucky because they represent part of the history of the area that became Kentucky; they also are included in the Virginia dataset because they are integral to the early history of Virginia, even though Virginia long ago ceded its authority over the area. In general, therefore, the dataset encompasses more data than a state, concentrating on one state (the principal point of focus) but possibly embracing data from one or more related, secondary states. Historically, almost every colony and territory transformed smoothly into statehood with no complications that might have required separate datasets for the state and its predecessors. The exception is Dakota Territory, which has its own dataset, and which split into a pair of states. Project standards character field CNTY_TYPE 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) Jefferson_Territory; an extralegal territory, never recognized by the United States, that included all of present Colorado and parts of present Nebraska, Wyoming, and Utah, (4) Proposal; proposed counties which never became operational, (5) County; all remaining counties and county equivalents included in this dataset. Project standards character field FULL_NAME name or other identification of county or equivalent colonial, territorial, state, and federal laws character field Dr. William M. Scholl Center for American History and Culture, The Newberry Library Director, Dr. William M. Scholl Center for American History and Culture mailing and physical address

60 W. Walton Street

Chicago Illinois 60610 USA scholl@newberry.org 8:00 am - 5:00 pm, M-F, CT Massachusetts Historical Counties Dataset shapefile No liability is assumed by the Atlas of Historical County Boundaries Project or the Newberry Library SHP Zipped file. 40.786 http://www.newberry.org/ahcbp To use this data requires software that supports ESRI GIS shapefiles. Fall 2009 and thereafter 2/12/2010 Dr. William M. Scholl Center for American History and Culture, The Newberry Library Director, Dr. William M. Scholl Center for American History and Culture mailing and physical address

60 W. Walton Street

Chicago Illinois 60610 USA scholl@newberry.org 8:00 am - 5:00 pm, M-F, CT FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile {A9740409-FBB1-4DBC-A9E1-038A6CC0B573} 20091008 13492500 TRUE 20100208 12512700 Massachusetts From the Newberry County Shapefile atlas /9j/4AAQSkZJRgABAQEAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCADIASwDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2yVwo wTyQapM6q6Ag5Y7Rj6Z/pVmccA5/Cq56+lc0nqQw70m4EY25HfIoP+RQqhcY4X3pNroIC65C9yeg pjMcZD4X6cj61Bf3n9n2hmMZdQQDhgMfnVOPXIbi6SCOFvMY4B3of5E0O71QGiZgGUNxvOOQe2B/ OkV/37EEHP0PPp/OoYbWSIszzyzEjG1gOD6jjp16+tVVsEtleWMRmbo5ZSeScnJH4fkKm4y7bsJS +M5AII6HvgCrKjziFBwWOCRUSIFGQFUsRu9zVmx8szuwzkc4Prgf/WrSmlfUTLgjCx7B1Ax0yarX QxGZPkDoGz34wR/hVvLbz064H0rMunOZlfJRvlOT0Pb+dVNlbE8IARWUjIAUHscjrSGCC5XyJ40l XrsdQR3xwe/FUpLprPTl5IJJER2Fst1A4zx1FRaNqk95cf6QQrBflHlMA3vkqMY/rSjtcaNEabY2 ZZrW0hhZhsLRIFJBPTPp/hUx2gYYY/2qGJIDKTgE/nSEcYbnByBijqIIlG0EN90EEntzz/n2oaeO IMcjCdcUTEJARwHOcce/Ss3zRMzRMhU53Mfbj/8AV+FKUrPQGK94X2RoxC5K8r1xjuT9RRcO8sLR FSGAPIxg54BrGuNXgjnkhLq6u+FlDKAp+hPbn681qQsHEUu4TK6jJBAPPTj05P5Vm79REwQITId4 JYgEnOMgcD0HFPsI1itAiDChmwPxJpFKmKUSkRKhyG3AZzjqeMdvyp9oyMj+Wysu7qrZB4B60pLS 5jX+Ell/1T/Q0+mS/wCqf6Gn1ByBTU6E+pNOpkZCjYSMjj60APooooAKRlzyOCO9LVaK7R4XlkKo iscNnqB39qdhjriRgioo+eRgnXGB3OfoCarNHDYiSQM2SMjp8i+3t/8AWFPLSTzQso2sn3xkEAHt 9eAPx/NLuyWaZZQvzAY3KBuX3BP+eld9CLjT5ktSkRXluZpMiKMzYGxj/CfUH8KcVhii2zBjM67i B8zjp39sD8vap5ZJooEO0s/8RUZxxnp+GPxqbYDy3OccHkVsqfvNrcLlWK2X7QtxM2ZM7UJ4JA3Y zjrwTx+lXKRVCLgdKWtoRUVZBcKKKM1Qie4wqY9+KqmpZ8+aQfwqE+vc9xXjt6ncwPHrmk5L8dB1 +tG3ljkDoPf/APVQpP1HHX+dLTqGw3JBO0kEn+7/AJ9qq3Jvly1uI35OFcHP1yCOPappLjylaRj8 qnaeMc0sNxHNb71bI6HcMc/p60APjMnl/viu8HqoIHtUZLi4GUG188j8ODn1pwIOVII3Zyp7jpTl 3FyRyuOp65z9KErsAJG9Sef6f41PZECfIHXK57k4HX8qgcMPm6N2PXH0FPg/1sfl4bPI9D6nP+f1 qob3C+ppH0OeKzbj5Wdd2Qxx93pkf/rrQZuvPJ5FUJVee1RySR97n3zxx6cU5K6KYy3KlCd2Cjbg VGcZ4I9uRVs5ZV4ztyenfkd6qW6kEkHqce3bn86thCU2lhnccEDP5/jRHYEOYbQADgYB56Ht/hUX VlQHoASQfcUQ7lh/eSBm3HnbgDJzjr6U9SeG/D5u9UA2QswHXhlP1Hf+dUWwZCQFAz07nHJ/pWiV ADNgbucn1qFVjDElOV6MRjJOKhq4FOOOUW8MxQySCMcDHJ+v+fWnW+moJDNhFZ+TtXBx/nnFWIvI ieO1SZS+B8m4biPUj86sureWApG7IHsRVSp63EuxEtuFiCHD8gHeM59agg4nulChQsoAVRgD5FNX Ytw2hs5A6Hr+f+etVI1K3FzuXBLg8f7ij+lTUXumVf4B0v8AqX/3TT6bIMxsD3BoV1bgHnHIrA4x 1IyqQcgc8UMwVSzEAAZJPaqUpNzKqPHuiIJXa2CDyMn2I/n3rSnTdR2Q0rjmvYlMQWZHDuFBXn/P 196svKkbKrsAW6ZrGhtDFCbmZTDiQZReMjfnPH48e5HStF4hdsGkTCKDtDDk5x27ela/V5OVinFE d1OLhZbWNsM+FDAg8HqfbgH8qRtOjFwjxErtbdsIynTAwPrg1bijWNAFRV9l6Cnc57Yrtp4eMY2e obDIgEHlAH5VGWI+9/8AX4pXmiiz5kioApYljgADvT6MDOcVvYBAeTwRj9aWiimIKKKKACkoNJTE TTgmTcBxjrUBAz71fO1x7e/eqswAcYHbtXjyXU9BkGAq8DgetHYgYxmiTJGMdfU00kLkqOnXvz/W oENKBnG77qcDPc+9K20nG05OCc9M9vb8P8acPlB3ZBHJ9KYuX+c5UDPGRjJ6j3pgIxG8uzFVXvnp /h/9enbyI3YKxdeijGT9M0jYAGRt68nrz/8ArpwcRqW/hHJPrQA0h5EBwFz95Sf8/wCTU9mp8zKg HjGeg98fpUZVnAA6g8ge9XraAwLjj8Bj/PJrW1nZBHXVj1yULn7/AEOe3tVZhMLYpamMuc4EhO0f l7VMzAK5yPvYx2PHI6VFv2HcCSpyACOR0/8Armm9GWUZBexMh8m25HzEsccZPX6etaCZyM8AjueD THdGhV85KnjHHPTHtyalZQhXIG1fUdPepAgZ4/MSAbQ7DO3uVHt+I/OrDMQy5Xdzxj+dNQs9zINp AUYz602WHz3XczqFYMApx0PcjsfSmIkkBZSowB2yOajAUgo2eRsA9RjP+fpUpDSN2IpcFjknp0AH X/69GzAprp9q+0+VkYwCWOBirDb0fngZ7Gpdqtjjg4NNeMSMAWOBg8HrWkZ8opR5hxYPyOg7iqay xyzuY3VlKggqcjqR/SrYRdgB61SODqM2BwsaKT75Y4/Ij86yqWs7Gdb4NSWmOvy/KOQcjFPormOI hmCTW7KX2q3BOcVVsrO3Ui5QEyFdocyM3y9BjJ9AOamjUNeTMyhmUja+PujHT69T+NWK9LC0eVc1 9y9gooorsEFFFFABRRRQAUUUUAFFFIaAEooopkl8AbsVBOjMwIHtxT7i6t7OIyXEyRKDjc5wM0/z FcKy4KtjBHcHoa8prQ9NookY4ximc/MfStCWLJxge1VHTYSBn8RWbi0SV2Jw2RkH360iqSdjbWAP HHQYp+3OAeQDn8qVAWbOflHSiMXJ2Qm7K4zY33WGRjoTnv70uzMMrBRlRk4H1P8An61OsZY56Ad6 eYlS0YOdob7zFsY/GnboCuyxCqhcBB9cVJI2Bxjmq8d3aqoC3EOO2JBUjqHb5zwCD9K06Fld5lif MhwM4HQc4HPPf/69VpZi023bwoLAk8nr2HTrRdnc7sM47jjJ9AM0xFZYFEmPMAAkb1/zzWbbvYTL MKt5bFsZOCcZxmhZ1a6EJUsSu8EA7AP97GM+3+FPidcBVyTkH8KUBg23jO7nPp/k01sCJFP7x2AA yFzTlbDPlgV9u1RwsdjMB0JyakIyhBzg9QKpgRxEgZYYOeAKWIoqnD5GTnPY9/1oA4IGAN3G3g9a k6D3z1o16jQnB49KeRnp26VDc2yXMPlylvLzkhHKn8wc1HbWVvYl44PMUucsXleTp7sTTYFk8nFU bnzYrkzfJ9nIHmEk7gemfp0/nV0sATlhwM49BVeWTd8xyFHQVE2rGVWUVGzE61AXd5mSNlATAYkZ 5649uMfnS2uwW6hMADOVB+6c8j8KIfmVpM/6w7h9Og/QU8NTUp+9sjitqOjjWKNUXoB+dOoor1Uh hRRRQAUUUUAFFFFABRRRQAU2lyKMUwEopcUYoEaJRSzZH0NRjIyDnhupFQ2huVZjdPEzHO3y1IGO OxJ5qyrAtjpxnmvM3PSE3ZI+XPcc0MgcYK89cGlJVlyCBgeuMUKyMBhhkHHHr6U2r7jIlgRPlwAO v608xKxAwOOgp2zncTn60gwe2ADgY4NKyQhpQdKiuDF8scm07j8qt/EetP3jzMFwTTvkYhiB8p79 qSQEC6fZsx3WduxPJzEvP+f6VOASRkZ9OaXpkYz649KRnUFT156U2CMya2JuWlB2kA4LcgH1xn6/ nWfBpjxXJm+0REsCHbysF89cnd1471qSAyM+GPlkEDB4Jz/nv3qIuiKduAO5PT0zWMtyWPhUSEhl K4XII9O3NWVf7pbBK8fMcfWlEY2ADrjr/n6VFIZhE32cI0m8YDkqvUdeDVJDSJ1P7sKuCzE9aQSo 7skbqzL1CsDg1Ws5bt3dbmKCNVb5fKctk/iBVoQQxlnhhjV2GSQAN341VwHKA0mMgj/P/wBelUdy MfWlAKjJweP1qvb/AGrLG6eA5A27FII69cmgZYbCpgfdxWa95q+8+TpcDpkgM11tJH02nFaZXOec /WnHA4PYYp9AKZd3C+YgRsDcoOefTPcCkYbhiiZ0ilfe2O9R5mb5vkQY6Nyfx9P1rnk3zHBVbc3c jltYpJPmBztw2CRuHTnHWnW9tDaxmOCNY0LFiF9T1NEEnmxB+OSeQcg89alr1aEFGCEFFFFbCEJp aQ9aAaYhaKKKQwooooAKDSCloAMUUUUAFFFJk0AXVUbSB07/AOfzpobnPIHWnHJBAwFpuFZSGxtb t/n8K8s9ECMht2Dk85PagPslIbnd2HP1pkgOcrzzkn8un4ZpxCsAd1O4EhlToW5x6/59KOvA7jPN VHBmbaWATJzhsZ+h+uP8ips5+fHJzgH60cwCiCLz/MKjeVxuyelJLIkUTM42hQWLYzxT2LZGMnnt S/K6jPTPQihAVNP1Kzv2dIHYvGAxDRMmM9DyB6VYl6rxkZ7ce9Sk7cnmql/N5MDFWAY/KmRnLNwP 1IpSYmVI42mUyrcMqOxZAm0jaTwRkdxg0n2cxsqiVsHvhf8AD6VZRFjRUUYVQAAOwpJCQUwM5bp+ BrncmcLqyvuNP2rqJ4/TmM9PzphW8JOZ4CDjI8k//FVOrbhmlo55B7WfcYGugMF4j6nYef1oE0+M pHEeO5Ix7dDT6ZH93PcnJ+tPnkP20+4Pc3mBttoCR6zn/wCJoW5uGQHyYwSO0p/+Jp9MMaY4UA+3 FHtGHtpki3MuDuhXr2f/AOtVWNVglaWK1n8xlI+efcmSc8gtx+AqZXPygqee5p9P2sh+3mMQsw3u 5ZiB26U+mMuASpI9h3pHk8uLeQWwOcVGrZk227srRzmGaWOcqCSWQA8kZ6fy/WrKOHXIz1wQexqP dLMmUxGrL8r53H8un60xbC2S5Fz5eZxn94xJPNerQ9pZKSKLNFFFdAhDSU49KbTQmLmlBzTaKAuO opAaM0h3Foo7U2gB1FFFABiim5pc0AW2w6lRn5h1NVp7aO5jRJiRtJ27WKkH/gJB71ZXDEgkHPUd 6aJVAyCSF6E9T7CvLPRGxQR28SxJuCrgD5yzAe5Jyfxp4OImY/LgZ5bB4600shAOR1GOc/5/Cs+/ vorS2jdiG3nCqHVenpk449KAL6bdrP1U8jHcUR7EkLgg7v4gKx7HWI7qR1UmIkhgC6kk98AE9/5/ Srv2ncPK3gtjlSOfrUt2Fc0TgnHWmnPmD0z+VVLWRgxgkxkcrzn5R/8AX/nVxAWxjOM557e1VF3A e2CeAM1Ru3LXMEYkK8szJjIYD/65FXZCAG5xjnPpWePmvJ3IIK4j56Hjdkf99Y/ClUdkRWlaDJaj B3ShuQqgjnuakqIxqZcYyMZK9s+v865jgHlB1UlT7Ug8wjnaD+dNibCIjAg44zQJcu2eE428cmnY BWdlX5gB9DTwMKAO1RtJG3DA5BBAKmliOVOM7egzSAkooooAZ96X/d4p9RMu5yBx0yc06Tnao6k9 j2oAV5FQcnnsPWsyG7S7ukgSRzGF3FQhwQRxlvyrQMZEgYfMOgyelUHgureTZDJv84geY5OUxk8D GDn5vTr+W9BxUryKjY0gABgcCioLedpQA6gEjhl+6fpU9erCSkroAoooqgENJSmkpiYUUUYoAKKX FGKAAUEUd6WgdhBS0DiikAmKSjNFMRJtkj+XkuRgnoT0H6ZprSjD4IAU4Bx0OSOPy/8A10MC7PCT gkYDH0x2/IUfZ9ylhtLEA15UvI9HYRLhRGFBz1Pvz/n9KheZuCMqAcEHkH6enFK1uyucklQOnOPS opI2YECRox/s4z6d81m2xakcs0kxZl2AqcZIznPp+Pfv1pAG85iSQA2FbOBn04PPT9cVGtu5JUyy yFkAZztGCD7Dr7dvxqzZwKysEQqM9egPH8u34VKXMwbsTWUQaWaZhgvhB8uN2Op5/L8K00+VQSe1 UcTRRs0cZkYcLHuxu5xnn2qeGWSWL97btA5/gZlJA/Amto6RGiVSGZgePUg81lW11CYgWnj3uS7A uMgk5x+GcVqcjGeD6etRjvxnc2SPxqZLmIqQ51a5AJY2xtdTn0NIhBLEnnOKPsUbztNJvkLAjY/3 fyP0qN7S3DGYR26qVyxKDjGaz9mYPD2WjJiFYcgEe9LVZLWMhWZAuVG6NQNpP+TTpYIFidjCmApJ woqDAmwM5wM+tNYbSCCRk8imLawbRugizjn5BTGsonLskUQ2IQBsHJI4P+fWmldlRjzOyLNFVxbQ tNHiFwA3I2so6GrH2OEOceZtA6CVvf3qlTbVy40XJXGSKCpJAz2PpSqgXoPx9aVtOhK4Vpg3UHzn P6ZqpDARI8bSyDAG5Nx689yc4+lJwaVxTpOC1J5J1TIALsBkqvOPr6Uixu8ivIV+XlVXoD0znv39 OtSKiqmxVAX0FCH5cHqODUmY2ZN6Ag4ZDuXnAz70RuJI1cdGAIomjMsTKDyffg+x9qrW7SwtHbtb hQQWLLJkDntnn/8AXXbg5pXi2NFs8CoFuombaW2n3/z7inyTwwkCWVELdNzAZqN/I8hXUK0e7jby Dnj8etds20roZYpDUEBmaRt0iNEuQBsIbPbnPP5VYqoyUldCaEFGaTFGKoQ6ikFLSGFFFFAAeKb1 pTQBTEGKWiikMnkijkdRIpJH3R/9cUyFDFM0ajAPIJHX8anKkMecjtio2YLcqBkfKefxFeWeiSYG Oc8UxoVYEsBuI6jjBp/YZH5UEA9c0CKclqoGFIXcfof/ANeKnJijX5iMUhBaXgD2P9ff/wCvTorR VdZGJZwMAnt68UkuwC5O0uRjI79hUjcdeKa4zkdvb6VUm0PSZpTLJptqzE5JaIHJz16VVtALjnIV dvUjr09f8/Socs5i4+VRuyCacwEe1FUbVUkccLjoPbg1HBEIk6k/xc+pOfy7e1ICb+DIxwOvWq12 DIwhXIXGSSeozyMd8jI/GrSgAFRnA7+tVLpxHPASw6Fdu7nkjn6cVMr20IqXUW0PpHUOjKehGKR3 WNSzHAFMEshziBx/vEf0Nc5wCxMZW27wuPXqeSP6VaSMx5AYtu5JqmjorL0I3bsfX/OanJs9QiMQ limUfeVXB/Hj8a3glY7KCTV7ak/PGKhlt4riQeYD8oBGGI5/CltbS2so/Lt4ljjH8IzxTlkG75v4 gP61ZsPyQDweKzWcx3jyys4VkUAEcDG7n9f5Vpn5sduwqndrjCnBI6NiqUOdNGdb4B4ORkdKjBKs SwPJxntjtUdtuVME8ZIA9Pb+dOuJRGqgjIbIPPIGCc1y8rvZHESsyqMswA9SarGbfOrIpaNQVZgM 8nH+H61AVmuZUmkCLbhW4DncT0Bxjjqf0q5AoitkU4AVRnHQVryypWmw2GMYLgBTIDzkbXwf0p3n KfuBnPbaOD+PSonaOdBIbaR8DjIxn8Cf85qYNK38CoO2Tk/l/wDXrs9tVkvdiMhgBSZkZwWCKNo5 249/xqzVO2TddTTkAEfu8gYDY6nH14/Crlb0U1BJjYUUUVoIKKKKACiiigAxRRRQAUUUUAW2IUgn qOmawdYsruS5W4tGnZTgMiTlAOuTgkD06f41ut82G7e9MZWYDDY+leU7WPQKliPs9mIpZCZ+SS8h ck+oJ/A496tscnKt1HUc02TbnG1SzdBjPNJEShZcgqOSV5x6D/8AVQkAs0y2cDSNHK4/uxxlz+Qp LK9F4pYQXEPGcTQsn88VZULgd1oL4zkrhRnOecVewyreGbZmCWOKTcDudCwIx0wCKZbG9QEXk8Mj EAqYoioHrnJOaXesbCPGEDA8+p5/nVgJ82SAM8nsaV77CI2LJuYJyy9f8aWMFQ4B3kDHpxT3wI3x nGO1U59Lsrty1xCHbG3JJHA5oTsBdXBJb1/Sq01lazSCeWANKpwJMYYD0B6ipwVRFVQcKMYJ/SkZ 8Rg9xzgCl6DsMa1h5McQMgbIZskj1wT049KaQVYqwAI/Woo7282c6ZLk8nEqH+tXmRW+8oOPUZpT gmZVKSkUmIVSwbjrinwWvk3Es52ZkIHCkEY7E55HJPTvVgIoIIXnPXpSEoDjdjrTp0mnoTCCp6tk S2IjuFmE90SpJ2mUlTnPUegzxUu3fK2e4H4daorFeK6sdTldVPI8lBn8cf5xV1ZkCn5TknNa+yl2 NPaR7izPPHt8i3Eo5zmTbj06jmqDSTvdkPb7E9Q+fTFXTcN2UAVDW0KLt7xhVqKSsiuyS7CsYCnc W3E8c/8A66cqOGWSVwCqbcD8Oc/hU1IVViCQDj1qo0IRd1uYEMjmQOg4QjBf/ClRFc/MXLL/AHuO Pw4pQXMmSuSvTPAH+NNljkmXBVBngkMen5VD5nP4boY+eR4oy6R7yOo5/oDTLaaSdC0kPljsCTk/ gQMVMTtXJzx6CmtIMELkt0GB3roclHcQ5VCDA9SaWmoSQQ33gcGnU4tNXQBRRRTAKKKKACiiigAo oooAKKKKALCkszAA7RwPemTXEFuAZ5Y4wem9gM/TNOTgAEg46t7Vn39omq7YVkkTYcl0AyT6cg+t eUegSR3kE10wimjdwMAB+nqeK0EiCpg5O7qaztP0WLT5fNSaZ2K42vtI+vAFaLHj26mmvMCIllO6 PAz+p/zioWJd8sx9iTx+HtVgEMAy4KkZzTGU7FBXOF5Pr7/pS3AjiXbzjBPr/n8asK24A55PtUSq ynIGR6GkDOISsbgPggFhkA/TP6VcbctgtqSmTAwOcnp2pAQnykk8dRWbEmpAKs13bFRw2y3IJ+h3 8H8KSKymjnWRtSu5VH/LN9mD164UHv8ApVxoykRKpGJbvTctHi1eJJSeGlUlQPoCKrW39o7/APTH tSmOBCjA547k9OtWqK6YUYxMJVpSVgaTYpYtgKMk5xio4LlLhTJGx4OD/Onld6lTnBGDg0lvaLAC i7lXOTuYnH51o3FbmaUpMeM9qCMVKMbiqLuGMH/Gk8tkO7pjnmp9oluVyO2hFk4AzwKKdwp5w3tT atMhobk78Y4xTqKKErCCiiimAAAdBiiiigApvlrnuPoxFOopOKluAiqFzjPPqaWiihJJWQBRRRTA KKKKACiiigAooooAKKKKALKhpQpyVXOSMYJpFQq7BB8vGfr/AJ/lTnWNHknBO8gKTmlaNMjHI69a 82x6JH5W6Z5A7btuDzwP/r0/blCpztAx7mnFwc4HHTGKR8KwDEZboPekBFMs5QfZfLUg87wSCPwx 3qBBcyRvHdmIMwx+5JHHfrVoll6LgeuetVrq5S1gaeRXYDHEaFyfoBzTTGiGLT4LJvOj88nsHuJH H5MxFNfTLF5VmltIHnXBDtGCc9jmmG9lvQyWaNHKhBzcwsq/kcE96lto9RE5N3JavFj5RFGykH8S ferVk9RO7WhbWMEEs3P1o2jI6f40vasSLRrq0vGuorxWUElIZDKRz2JMhHoM7eOuKbqTexKpRRtb UBHr9acu1jjPtxWLPBNeTxm80bTZ8cb3l37R14zH/k1HJrMenXo0+C0hRQwVQJQo+bB+7jjk0nGb +ISlBbHSKwX5QR9aZMF2csT9DVcuT7fSm1tCg1q2ZTrJqyRKsoRRtUZ9xTGdnOWNNordQSdzFzbV goooqiAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAfBYR2kRjheZs45mn eQ5HuxOPwqzH8zMjqNw5yDRRXmnpCJbxq7FQQS24kd/84p0kKSMjMiFlOVJHQ4xn/PrRRTAbJmK3 kdUZ2C8KMAsfQfWqdvM9wmZ7WS3KnlJCpPT/AGSR/wDqooqopNik7IVmZQxiVd3bPSs+ztby2unl a5Z1ZuEaViFB7Yoorq9lE4nVkanmn0FM3H/69FFWopbEucpbiEk9aKKKpCCiiigQUUUUAFFFFABR RRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQB/9k=