You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 18, 2022. It is now read-only.
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.
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Discussion topic 4 for CIRN Webinar 12 February.
The text was updated successfully, but these errors were encountered: