TADAShiny provides a user interface (https://owshiny-dev.app.cloud.gov/tada-dev/) on top of the TADAPackage (https://github.com/USEPA/TADA). This application can be used to compile and evaluate Water Quality Portal (WQP) data for samples collected from surface water monitoring sites on streams and lakes.
In 2012, the WQP was deployed by the U.S. Geological Survey (USGS), the U.S. Environmental Protection Agency (USEPA), and the National Water Quality Monitoring Council to combine and serve water-quality data from numerous sources in a standardized format. The WQP holds over 420 million water quality sample results from over 1000 federal, state, tribal and other partners, and is the nation's largest source for single point of access for water-quality data. Participating organizations submit their data to the WQP using the EPA's Water Quality Exchange (WQX), a framework designed to map their data holdings to a common data structure.
TADAShiny (Module 1: Data Discovery and Cleaning) retrieves data from the WQP, and runs it through a series of data discovery, wrangling, and cleaning steps. Features include WQP data retrieval, flagging invalid results and metadata using validation reference tables, harmonization of synonyms, result and depth unit conversions, censored data substitutions, dataset filtering, and data visualizations. Users will be able to review and download summary information about their dataset, along with a data file and that is ready for additional manual review and use in subsequent analyses. Users make all decisions using the app to flag data for removal or keep data depending on its quality and relevance for their analysis.
More about the EPA TADA Project
You can install and run the development version of TADAShiny from GitHub by running:
if(!"remotes"%in%installed.packages()){
install.packages("remotes")
}
remotes::install_github("USEPA/TADAShiny", ref = "develop", dependencies = TRUE)
TADAShiny::run_app()
This repository also has devcontainers to allow it to run in GitHub codespaces. To use those:
- Fork the repository to your account
- In the "Code" button on the upper right of your browser, within the Codespaces tab click on the three dots and choose "New with Options", then you will have the choices:
- R Studio Server (the default useful for coding; you should set the RSTUDIO_PASSWORD with this option)
- Shiny apps for demos (useful for training or demoing)
- To stop or delete your codespace when you are done: go to GitHub Codespaces
Please visit the North American Lake Management Society (NALMS) Shiny Apps site to access other R Shiny applications that you may find useful (https://nalms.shinyapps.io/NALMS_Shiny_Home/), and for information on how to develop R Shiny Applications (https://nalms.shinyapps.io/Shiny_for_Water_Resources/).
This site has been created to be a resource for both those who are interested in learning how to create Shiny apps and those who are already experienced with making apps but want to see what other people are doing and what tools and packages are available for the community to use. It was created as a companion to the 2023 National Monitoring Conference, with the goal that it be used beyond that event and be useful to anyone who is interested in this topic.
The NALMS shinyapps.io service also provides a place for the water resources community to make their Shiny Apps readily available to the public. It is free for anyone to use. If you would like to submit a Shiny App for deployment of the NALMS shinyapp.io service, please follow the directions on the "Submit a Shiny App" page.
Effective August 8, 2016, the OMB Mandate: M-16-21; Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software applies to new custom-developed code created or procured by EPA consistent with the scope and applicability requirements of Office of Management and Budget's (OMB's) Federal Source Code Policy. In general, it states that all new custom-developed code by Federal Agencies should be made available and reusable as open-source code.
The EPA specific implementation of OMB Mandate M-16-21 is addressed in the System Life Cycle Management Procedure. EPA has chosen to use GitHub as its version control system as well as its inventory of open-source code projects. EPA uses GitHub to inventory its custom-developed, open-source code and generate the necessary metadata file that is then posted to code.gov for broad reuse in compliance with OMB Mandate M-16-21.
If you have any questions or want to read more, check out the EPA Open Source Project Repo and EPA's Interim Open Source Code Guidance.
All contributions to this project will be released under the CCO-1.0 license file dedication. By submitting a pull request or issue, you are agreeing to comply with this waiver of copyright interest.
This United States Environmental Protection Agency (EPA) GitHub project code is provided on an "as is" basis and the user assumes responsibility for its use. EPA has relinquished control of the information and no longer has responsibility to protect the integrity, confidentiality, or availability of the information. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by EPA. The EPA seal and logo shall not be used in any manner to imply endorsement of any commercial product or activity by EPA or the United States Government.
If you have any questions, please reach out to the TADA Team at [email protected].