Rachel Ramirez 2018-02-21
1.1 Provide a short name (either a single word or an acronym) for the analytic you plan to develop. NPS National Park Service (NPS) acoustic summary data
1.2 Provide a brief title (1-2 sentences) describing – at the 50,000-foot level – what your analytic does. Your title should be short and to the point, but should also be clear to an end user: Interactive Visualizer for National Park Service Acoustic Summary Data
1.3 Provide a description (2-3 paragraphs) of why this analytic data product will be useful for an end-user. This description should address the following points (where applicable): There are many variables in the National Park Service acoustic summary data, thus many ways to do exploratory data analysis or visual analysis. Even if an end-user owns JMP or is an expert programmer, taking time to code and visualize all the different ways to view the variables will take a long time and the time spent coding is wasted when one can be easily manipulating the data interactively.
1.4 How will end-users access your analytic data product? End-users will access the NPS analytic via github or public webpage.
1.5 Are there any security concerns that need to be addressed? No security concerns need to be addressed.
1.6 Are there any appearance/design constraints that your analytic must adhere to? There are no known appearance or design constraints, however it would be nice if the data-analytic could adhere to the color-guidelines given in National Land Cover database for Land Cover Land Use Category Indicators. Those colors are provided by Red-Green-Blue schemes that may help an end-user visualize geographical data more easily.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.