-
Notifications
You must be signed in to change notification settings - Fork 5
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
Users cannot enter multiple HUCs or projects on import tab #190
Comments
I will need to
|
I am able to pull data using multiple HUCS. I tested using
I also cut-and-pasted your attempt - trying to use your 2 HUC codes, and found the fatal error. I think it has to do with the space in your list of HUCS. You have a space in there and that is crashing WQP. We can clean the user input by stripping spaces from the user input.
|
A similar issue is occurring with project but the comma is the problem here. Not sure yet if this one should be a semicolon "AK164406;AK538329" or separated "AK164406" "AK538329. I think the latter. $project Note: there was also an issue with entering multiple Characteristic and CharacteristicType but these have been resolved the same way as samplemedia and sitetype: |
@JamesBisese resolved the huc space issue (line 420 in mod_query_data_server: https://github.com/USEPA/TADAShiny/pull/191/files). |
I addressed the issue with projects here: #193 This issue can now be closed |
Describe the bug
On the import tab, users should be able to enter more than one HUC (separated by a semicolon, for example: "03010201; 02070010") . Currently, only one can be entered and if multiple are it will crash the application.
In theory, the WQP accepts multiple with each separated by a semicolon ; in the WQP UI, but I couldn't it to work there either. Example: https://www.waterqualitydata.us/#huc=03010201%3B%2002070010&startDateLo=01-01-2022&startDateHi=01-01-2023&mimeType=csv&dataProfile=resultPhysChem&providers=NWIS&providers=STORET
Expected behavior
Users should be able to enter multiple HUC's.
The text was updated successfully, but these errors were encountered: