Data Package Metadata   View Summary

Settlement Trees, Southern Michigan Level 0

General Information
Data Package:
Local Identifier:msb-paleon.30.1
Title:Settlement Trees, Southern Michigan Level 0
Abstract:

We provide a Level 0 record of trees from 41 counties in the southern two-thirds of Michigan's Lower Peninsula 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:
1816
End:
1907

People and Organizations
Contact:Peters, Jody (University of Notre Dame) 
Creator:McLachlan, Jason (University of Notre Dame)
Creator:Williams, John W (University of Wisconsin)
Associate:Goring, Simon (University of Wisconsin, Content Provider)
Associate:Cogbill, Charlie (Harvard Forest, Content Provider)

Data Entities
Data Table Name:
PLS_southernMichigan_trees_Level0_v1.0.csv
Description:
Southern Michigan Public Land Survey Tree Records
Detailed Metadata

Data Entities


Data Table

Data:https://pasta-s.lternet.edu/package/data/eml/msb-paleon/30/1/ba786b9a29528a1d02de9af73bc8231d
Name:PLS_southernMichigan_trees_Level0_v1.0.csv
Description:Southern Michigan Public Land Survey Tree Records
Number of Records:29278
Number of Columns:39

Table Structure
Object Name:PLS_southernMichigan_trees_Level0_v1.0.csv
Size:5503638 byte
Text Format:
Number of Header Lines:1
Record Delimiter:#x0A
Orientation:column
Simple Delimited:
Field Delimiter:,

Table Column Descriptions
 
Column Name:FID  
species1  
diam1  
q1  
az1  
az1_360  
dist1  
species2  
diam2  
q2  
az2  
az2_360  
dist2  
species3  
diam3  
q3  
az3  
az3_360  
dist3  
species4  
diam4  
q4  
az4  
az4_360  
dist4  
uniqueID  
year  
good  
notes  
point_x  
point_y  
town  
range  
twnrng  
quad  
county_num  
county_name  
sec_corner  
cornertype  
Definition:Arc GIS identification numberTree 1 taxa abbreviation from the mylar maps. A conversion table for species 1 to Level 3a PalEON taxon can be found in the GitHub repository: https://github.com/PalEON-Project/PLS_products.Diameter of tree 1 in inchesThe Quadrant where tree 1 is located (Values typically are 1-4 - see how the quadrant is used to caluclate the az_360 values below. However, there are 998 q1 values of 0 and one q1 value of 5.)Azimuth from the mylar maps for tree 1Azimuth that takes into account the quadrant tree 1 is in. e.g., if the quadrant number was 1, the AZ as read from the mylar maps was used as is. If the quadrant number was 2, az1_360 is 180-az1. Quadrants of 3 were 180+az1 and quadrants of 4 were 360-az1. NOTE: Missing azimuths are listed as "0” in az1_360. Here is Charlie Cogbill's decision tree when he was determining the az1_360: "I have used a decision tree for southern Michigan: which goes as follows: if cardinal alphabetic directions (E, S, W, N) are given with no azimuth they are converted to 90, 180, 270, 360 bearings (note N is 360 not 0 which is a hard zero for no recorded direction of any kind). If two alphabetic directions are given with no azimuth (NE, SE, SW, NW either together or in azimuth columns 1,3) these are retained and a 45 azimuth is inserted between them. If one of these ordinals is missing with an azimuth, a logical substitution (correct typos, complete quadrants or put on same side for external corners or opposite side for internal corners) is inserted. A 0 azimuth (soft 0) with cardinal directions is accommodated as above. A 0 ordinal direction is problematic, but follows as above. Azimuths below 0 are converted to positive values and the quadrant remains as indicated by alphabetic direction. Azimuths of 90 are converted to cardinal (E or W) bearing. Azimuths above 90 are checked for obvious typos --double numbers, sticky finger (adjacent numbers on keyboard)-- and corrected. If two alphabetic directions are given in a logically consistent quadrant and the azimuth is still greater than 90, a 45 azimuth is substituted. Otherwise (seldom) the corner is ignored for quadrant or pair angle correction. If the azimuth is > 3 digits and distance is 0, the numerals are redistributed in the most parsimonious way. Also an observation for many of the negative values are 999 (or 888) azimuths, so these must be stripped before any calculation. Once the bearing is established a 360 azimuth is calculated as 0 + bearing for quadrant 1 (NE), 180 - bearing for quadrant 2 (SE), 180 + bearing for quadrant 3 (SW), 360 - bearing for quadrant 4 (NW), and 0 for everything else."Distance of tree 1 from the corner post in links (convert to meters by multiplying by 0.201168)Tree 2 taxa abbreviation from the mylar maps. A conversion table for species 2 to Level 3a PalEON taxon can be found in the GitHub repository: https://github.com/PalEON-Project/PLS_products.Diameter of tree 2 in inchesThe Quadrant where tree 2 is located (Values typically are 1-4 - see how the quadrant is used to caluclate the az_360 values below. However, there are 1924 q2 values of 0 and one q2 value of each 8 and 16.)Azimuth from the mylar maps for tree 2Azimuth that takes into account the quadrant tree 2 is in. e.g., if the quadrant number was 1, the AZ as read from the mylar maps was used as is. If the quadrant number was 2, az2_360 is 180-az2. Quadrants of 3 were 180+az2 and quadrants of 4 were 360-az2. NOTE: Missing azimuths are listed as "0” in az2_360. See the description az1_360 for Charlie's decision tree regarding the azimuths.Distance of tree 2 from the corner post in links (convert to meters by multiplying by 0.201168)Tree 3 taxa abbreviation from the mylar maps. A conversion table for species 3 to Level 3a PalEON taxon can be found in the GitHub repository: https://github.com/PalEON-Project/PLS_products.Diameter of tree 3 in inchesThe Quadrant where tree 3 is located (Values typically are 1-4 - see how the quadrant is used to caluclate the az_360 values below. However, there are 29229 q3 values of 0.)Azimuth from the mylar maps for tree 3Azimuth that takes into account the quadrant tree 3 is in. e.g., if the quadrant number was 1, the AZ as read from the mylar maps was used as is. If the quadrant number was 2, az3_360 is 180-az3. Quadrants of 3 were 180+az3 and quadrants of 4 were 360-az3. NOTE: Missing azimuths are listed as "0” in az3_360. See the description az1_360 for Charlie's decision tree regarding the azimuths.Distance of tree 3 from the corner post in links (convert to meters by multiplying by 0.201168)Tree 4 taxa abbreviation from the mylar maps. A conversion table for species 2 to Level 3a PalEON taxon can be found in the GitHub repository: https://github.com/PalEON-Project/PLS_products.Diameter of tree 4 in inchesThe Quadrant where tree 4 is located (Values are 1-4 - see how the quadrant is used to caluclate the az_360 values below. However, there are 29276 q4 values of 0.)Azimuth from the quad maps for tree 4Azimuth that takes into account the quadrant tree 4 is in. e.g., if the quadrant number was 1, the AZ as read from the mylar maps was used as is. If the quadrant number was 2, az4_360 is 180-az4. Quadrants of 3 were 180+az4 and quadrants of 4 were 360-az4. NOTE: Missing azimuths are listed as "0” in az4_360. See the description az1_360 for Charlie's decision tree regarding the azimuths. See the description az1_360 for Charlie's decision tree regarding the azimuths.Distance of tree 4 from the corner post in links (convert to meters by multiplying by 0.201168)This is a concatenation of the data from the four trees. It was originally used by Jody to find duplicate entries and before entries that needed checking were double checked. Use the data included in these concatenations to see what the orignal entries had been.These data came from the original file from U-W. Do not use these data to find the year the survey was conducted. The majority of year values are 0 (n=29274), then there are year values of 3,7, and 30.These are notes from the students that transcribed the data from the mylar maps to GIS. The “good” and “notes” attributes seem to go together. If there is an “n” in the “good” column, then there are comments in the “notes” column that describes why it was not good. There are also some comments in the “good” column that look more like general comments about the quality of the data/scan for that corner.See description regarding the “good” columnThe x-coordinate of the corner. Projection is NAD 1983 Great Lakes St Lawrence AlbersThe y-coordinate of the corner. Projection is NAD 1983 Great Lakes St Lawrence AlbersThe Township number and directionThe Range number and directionThe township label (township and range concatenated)The quadrangle map associated with this cornerThe county numberThe county nameLocation of the corner in the township. Intsec = corners on the interior of the township, Extsec = corners on the south and east borders of the township.Type of corner. Section (typically the surveyors set these at 80 chains or on the mile) or 1/4 Section corner (typically the surveyors set these at 40 chains or on the half mile).
Storage Type:                                                                              
Measurement Type:rationominalratioratioratioratiorationominalratioratioratioratiorationominalratioratioratioratiorationominalratioratioratioratiorationominalrationominalnominalratiorationominalnominalnominalnominalrationominalnominalnominal
Measurement Values Domain:
Unitdimensionless
Typewhole
DefinitionTree 1 taxa abbreviation from the mylar maps
Unitinch
Typewhole
Unitdimensionless
Typewhole
Unitdegree
Typewhole
Unitdegree
Typewhole
Unitlink
Typewhole
DefinitionTree 2 taxa abbreviation from the mylar maps.
Unitinch
Typewhole
Unitdimensionless
Typewhole
Unitdegree
Typewhole
Unitdegree
Typewhole
Unitlink
Typewhole
DefinitionTree 3 taxa abbreviation from the mylar maps.
Unitinch
Typewhole
Unitdimensionless
Typewhole
Unitdegree
Typewhole
Unitdegree
Typewhole
Unitlink
Typewhole
DefinitionTree 4 taxa abbreviation from the mylar maps
Unitinch
Typewhole
Unitdimensionless
Typewhole
Unitdegree
Typewhole
Unitdegree
Typewhole
Unitlink
Typewhole
DefinitionConcatenation of the original entries for the 4 trees. Do no use in analyses, use to assess how the data was checked and updated.
Unitdimensionless
Typewhole
DefinitionNotes from the students that transcribed the data from the mylar maps to GIS.
DefinitionSee description regarding the “good” column
Unitmeter
Typereal
Unitmeter
Typereal
DefinitionThe Township number and direction
DefinitionThe Range number and direction
DefinitionThe township label (township and range concatenated)
DefinitionThe quadrangle map associated with this corner
Unitdimensionless
Typenatural
DefinitionThe county name
Allowed Values and Definitions
Enumerated Domain 
Code Definition
CodeExtsec
Definitioncorners on the south and east borders of the township
Source
Code Definition
CodeIntsec
Definitioncorners on the interior of the township
Source
Allowed Values and Definitions
Enumerated Domain 
Code Definition
Codesection
DefinitionSection corner
Source
Code Definition
Code1/4 section
Definition1/4 section corner
Source
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)Michigan, 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 1816-1907 in Michigan. As described in Goring SJ, Mladenoff DJ, Cogbill CV, Record S, Paciorek CJ, Jackson ST, et al. (2016) Novel and Lost Forests in the Upper Midwestern United States, from New Estimates of Settlement-Era Composition, Stem Density, and Biomass. PLoS ONE 11(12): e0151935. doi:10.1371/journal.pone.0151935, "Michigan surveyor observations were transcribed to Mylar sheets overlaid on State Quadrangle maps, so that the points were displayed geographically, and then digitized to a point based shapefile (Ed Schools, pers.comm.; Great Lakes Ecological Assessment. USDA Forest Service Northern Research Station. Rhinelander, WI. http://www.ncrs.fs.fed.us/gla/)". Students, with the help of Simon Goring at the University of Wisconsin, Madison in the Williams lab transcribed the data from the Mylar maps to a GIS shapefile. That version 0.1 GIS shapefile was sent to Jody Peters at the University of Notre Dame where she worked with Charlie Cogbill to conduct a number of quality control checks which updated the data for southern Michigan.

Data Processing Steps going from the original file sent from UW through the final processing at Notre Dame (the final version number from the processing was 1.6, but the file was renamed as version 1.0 for the official archiving of the data pacakge msb-paleon.30) 1.Simon sent the so_michigan.shp which had 33,719 records (or corners). We updated the file to provide information for each corner on whether 1) corners were exterior on a township border or on the interior of the township, 2) labeled corners as ¼ section or sections corners, and 3) what county each corner was in. 2.Removed corners that were in the northern Michigan database that were already a part of the Upper Midwest Files. 3.Removed corners with identical tree data found at the same location (used the uniqueID attribute column to find corners with identical tree data). 4. Removed corners that were on the west border of townships 5.Charlie went through the data and made corrections when there were obvious errors such as when the data was shifted over a column. He also calcuated new azimuths for each tree (AZ1_360, AZ2_360, AZ3_360, AZ4_360) that incorporated information about the quadrant the tree was located in. So if the quadrant number was 1, the AZ as read from the mylar maps was used as is. If the quadrant number was 2 Charlie took 180-the WI AZ. Quadrants of 3 were 180+the WI AZ and quadrants of 4 were 360-the WI AZ. In the Azimuths Charlie also changed the “9999” standing for missing values to be “0”. NOTE from Charlie about the general QA/QC that has been done for the corners to the East of the Meridian in southern MI (that is any entry with with an "E" in the range column): First, if azimuth is missing -- 9999 or comment "missing", but not 0-- and the quadrant is known, a 45 bearing is inserted which preserves the quadrant and "averages" the bearing. If the bearing is >90, --usually double hits or overlapping fields-- the obvious typographical errors were corrected otherwise the corner is discarded. Second, trees >100" had numerals redistributed over clearly empty fields or the corner discarded. Third, all 0 bearings were scanned for notes in the comment field to assign cardinal directions, that is true 0 to 360 azimuths. Fourth --most importantly due to numerous large diameters up to 89" in Detroit region-- any tree with a remaining 0 bearing was assumed to have corrupted diameter and azimuth fields and the corner discarded. This is very conservative as bearing errors do not affect density, and diameter errors were eliminated for the least reason. 6. The final version of the data have 29,278 corners

