innovate-inc / enviroatlas Goto Github PK

From the table of contents, a user should be able to link to the REST endpoint, metadata and fact sheet for each layer.

This is equivalent to the old "identify tool" functionality. Probably needs to be part of table of contents, driven by the TOC JSON.

From the table of contents a user should be able to dynamically change the symbology and of any layer (should this also include layers added/uploaded by the user at runtime?).
There should be existing code that we can reuse for this, but whether that is practical to integrate into the TableofContents (as in the standard ArcGISOnline viewer), or whether it might better exist as a standalone widget is worth discussing.

• Widget will work only with core Enviroatlas layers, not ancillary or added layers
• Widget will initially inherit and display default symbology from map service, and allow user to reset to this default.
• Widget will allow 5 options for "classification": Natural Breaks, Equal Interval, Standard Deviation, Quantile, and Manual.
• User will be able to specify the number of classes between 1 and 10.
• Widget will show a simple histogram showing the distribution of the data.
• User will be able to edit the min and max values and use sliders to adjust class breaks.

Initialize repository with base template from WebAppBuilder 1.2.

The goal is to be able to split a service by scales, so small scales can be cached and large scales dynamic, but to the user it all appears as a single entry in the table of contents.

Travis Bock has implemented this in another interface (non-WAB) and might have some insight.

Leaving issue unassigned for now - will assign at later point when we're ready to get started. Reference issue #13 for background information.

Will start with legacy text.

Per discussion 11/12.
Be careful of leading zeros on HUC IDs.

This looks like it was a fantastic reusable Flex widget - if no equivalent exists, assign ticket to Barb for a decision about priorities - there's a widget included in the WAB by default that will grab the coordinates for a single point, but the old Flex widget had all sorts of other functions - we'll want to unpack these and discuss whether they're used by the EA community.

The COTS geographic search functionality in WAB seems comparable to the legacy flex application. Is this adequate or was there some discussion about searching within the data, which might require something like rscheitlin's "Enhanced Search Widget"
https://geonet.esri.com/docs/DOC-1731
Much more complex, not so user-friendly. If I remember correctly, there was less interest in searching the data (which is mostly numeric) as in searching for available layers. If that is the case, it seems to make most sense to stick with the base search functionality (for locations), and then embed a subject matter/layer content search tool within the TOC widget. Barb, can you confirm?

is there some sort of session time out? let's investigate.

Search should include layer titles, descriptions, categories, subcategories, and communities.

Load and display layers from config file in some presentable table.

Two presented TOCs (search tool and filter) have been combined into one larger TOC - both functions were presented as the "look" users would like. ii. 4 basic panels: select geography, select data categories, select subcategories (sometimes hidden), and layer list. Select multiple communities,icons grayed or color depending on status. Refer to mockup pdf for proposed look and feel. This is a huge amount of functionality, hopefully it can be broken down into more discrete tasks. Possible subtasks:

• design JSON schema to track all necessary information
• add embedded legend
• add search functionality
• add faceted filter functionality based on data categories, subcategories, and community
• add clear-all-layers functionality
• in-context help

See how we can control this and prevent it.

User would like to be able to display two different maps side-by-side, with navigation linked/synchronized. Would need to design UI to link table of contents to both maps.

Charting tool displaying HUC data. Port directly from Flex, or explore other off-the-shelf charting widgets?

Develop tool that allows data extraction. Need to decide how clips can be performed:

• Bounding box
• Custom (hand drawn) polygon
• Selected features
• Uploaded polygon
• Attribute filter
  Esri sample code required very specific setup of data and geoprocessing service that might be challenging to incorporate into EA, depending on the reorg of the map services, so might have to explore options.

To explore code based seamless switch between cached and non-cached.

For potential discussion

Combine graphics and develop address schema

Data categories, subcategories, and communities should all be available filters.

Two presented TOCs (search tool and filter) have been combined into one larger TOC - both functions were presented as the "look" users would like. ii. 4 basic panels: select geography, select data categories, select subcategories (sometimes hidden), and layer list. Select multiple communities,icons grayed or color depending on status. Refer to mockup pdf for proposed look and feel.

Decide on a standard set of map settings that the application can set at startup (map extent, active layers, customized symbology, added data?) and allow all of them to be saved to a user's desktop as a .json file that the user can reload the next time they visit the site. Once this functionality has been created, it should be just as easy to enable it as REST parameters, so that someone could create a URL link directly to a specific view.

Add any useful widgets to EPA WAB Repo.

Low priority, but need to make sure it happens.

Options should include "Map Description", "Data Fact Sheet", "Access Web Service", and "Metadata/Download". All of the appropriate links should be embedded in export from spreadsheet (issue #35)

Confirm that COTS navigation widget meets all needs.

Either as a theme or widget - investigate.

The default overview map seems adequate. Can we accept it as-is?

COTS functionality, tracking as standalone issue.

Synchronize any changes with Master branch.

I believe Vincent's widget is most of the way there:
https://github.com/USEPA/AddLayerFromWeb-widget-js
Though in his readme, it seems like there might be issues with how it interacts with our TOC. Let's leave this issue open until the TOC matures some.

Details in WABOT repo.

Use as exercise to become familiar with creating a branch, checking out the code, adding the widgets and submitting pull request.

We can probably start with the bland/generic print service here:
http://geopub.epa.gov/arcgis/rest/services/Utilities/PrintingTools/GPServer
and discuss whether we want a custom EnviroAtlas template.

Share in new scripts folder.

This is mostly a placeholder issue - users desired extensive help (static help, video tutorials, or even the site itself seeming to animate and automagically demonstrate functionality). We should evaluate options for these features when the site is more mature.

This should be straightforward COTS functionality, but tracking as an issue to capture any tweaks.

Use background information from #6, coordinate with Brad Cooper at Indus ([email protected]) to be sure there isn't a parallel effort.

This functionality exists in the JS API, I can't remember seeing it in a WAB, might have to roll our own.

Widget? Possible in a reliable cross-browser way, or should we postpone this until HTML5 is adopted more broadly.

Right now all the layers load with the box checked "on", even though the config file says visibility: false. Figure out why and correct.

Ensure it's in the repository.

@David-Yarnell should have the latest code. Please use a new branch.

Use background info from #5