October 14th, 2020: Serving the U.S. Geological Survey’s geochronological data, Rocky Mountain Science Exchange, and CDI Pop-Up Lab
The Community for Data Integration (CDI) meetings are held the 2nd Wednesday of each month from 11:00 a.m. to 12:30 p.m. Eastern Time.
Agenda (in Eastern time)
Times are approximate.
11:00 am Welcome and Opening Announcements - Leslie Hsu and Kevin T. Gallagher
11:15 am Collaboration Area Announcements
11:25 am Serving the U.S. Geological Survey’s geochronological data - Leah Morgan and Amy Gilmer, USGS
11:50 am Rocky Mountain Region Science Exchange - Alicia Torregrosa, USGS
12:10 pm CDI Pop-up Lab
Using Git - an interview - Richie Erickson, USGS
Remote Sensing Forest Classification for Timber Appraisal - Joe Adams, USGS
12:30 pm Adjourn
- CDI FY2021 Statements of Interest are due Friday, October 16th, at 5pm Eastern.
- Don't miss the SOI Lightning Presentation Session on Thursday, October 22nd, at 2pm Eastern.
- Welcome and Opening Announcements - Leslie Hsu and Kevin T. Gallagher
- Update on meeting the CDI community
- Used the entire CDI email list to look at job titles and expertise terms
- (see recording for word cloud)
- Kevin Gallagher
- Deadline for Statements of Interest for FY2021 are due this Friday, October 16, 5pm Eastern
- RFP themes are fire science and coastal resilience, but proposals with any topic are accepted
- SOI Lightning Presentation Session: Thursday, October 22, 2pm Eastern
- Join the comment and voting period, starting October 20
- Collaboration Area Announcements
- See full details on slides/recording, and on the collaboration area wiki page
- Software Development
- Next meeting 10/22, focusing on Agile, with presentations from Michelle Guy and Sophie Hou
- Data Visualization
- Next meeting 10/29, Data sketches with Nadieh Bremer
- See wiki for more info
- Next meeting 10/21, FY21 planning
- GeDWG 4th annual workshop has been announced (see eDNA wiki page)
- See wiki page for forum discussions and Mendeley group
- Released survey (RFI), looking for examples of the kind of work EarthMap represents
- NTK blog post went out yesterday
- Data Management Working Group
- Next meeting 11/9, BCO-DMO speakers on capturing provenance of data curation; frictionless data (more here)
- Risk CoP
- Annual Risk RFP is now open (more info here)
- 11/20 deadline for letter of intent
- 1/15 deadline for full proposal
- Theme: concurrent disruptions
- Next meeting 10/15, FY21 RFP Information session; using CoSMos for determining costs and benefits of adaptation strategies
- Next meeting 12/1, General Dynamics IT Division
- Serving the U.S. Geological Survey’s geochronological data - Leah Morgan and Amy Gilmer, USGS
- Project goal is to bring together and serve USGS geochronological data
- National Geochronological Database (NGDB) was last updated in the 90's. There is currently no central, integrated source for this data and new data.
- To serve this data, project team is:
- Working with collaborators to build a database in a Post-Gres SQL structure
- Populating the database with useful data
- 3 parallel approaches:
- Migrate data from old NGDB database
- NAGT USGS intern will manually input data from published literature, first with scientists nearing retirement
- Work with University of Kansas and geochron.org to build APIs to automatically populate data (new data releases as posted to SB)
- Database schema model built by Andy Park at Eastern Energy Resources Science Center (see slide)
- Schema captures info about each sample (material type, location information, temporal information, etc.)
- Schema also captures info about analysis/techniques
- Integrating data with the National Cooperative Geologic Mapping Programs Intermountain West Geologic Framework project
- Having geochronological data is essential to making comprehensive compilation work
- Integration of geochronology with geologic mapping
- Geochronological data with critical mineral studies (how it formed, looking for additional resources)
- Rocky Mountain Region Science Exchange - Alicia Torregrosa, USGS
- Objectives for the Rocky Mountain Science Exchange are exchange of knowledge, cross-center collaboration. 2020 goals were focused on drought, EarthMap and the creation of this new culture, and creating an online presence.
- RMR Science Exchange
- Held entirely on Teams
- 216 attendees and 37 science talks
- SharePoint site has all recordings
- ArcGIS online spatial catalog linked by StoryMap to participant entries
- Internal access only
- EarthMap set the stage
- Provided background information
- Included Office of Science Quality and Integrity initiatives
- Lightning talks and panel discussions focused on themes of EarthMap and drivers of landscape change
- Colorado River Basin use case presentations (EarthMap pilot project)
- These types of use cases are being solicited by EarthMap - submit if you have a use case.
- This pilot evaluates and predicts impacts of severe drought on earth system components.
- One objective was to gauge knowledge of EarthMap - participants in the workshop had a stronger understanding after workshop ended.
- CDI Pop-up Lab
- Using Git - an interview - Richie Erickson, USGS
- (see slide for full details)
- Git helps with version control (what got changed, when, and by who)
- Allows code to be put in the cloud
- Git is an open source tool that is free; there are also commercial vendors like GitLab
- Git project homepage has several nice video tutorials. Software carpentry also has nice tutorials.
- Richie has also gathered tutorials as a part of a CDI project. Come to the December CDI monthly meeting to learn more.
- CDI calls are a great spot to see what others are using.
- Remote Sensing Forest Classification for Timber Appraisal - Joe Adams, USGS
- (see slide for full details)
- Pain point: appraising land that has timber on it.
- FRASS (forest resource analysis system software)
- PoTree Viewer: https://uas.usgs.gov/outgoing/Visualizations/Warm_Springs_Stand_of_Trees_Test/
- Trimble presentation tomorrow
Questions & Answers
- Does the interaction with the National Geologic Map Database allow the Geolex data (geologic fm names) to join the geochron data?
- No, we have not integrated.
- Was there anything that was new or difficult ot fit into the schema based on newer ScienceBase Data releaseas?
- Flexible approach - schema will need to add info later
- Varying levels of info in new data vs old data
- Several levels of geochronological data; age for one sample or one formation (parent child relationships can incorporate all these data)
- Will guidance be released?
- Working with geochronologists who are actively collecting data - schema reflects data release structure. Will provide documentation to capture that information
- Do you have a tentative timeline for rolling out a publicly-accessible version?
- No timeline as of now.
- Are you keeping a link to the ScienceBase item in your database so if someone wants to get back to the original data they will be able to do so?
- Yes. Also keeping links for older publications that have been incorporated but do not have a ScienceBase data release
- Who can I contact at KSU (?) about the SB harvesting scripts?
- Working with Noah McClean in the geology department and Jason Ash
- Updates on the geochronological database effort?
- Contact Leah Morgan or Amy Gilmer
- Within next year, hope to have an interface begun through the National Geologic Mapping Database project
- Do we have access to the EarthMap SharePoint site and the primer video? If so, can we share the link in this chat or are the slides available some place?
- Yes. https://atthecore.usgs.gov/special-groups/earth-monitoring-analyses-and-prediction-earthmap
- RMR SharePoint: https://doimspp.sharepoint.com/sites/gs-rmr-scienceexchange487
- Do you have any tips for holding a large virtual meeting?
- Much more work than you think. Did not bring on IT support soon enough. Made heavy use of OneNote. ArcGIS Online and the Power Flow in O365 were useful. Did lots of dry runs to get everything working correctly. Challenge with overloaded Microsoft servers, so were encouraged to record the presentations with another program like Camtasia. The screen capture did not always work.
- Can you quickly cover using Git vs Jupyter? Pros/cons?
- Two different things. Git keeps track of code, can use with any plain text code. Jupyter is an interactive way to work with code. Jupyter = Microsoft Word; Git = SharePoint. Jupyter is part of the conda project, and they have their own way of sharing things.
- Is there a write-up anywhere of this RFP / need?ere a write-up anywhere of this RFP / need?
- Joe's post: https://teams.microsoft.com/l/message/19:email@example.com/1601482340361?tenantId=0693b5ba-4b18-4d7b-9341-f32f400a5494&groupId=8d63facc-9fdc-4c6e-9a32-9a4172553b46&parentMessageId=1601482340361&teamName=GS-CDI-CommunityForDataIntegration&channelName=Questions%20and%20Answers&createdTime=1601482340361
- Trimble link