Canal Length (Vector) L16 - the symbology is loading, but the symbology breaks are not set well for the dataset. Blue colors hard to distinguish
Canal Density (Vector) L17 - the symbology is loading, but the symbology breaks are not set well for the dataset. Blue colors hard to distinguish
Road Crossing Count (Vector) L18 - the symbology is loading, but the symbology breaks are not set well for the dataset. Color ramp very hard to distinguish
Road Crossing Density (Vector) L19 - the symbology is loading, but the symbology breaks are not set well for the dataset. Color ramp very hard to distinguish
Diversion Point Count (Vector) L20 - the symbology is loading, but the symbology breaks are not set well for the dataset, and the colors are hard to distinguish.
Diversion Point Density (Vector) L21 - the symbology is loading, but the symbology breaks are not set well for the dataset, and the colors are hard to distinguish.
Intermediates/Land Use Intensity Raster tiling issue, not displaying in WebRave
Note if there is no railroad, canal, point of diversion in the watershed, the reach lines are just black. Maybe this isn't a issue with the model, but should be documented. The IGOs load with symbology.
Tested using HUC 1601010103 Yellow Creek v 0.2.0 & HUC 1009010210 Pumpkin Creek v 0.2.0
To-Do
Instructions for tasks:
delete those tasks not needed;
check off tasks as you complete them;
do not close issue until all tasks completed
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)
[ ] 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 WebRAVE
[ ] Delete local branch(es) you used for your pull request(s)
Specification
Project Type:
Anthro
Layer(s):https://github.com/Riverscapes/RiverscapesXML/blob/master/RaveBusinessLogic/V2/Anthro.xml
Description and/or Explanation of Need
Note if there is no railroad, canal, point of diversion in the watershed, the reach lines are just black. Maybe this isn't a issue with the model, but should be documented. The IGOs load with symbology.
Tested using HUC 1601010103 Yellow Creek v 0.2.0 & HUC 1009010210 Pumpkin Creek v 0.2.0
To-Do
Instructions for tasks:
#33
notation where 33 is issue number)*.qml
for QRAVE of layer(s) and test in QRAVE and commit