search

Coastal-Imaging-Research-Network / UAV-Processing-Toolbox

LEGACY - Use CIRN-Quantitative-Coastal-Imaging-Toolbox instead. Codes, documentation and discussion for the use of single stationary cameras and small drones for Argus-like sampling.
https://github.com/Coastal-Imaging-Research-Network/UAV-Processing-Toolbox/wiki/UAV-Processing-Manual
GNU General Public License v3.0
33 stars 28 forks source link

What is your level of use? How often do you use it? #82

Open mpalmsten opened 5 years ago

mpalmsten commented 5 years ago

Discussion topic 4 for CIRN Webinar 12 February.

burritobrittany commented 5 years ago

I typically download a copy of the toolbox and support routines and modify them for my needs and data structures. I don’t typically us the toolbox as is. I look into the routines and pull out methods and functions necessary for my purposes. Right now I just use it for stationary multi-camera stations, i.e. no image stabilization. I am a high level, but not ‘guru’ user with few years experience in georectifying images.

SRHarrison commented 5 years ago

I do something similar to burritobrittany. My fixed-video stations all use hotm to handle the video stream, which creates imageproducts and timestacks at the station level. What's left is establishing the geometry, and building the pixel instruments structure (r). All the tools are within the UAV-Toolbox, Support-Tools, and PIXel-Toolbox. But I typically custom make the tools I need for each site from components found within these toolboxes. I use these tools all the time - 'weekly'.

On the otherhand, I tend to use the cBathy-toolbox as is, with very little modification. Maybe feed in a site-specific waterlevel file and wave record, and maybe elevations of my hRefs if using a UAV.