Skip to content
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

Symbology for VBET issues #666

Open
12 tasks
CHafen opened this issue Nov 17, 2023 · 2 comments
Open
12 tasks

Symbology for VBET issues #666

CHafen opened this issue Nov 17, 2023 · 2 comments
Assignees
Labels
symbology Use for new symbology work

Comments

@CHafen
Copy link
Contributor

CHafen commented Nov 17, 2023

VBET (Valley Bottom for Whychus Creek)
Centerline of valley bottom - no symbology for web

Symbology in Q and web don't match for:
Acres of Estimated Low-Lying Valley Bottom per Mile
Acres of Estimated Elevated Valley Bottom per Mile
Hectares of Estimated Low-Lying Valley Bottom per Kilometer
Hectares of Estimated Elevated Valley Bottom per Kilometer
acres_elevated_vb_perMile
acres_elevated_vb_perMileQ

Moving Window Analysis Distance - legends don't match for Q and web
moving_windows
moving_windowsQ

Transformed Slope Evidence - The color ramp in web is the opposite of what's in Q
transformed_slope
transformed_slopeQ

Valley Bottom Level Paths - just showing up grey in web.
VB_level_paths
VB_level_pathsQ

Channel Network Levelpaths - only the labels show up in web, no line for the stream

Instructions for tasks:

  1. delete those tasks not needed;
  2. check off tasks as you complete them;
  3. do not close issue until all tasks completed
  4. reference this issue in all commits (e.g. with #33 notation where 33 is issue number)
  • Start new branch with descriptive name for these changes (e.g. curation_Veg_RCAT)
  • 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 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 WebRAVE
  • Delete local branch(es) you used for your pull request(s)
@CHafen CHafen added the symbology Use for new symbology work label Nov 17, 2023
@CHafen CHafen self-assigned this Nov 17, 2023
@CHafen
Copy link
Contributor Author

CHafen commented Nov 28, 2023

@jtgilbert will give these a quick look over. I will work on fixing these issues. I'm going to assume the symbology in Q is the correct and that the Web symbology is incorrect unless I hear from you otherwise.

@jtgilbert
Copy link
Contributor

Sounds good @CHafen. I do see a couple potential non-issues here at first glance. In those first two figures you're comparing two different things (vb acres/mile and _elevated _ vb acres/mi, and then the transformed slope is the same ramp, just a different range)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
symbology Use for new symbology work
Projects
None yet
Development

No branches or pull requests

2 participants