Loading...
 
ESA > Join & Share > Technology Projects > Osprey Project
Print

Osprey Project

Project Title   Satellite Data Dissemination via JPEG2000 & Java Technologies
Project Acronym   Osprey
Contractor(s)   ITT VIS UK (formerly RSI UK)

 

Project Context
       Objectives
             Architecture
       How it Works
Output

  


Context

Discovery and streaming of large satellite data across constrained bandwidth systems currently relies on proprietary solutions which incorporate patented compression and streaming J2EE technologies. Osprey implements JPEG2000 for compression and JPEG2000 Interactive Protocol (JPIP) streaming technology within a scaleable OGC compliant environment, accessible via a catalogue interface.

Top  


Objectives

ITT have taken their experience with existing IAS technology, a standalone JPEG2000 client-server streaming technology, and reengineered it as a scalable J2EE application to provide integration with existing image catalogue and OGC systems.

We see this as an important enabling technology for fast image dissemination of the new generation of high spatial and spectral resolution Earth Observation (EO) sensors. These data are large by definition and have an increasing audience of interested users. Dissemination of data is currently restricted by relatively large dataset sizes and relatively narrow bandwidths between image data providers and users.

Top  


Architecture

As this project provides an open-standard OGC client/server interface, the integration with OGC W*S implementations is expected to be readily achievable. Also, subsequent development overhead is significantly reduced. It provides a deployable fault-tolerant ground-station and data-provider implementation via OGC standard interfaces. Osprey is a J2EE enterprise system allowing integration with other enterprise components e.g. Enterprise Java Beans (EJBs).

The Osprey software components are as follows

Osprey Server

The Osprey Server is be developed using J2EE technologies as outlined in the original proposal document to the ESTEC Innovation Triangle Initiative.

Container
To reduce the introductory cost to the Osprey Server, the Osprey J2EE components are developed using JBOSS, an Open Source J2EE container.

JBoss is the premier open source J2EE container which is recently been purchased by Red Hat. JBoss has commercial support, training, and licensing. The J2EE container itself is free to download and use, care has to be taken not to build a component that is dependent on the product.

OGC Interfaces
The development of the Osprey Server utilizes the ebRIM registry information model and allow the search, discovery and registry of geographic datasets and services. Consumers of the system can search the registry for data offered by this service including JPEG2000 images that can be streamed. Additional output services such as WCS/WMS/WFS can also be registered and classified with the registry according to ISO standard naming conventions.

A spatial extension to the Sun ebxmlrr reference implementation is implemented, and OGC ebRIM catalog profile imported to create a catalog registry service for Osprey.

Osprey Client

Server Management Web Client
Osprey delivers a web client to assist in the management of the server. The web client delivers the following key pieces of functionality;
 

  • Perform file conversion
  • Manage users/security
  • Register data sources with the catalogue
     

This includes development of a simple web interface to the Osprey System.

JPIP Retrieval
Jpeg2000 Interactive Protocol requires a rich client application capable of displaying the streamed data. JPIP is itself an open ISO standard, potentially allowing any client to to connect to the Osprey Server. The development of Osprey is primarily focused on the development of the server, and associated management web pages.

The default JPIP client for Osprey is the free IAS viewer from ITT, however any JPIP compliant viewer can be used (including larger applications such as the ENVI Zoom software from ITT VIS).

OGC Retrieval
Any OGC-compliant web service may be registered with the Osprey Server and it's data therefore retrieved by searching the registry. Upon request the Osprey server will make the OGC query on the users behalf and deliver the image data to the client for visualization.

 

Top  


How it Works

The Osprey system provides services to publish, search, discover and retrieve data. In support of these activities a range of functionality is required such as user authentication and conversion of uploaded data to JPEG 2000 format. Essentially this process breaks into two areas of functionality as follows.

Data Registration (Administrator)
When a new data source is identified, this needs to be registered by an Osprey administrator so that the data is available for subsequent searches. This registration is web-based and accessed via an internet browser.

If the data source is an OGC compliant web service, the administrator logs the details on a web based form and the registration process queries the service to identify the details required in the catalogue.

If the desired data source is a JPEG 2000 file(s), another web form can be used to upload this to the server at which point they are converted to JPEG2000 for subsequent streaming to image analysts.

Data Search, Discovery and Retrieval (Image Analyst)
Initially, the user will browse the catalogue using interactive geographic area identification and keywords (e.g. data format), refining search criteria to identify the file(s) of interest. This done, the data (or part of it in the case of streamed data) is retrieved to client machine. The viewer associated with the incoming image type will start to view the result.
 

Top  


Output

The results of the work fall into the following categories.

High-level Design Document with Use-Case Analysis
The project solution is developed by integrating ITT proprietary technology into an open standard implementation. The architectural design of this system is a key deliverable and will facilitate the propagation of the technology in the space sector. The use cases show specifically how the components interact to meet the conversion, connectivity and streaming requirements. The use cases are drawn from the specific requirements as developed with the stakeholders identified in the proposal.

J2EE Application
The development activities result in an enterprise application which will work with OGC-compliant W*Ss. The system may also be configured as an OGC server such that any OGC-compliant client can retrieve data. The application will provide the following:
 

  • GML encoded JPEG2000 implementation
  • JPIP streaming JPEG2000 enterprise imagery resource adapter
  • Image converter/compression EJBs
  • Free JPIP enabled Client
  • Ingestion tools
     

Catalogue Integration Report
This report describes the methodology on how a ground-segment or data-provider can integrate a catalogue service.

The Osprey final presentation was held at ESRIN on September 24, 2007.

 


Contributors to this page: .

Page last modified on Wednesday 15 of December 2010 16:13:38 CET by .