Data Package Metadata View Summary

Settlement Trees, Illinois Level 0

General Information

Data Package:
Local Identifier:	msb-paleon.28.0
Title:	Settlement Trees, Illinois Level 0
Alternate Identifier:	DOI PLACE HOLDER
Abstract:	We provide a Level 0 record of trees in Illinois transcribed from Public Land Surveys conducted by surveyors from the General Land Office of the United States in the 1800s. Posts were set every half mile in townships that were typically 6 miles by 6 miles square. Surveyors recorded details about the one to four trees closest (but typically recorded information for the two closest trees) to the posts and included information about the tree name (taxonomic specificity ranged by surveyor), tree diameter (inches), and distance and bearing from the post. Our records include the tree information and the location of the posts from which the tree information came from. These Level 0 tree data were aggregated to the 8km grid resolution Level 1 product (see msb-paleon.26 package). That product was then statistically smoothed using a statistical model that accounts for zero-inflated continuous data with smoothing based on generalized additive modeling techniques and approximate Bayesian uncertainty estimates for the Level 2 products estimating aboveground biomass (msb-paleon.23), density (msb-paleon.24), and basal area (msb-paleon.25). The data processing steps and associated code are available in the GitHub repository: https://github.com/PalEON-Project/PLS_products. These products are used in the manucript, Paciorek et al., 2020, The forests of the midwestern United States at Euro-American settlement: spatial and physical structure based on contemporaneous survey data. ADD BIOARCHIVE LINK. This material is based upon work supported by the National Science Foundation under grants #DEB-1241874, 1241868, 1241870, 1241851, 1241891, 1241846, 1241856, 1241930.

Time Period

Begin:

1804

End:

1849

People and Organizations
Contact:	Peters, Jody (University of Notre Dame) [ email ]
Contact:	McLachlan, Jason (University of Notre Dame)
Creator:	McLachlan, Jason (University of Notre Dame)

Data Entities
Data Table Name:	PLS_Illinois_trees_Level0_v1.0.csv
Description:	Illinois Public Land Survey Tree Records

Detailed Metadata

Data Entities

Data Table


Data:	https://pasta-s.lternet.edu/package/data/eml/msb-paleon/28/0/f8e485d33ef6a62377bb175a556badb2
Name:	PLS_Illinois_trees_Level0_v1.0.csv
Description:	Illinois Public Land Survey Tree Records
Number of Records:	69042
Number of Columns:	88

Table Structure

Object Name:

PLS_Illinois_trees_Level0_v1.0.csv

Size:

27234531 byte

Text Format:

Number of Header Lines:

Record Delimiter:

#x0A

Orientation:

column

Simple Delimited:

Field Delimiter:

Table Column Descriptions

Column Name:

TRP

version

entry_id

timestamp

reader_initials

surveyor_name

volume

page

year

state

hubtack_county

baseline

meridian

township

townshipdir

rangenum

rangedir

sectiona

sectionb

interiorsection

interiordir

refcorner

traveldir

secondpass

chains

typecorner

cornerid

species

speciescode

verbatim

L1_tree1

L3_tree1

diameter

bearing

degrees

bearingdir

chainstree

species2

speciescode2

verbatim2

L1_tree2

L3_tree2

diameter2

bearing2

degrees2

bearingdir2

chainstree2

species3

speciescode3

verbatim3

L1_tree3

L3_tree3

diameter3

bearing3

degrees3

bearingdir3

chainstree3

species4

speciescode4

verbatim4

L1_tree4

L3_tree4

diameter4

bearing4

degrees4

bearingdir4

chainstree4

ecotype

ecotypenotes

ecotype2

ecotypenotes2

ecotype3

ecotypenotes3

water

nodata

notree

feature

featurenotes

timbernotes

understorynotes

landnotes

landnotesvb

generalnotes

recheck

reason

fixed

Definition:

The township, township direction, range, range direction and primemeridian concatenated for each corner

The x –coordinates in meters for the location of the corner the tree data is associated with. These coordinates come from the NAD 1983 Great Lakes and St. Lawrence Albers (epsg:3175) projection.

The y –coordinates in meters for the location of the corner the tree data is associated with. These coordinates come from the NAD 1983 Great Lakes and St. Lawrence Albers (epsg:3175) projection.

This is the version number as the data was entered into Notre Dame's data entry system and then subsequently georeferenced. The individual corner and tree entries have been entered into Notre Dame's database starting in 2013 and go up to version 2.0, which was renamed version 1.0 when it was archived in NIS as package msb-paleon.28. Data entry for Illinois is ongoing so additional data will be added in the future until all townships have been completed.

Unique identification number given each entry when entered into ND’s MySQL (values range from 421460-714173)or Qualtrics (values start with "R", followed by a random alpha-numeric value, e.g., R_3iEDyGzsS632hUU) databases.

The date and time when the entry was entered or modified. When making the shapefile for GIS, this data does not convert, so in most entries it is removed here. If you need this information, Jody Peters can get it from Notre Dame's MySQL or Qualtrics database.

