Closed joewheaton closed 3 years ago
Hey @joewheaton, I've been looking into creating branches and working from those. I have made a VBET-bl-2 branch locally, but when I tried to publish the branch it's saying I don't have the right access to riverscapes/RaveAddIn. I could have sworn you guys had given me access. Any suggestions?
Let me try increasing your permissions
Thanks @philipbaileynar. Let me know what I can/need to do on my end.
Please try again @Cashe93
That seems to have worked. Thanks @philipbaileynar!
@joewheaton could you elaborate a bit more on 'Drainage Network should use same as Hydrography in RS_Context'? Did you want the contents of VBETs Drainage Network to match the contents of Hydrography from RS Context? i.e. same shapefiles, labeling and symbology?
@joewheaton I just submitted a pull request. I've placed the symbology layers for the intermediate thresholds in the VBET symbology folder (within the VBET-bl-2 branch).
Sorry for slow reply @Cashe93 ... been slammed.
@joewheaton could you elaborate a bit more on 'Drainage Network should use same as Hydrography in RS_Context'?
I just mean to copy the same business logic over. We have the same files for the network in both places, so might as well just bring in those business logic nodes under the Hydography:
.
Did you want the contents of VBETs Drainage Network to match the contents of Hydrography from RS Context? i.e. same shapefiles, labeling and symbology?
Exactly. And those layer files can just be moved into Shared.
Hey @joewheaton, how do I request a review on changes I've made to a branch with an existing pull request?
@joewheaton could you elaborate a bit more on 'Drainage Network should use same as Hydrography in RS_Context'? Did you want the contents of VBETs Drainage Network to match the contents of Hydrography from RS Context? i.e. same shapefiles, labeling and symbology?
Exactly. You should have same fcode so should be able to just copy business logic over from RS Context and just point to correct node.
I think (not sure) this is done? Please take a look @Cashe93
Yes @joewheaton, it looks like this task was completed back in June.
The Problem
We need to update the VBET business logic to be more consistent with the Riverscape Context. Special care should be made to use symbology keys that are common and in
Shared
, and to use consistent labels. Namely:This will be iterative. Try some things, post them here for me to give you feedback on and make as separate commits to a VBET-bl-2 branch you create.