Confluence Retirement

In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is scheduled for retirement on January 27th, 2023. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact Thank you for your prompt attention to this matter.
Skip to end of metadata
Go to start of metadata

Providing High Value Data for a Unified Access Framework

Team: Rich Signell, Mark Bultman, Bob Kucks, Tim Kern, Dave Greenlee, Tom Zarriello, Jeanne Jones, Curtis Price, Roland Viger


To provide high-value gridded and vector datasets through a uniform set of services (WCS, WMS, WFS, and OpenDAP + CF). This will enable immediate access by companion CDI projects such as ... as well as specific use cases (e.g.).   Build community and spread information on the benefits of a unified access framework within the USGS.

General Work Plan

  • Add high value datasets into a standard framework of web services
  • Document the process: Provide best practices documentation for enabling standard data services
  • Develop an installer package and virtual appliance for the full technology stack, so Centers can establish their own stacks
  • Develop a user help process for Centers to build and maintain the technology stack

Priority Data List



















EROS Landsat Imagery



EROS Digital Raster Graphics



Marine Sidescan



Marine Swath Bathy






Surficial Geology


Geophysical grids


Carbon model output



USGS Partners for Initial Effort

  • National Map Team
  • CIDA GDP Team
  • Data Uploader Team
  • CMSP Team (Shawn Dadisman, Greg Miller, & Co.)
  • MOWS Team (Viger & Co.)

Use Cases

  • Enable the National Mineral Resource Assessment (Eric Anderson (ask for specifics))
  • Provide WMS Basemap services from the National Map for the Godiva2 WMS Client. (Rich & Dave)
  • Drive a hydrology model using the GDP (Roland and
  • Search all ocean model output, in situ observations, remote sensing, and seafloor bathymetry in the northern gulf of mexico between April 20-August 3) to enable spill model assessment.  An example of data mining for Coastal and Marine Spatial Planning. (Rich, Dave, Shawn)
  • Enable Arc Model Builder to consume landcover data from the National Map to ... (Curtis & Dave)
  • Compare carbon model results from different managment scenarios using R. (Leo & Rich)

End User Applications

  • ArcGIS
  • GeoData Portal
  • Scientific Analysis Environments (Matlab, IDL, R, Python)
  • Integrated Data Viewer
  • WMS Clients (Godiva2)
  • GeoMapApp (Virtual Ocean)

Work Plan

   Work with EROS to enable THREDDS Data Server (adding OPeNDAP+CF, ISO Metadata Service) - Rich Signell,

General Overview

Comment on the inclusion of imagery: Not aware of a use-case wherein imagery is actually analyzed (as opposed to visualized and visually interpreted). If we have no such use case, then it seems that only something like WMS access is needed for these data., 13-Aug-2010

I had a phone conversation w/Jeanne Jones that made me realize I should clarify my use of terminology. When I use the term "imagery," I'm thinking of a raster data set where cell values either are used mostly for visual interpretation, as is the case with DRGs or DOQQs, or are "raw", like with LANDSAT imagery. In the latter case, what is considered “raw” is ultimately arbitrary and somewhat fuzzy. I usually think of measurements that need relatively sophisticated analysis or interpretation to be consumed in most scientific contexts as “raw.” I do not consider NDVI (a continuous surface) or land cover trends (categorical) values to be raw data sets because they are much more frequently directly usable (or with simple transformation like thresholding or reclassification)., 30-Aug-2010