-
Notifications
You must be signed in to change notification settings - Fork 3
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
How to handle different water rights amount search cases? #101
Comments
Good comment on should these two filters work on an AND, OR, or both query? This might be an issue of not tracking how, and the why, the states track water right data as either CFS or AF, or even both. Use cases that 'might' pop up in the future in the event somebody is searching for water rights...
Wonder if it's possible to add a AND / OR button between these two filters? |
Related to this issue, do the states provide the Volume of Flow value as "unknown," or is this introduced in the data mapping or importing? If the state does not provide the value, we need to keep it blank in our database. The "unknown" value might affect this WestDAAT filter as it compares numeric values logically. Rights with "unknown" values might be excluded because of this issuue. https://westdaat.westernstateswater.org/details/right/WYwr_WR10573?state=N4IgtgziBcIQhgFwKYBtUEsUFoBuBOEAGnHgAcZQAvAexrABllc0YBGABhNSSwFcAJshgAWAEwA6AMwAOfFIBsHZSuVtuNAHYBzfkJjZOCiWLZsZU1arEBfG0A |
Here is the WestDAAT code that has the min and max values for flow and volume. I'm not sure if there is an AND or even OR clause between these filters. It could be the "unknown" issue that is causing that behavior.
|
In another example in Utah, the Assigned Volume (AF) value is "0" |
We decided to design the flow and volume range filters to be simplisitic. In reality, there are many complex cases that we need the filters to handle as summarized in this table. We need to see how to support handling the AND OR cases
Use case: show me water rights that have a flow of more than 5 CFS or a volume of more than 7,000 AF. I think the current implementation handles the AND case, not the OR. What if the user wants to limit the search to the AND case?
Notes
SQL Query
This basic SQL query is a starting point to see the distribution of CFS and AF types of values across states
The text was updated successfully, but these errors were encountered: