Telcordia Technologies

Telcordia Geospatial Information Filtering System (GeoLens)



This page provides technical information about GeoLens architecture, development and technological inputs.


Background

In March 1994, NASA's Information Infrastructure Technology and Applications (IITA) initiative of the High Performance Computing and Communications (HPCC) program issued a Cooperative Agreement Notice (CAN-OA-94-1) , "Public Use of Earth and Space Science Data Over the Internet". In response, the Universal Spatial Data Access Consortium was formed (then consisting of Bellcore, Camber Corp., the OpenGIS Consortium, Rutgers Center for Remote Sensing and Spatial Analysis, NASA's Space Science Data Center, and the California Resource Agency's CERES Program). The USDAC submitted a proposal for a project entitled, "Usability and Interoperablity: A Dual Strategy for Enabling Broader Public Use of NASA's Remote Sensing Data on the Internet." This project was funded for three years under the Digital Library Technology Development Area of Interest in the CAN and the USDAC received $2.3M from NASA and contributed another $2M in cost-sharing.

The "Problem"

Geospatial data are difficult to use because they:

Overall Approach

Propose a comprehensive strategy that makes geospatial data more usable and interoperable by:

GeoLens Architecture

The figure below illustrates conceptually the distributed Web/Internet architecture of the GeoLens System. The system consists of a GeoLens Client, a GeoLens Catalog Server, GeoLens Data Access Servers and, potentially, other servers to process geospatial data or their metadata.

(Enlarged diagram is 35KB)

The GeoLens Client locates geospatial data on the Internet by using an agent called the "GeoLens Catalog Server" to search metadata catalogs. A Metadata Analyzer and Schema Loader extracts metadata for geospatial data objects as they are added to a repository. These metadata are analyzed for their type, range and other properties, and their schema is determined. Metadata are then added to a catalog, in this implementation an O2 database, and schema information is authenticated by a Schema Mapping Server before updating its repository of cross-schema attribute mappings. A user launches a search for geospatial data by querying the contents of metadata catalogs with the help of one or more GeoLens Catalog Servers. Catalogs may be queried for the schema used to structure and document metadata for a collection of data objects, or for any of the attributed metadata that describe a particular data object. Queries may be spatial, temporal or built from any metadata attributes used to catalog a data object. Since a query may be issued to one or more catalogs, each with collection metadata that might be organized consistent with different metadata schema, a Schema Mapping Server may be invoked by query services provided in the GeoLens Catalog Server to translate between schema with different attribute names and structure. This feature enables a user to search recursively all or part of the catalogs known to GeoLens Catalog Servers for geospatial data objects that satisfy a query.



Once a list of candidate data objects has been returned to the GeoLens Client, a user can select objects from this list for retrieval. The GeoLens Client sends a message to a GeoLens Data Access Server with the ID for the data object and a user-provided Minimal Bounding Rectangle. This MBR is applied by the GeoLens Data Access Server to clip the data object. The data extract is remodeled as an OpenGIS-like Well-known Structure (WKS) and returned to the GeoLens Client where it may be stored locally, or immediately exploited by an application, e.g., a commercial GIS, that implements OpenGIS interfaces. In addition, the GeoLens architecture provides support for other services, e.g., geoprocessing, that may be requested by the GeoLens Client or GeoLens Data Access Servers.



A major thrust of the GeoLens Project involves the evaluation of new Web/Internet technologies, support of Federally-mandated information processing standards, and use of public domain software to implement GeoLens clients and servers. With these objectives, highlights of the current GeoLens system include:

Online Demo

- The GeoLens demo with scripted highlights!

Technical Documents

These documents describe GeoLens software requirements, architecture and features.

Also see:

Pointers to related Digital Library technologies that have informed design of GeoLens.


Page authored by Cliff Behrens.
Last modified 03/06/98 for content, 5/99 for Telcordia name and 3/00 for product naming.