Symbology for All Layers in LTPBR Design Project Type

joewheaton commented 3 years ago

Specification

Project Type: LTPBR Design Project Type Layer(s):

Zone of Influence - Polygon
Complex Footprint - Polygon
Structures (as points or polyline crests)

Description and/or Explanation of Need

Just a container for LTPBR designs to be typically populated in QRiS

Example(s) of Inspiration

See fmLTPBR

To-Do

[ ] Start new branch called LTPBR_Design for these changes
[ ] Make necessary edits to business logic and commit to new branch
[ ] Author *.qml for QRAVE of layer(s) and test in QRAVE and commit
[ ] Produce screen shot of each qml layer to provide in commit or later pull request for reviewer (include legend). Also, provide warehouse link to riverscape project you did testing on (use same project(s) for testing ArcRAVE and WebRAVE)
[ ] Make pull request for just QRAVE changes. Choose appropriate reviewer(s)
[ ] Author *.lyr for ArcRAVE of layer(s) and test in ArcRAVE and commit
[ ] Make pull request for just ArcRAVE changes. Choose appropriate reviewer(s)
[ ] Produce screen shot of each lyr file to provide in commit or later pull request for reviewer (include legend)
[ ] Author symbology files for WebRAVE and provide link in commit to webRAVE of project it can be tested on
[ ] Make pull request for just WebRAVE changes. Choose appropriate reviewer(s)
[ ] Author or Update any project type documentation
[ ] Update or Add Project Views to Reflect Changes (if necc.)
[ ] After pull request(s) merged, test in updated qRAVE
[ ] After pull request(s) merged, test in updated ArcRAVE
[ ] After pull request(s) merged, test in updated WebRAVE
[ ] Delete local branch(es) you used for your pull request(s)

joewheaton commented 3 years ago

@nick4rivers please try to prioritize this next week. and delegate to @CHafen as you see fit. I changed milestone.

joewheaton commented 3 years ago

@MattReimer I think what happened was over here I was showing @nick4rivers how these templates worked and one of us just clicked on the create issues. I am closing each for now. @nick4rivers these tasks all need to get done still and we can just create them as sub-issues if necessary to add more detail.

joewheaton commented 3 years ago

@nick4rivers please prioritize this one. You need to be doing this anyway for integration with QRiS. This will be pretty tight and simple.

joewheaton commented 2 years ago

@nick4rivers please work with @CHafen on this one. Reminder...

nick4rivers commented 2 years ago

@joewheaton There is still a lot of refinement on the structure of a design that needs to happen on this. These decisions need to be made with more than just myself. You and others and Anabranch are very opinionated about the data structure that defines a design.

Riverscapes / RiverscapesXML