You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When @joewheaton and I were looking at the Custom VBET run for HUC 160102020701 (Summit Creek, UT), we noticed that the IGO layer seems to be having a display issue. Specifically, it appears offset, with many points displaying outside of the valley bottom extent. I'm flagging this along with a few other observations in the hopes that it's helpful for the curation of future custom runs. @jtgilbert tagging you, as I don't have assigning or labeling privileges in this repo.
Here are a few examples from Web Viewer:
Some additional observations:
This "offset" error did not occur when I opened the project in Q Viewer
The "Stream Names" and "Channel Network Level Paths" do not display in either viewer. This is likely because the drainage network was derived differently than standard Production Grade 3.1.0 runs.
The text was updated successfully, but these errors were encountered:
I'm guessing this has to do with something funky going on with projection in the Web viewer. This is (as far as I know) the first network model hosted that has data in a projected CRS.
The Problem
When @joewheaton and I were looking at the Custom VBET run for HUC 160102020701 (Summit Creek, UT), we noticed that the IGO layer seems to be having a display issue. Specifically, it appears offset, with many points displaying outside of the valley bottom extent. I'm flagging this along with a few other observations in the hopes that it's helpful for the curation of future custom runs. @jtgilbert tagging you, as I don't have assigning or labeling privileges in this repo.
Here are a few examples from Web Viewer:
Some additional observations:
The text was updated successfully, but these errors were encountered: