Licensed Quantity Tab (Highest #2)
- Dominant language
- Python
- Stars
- 5
- Forks
- 2
- Avg merge
- 3h 3m
- Merged PRs (30d)
- 8
Description
**As a** WALLY user **I want** the [Water Approval Points](https://catalogue.data.gov.bc.ca/dataset/water-approval-points) (aka Water Sustainability Act Approvals), Short Term Use (STU) Licenses (S10) quantity and Licence Application (Water Rights Application layer) demand included **so that** I am able to further analyze EFN (Environmental Flow Needs) risk, pre-application and post-application or make further adjustments as necessary.
**Additional Context**
- Would be highly beneficial to have an option to include an application volume (could be a blank box for someone to include their proposed monthly application volume, to compare before and after application demand in cumulative demand, and see associated EFN risk levels)
- As far as I’m aware this should have been in WALLY (especially b), and is a provincial layer. I’m unsure why this doesn’t show up, because it seems like it should. I will leave it up to your team to determine if this is an enhancement since it is unclear to me when the original WALLY team left and what they had been working on at that time (the EFN tab was in progress when WALLY staff left from my understanding).
- Would also like STU = Short Term Use included. Is tricky because it includes filtering, so less important



**Acceptance Criteria**
- [ ] Given a WALLY user accesses the Licensed Quantity tab, when they are provided with the Water Approval Points quantity and Licence Application demand, then they will be able to analyze and make further adjustments as necessary
Contributor guide
Research direction
No files or tests are named. Start by locating the Licensed Quantity tab and tracing how WALLY loads the Water Approval Points, STU Licenses, and Licence Application layers; review the existing EFN analysis flow before assessing the proposed application-volume input. Done means the tab exposes the requested quantities and demand so users can analyze and adjust EFN risk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100