DATA
Public Databases
In general, we try to publish data with papers as they come out, so for specific projects please look to publications for info about where to access data. Some public databases we have contributed to include the following:
the TRY plant trait database the EcoSIS spectral library |
UMBS AOP Data
In July/August of 2019 the NEON Airborne Observation Platform (AOP) collected data over the University of Michigan Biological Station (UMBS) as part of our NSF Macrosystems project. We did this through the NEON Assignable Asset program. If you have questions about the details of the process, please email Kyla to ask!
To access these data, first please read our data sharing agreement and data info page, here. We plan to update this after some initial results from our work are published, but overall this is ~1 TB of data, so it's difficult and probably unnecessary to host all of it for easy download. If you are thinking about projects to do with these data, you may be interested in our project table, which is accessible here. Our goal is to share these data with anyone who has a project that could use them, but to make sure there isn't tons of overlap between projects (and to encourage collaboration!)
Finally, to get a sense of where the data were collected, you can access a .kml file here (open in Google Earth) to see each individual flightline.
Below are some quick looks at the data and info (click on the images to read a brief explanation).
To access these data, first please read our data sharing agreement and data info page, here. We plan to update this after some initial results from our work are published, but overall this is ~1 TB of data, so it's difficult and probably unnecessary to host all of it for easy download. If you are thinking about projects to do with these data, you may be interested in our project table, which is accessible here. Our goal is to share these data with anyone who has a project that could use them, but to make sure there isn't tons of overlap between projects (and to encourage collaboration!)
Finally, to get a sense of where the data were collected, you can access a .kml file here (open in Google Earth) to see each individual flightline.
Below are some quick looks at the data and info (click on the images to read a brief explanation).
CODE
We publish most of our code with projects. Depending on the project we work either in R or Google Earth Engine (or both) with occasional detours into proprietary software.
We are not github superusers, but we do use this platform for some code sharing. Lab member github pages are listed below:
Kyla - https://github.com/kdahlin
Aaron - https://github.com/akamoske
Ryan - https://github.com/nagelkirk
Other github users (ersam lab collabafriends) that might be of interest, depending on your applications, include:
Jean-Baptiste Feret - https://github.com/jbferet
Shawn Serbin - https://github.com/serbinsh
Annie Smith - https://github.com/AnnieCooper
Quentin Read - https://github.com/qdread
Adam Wilson - https://github.com/AdamWilsonLab
Phoebe Zarnetske - https://github.com/plzmsu
If you have questions about this or other projects where code is not obviously available, don't hesitate to ask the corresponding author!
We are not github superusers, but we do use this platform for some code sharing. Lab member github pages are listed below:
Kyla - https://github.com/kdahlin
Aaron - https://github.com/akamoske
Ryan - https://github.com/nagelkirk
Other github users (ersam lab collabafriends) that might be of interest, depending on your applications, include:
Jean-Baptiste Feret - https://github.com/jbferet
Shawn Serbin - https://github.com/serbinsh
Annie Smith - https://github.com/AnnieCooper
Quentin Read - https://github.com/qdread
Adam Wilson - https://github.com/AdamWilsonLab
Phoebe Zarnetske - https://github.com/plzmsu
If you have questions about this or other projects where code is not obviously available, don't hesitate to ask the corresponding author!