1. Web App Integration Framework Exploration Team Included people from Hazards, National Map EA and CEGIS, Information Office, Water, Biology, Geology

2. What is needed to improve the Application Integration Experience Users are creating web views, adding services, studying in that view, zooming in, etc., but there is no way to port that view out to use in other views except re- doing it manually, sometimes requires developers or just creating new viewers – Scientists would like an easy way to save that context and open in ArcMap, Google Earth, Google Maps, other views Users in catalogs are searching, adding services manually one by one, but no easy way to one-click view in other views – Users of catalogs would like to open in something like The National Map, then could setup the context, then save in KML or MXD

3. Web Application Integration Framework Summary TNM Hooks – Save Current View Context as KML or MXD Function – Extend current View In Widget to support opening KML in Google Maps, Bing Maps, Specific OpenLayers ScienceBase Hooks – Add View Service or Context in ArcMap, Google Earth, The National Map Options – Support registering MXD, KML, Web Apps Coordinate with Other Viewers and catalogs if they want to use the new widgets

4. Decided out of scope For FY11, not recommending making Functions used in context easily to save and copy down – We do not believe technology direction is clear and ready to do it, but we recommend considering sharing/uploading function ZIPs/WARs, tagging as Product Readiness, and which APIs it supports Configuration-based Viewers for all APIs – felt not needed yet if viewers can just open KML files

5. Core Capabilities Catalog Register Types Format Saving Core Capabilities API Adapters JSON Config Google Earth KML OGC Context Google Map KML Discovery in Catalog “Re-Use” ArcObjects MXD Register Bookmarks Register MXD Register KML Register Gadget Code* Register Web URLs Register View In Widget (Context) Config Reader Clone/Save Config Bing Map Adapter (DHS) ESRI JS API (TNM Px3 Map Adapter (TNM) Flex Map Adapter (TBD) Google Map Adapter (TBD) OpenLayer Adapter (TBD) RJH Maps JS API Adapter (WRD) Save As “Port” Save As “Port” *For FY11, not recommending making Functions easy to clone – We do not believe technology direction is clear and ready to do it, but we recommend sharing/uploading function ZIPs/WARs, tagging as Product Readiness, and which APIs it supports Candidate Sites to Use The National Map – Px3 Data.gov View In Widget RJH Maps JS API Embed Sites Register Gadget Code* ScienceBase View In Widget and Port Register Styles/HTML Templates General Functions?* WMS ReProject Hooks WCS/WFS Hooks WebService Hooks TNM Toolbar? Download Framework Function Widgets (Server-Side)* Port GeoWeb API Hooks Port Function Principles Use Case Examples 1.Saving a Web View as MXD in one-click 2.Save KML in One-Click 3.Catalogs have a one-click open service or context in TNM Use Case Examples 1.Saving a Web View as MXD in one-click 2.Save KML in One-Click 3.Catalogs have a one-click open service or context in TNM National Atlas? ArcMap MXD (ArcObjects, TBD) ArcMap MXD (ArcObjects, TBD) DHS Bing? ANSS Mobile - Android App (TBD) View In Widget (BookMark) CDI Scope Proposed

6. Candidate Scope to Flush Out Core Capabilities – Reader, Save, View In, Save As/Port, Register, Function Widget Principles* API Adapters – TNM Px3, OpenLayers, Google, Bing, WRD JS, Flex Port Formats – GM KML, GE KML, WMC Context Profile, MXD Candidate Sites – TNM, WRD, DHS Bing, data.gov, Atlas, Candidate Use Cases – TBD Catalog New Register Types General Function