Check out the Webex Recording (Click Here) of this meeting or scroll through the meeting notes below.
- USGS/DOI Number: 703-648-4848 (for calls from a USGS/DOI office)
- Toll Free Number: 855-547-8255 (for calls from a telecommute location)
- Access Code: 47919# (same for both numbers)
(30 minutes) Matt Tricomi - The National Map: Save Map As, Firing it up for the tech stack group!
PRESENTATION THAT WILL BE USED
- FY11 Summary/Progress on the The National Map: Save As/Open In effort
- FY12 Proposal - Moving toward USGS Wide App Service
- Expanding Expand TNM Save As/Open In concept to USGS Wide - USGS Wide approach to Mashup Same Context File Demos of Open Mashup in other Viewers Preferrably OpenLayers, Flex, Silverlight and JS API Mashup reader developed for reuse
- Vet the TNM Concept, Discover issues for expanding, Explore JSON Context Scope , Explore Standardization Process
- Explore how have 1 Save As/Open In App service that USGS can use leveraging TNM efforts
- Looking for Web Viewer UI (Preferrably OpenLayers, Flex, Silverlight and JS API ) developers and management representatives from other USGS areas interested in
(20 minutes) Discussion of TSWG proposals to CDI, to be presented at the workshop
8-9-11 TSWG Call
Presentation from Matt Tricomi on Saving and Opening Mashups work completed in FY11 and FY12 proposal.
- There are numerous viewer technologies for generally viewing data.
- KML based (google maps, bing maps, openstreetmap, openlayers, etc.)
- Thick Clients (ArcMap, Google Earth)
- National Map (Palenterra x3 viewer via NGA)
- Target Vision:
- User starts viewing
- Maches up some data
- Save changes
- Export to a new viewer
- Open export in 1 click!
To do this we need a standard!
Demo of concept in Palanterra viewer.
- Context profile: a little configuration file that defines the base layers and map details you want to see when opening the context profile.
- Shows that a context profile can be set using a key value pair in a url.
- Shows similar map content in a flex viewer, and openlayers, and on arcGIS.com...
- All viewers have a different "context profile"
- Google uses kml
- Esri uses their json context
- Palanterra uses their json context
- NGA/Palanterra will be standardizing the base of their context with ESRI's but keeping the extensions that go beyond ESRI's.
- Shows existing configuration file for the palanterra viewer.
- Outlines vision for a "Save As Module" service for more than just the Palanterra TNM viewer.
- kml, mxd, image formats.
- Shows large slide with requirements. on meeting wiki page.
- mentions wiki documentation here: