-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VBET Tweaks and Refinements - 8/16/2021 #381
Comments
Note that if we stick with the pixelated vectors then note that channel area vector will be smooth while 80 and 68 will be jagged. This affects the active floodplain feature class which will have a smooth donut and jagged exterior. |
Thanks a ton @philipbaileynar for the clarifications and fixes above. Perfect.
Understood and happy with that. |
All changes were made except for adding the centerline. The rasterized edges of the new polygons are throwing off the centerline method (the increased number of vertices is adding several hours to the processing time and the jagged edges are producing bad results). Will investigate... |
I approve of the decision to put centerlines on hold for now. Kelly, please close this issue and proceed to run the MHFD HUC for review by @joewheaton @lauren-herbine and @shelbysawyer |
Thanks for updates guys. @philipbaileynar lets discuss a strategy for the centerlines. I will start a new ticket to explore this. |
The two outstanding tasks here are already queued up in: Therefore I am closing this. |
On 8/16/21 @philipbaileynar, @shelbysawyer, @lauren-herbine and @joewheaton discussed latest version of VBET. This feedback was based on progress in https://github.com/Riverscapes/RiverscapesData/issues/19 and from #369.
My recollection was there were five things you wrote down (please elaborate as you and @KellyMWhitehead need to):
active_floodplain
(vbet_80 with channel areas cut out)inactive_floodplain
(vbet_80 with vbet_68 cut out)vbet_channel_area
Once these above tweaks are done, please have @KellyMWhitehead
The text was updated successfully, but these errors were encountered: