Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

TNM Catalog Basics.ppt


Published on

  • Be the first to comment

  • Be the first to like this

TNM Catalog Basics.ppt

  1. 1. TNM Catalog BASICS
  2. 2. What is a Catalog? <ul><li>Catalogs… </li></ul><ul><ul><li>Are Distinct Collections of Referenced Items </li></ul></ul><ul><ul><ul><li>Items are not stored in the catalog – only references </li></ul></ul></ul><ul><ul><ul><li>There are no super-catalogs </li></ul></ul></ul><ul><ul><ul><ul><li>Each has some qualifying constraint </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Each has a distinct purpose. </li></ul></ul></ul></ul><ul><ul><li>Containing Adequate Descriptions of the Items </li></ul></ul><ul><ul><ul><li>This “metadata” is directly related to the item </li></ul></ul></ul><ul><ul><ul><li>It is only as detailed as required for the purpose </li></ul></ul></ul><ul><ul><li>Organized for Discover </li></ul></ul>
  3. 3. What is the TNM Catalog? <ul><li>The National Map (TNM) Catalog is… </li></ul><ul><ul><li>A Collection of TNM Web Service Metadata </li></ul></ul><ul><ul><ul><li>Storing Service metadata - not the actual data. </li></ul></ul></ul><ul><ul><ul><li>Stores references to “approved data” not a discovery mechanism. </li></ul></ul></ul><ul><ul><li>Described by TNM and Service metadata </li></ul></ul><ul><ul><ul><li>TNM -specific attributes (theme,resolution,…) </li></ul></ul></ul><ul><ul><ul><li>WMS Layer and WFS Feature Type attributes </li></ul></ul></ul><ul><ul><ul><li>Supports any TNM Client application </li></ul></ul></ul><ul><ul><li>Accessible Through Standard Interfaces </li></ul></ul><ul><ul><ul><li>OGC Catalog/Registry specifications </li></ul></ul></ul><ul><ul><ul><li>Web Service Interface (Java and .Net compatible) </li></ul></ul></ul>
  4. 4. How It Is Used - Basic TNM Client TNM Catalog 1 - CLIENT REQUEST TO CATALOG A client requests all the TNM Service Information matching the user-specified spatial and non-spatial constraints of the client. 2 - CATALOG RESPONSE The Catalog resolves spatial and non-spatial queries against it’s data store and responds with a list of Service Information matching the request. 3 - CLIENT REQUEST TO DISTRIBUTED SERVICES Based on the Catalog response, the Client then makes a request to each distributed service for it’s applicable information. 4 – DISTRIBUTED SERVICES RESPONSE Each service processes the request from the client and returns the data (an image, feature info, or actual features) to the client. Service Service Service Service 1 2 3 4
  5. 5. How It Is Used - Expanded TNM Viewer TNM Catalog WMS WMS WMS WMS TNM PG WFS WFS WFS WFS TNM Internal WMS WFS WFS WMS
  6. 6. Catalog Significance <ul><li>Logically Centralizes Critical TNM Metadata </li></ul><ul><ul><li>Maintenance is simplified </li></ul></ul><ul><ul><li>Metadata consistency between clients. </li></ul></ul><ul><li>Avoids Duplication of Query Resolution Operations </li></ul><ul><li>Leverages a Service-Oriented Architecture (SOA) </li></ul><ul><ul><li>Takes advantage of common network services </li></ul></ul><ul><ul><li>Supports multi-client interoperability </li></ul></ul><ul><ul><li>Minimizes the effects of change by being loosely-coupled. </li></ul></ul>
  7. 7. Catalog Milestones Release of TNM Phase-D Viewer Capability (Proposed) March 2003 TNM Phase-D Viewer telecons to discuss requirements and work assignments. January 2003 Ported XML-based Catalog to Oracle with Oracle Spatial. The addition of Area of Coverage Footprints in the database with the implementation of spatial operators allowed spatial query resolution against polygonal footprints rather than the inadequate Minimum Bounding Rectangles (MBR). November 2002 Completed development of a Phase-D Viewer prototype which used the TNM Viewer Design Team’s GUI template and MCMC developed middleware to communicate with Catalog. October 2002 Catalog task added to Basis+ July 2002 Catalog/Registry conceptual demonstration at OGC TEM in Reston. April 2002
  8. 8. TNM Catalog Components WSDL DB API <ul><li>Query Resolution Engine </li></ul><ul><ul><li>Spatial Extents (MBR & Polygon) </li></ul></ul><ul><ul><li>Theme & Classification – Layer/FeatureType </li></ul></ul><ul><ul><li>Attributes (Theme, Class, Resolution, …) </li></ul></ul><ul><li>Catalog API </li></ul><ul><ul><li>Interface to Query Resolution Engine </li></ul></ul><ul><ul><li>Implemented as OGC Stateless Catalog </li></ul></ul><ul><ul><li>Implemented as Java Web Service </li></ul></ul><ul><li>Middleware Servlets </li></ul><ul><ul><li>Interface between Viewer & Catalog API </li></ul></ul><ul><ul><li>Handles service disruptions </li></ul></ul><ul><ul><li>Advanced Image Handling </li></ul></ul><ul><ul><li>Business rule configuration </li></ul></ul><ul><li>GUI </li></ul><ul><ul><li>Handles view parameters </li></ul></ul><ul><ul><li>Handles user-specific requests </li></ul></ul>OGC Oracle Spatial Catalog API Oracle Middleware Servlets GUI
  9. 9. TNM Catalog Attributes
  10. 10. Catalog Issues <ul><li>Oracle/Oracle Spatial vs. SQLServer/SDE </li></ul><ul><li>TNM Feature Classifications </li></ul><ul><li>OGC WMS Versions </li></ul><ul><ul><li>WMS Optional Features </li></ul></ul><ul><ul><ul><li>getFeatureInfo option </li></ul></ul></ul><ul><ul><ul><li>Styled-Layer Descriptor option (SLD) </li></ul></ul></ul><ul><ul><li>WFS Dependencies </li></ul></ul><ul><ul><ul><li>Feature query capability??? </li></ul></ul></ul><ul><ul><ul><li>Download capability??? </li></ul></ul></ul><ul><li>Overlapping Data Handling </li></ul><ul><ul><li>Spatial Overlap </li></ul></ul><ul><ul><ul><li>Query </li></ul></ul></ul><ul><ul><ul><li>Image </li></ul></ul></ul><ul><ul><li>Attribute Resolution </li></ul></ul><ul><li>TNM Catalog Roles </li></ul><ul><li>Symbology Data Model and Process </li></ul>
  11. 11. References & Links <ul><li>Current Under Catalog Instances </li></ul><ul><li>OGC Catalog Web Service: </li></ul><ul><li>Catalog-based Viewer (prod) : htm </li></ul><ul><li>Catalog-based Viewer (dev) : </li></ul><ul><li>Open GIS Consortium Links </li></ul><ul><li>OGC Home Page: </li></ul><ul><li>Stateless Catalog Discussion Paper: </li></ul><ul><li>Services and data discovery Paper: pdf </li></ul><ul><li>OGC Catalog Revision Working Group: htm </li></ul><ul><li>OGC Catalog Revision Working Group (portal): php </li></ul><ul><li>Contacts </li></ul><ul><li>Rick Brown – [email_address] 573-308-3525 </li></ul><ul><li>Jeff Wendel - [email_address] 573-308-3632 </li></ul>
  12. 12. Catalog Demo - ArcXMLConnector ArcXML Viewer ArcXMLConnector TNM Catalog <ul><li>Purpose </li></ul><ul><li>Provide TNM look-and-feel to Catalog efforts. </li></ul><ul><li>Reduce Client-Side development time. </li></ul><ul><li>Accommodate parallel development efforts that depend on ArcIMS functionality. </li></ul><ul><li>Investigate ArcXML incompatibilities with TNM. </li></ul><ul><li>Components </li></ul><ul><li>ArcXML Viewer – essentially the out-of-the box ArcIMS HTML client – communicating requests and responses using the ArcXML format. Instead of connecting to an ArcIMS map service the viewer connects to the USGS TNM ArcXML Connector. </li></ul><ul><li>ArcXMLConnector – middleware implemented as a Servlet to provide translation of ArcXML requests into TNM Catalog queries and TNM Catalog responses back to ArcXML responses. </li></ul><ul><li>TNM Catalog – The storage application for TNM service metadata. The interface to the catalog is an OGC Web Registry Service (WRS). </li></ul>ArcXML Request ArcXML Response