Initials/name of person who entered the data

Name of surveyor from PLS notes. 99999 represents missing name

PLS volume data came from. Illinois has volume numbers (unlike Indiana which does not).

Page in the PLS notes data came from

Year of PLS survey

State (IL) the survey was conducted in. There are some corners in townships 10N11W2, 9N11W2, and 8N11W2 on the border with Indiana where notes may be from Indiana records, but are physically located within Illinois. The state listed in this column are where the corners are physically located. The state where the notes were read from are listed in the General Notes section.

The county the township is located. Hubtack is the resource Notre Dame uses to get PLS records for Illinois and since our database was set up to first record data from Illinois, this column is still labeled as Hubtack_county.

Baseline number (1-4) of the township. These were entered the same as the prime meridian values so may not actually be the true baseline numbers.

Prime meridian number (1-4) of the township

The township number

Township direction (N or S)

Range number of the township

Range direction (E or W)

One of two interior sections the surveyor was traveling between (values range from 1-36)

The other of the two interior sections the survey was traveling between

The southern (31, 32, 33, 34, 35, ,36) or eastern (1, 12, 13, 24, 25, 36) township boundary section numbers. The name is a bit misleading because these sections are on the boundaries not on the interior of the township.

The township border that was entered. Typically the data was only entered for the southern and eastern borders for each township, not the northern and western borders.

Notre Dame has a standard numbering system for the 1/4 and section corners in a township. You can find the map here: https://www.dropbox.com/s/r0x3c9bf9vci02v/PLS%20Township%20Grid%20PalEON.pdf?dl=0. The refcorner is the corner ID number from this map that the surveyors were traveling from

The direction the surveyors were traveling (E, W, N, S)

This denotes whether the surveyors were traveling over that portion of the township a second time. Y (yes) is used in cases when the surveyors have set a temporary post going one direction on a random line (typically when they travel east or west) and have come back on a true line and set the actual post and recorded trees. N (no) is used when the surveyors travel over a line only once (typically when they travel north or south).

The chains the section or 1/4 section corners were recorded at. Typically corners are 80.00 chains (or very close to 80) and 1/4 section corners are 40.00 chains (or very close to 40).

Labels are (¼) Section (i.e., corners set at the ½ mile, 40 chains), Section (i.e., points on the mile, 80 chains) or Township (i.e., the most NE, SE, and SW corners on the Township which are corners that could be found in adjacent townships). The township corners are labeled 100100, 700100, or 700700 on the corner map linked in the reforner description above.

The corner ID where the corner posts were set. These ID numbers come from the corner map linked in the refcorner description above.

This is the species for the first tree the surveyor recorded. The species name comes from a drop down list of options in the data entry form. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

2 letter abbreviation used for the first tree the surveyor recorded. These typically correspond with the species codes used by David Mladenoff from the University of Wisconsin, Madison. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

This is the tree name as written in the PLS notes for the first tree listed in the notes.

