A web app for exploring section 7 consultation data from the US Fish and Wildlife Service.
| Version | DOI |
|---|---|
| v1.0 |  |
| v2.0 |  |
| v3.0 |  |
Section 7 of the US Endangered Species Act directs federal agencies to use their authority to help conserve listed species. One way they do this is by consulting with the US Fish and Wildlife Service (FWS) and National Marine Fisheries Service to ensure the agency's action won't jeopardize the continued existence of a species, or destroy the species critical habitat. Many myths surround section 7 consultations; we got data on all consultations recorded by FWS since 2008 and analyzed it. The results have been released in Proceedings of the National Academy of Sciences, but because communicating results with broader audiences is a key component of improving policy implementation, we also made this Shiny app. We plan to update the data and the app on a regular basis and appreciate feedback that can improve either the code or the user experience.
21 Mar 2017: Version 3.0 of the app includes data for >10,000 new consulations and some minor UI tweaks.
13 May 2016: Version 2.0 of the app includes both new data (from March, 2015, through February, 2016) and UI tweaks.
While the app is available at shinyapps.io, you may clone this repository and run the app locally.
git clone git@github.com:Defenders-ESC/section7_explorer.git- Open either
ui.Rorserver.Rin RStudio then chooseRun Appor runRfrom a terminal and useshiny::runApp() - Explore.
We welcome bug reports and feedback. If you find a bug then submit an issue here.
If you want to propose a code change then submit a pull request. In general, read through the code base and use the app a bit, so you understand how the bits-and-pieces are connected. Then, if you would like to suggest a change or update to the project, please follow these steps:
- Open an issue to discuss your ideas with us.
- Please limit each pull request to less than 500 lines.
- Please encapsulate all new work in short functions (less than 50 lines each). We currently do not have unit tests for our functions (that will change!), but please include tests with the pull request.
- Please ensure all tests (new and old) pass before signing off on your contribution.
- Do something nice for yourself! You just contributed to this research, and we really appreciate you taking the time to check it out and get involved.
The most important step is the first one: open that issue to start a conversation, and we can offer help on any of the other points if you get stuck.
Thanks to Bill Mills for the great Contributing suggestions and for the pointers on adding release information to this README.