In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is scheduled for retirement on January 27th, 2023. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact email@example.com. Thank you for your prompt attention to this matter.
Based on recent USGS guidance, will this call be moved off of Zoom to Teams?
Leslie: We are testing external participation now and will keep the CDI informed of tech choice. Anyone interested in testing or discussing further, get in touch with me!
Would you be able to see if you have any "surprising" new users as a result of the tool, or do you have ideas of how to learn if you do?
The package is not officially released on GitHub but we are working on it, and there will be a publication in Journal of Open Source Software. Hope we see people fork code, can incorporate user modifications back into the main branch. Hoping the user community picks this up and makes it into a bigger and better toolbox.
What was your process for identifying your main users and their needs?
Our center is part of a USGS network meant to work with natural resource management partners to help understand climate adaptation science. Work We have worked quite extensively with Fish and Wildlife Service and National Park Service over 7 years on supporting their science needs. Saw We saw inefficiencies in the workflow. Commonalities in , and commonalities existed in the data requested, but we were starting from the ground up whenever having we had to provide it. Anyone doing research across continental US can use it, so hoping to expand past initial stakeholders.
Is the climate reanalysis data included so that historical climate (and weather) can be downloaded too?
Yes, it can do historical and future comparisons.
Could you say more about the Journal of Open Source Software?
Open review process; way to release new tools that are allowing people access to new data. Write-ups for publication are pretty short; description of the package/software, what problem it solves, and how you are contributing (not doing something that is already done). Goes through peer review process and is released as a publication. Nice way to get the tool out to a broader community.
Is it possible to include a vignette that uses the software in a JOSS publication?
Will find that out and get back to you.
Is "edge computing" the same as "data proximate analysis"? Can you explain it a bit more?
No (don't know what data proximate analysis is). Edge computing is putting some sort of internet-connected device (like RaspberryPIs) at the edge, in the environment its meant to be in. Camera on the bank of a river. Phone , phone in your pocket, etc.
Can a user trigger the camera remotely? Or, based on water surface elevation?
Yes. You can trigger the RaspberryPI to record video based on an external trigger. If it's an internet-connected PI, you can query another streamgage or other sensor and trigger that way. In the process of testing some other methods.
How do you handle security with IoT? Are these RaspberryPIs protected since they have AWS credentials to upload the data? Is there a DMZ for video uploads?
We are developing a stig for RaspberryPIs. Enforce We enforce how people set up modems in the field so its it is unreachable from the outside world.
Are you using raspberri Pi camera?
Yes. We use many different cameras. Rely on security web cameras that are NDAA compliant cameras.
Can you elaborate a bit on Infrastructure as Code practices you're using for this IoT project? You mentioned that you had to create infrastructure first
Foundry is the infrastructure. Code is Python-based.
How many IoT RPis cameras are there. Do they provide constant video feed?
Two cameras enabled IoT. 20-40 connected cameras not on IoT.
Is that RPi stig available anywhere?
What happens to the video stream after processing? Is it archived somwheresomewhere?
You can do whatever you want with the video stream artifacts. That is up to the owner of the system.
Can you comment about any "disagreements" that came up on the submission form when you got input from your community?
Earliest iteration was just a CSV file, and more work would be done to vet data. Idea for pre-submission survey came up as input from the community. Lots of conversations about controls, that controls were in place, making sure we had questions that vetted the assay that was being run, making sure people were taking multiple samples from the field. Wanted to be as inclusive as possible, while maintaining a high level of quality.
Is the eDNA data being used to validate/reinforce other species detection/occurrence data in NAS?
Not specifically, but can work to the ability to do that. NAS does a lot of work to vet photos/data that come in.
can you talk a bit more about spatial controls? links to NHD?
This data layer is not going to be linked to anything, but this is one of the types of areas that might help to inform broader understanding of species distribution. We are interested in ways to pair eDNA with covariates.
Have you looked at how your community standard will translate to the biological data standard: Darwin Core?
Yes, they are similar. There's going to be a lot of overlap, and would like to make it overlap as much as possible.