Additional details can be found in the methods sections in: Paciorek et al., 2019, ADD TITLE AND BIOARCHIVE LINK. Code for the data processing and analyses can be found on GitHub: https://github.com/PalEON-Project/PLS_products.

People and Organizations

Creators:
Individual:Dr. Jason McLachlan
Organization:University of Notre Dame
Individual:Dr. John W Williams
Organization:University of Wisconsin
Contacts:
Individual:Dr. Jody Peters
Organization:University of Notre Dame
Associated Parties:
Individual:Dr. Simon Goring
Organization:University of Wisconsin
Role:Content Provider
Individual:Dr. Charlie Cogbill
Organization:Harvard Forest
Role:Content Provider

Temporal, Geographic and Taxonomic Coverage

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

Time Period
Begin:
1816
End:
1907
Geographic Region:
Description:41 counties in the lower 2/3 of Michigan's Lower Peninsula
Bounding Coordinates:
Northern:  44.375Southern:  41.125
Western:  -87.75Eastern:  -82.25
Taxonomic Range:
Classification:
Rank Name:Genus
Rank Value:Abies
Classification:
Rank Name:Species
Rank Value:balsamea
Common Name:Fir
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:Alnus
Classification:
Rank Name:Species
Rank Value:spp
Common Name:Alder
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:Castanea
Classification:
Rank Name:Species
Rank Value:dentata
Common Name:Chestnut
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:Larix
Classification:
Rank Name:Species
Rank Value:laricina
Common Name:Tamarack
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:Picea
Classification:
Rank Name:Species
Rank Value:spp
Common Name:Spruce
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: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:Tsuga
Classification:
Rank Name:Species
Rank Value:canadensis
Common Name:Hemlock
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' = '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  '

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

UNM logo UW-M logo