Level 1 tree names. These are the names written verbatim, unless the verbatim entries have a ditto (also written do or ", etc). For example, if the verbatim notes say “ditto" and the previous tree surveyed was a beech, then L1_tree1 will be beech.

Level 3 tree names. These are standardized tree names that convert the Level 1 names to a genera level common name. e.g., Level 1 = White Oak, Level 3 = Oak. The conversion files can be found in the GitHub repository: https://github.com/PalEON-Project/PLS_products

Diameter in inches of the first tree the surveyor recorded. NOTE: there are some trees that have very large diameters (greater than 60 in). If you have a question about the size of the tree, check the "fixed" column to see if the notes have been double checked.

First bearing direction of the first tree the surveyor recorded (N, S, E, W – typically N or S).

Bearing degrees of the first tree the surveyor recorded (0-90; NOTE: degrees greater than 90 were double checked by Jody - see the notes for information about these entries).

The second bearing direction of the first tree the surveyor recorded (E, W).

Although this says “chains” this is the distance in links (NOT chains) from the post to the first tree the surveyor recorded.

This is the species for the second tree the surveyor recorded. The species name comes from a drop down list of options in the data entry form. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

2 letter abbreviation used for the second tree the surveyor recorded. These typically correspond with the species codes used by David Mladenoff from the University of Wisconsin, Madison. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

This is the tree name as written in the PLS notes for the second tree listed in the notes.

Level 1 tree names. These are typically the names written verbatim, unless the verbatim entries have a ditto (also written do or ", etc). For example, if the verbatim notes say “ditto" and the previous tree surveyed was a beech, then L1_tree2 will be beech.

Diameter of the second tree the surveyor recorded. If you have a question about the size of the tree, check the fixed column to see if the notes have been double checked.

First bearing of the second tree the surveyor recorded (N, S, E, W – typically N or S).

Bearing degrees of the second tree the surveyor recorded

The second bearing direction of the second tree the surveyor recorded (typically, E or W).

Although this says “chains” this is the distance in links (NOT chains) from the post to the second tree the surveyor recorded

This is the species for the third tree the surveyor recorded. The species name comes from a drop down list of options in the data entry form. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

2 letter abbreviation used for the third tree the surveyor recorded. These typically correspond with the species codes used by David Mladenoff from the University of Wisconsin, Madison. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

This is the tree name as written in the PLS notes for the third tree listed in the notes.

Diameter of the third tree the surveyor recorded. If you have a question about the size of the tree, check the fixed column to see if the notes have been double checked.

First bearing of the third tree the surveyor recorded (N, S, E, W – typically N or S)

Bearing degrees of the third tree the surveyor recorded (0-90)

The second bearing direction of the third tree the surveyor recorded (E, W)

Although this says “chains” this is the distance in links (NOT chains) from the post to the third tree the surveyor recorded

This is the species for the fourth tree the surveyor recorded. The species name comes from a drop down list of options in the data entry form. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

2 letter abbreviation used for the fourth tree the surveyor recorded. These typically correspond with the species codes used by David Mladenoff from the University of Wisconsin, Madison. DO NOT USE THIS OR THE SPECIES TO ASSESS TREE SPECIES, INSTEAD USE THE VERBATIM, LEVEL 1 OR LEVEL 3 TREE NAMES.

This is the tree name as written in the PLS notes for the fourth tree listed in the notes

Diameter of the fourth tree the surveyor recorded. If you have a question about the size of the tree, check the fixed column to see if the notes have been double checked.

First bearing of the fourth tree the surveyor recorded (N, S, E, W – typically N or S)

Bearing degrees of the first tree the surveyor recorded (0-90)

The second bearing direction of the fourth tree the surveyor recorded (E, W)

Although this says “chains” this is the distance in links (NOT chains) from the post to the fourth tree the surveyor recorded.

When Notre Dame had used the GLO form/MySQL database to enter data, this had been the letter abbreviations regarding ecotypes. For example – G = grove, L = lake, P = prairie. When we switched to using the Qualtrics form to enter data, the ecotype names were no longer abbreviated. Although this wasn’t used extensively, there are some corners where students noted this. Corners in townships that were part of the Kankakee project are the most likely to have entries in this column with a focus on water notes. When we switched to entering data using the Qualtrics form in Fall 2017, ecotypes was used to describe corners with water/wet features.

Verbatim notes regarding the ecotype abbreviation

Another option to add more ecotype information

Attribute that characterized if corner post was set in Water or a Wet location. Water = a perpetually wet spot in a lake, creek, river, marsh, swamp, etc. Wet = a location that was noted as seasonally wet. See the generalnotes, features or ecotype columns to see why these corners were classified as water or wet.

A “Yes” entry means there was no data available for this corner (data was missing from the notes because the page was missing or the entry was just not written in. See the description in the general notes about why there was no data)

A “yes” entry means there was no tree listed at this corner either because it was water/wet or was in prairie. See the description in the generalnotes, ecotype or features to see why there was no tree.

Attribute for entering notes about non-ecological features. Examples include Post, Post in Mound, Road, House, etc. This was mainly used to note when there are no trees and surveyor sets a “post in mound”.

Verbatim description of the features

Notes about the type of timber for the past mile or 1/2 mile survyed getting to this corner. Students entered this data early in the data entry process, but stopped doing it around the summer of 2013.

Notes about the understory vegetation for the past mile or 1/2 mile surveyed gettin to this corner. Students entered this data early in the data entry process, but stopped doing it around the summer of 2013.

Drop down list of general landnote features. The surveyors often provided a general description of the land for the preceding half mile (notes are included with the tree information for the 1/4 section corner at 40 chains) or mile (notes are included with the tree information for the section corner at 80 chains). Notes often included information about the potential for cultivation or natural resources. NOTE: this description is for the land for the last half to one mile, so it does not necessarily pertain to the land specifically at the post. For example, there could be water features in the 1/2 mile surveyed, but that doesn't mean the post is set in water.

Verbatim land notes. This is used when the notes are more detailed or complicated or cannot be summarized with the options provided in the dropdown menu in Notre Dame's data entry system.

Attribute for general notes notes about this corner.

If data enterer was unsure of one of the aspects in this entry ID they could request that the person that did a double check on the data look over this entry.

Description of what needs to be rechecked in this entry

Description of anything that was changed from what was originally entered. If any entry looks questionable, check this column first to see if it has already been checked. If it hasn’t or if you still have questions about the entry, send Jody an email: peters.63@nd.edu

Storage Type:

Measurement Type:

nominal

ratio

ordinal

nominal

dateTime

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

ratio

nominal

Measurement Values Domain:

Definition

Township, Range, and Primemeridian

Unit	meter
Type	real

Unit	meter
Type	real

Definition

version number as the data was entered into Notre Dame's data entry system and subsequently georeferenced

Definition

Entry IDs

Format	MM-DD-YYYYY hh:mm
Precision	0

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	cbroder1
Definition	Caitlin Broderick
Source

Code Definition

Code	alevesqu
Definition	Anna Levesque
Source

Code Definition

Code	ahamlin
Definition	Quercus Hamlin
Source

Code Definition

Code	jcooney3
Definition	Jaclyn Cooney
Source

Code Definition

Code	mkivi
Definition	Marissa Kivi
Source

Code Definition

Code	dkim19
Definition	Da Som Kim
Source

Code Definition

Code	Ye Na Han
Definition	Annie Han
Source

Code Definition

Code	Emily Miller
Definition	Emily Miller
Source

Code Definition

Code	abuerger
Definition	Amanda Buerger
Source

Code Definition

Code	Kaitlin Powers
Definition	Kaitlin Powers
Source

Code Definition

Code	gsaalman
Definition	Grace Saalman
Source

Code Definition

Code	mmuelle2
Definition	Michelle Mueller
Source

Code Definition

Code	emears
Definition	Emily Mears
Source

Code Definition

Code	enguyen2
Definition	Erin Nguyen
Source

Code Definition

Code	yhan3
Definition	Annie Han
Source

Code Definition

Code	wchronis
Definition	Will Chronister
Source

Code Definition

Code	bbruns
Definition	Bridget Bruns
Source

Code Definition

Code	mcuellar
Definition	Mariel Cuellar
Source

Code Definition

Code	Michael Spoltore
Definition	Michael Spoltore
Source

Code Definition

Code	gblad
Definition	Garrett Blad
Source

Code Definition

Code	jdeines
Definition	Jill Deines
Source

Code Definition

Code	Ievans
Definition	Isaac Evans
Source

Code Definition

Code	bfoster1
Definition	Benjamin Foster
Source

Code Definition

Code	nmicelot
Definition	Nicole Micelotta
Source

Code Definition

Code	cwiech
Definition	Christina Wiech
Source

Code Definition

Code	ahelmke
Definition	Alec Helmke
Source

Code Definition

Code	zvolenec
Definition	Zoe Volenec
Source

Code Definition

Code	kpowers3
Definition	Kaitlin Powers
Source

Code Definition

Code	kbauer3
Definition	Kim Bauer
Source

Code Definition

Code	jpeters
Definition	Jody Peters
Source

Code Definition

Code	mcorcor5
Definition	Margaret Corcoran
Source

Code Definition

Code	hlegatzk
Definition	Hannah Legatzke
Source

Code Definition

Code	Luke Onken
Definition	Luke Onken
Source

Code Definition

Code	Matthew Donahue
Definition	Matthew Donahue
Source

Code Definition

Code	cmattiso
Definition	Claire Mattison
Source

Code Definition

Code	Emily Mears
Definition	Emily Mears
Source

Code Definition

Code	Jody Peters
Definition	Jody Peters
Source

Code Definition

Code	amuench
Definition	Alex Muench
Source

Code Definition

Code	kaugust1
Definition	Kate Augustine
Source

Code Definition

Code	nfantozz
Definition	Nicole Fantozzi
Source

Code Definition

Code	roneil1
Definition	Rebecca O'Neil
Source

Code Definition

Code	specorar
Definition	Sam Pecoraro
Source

Code Definition

Code	wtintor
Definition	Will Tintor
Source

Definition

Name of surveyor from PLS notes. 99999 represents missing name

Unit	dimensionless
Type	natural

Unit	dimensionless
Type	natural

Unit	nominalYear
Type	natural

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	IL
Definition	Illinois
Source

Definition

County name

Unit	dimensionless
Type	natural

Unit	dimensionless
Type	natural

Unit	dimensionless
Type	natural

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	N
Definition	North
Source

Code Definition

Code	S
Definition	South
Source

Unit	dimensionless
Type	natural

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	E
Definition	East
Source

Unit	dimensionless
Type	natural

Unit	dimensionless
Type	natural

Definition

southern and eastern section numbers

Definition

township border

Unit	dimensionless
Type	natural

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	E
Definition	East
Source

Code Definition

Code	N
Definition	North
Source

Code Definition

Code	S
Definition	South
Source

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	Y
Definition	Yes
Source

Code Definition

Code	N
Definition	No
Source

Unit	chains
Type	natural

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	(1/4) Section
Definition	1/4 section corner
Source

Code Definition

Code	Section
Definition	section corner
Source

Code Definition

Code	Township
Definition	Township corner this is the most NE, SE, and SW corners in the township which are corners that could be found in adjacent townships
Source

Unit	dimensionless
Type	natural

Definition

Species from a drop down list of options in the data entry form

Definition

2 letter abbreviation for a species

Definition

This is the tree name as written in the PLS notes for the first tree listed in the notes.

Definition

Level1 tree names

Definition

Level 3 tree name

Unit	inch
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	S
Definition	South
Source

Code Definition

Code	N
Definition	North
Source

Code Definition

Code	E
Definition	East
Source

Code Definition

Code	NA
Definition	Not Applicable
Source

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	99999
Definition	Missing from PLS notes
Source

Code Definition

Code	88888
Definition	PLS notes Illegible
Source

Unit	degree
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	E
Definition	East
Source

Code Definition

Code	99999
Definition	PLS notes are Illegible
Source

Code Definition

Code	88888
Definition	Missing from PLS notes
Source

Unit	link
Type	real

Definition

Species from a drop down list of options in the data entry form

Definition

2 letter abbreviation for a species

Definition

This is the tree name as written in the PLS notes for the second tree listed in the notes.

Definition

Level 1 tree names

Definition

Level 3 tree name

Unit	inch
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	N
Definition	North
Source

Code Definition

Code	S
Definition	South
Source

Code Definition

Code	E
Definition	East
Source

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	99999
Definition	Missing entry in PLS notes
Source

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	88888
Definition	PLS notes Illegible
Source

Unit	degree
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	E
Definition	East
Source

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	99999
Definition	Missing from PLS notes
Source

Code Definition

Code	88888
Definition	Illegible in PLS notes
Source

Unit	link
Type	real

Definition

Species from a drop down list of options in the data entry form

Definition

2 letter abbreviation for a species

Definition

This is the tree name as written in the PLS notes for the third tree listed in the notes.

Definition

Level 1 tree names

Definition

Level 3 tree name

Unit	inch
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	S
Definition	South
Source

Code Definition

Code	N
Definition	North
Source

Code Definition

Code	99999
Definition	Missing from PLS notes
Source

Unit	degree
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	E
Definition	East
Source

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	99999
Definition	Missing from the PLS notes
Source

Unit	link
Type	real

Definition

Species from a drop down list of options in the data entry form

Definition

2 letter abbreviation for a species

Definition

This is the tree name as written in the PLS notes for the fourth tree listed in the notes

Definition

Level 1 tree name

Definition

Level 3 tree name

Unit	inch
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	S
Definition	South
Source

Code Definition

Code	N
Definition	North
Source

Unit	degree
Type	real

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	W
Definition	West
Source

Code Definition

Code	E
Definition	East
Source

Unit	link
Type	real

Definition

Letter abbreviation of ecotypes

Definition

Verbatim notes regarding the ecotype abbreviation

Definition

Another option to add more ecotype information

Definition

Another option to add more ecotype information

Definition

Another option to add more ecotype information

Definition

Another option to add more ecotype information

Definition

Corner set in a perpetually wet spot such as lake, creek, river, marsh, swamp, etc

Definition

No data available for this corner

Definition

Corner is set in a location that is water/wet or in a prairie

Definition

Type of non-ecological features

Definition

Verbatim description of the features

Definition

Timber listed for the past mile or 1/2 mile in the notes

Definition

Understory vegetation

Definition

Summary of land notes for the past 1/2 to 1 mile surveyed

Definition

Verbatim land notes. This is used when the notes are more detailed or complicated.

Definition

Attribute for general notes notes about this corner.

Allowed Values and Definitions

Enumerated Domain

Code Definition

Code	NA
Definition	Not applicable
Source

Code Definition

Code	N
Definition	Corner requested to be checked and was checked
Source

Code Definition

Code	Y
Definition	Corner requested to be checked by second individual
Source

Code Definition

Code	Yes
Definition	Corner requested to be checked by second individual
Source

Code Definition

Code	Done
Definition	Corner requested to be checked and was checked
Source

Definition

Description of what needs to be rechecked in this entry

Definition

Description of anything that was changed from what was originally entered.

Missing Value Code:

Accuracy Report:

Accuracy Assessment:

Coverage:

Methods:

Data Package Usage Rights

PalEON uses the CC-BY 4.0 (Creative Commons Attribution 4.0 International) License for data products that get archived on NIS or elsewhere. Details of this license can be found here: https://creativecommons.org/licenses/by/4.0/legalcode

Keywords

By Thesaurus:
(No thesaurus)	Public Land Survey (PLS), forest, Pre-EuroAmerican Settlement, witness trees

Methods and Protocols

These methods, instrumentation and/or protocols apply to all data in this dataset:

Methods and protocols used in the collection of this data package

Description:

The PLS Surveys were conducted from 1804-1849 in Illinois. These records were aquired from Hubtack Document Resources (https://new.hubtack.com/). The PLS data from the records were transcribed by 39 individuals at Notre Dame from June 2013-January 2019. Individuals from Notre Dame who entered the data are: Sam Pecoraro, Jill Deines, Christina Wiech, Will Tintor, Jaclyn Cooney, Rebecca O'Neil, Margaret Corcoran, Benjamin Foster, Alex Muench, Nicole Fantozzi, Grace Saalman, Nicole Micelotta, Matthew Donahue, Claire Mattison, Isaac Evans, Will Chronister, Kate Augustine, Garret Blad, Michelle Mueller, Hannah Legatzke, Zoe Volonec, Anna Levesque, Annie Han, Luke Onken, Jody Peters, Caitlin Broderick, Kim Bauer, Amanda Buerger, Alec Helmke, Michael Spoltore, Emily Mears, Erin Nguyen, Da Som Kim, Kaitlin Powers, Emily Miller, Mariel Cuellar, Marissa Kivi, Quercus Hamlin, and Briget Bruns. The notes were originally entered into Notre Dame's online GLO form (http://www3.nd.edu/~paleolab/GLO/).This online form was disabled in Summer 2017 and data entry was moved to a form connected to a Qualtrics project. After data for each township was entered, the individual that entered the data, double checked it and then another individual who did not enter the data did a second check. Contact Jody Peters (peters.63@nd.edu) to see protocols for this first set of data checking. Data in the MySQL database was then exported to a csv, double checked and used to georeference the corners to the x,y coordinates for each corner from a GIS shapefile. For version 1.8 and later (see the version column in the dataset)the georeferencing and quality control checks were done using the Georef_R.R and PLS Summary Code.R code found in this GitHub repository: https://github.com/PalEON-Project/IN_ILTownshipChecker For versions 1.7 and lower (see the version column in the dataset), the following is the set of quality control checks conducted.These checks were transferred to the Georef_R.R code checks as the corners in each township were georeferenced for version 1.8. And additional checks were added with the PLS Summary Code.R for the overall checks of all the townships combined prior to the data being pushed to GitHub. The PLS Summary Code.R had additional checks added after it was run on version 1.8-1 so was run again for version 1.8-2 and corrections were made. Data Processing Steps for ndinpls_v1.5-1, 1.6, and 1.7 1.Added GIS pointX and pointY using the entryID and UniqueID for the corners. 2.Left in Understory notes. 3.Added column for the TRP (township, range, primemeridian concatenated) 4.Added column for the version number 5.We had added the waterwet column after the v1.5 data was entered, so went back and checked all No tree/No data in each township grouping to entries to make sure they were labeled correctly and labeled if they were Water or Wet. 6.Removed preceding spaces. Make new column (i.e., verbatim_b, verbatim2_b, etc). Sort by verbatim, then use formula =trim(cell#). Don’t use this formula for the 88888s and 99999s. Just copy those over. Copy full column, then paste special. Then delete old verbatim column and rename verbatim_b as verbatim. 7.Sort by verbatim, then copy verbatim to L1_tree1 column, then sort by verbatim2 (and 3 and 4) then create L1_tree2 (and 3 and 4) by doing an if statement that changes “dittos”s (“, Do, etc) to the tree in the L1_tree1 column for that corner. 8.L3_tree1, tree2, tree3 and tree4: convert Trees 1, 2, 3, and 4 into Level 3 tree names 9.Put No Tree and No Data and Water in the L1_tree1 column (But not in the other 3 tree columns. Put in NAs in for the other 3 columns in step 12). 10.Put in NAs in L1_trees, L3_trees, diameter, degrees, chainstrees for Tree 2, 3, 4 with No Trees and for Tree 1,2,3,4 with No Trees, No Data, and Water. 11.Remove “Null” entries which will mainly be found in ecotype notes through the fixed column 13.Create Pivot Table in new worksheet with Summary of a. TRP counts b. L3 then L1 trees (nested) with counts of L1 trees for all 4 trees (to make sure the L1 trees are in the correct L3 tree categories) (make sure all L1 trees are in the correct L3 category) c. Diameter counts for all 4 trees (make sure there aren’t any weird diameters – check diameters 60 or greater) d. Degrees counts for all 4 trees (make sure no degrees >90 or if so include a note) e. Chainstrees counts for all 4 trees (look for any weird tree distances) f. Check that all the pivot table counts are the same for diameter, degrees, chainstrees g. Get counts of x and y coordinates. Make sure there is the same number of unique coordinates as there are TRPs. Then make sure the counts for the TRPs, x and y coordinates match up. NOTE: There are 2 pair of corners (4 individual corners) where the tree information is identical in each pair of corners. The notes for these corners were double checked and it was not a data transcription error on our part, this was how the notes were written from the PLS records. We are leaving these corners in the dataset as of now since we assume that one of the corners did have the trees recorded, we just aren't sure which corner it is. However, we are removing these entries for the biomass statistical analyses as described in the GitHub repository: https://github.com/PalEON-Project/PLS_products. Here is the list of corners that have the identical tree information: TRP entry_id reader_initials hubtack_county cornerid tree1-4_concatenated 23N5W3 96 648480 ahamlin Tazewell 700500 syckamore30S66W50NANANANANANANANANANANANA 23N5W3 188 648496 ahamlin Tazewell 640500 syckamore30S66W50NANANANANANANANANANANANA 5N2E4 144 884 wtintor Fulton 400140 wo10S75W114NANANANANANANANANANANANA 5N2E4 140 820 wtintor Fulton 500140 wo10S75W114NANANANANANANANANANANANA

People and Organizations

Creators:

Individual:	Dr. Jason McLachlan
Organization:	University of Notre Dame

Contacts:

Individual:

Dr. Jody Peters

Organization:

University of Notre Dame

Email Address:

peters.63@nd.edu

Individual:	Dr. Jason McLachlan
Organization:	University of Notre Dame

Temporal, Geographic and Taxonomic Coverage

Temporal, Geographic and/or Taxonomic information that applies to all data in this dataset:

Time Period

Begin:

1804

End:

1849

Geographic Region:

Description:

Midwestern United States, Illinois

Bounding Coordinates:

Northern:	42.34	Southern:	36.52
Western:	-91.37	Eastern:	-87.25

Taxonomic Range:

Classification:

Rank Name:

Genus

Rank Value:

Acer

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Maple

Classification:

Rank Name:

Genus

Rank Value:

Aesculus

Classification:

Rank Name:	Species
Rank Value:	glabra
Common Name:	Buckeye

Classification:

Rank Name:

Genus

Rank Value:

Betula

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Birch

Classification:

Rank Name:

Genus

Rank Value:

Carpinus

Classification:

Rank Name:	Species
Rank Value:	caroliniana
Common Name:	Ironwood

Classification:

Rank Name:

Genus

Rank Value:

Carya

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Hickory

Classification:

Rank Name:

Genus

Rank Value:

Celtis

Classification:

Rank Name:	Species
Rank Value:	occidentalis
Common Name:	Hackberry

Classification:

Rank Name:

Genus

Rank Value:

Cornus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Dogwood

Classification:

Rank Name:

Genus

Rank Value:

Fagus

Classification:

Rank Name:	Species
Rank Value:	grandifolia
Common Name:	Beech

Classification:

Rank Name:

Genus

Rank Value:

Fraxinus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Ash

Classification:

Rank Name:

Genus

Rank Value:

Gleditsia

Classification:

Rank Name:	Species
Rank Value:	triacanthos
Common Name:	Locust

Classification:

Rank Name:

Genus

Rank Value:

Juglans

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Walnut

Classification:

Rank Name:

Genus

Rank Value:

Juniperus

Classification:

Rank Name:	Species
Rank Value:	virginiana
Common Name:	Cedar/juniper

Classification:

Rank Name:

Genus

Rank Value:

Liquidambar

Classification:

Rank Name:	Species
Rank Value:	styraciflua
Common Name:	Sweet gum

Classification:

Rank Name:

Genus

Rank Value:

Liriodendron

Classification:

Rank Name:	Species
Rank Value:	tulipifera
Common Name:	Tulip poplar

Classification:

Rank Name:

Genus

Rank Value:

Morus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Mulberry

Classification:

Rank Name:

Genus

Rank Value:

Nyssa

Classification:

Rank Name:	Species
Rank Value:	sylvatica
Common Name:	Black gum

Classification:

Rank Name:

Genus

Rank Value:

Ostrya

Classification:

Rank Name:	Species
Rank Value:	virginiana
Common Name:	Ironwood

Classification:

Rank Name:

Genus

Rank Value:

Pinus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Pine

Classification:

Rank Name:

Genus

Rank Value:

Platanus

Classification:

Rank Name:	Species
Rank Value:	occidentalis
Common Name:	Sycamore

Classification:

Rank Name:

Genus

Rank Value:

Populus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Poplar

Classification:

Rank Name:

Genus

Rank Value:

Prunus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Cherry

Classification:

Rank Name:

Genus

Rank Value:

Quercus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Oak

Classification:

Rank Name:

Genus

Rank Value:

Salix

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Willow

Classification:

Rank Name:

Genus

Rank Value:

Taxodium

Classification:

Rank Name:	Species
Rank Value:	distichum
Common Name:	Bald cypress

Classification:

Rank Name:

Genus

Rank Value:

Thuja

Classification:

Rank Name:	Species
Rank Value:	occidentalis
Common Name:	Cedar/juniper

Classification:

Rank Name:

Genus

Rank Value:

Tilia

Classification:

Rank Name:	Species
Rank Value:	americana
Common Name:	Basswood

Classification:

Rank Name:

Genus

Rank Value:

Ulmus

Classification:

Rank Name:	Species
Rank Value:	spp
Common Name:	Elm

Project

Parent Project Information:

Title:

Paleo-ecological Observatory Network (PalEON)

Personnel:

Individual:

Jason McLachlan

Address:

100 Galvin Life Sciences,

Notre Dame, IN 46615 USA

Phone:

(574) 631 1850 (voice)

Email Address:

jmclachl@nd.edu

Role:

Lead PI

Individual:

Jody Peters

Address:

100 Galvin Life Sciences,

Notre Dame, IN 46615 USA

Email Address:

peters.63@nd.edu

Role:

Co - Information Manager

Abstract:

PalEON (the PaleoEcological Observatory Network) is an interdisciplinary team of paleoecologists, ecological statisticians, and ecosystem modelers. Our goal is to reconstruct forest composition, fire regime, and climate in forests across the northeastern US and Alaska over the past 2000 years and then use this to drive and validate terrestrial ecosystem models. We will develop a coherent spatiotemporal inference framework to quantify trends and extreme events in paleoecological and paleoclimatic time series. Variables such as forest composition, fire regime, and moisture balance will be inferred from corresponding paleoecological proxies, with rigorous estimates of uncertainty.

These datasets will be applied to improve terrestrial ecosystem models in two contexts. First, we are developing specific data products, such as high- resolution settlement-era forest composition maps from witness tree and General Land Office data, that can be used to drive ecosystem models. PalEON will develop formal data assimilation tools that will allow the models we use to forecast on centennial scales to be informed by decadal- to centennial-scale data. Second, are developing data products for the purpose of model validation (e.g. fire-frequency reconstructions from sedimentary charcoal data). These long-term validation datasets will help us assess the ability of these models to capture past dynamics correctly, and will help us understand why their future projections are so divergent.

Funding:

This material is based upon work supported by the National Science Foundation under Grants #DEB-1241874, 1241868, 1241870, 1241851, 1241891, 1241846, 1241856, 1241930. Any opinions, findings, conclusions, or recommendations expressed in the material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.

Other Metadata

Additional Metadata

additionalMetadata
        |___text '\n    '
        |___element 'metadata'
        |     |___text '\n      '
        |     |___element 'unitList'
        |     |     |___text '\n        '
        |     |     |___element 'unit'
        |     |     |     |  \___attribute 'id' = 'chains'
        |     |     |     |  \___attribute 'multiplierToSI' = ' '
        |     |     |     |  \___attribute 'name' = 'chains'
        |     |     |     |  \___attribute 'parentSI' = 'meter'
        |     |     |     |  \___attribute 'unitType' = 'length'
        |     |     |     |___text '\n          '
        |     |     |     |___element 'description'
        |     |     |     |     |___text 'Surveyors used chains to measure distances.  1 mile is 80 chains. There are 100 links per chain. 1 chain equals 66 feet or 20.1 meters. 1 link equals 7.92 inches.'
        |     |     |     |___text '\n        '
        |     |     |___text '\n      '
        |     |___text '\n    '
        |___text '\n  '

Additional Metadata

additionalMetadata
        |___text '\n    '
        |___element 'metadata'
        |     |___text '\n      '
        |     |___element 'unitList'
        |     |     |___text '\n        '
        |     |     |___element 'unit'
        |     |     |     |  \___attribute 'id' = 'link'
        |     |     |     |  \___attribute 'multiplierToSI' = ' '
        |     |     |     |  \___attribute 'name' = 'link'
        |     |     |     |  \___attribute 'parentSI' = 'meter'
        |     |     |     |  \___attribute 'unitType' = 'length'
        |     |     |     |___text '\n          '
        |     |     |     |___element 'description'
        |     |     |     |     |___text 'Length of measure used by surveyors.  1 link = 7.92 inches.  100 links = 1 chain = 66 feet = 20.1 meters'
        |     |     |     |___text '\n        '
        |     |     |___text '\n      '
        |     |___text '\n    '
        |___text '\n  '

Additional Metadata

additionalMetadata
        |___text '\n    '
        |___element 'metadata'
        |     |___text '\n      '
        |     |___element 'description'
        |     |     |___text '\n                Publications: Paciorek et al. 2020. The forests of the midwestern United States at Euro-American settlement: spatial and physical structure based on contemporaneous survey data.INSERT BIOARCHIVE LINK. Code for the data processing and analyses can be found on GitHub: https://github.com/PalEON-Project/PLS_products.\n            '
        |     |___text '\n    '
        |___text '\n  '

Copyright 2024 Environmental Data Initiative. This material is based upon work supported by the National Science Foundation under grants #2223103 and #2223104. Any opinions, findings, conclusions, or recommendations expressed in the material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation. Please contact us with questions, comments, or for technical assistance regarding this web site or the Environmental Data Initiative. Please read our privacy policy to know what information we collect about you and to understand your privacy rights.

EDI is a collaboration between the University of New Mexico and the University of Wisconsin – Madison, Center for Limnology:

Data Package Metadata View Summary

Settlement Trees, Illinois Level 0

Data Entities

Data Table

Data Package Usage Rights

Keywords

Methods and Protocols

These methods, instrumentation and/or protocols apply to all data in this dataset:

People and Organizations

Temporal, Geographic and Taxonomic Coverage

Project

Parent Project Information:

Additional Metadata

Additional Metadata

Additional Metadata

Recently Added

Recently Updated

Data Package Metadata View Summary

Settlement Trees, Illinois Level 0

+/- Data Entities

Data Table

+/- Data Package Usage Rights

+/- Keywords

+/- Methods and Protocols

These methods, instrumentation and/or protocols apply to all data in this dataset:

+/- People and Organizations

+/- Temporal, Geographic and Taxonomic Coverage

+/- Project

Parent Project Information:

+/- Additional Metadata

+/- Additional Metadata

+/- Additional Metadata

Data Entities

Data Package Usage Rights

Keywords

Methods and Protocols

People and Organizations

Temporal, Geographic and Taxonomic Coverage

Project

Additional Metadata

Additional Metadata

Additional Metadata