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

Allow analyses and climate engine with AOIs and valley bottoms #561

Open
philipbaileynar opened this issue Jan 16, 2025 · 4 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@philipbaileynar
Copy link
Contributor

QRiS release 1.0.8 combines sample frames, AOIs and valley bottoms into a single feature class. This allows analyses to be applied to any one of these three feature classes, unlike before when it was limited to just sample frames.

The next step is to enhance the user interface to allow the user to pick an AOI or VB when creating an analysis.

  1. Include AOIs and VBs in the drop down where the user picks the Sample Frame. I'll talk to @joewheaton and discuss what the label should be. I suspect that he's going to say "Polygon Mask", in which case we change all related analysis user interface forms to consistently use the word "mask" where we currently have "sample frame". Regardless we can do the work to include the other polygon layer types in the dropdown.
  2. When the user picks a VB as the sample frame, we should probably do the following:
    • pre-select the same VB in the valley bottom dropdown.
    • lock the VB dropdown to prevent the user choosing a different one.
    • Remeber to unlock the VB dropdown if the user switches their selection to a different sample frame.
Image
@KellyMWhitehead
Copy link
Collaborator

Ready for version 1.0.9

@philipbaileynar
Copy link
Contributor Author

Please add the same ability for Climate Engine.

@philipbaileynar philipbaileynar changed the title Allow analyses with AOIs and valley bottoms Allow analyses and climate engine with AOIs and valley bottoms Jan 22, 2025
@KellyMWhitehead
Copy link
Collaborator

Added AOI and Valley Bottom to Climate Engine for 1.0.9.

Please note that large features (meaning large # of coordinates, e.g. huc boundaries) will still struggle with Climate Engine. I am working on some strategies to fix this.

@philipbaileynar
Copy link
Contributor Author

Yes, this is important. Please are going to try and use this feature with VBET polygons and other model outputs that have complex geometries. A solution for this is definitely needed.

Don't forget that many of the underlying Climate Engine data are 30m or coarser resolution. A bit of geometry simplification won't hurt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants