TNM Catalog

1
TNM Catalog

• BASICS

2
What is a Catalog?

• Catalogs
• Are Distinct Collections of Referenced Items
• Items are not stored in the catalog only
  references
• There are no super-catalogs
• Each has some qualifying constraint
• Each has a distinct purpose.
• Containing Adequate Descriptions of the Items
• This metadata is directly related to the item
• It is only as detailed as required for the
  purpose
• Organized for Discover

3
What is the TNM Catalog?

• The National Map (TNM) Catalog is
• A Collection of TNM Web Service Metadata
• Storing Service metadata - not the actual data.
• Stores references to approved data not a
  discovery mechanism.
• Described by TNM and Service metadata
• TNM-specific attributes (theme,resolution,)
• WMS Layer and WFS Feature Type attributes
• Supports any TNM Client application
• Accessible Through Standard Interfaces
• OGC Catalog/Registry specifications
• Web Service Interface (Java and .Net compatible)

4
How It Is Used - Basic
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 its 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 its 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.
TNM Catalog
2
1
TNM Client
3
4
Service
Service
Service
Service
5
How It Is Used - Expanded
TNM Catalog
TNM Internal
TNM Viewer
TNM PG
WMS
WMS
WFS
WMS
WMS
WFS
WFS
WMS
WFS
WFS
WMS
WFS
6
Catalog Significance

• Logically Centralizes Critical TNM Metadata
• Maintenance is simplified
• Metadata consistency between clients.
• Avoids Duplication of Query Resolution Operations
• Leverages a Service-Oriented Architecture (SOA)
• Takes advantage of common network services
• Supports multi-client interoperability
• Minimizes the effects of change by being
  loosely-coupled.

7
Catalog Milestones
8
TNM Catalog Components

• Query Resolution Engine
• Spatial Extents (MBR Polygon)
• Theme Classification Layer/FeatureType
• Attributes (Theme, Class, Resolution, )
• Catalog API
• Interface to Query Resolution Engine
• Implemented as OGC Stateless Catalog
• Implemented as Java Web Service
• Middleware Servlets
• Interface between Viewer Catalog API
• Handles service disruptions
• Advanced Image Handling
• Business rule configuration
• GUI
• Handles view parameters
• Handles user-specific requests

Oracle
Oracle Spatial
DB API
Catalog API
WSDL
OGC
Middleware Servlets
GUI
9
TNM Catalog Attributes
10
Catalog Issues

• Oracle/Oracle Spatial vs. SQLServer/SDE
• TNM Feature Classifications
• OGC WMS Versions
• WMS Optional Features
• getFeatureInfo option
• Styled-Layer Descriptor option (SLD)
• WFS Dependencies
• Feature query capability???
• Download capability???
• Overlapping Data Handling
• Spatial Overlap
• Query
• Image
• Attribute Resolution
• TNM Catalog Roles
• Symbology Data Model and Process

11
References Links

• Current Under Catalog Instances
• OGC Catalog Web Service http//isis.er.usgs.gov
  9080/catprod/start?requestgetRecords
• Catalog-based Viewer (prod) http//isis.er.usgs
  .gov9080/tnmcatprod/Run.htm
• Catalog-based Viewer (dev) http//isis.er.usgs.
  gov9080/tnmcatdev/Run.htm
• Open GIS Consortium Links
• OGC Home Page http//www.opengis.org/
• Stateless Catalog Discussion Paper
  http//member.opengis.org/tc/archive/arch01/01-062
  .pdf
• Services and data discovery Paper
  http//member.opengis.org/tc/archive/arch02/02-047
  .pdf
• OGC Catalog Revision Working Group
  http//member.opengis.org/tc/revision.tf/cat.htm
• OGC Catalog Revision Working Group (portal)
  http//member.opengis.org/portal/index.php
• Contacts
• Rick Brown reb_at_usgs.gov 573-308-3525
• Jeff Wendel - jwend_at_usgs.gov 573-308-3632

12
Catalog Demo - ArcXMLConnector

• Purpose
• Provide TNM look-and-feel to Catalog efforts.
• Reduce Client-Side development time.
• Accommodate parallel development efforts that
  depend on ArcIMS functionality.
• Investigate ArcXML incompatibilities with TNM.
• Components
• 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.
• ArcXMLConnector middleware implemented as a
  Servlet to provide translation of ArcXML requests
  into TNM Catalog queries and TNM Catalog
  responses back to ArcXML responses.
• TNM Catalog The storage application for TNM
  service metadata. The interface to the catalog
  is an OGC Web Registry Service (WRS).

TNM Catalog
ArcXMLConnector
ArcXML Request
ArcXML Response
ArcXML Viewer