TNM Catalog

BASICS

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

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)

How It Is Used - Basic

TNM Client

TNM Catalog1 - CLIENT REQUEST TO CATALOGA client requests all the TNM Service Information matching the user-specified spatial and non-spatial constraints of the client.

2 - CATALOG RESPONSEThe 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 SERVICESBased on the Catalog response, the Client then makes a request to each distributed service for it’s applicable information.

4 – DISTRIBUTED SERVICES RESPONSEEach 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

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

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.

Catalog MilestonesApril 2002 Catalog/Registry conceptual demonstration at OGC TEM

in Reston.

July 2002 Catalog task added to Basis+

October 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.

November 2002

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).

January 2003 TNM Phase-D Viewer telecons to discuss requirements and work assignments.

March 2003 Release of TNM Phase-D Viewer Capability (Proposed)

WSDL

DB API

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

OGC

Oracle Spatial

Catalog API

Oracle

Middleware Servlets

GUI

TNM Catalog Attributes

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

References & LinksCurrent Under Catalog Instances

OGC Catalog Web Service: http://isis.er.usgs.gov:9080/catprod/start?request=getRecords

Catalog-based Viewer (prod) : http://isis.er.usgs.gov:9080/tnmcatprod/Run.htm

Catalog-based Viewer (dev) : http://isis.er.usgs.gov:9080/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@usgs.gov 573-308-3525

Jeff Wendel - jwend@usgs.gov 573-308-3632

Catalog Demo - ArcXMLConnector

ArcXML Viewer

ArcXMLConnector

TNM Catalog

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).

ArcXML Request

ArcXML Response