July 2011 - Information Flow Review
August 2011 - Application Architecture Review
FY12 Continuation: Project Proposal to extend to look at USGS-wide adoption.
Discussion on how to approach at:https://my.usgs.gov/confluence/display/cdi/ESRI+REST+API+as+an+OGC+Specification
Total Funding Needed
Temporary Abstract/Planning Text (Dump from Etherpad Brain Dump session)
Expand TNM Save As/Open In to USGS Wide
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
Representatives from other USGS areas interested in Mashup Travel $ may be needed
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
Travel $ resources from other programs for devel time may be needed
See Save As/Open In project in CDI Wiki under Tech Stack
Ryan Zoerb, Rob Hollister (Nate Booth), Center for Integrated Data Analytics, Water%%Greg Smoczyk, Hazards
Rob Dollison, Matt Tricomi (Kevin Hope), Robert Djurasaj (David Hughes) National Geospatial Program, The National Map
RolandViger Modeling of Watershed Systems, National Research Program, Water
Sky Bristol and Scott McEwen_,|https://my.usgs.gov/confluencenull] Informatics and Data Integration
In FY10, Goal one focused on making it easier for ArcMap users to access Corporate databases. This was achieved by combining the recent service modernization of _The National Map (_TNM), and setting up Palette MXDs with all base geospatial layers from TNM Services pre-loaded along with Character of underlying rock units, and geochemical survey data (MRDATA), Biologigal GAP Land Cover (NBII), and denormalized Stream Flow information. As well, Hydrology build test Web API frameworks for easily adding/ setting up TNM Services in Water Web Application Viewers. %%
The FY10 goal of this would support scenarios such as bureau scientist studying multi-county region to locate sources of contaminants in water and soils.
In FY11, the team is proposing to continue supporting these two users – ArcMap and Web User – by combining the two user stories and automating the web transition to the heavy client. Supporting a user who is searching and exploring services on the web, mashing them up, and wanting to setup the same mashup context view in heavy clients like ArcMap or Google Earth with one-click and without needing technical support to do so.
Save in Single Click
Figure 1 - This continuation of FY10 Goal 1 and supporting scenario intends to deliver simpler usability for migrating contexts setup on the web with easy one-click saving and opening in the popular heavy clients of USGS users. As well, looking to save those contexts and make them registerable and thus searchable in key catalogs.*
Relevance and BenefitsFrom|https://my.usgs.gov/confluence/label/cdi/404040%7Dfrom] FY10 Goal 1:Well over a third of all USGS employees have access to or use enterprise GIS software. These scientists commonly and frequently overlay and integrate USGS collected or managed datasets to conduct their investigations within this GIS. Yet many corporate data systems within USGS do not provide ready and efficient access within a GIS environment.
Users|https://my.usgs.gov/confluence/label/cdi/404040%7Dusers] 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
1. Create|https://my.usgs.gov/confluence/label/cdi/404040%7Dcreate] Core Capabilities to Port Context Configurations in TNM Viewer to JSON, KML and MXD (.25 FTE)
2. Create|https://my.usgs.gov/confluence/label/cdi/404040%7Dcreate] ScienceBase “Catalog context” to test uploading and discovering the “web mashup context” (JSON, KML and MXD) (.1 FTE)
3. Create|https://my.usgs.gov/confluence/label/cdi/404040%7Dcreate] User Story Examples, Training for Objectives 1 and 2 (.2 FTE)
Total Level of Effort for Objectives: .45 FTE
*Level of Efforts estimates are unvalidated “swags”, based on general experience in these areas.
Click to see the User Stories
This goal is structured into five consecutive components and will be led by staff at CIDA in cooperation with Geography and the GIO.
Objective 1: Create Core Capabilities to Port Context Configurations in TNM Viewer to KML and MXD
First the Viewer would need port the services setup and/or turned on (users choice) to JSON – users setup already in the configuration, as well as the user added content. TNM Team recently did this for another service, so the effort to make this a module to be used in this case should be minimized (40)
Then the Port capability would read that JSON file and save as JSON, KML, MXD by performing the target format adapter call which would need to be developed. The KML portion will be coded by the Water team led by Rob Hollister and the MXD led by Gerg Smoczyk in Hazards, likely to be written in Python or VB.net. Since TNM will already be saving the JSON, that format will be available as well for those users as well. (100)
The TNM Viewer becomes a nice gathering point for users to create these mashups in given its current support of KML, RSS, WMS, REST, and IMS Services from a technology point of view, but more importantly, TNM investment of foundational is core to USGS as cross-foundational key topographical data. Re-opening JSON or KML in the TNM Viewer would include some extension to the current TNM “View In” capability to assure TNM can add 1 service at a time via the URI not only in KML and RSS (Today), but also as WMS, IMS, and REST.
As well, it would need to make sure context files can be opened from context files or other URLS not hosted on TNM and be compliant with security. The latter can be added manually, but is currently queued to be added in the URI. TNM would manage hosting the Porting capability, as a separate service, likely REST, and could be planned to be made prototype ready or ready for CDI Users in FY11, but would need to be blessed through NGP governance before committing to operational impact. (60)
Level of Effort: .25 FTE (HollisterWater/KML Port, SmoczykHazards/MXD Port, TricomiTNM/JSON Port/TNM UI)
Objective 2: Create ScienceBase “Catalog context” to test uploading and discovering the “web mashup context” (JSON, KML and MXD)
First, need to test how the uploading experience works in ScienceBase catalog – as well as consider the role of data.gov. This testing needs to be multi-dimensional: Search, Viewing, and Cross-Referencing (40)
Test Search experience for how contexts are discovered and presented in Discovery (24)
Test add View a single service or a context in ArcMap (MXD), Google Earth(KML), The National Map (JSON) Options to make easier for science to see the service or context in their tool and environment. (40)
Test concepts – at minimum at mockup level – for cross-reference searches – i.e. if a service comes up in a result and is in some web mashup contexts, how can we inform the user of such. As well, for upload impacts on metadata to improve the categorization, discovery, and proper tracking of the web mashup contexts. (40)
As well, it would be advisable to keep in coordination with Other Viewers and catalogs (i.e. data.gov) if they want to use the new capabilities or design principles
Level of Effort: .1 FTE (Bristol Team Informatics/Catalog Tasks, TricomiTNM/TNM View In Coordination)
Objective 3: Create User Story Examples, Training for Objectives 1 and 2
Capturing Steps for saving mashups for 3-4 examples
- Hazards Example – EarthQuake Single-Click add to Viewer, then save Mashup Context in MXD and open in ArcMap(24)
- Science Example 1 - bureau scientist studying multi-county region to locate sources of contaminants in water and soils to save in KML and open in Google Earth(24)
- Science Example 2 – Climate, LandScape, and Ecosystem example searching for services in catalog and opening in TNM Viewer(24)
- Web App Example – Saving a Mashup Context, and setting up in Water Web Application – proving quicker setup time using context discovered in catalog(40)
For each capture steps on how the example is setup, provide user steps to assist in training either in documentation, or if time permits video screen captures. This includes steps for:
- Searching Catalog for Contexts (32)
- Saving Viewer Contexts (32)
- Opening Viewer Contexts in KML in KML Viewers and Clients (16)
- Opening Viewer Created-Contexts in MXD (16)
- Opening Services or Contexts from Catalog into KML Viewers (16)
- Opening Services or Contexts from Catalog into MXD (16)
- Opening Services or Contexts from Catalog into TNM Viewer (JSON or KML) (16)
- Support Executive Level Presentation (40)
Level of Effort: .2 FTE (HollisterWater/KML Use Cases, SmoczykHazards/MXD Use Cases, TricomiTNM/Coordinate Use Cases into Stories, Bristol Team/Catalog Context Setup for Examples)
Figure 2 - As part of this continued effort to extend off FY10 Goal, the team reviewed what was on the possible table, and after two days or architectural, use case, value-add, discussions with CDI Users/Scientists, the scope (highlighted in Red) was decided upon for FY11.