VOYAGER Data Explorer: Architecture and Technologies See also the the Voyager Developer Website and early ApplicationsDeveloper WebsiteApplications Layered Map Time Chart ProvidersUsers Vector GIS Data XDim Data SQL Tables Web Images Voyager Web Services Publish, Find, Bind Data & Tool Catalog Uniform Access Scatter Chart S u p p o r tCoord./Cooperation T e c h n o l o g i e s

Select, Overlay, Explore; Multidimensional data Maintain Distributed Data; Heterogeneous coding, access Connect providers to users; Homogenize data access Voyager Spatio-Temporal Data Explorer Built and Used by a Virtual Community Layered Map Time Chart ProvidersUsers Vector GIS Data XDim Data SQL Table Web Images Voyager Web Services Publish, Find, Bind Data & Tool Catalog Uniform Access/Retrieval Scatter Chart

The Dvoy Project DVOY is a graphic browser for distributed, heterogeneous, multidimensional datasets The initial Dvoy infrastructure was developed at CAPITA, with NSF supportDvoy Further services for data access, processing and viewing are expected from the community The project evolution is to ride 'web services wave‘ of the Internet CAPITA Support: –NSF ITRWorkgroup Collab. Tool:Aug Aug 2004 –EPA Web-based Visibility:Aug Apr 2003 –NOAAASOS Visibility:Aug May 2002 –MARAMAChemical Trajectory Tool:Aug July 2003 –EPA OAQPS Global Transport Analysis:Nov 2002 – Oct 2003 In-kind support by organizations participating in DVOY-based data sharing

Dvoy Data Model

Multi-Dimensional Data Model Data can be distributed over 1,2, …n dimensions 1 Dimensional e.g. Time dimension i j k j i Data Granule i 1 Dimensional e.g. Location & Time 1 Dimensional e.g. Location, Time & Parameter View 1 Data Space View 2 Views are orthogonal slices through data space

4 D Geo-Environmental Data Cube (X, Y, Z, T) Environmental data represent measurements in the physical world which has space (X, Y, Z) and time (T) as its dimensions. The inherent dimensions for geo-environmental data are: Longitude X, Latitude Y, Elevation Z and Time T.

Semi-Static Views (slices) through 4D Data Space Possible Cross-sections through the 4 D Data space - data point..Temperature (x i, y i, z i, t i ) - image Temperature (x range, y range, z range, t range ) XY MAP: Z,T fixed Vertical Profile:XYT fixed Time Chart: X,Y,Z fixed Vertical Cross sect: YT fixedVertical Cross sect: XT fixed Vertical Profile Trend: X,Y fixed

Web Services

Web Services Components and Actions Service providers publish services to a service broker. Service users find the needed service and get access key from a service broker With the access key, users bind to the service provider The result is a dynamic binding mechanism between the service users and providers Service Broker Service Provider Publish Find Bind Service User Components:Provider – User – Broker Actions: Publish – Find - Bind

Interoperability through a Layered Protocol Stack Web Services are implemented on a layered stack of technologies and standards The lower layers enable binding and exchange of messages; higher levels enable interoperability Applications are formed dynamically from distributed components through publish-find-bind mechanisms TCP/IP, HTTP, FTP ASCII, XML, etc. HTML, XML OGC -GML OGC Coverage, CoordTransfom, WMS HTTP, SOAP WSDL UDDI OGC Catalog WSFL, XLANG Standards Interoperability Comm. Protocols Data Encoding Data Schema Data Binding Web Service Service Integr. Service Discovery Service Descript. Connectivity

Web Publish HTTP, FTP Data Access though a Web Service Adapter Service Cataloger Service Consumer Ordinary web content can be delivered as a Web Service through a Proxy Server. The Wrapper Service converts HTTP/FTP service to XML Web service The Wrapper Service is published as a web service to the Broker The User finds the service from the broker and accesses the Wrapper to use the service Service Wrapper HTTP/FTP Service User Chain Find UDDI, WSDL Publish UDDI, WSDL Access SOAP, XML

Web Application: Chained Web Services A Web Service Provider may also be a User of other services Multiple web services can be chained into an interactive workflow system The result is an agile application that can be created ‘just in time’ by the user for a specific need Service Broker Service Provider/User Publish Find Bind Service User Chain Service Provider Bind Chain

Features of the DVOY XML Web Service Architecture Interoperability: Platform and language independence; based on Web Services (XML,SVG) Legacy Support: Encapsulating existing data and exposing them as Web Services. (Access to standard HTTP/FTP servers) Just-in-time integration: Discovery, access to and ad-hoc chaining of services. (Future: Agile app building)

DVOY Web Services DVOY draws on three basic web services: DataCatalogWrapping service is for data registration, finding and wrapping information DataAccess service provides uniform access to heterogeneous, distributed, multidim. data DataPortrayal service prepares input data in form suitable for rendering

Applications…. Voyager Data Browser

Data Catalog All the data in the system are to be distributed on the Web and maintained by their custodians The purpose of the catalog is to help finding and and accessing the data Catalog would be limited to data that can be accessed/merged in DVOY

Catalog of Multidimensional Datasets Designed to Publish, Find(Select), Bind(Access) and Render distributed datasets Publishing is though an open web interface for user/broker registration of datasets Finding a dataset is aided by a metadata on Provider and Dataset Binding (data access) information is contained in the Dimensional Tables Rendering parameters are also contained in the Dimensional Tables

Geo-referenced Map Image: Image Indexed Variable Time, Var GeoRect, Var Sensor SatGeoImg CapImgIDUniversal ID ProviderURLURL SourceURLURL ImageURLURL ProviderAbbrevNASA GSFC ImageDescriptionText SensorEnumerated DateTime LatMin-65 LatMax 65 LonMin- 180 LonMax180 ImageWidthFor size verification ImageHeight MarginLeftFor trimming MarginTop MarginRight MarginBottom SQL Table … see table left NO DIMENSION TABLES XML Example: SeaWiFS

Geo-referenced Map Image: Time Indexed Regular Time Series; Fixed Georect; Image Trim < time_dimension handler_assembly="CAPITA.data.index.impl" handler_class="CAPITA.data.index.impl.datetime_interval" start_time=" " end_time="yesterday"> sample_periodicity _unit = "day" sample_periodicity_mult = “1" TOMSFact TimeIndex Int, Calc from date DailyImage Img, Parsed from date LatMin Fixed, -65 LatMax Fixed, 65 LonMin Fixed, LonMax Fixed, 180 TOMSTime TimeIndex DateTime Virtual Tables (No physical StarTables)XML Example: TOMS ftp://jwocky.gsfc.nasa.gov/pub/eptoms/images/aerosol/y2002/ea gif

Astronaut Photos: Image Indexed Variable Time, Image Center, Platform SatImg NASAImageIDUniversal ID ProviderURL SourceURLhttp://eol.jsc.nasa.gov/script s/sseop/photo.pl?mission=IS S004&roll=E&frame=11079 ImageURLhttp://eol.jsc.nasa.gov/sseop/ images/ESC/small/ISS004/I SS004-E JPG ProviderAbbrevNASA JSC ImageDescriptionText PlatformISS004 GeoRegionGUATEMALA FeaturesSMOKE, GULF OF HONDURAS DateTime Lat17.6 Lat-90.2 SQL Table <data_source service_url=" /> … see table left XML Example: ISS004

Atmospheric Photos: Image Indexed Variable Time, Image Center, Platform AtmoImg ImageIDUniversal ID ProviderURLhttp://capita.wustl.edu/capita /people/RHusar/rhusar.html SourceURLhttp://capita.wustl.edu/capita /people/RHusar/Pic/9812San FranciscoAGU/9812SanFra nciscoAGU.htm ImageURLhttp://capita.wustl.edu/capita /people/RHusar/Pic/9812San FranciscoAGU/Dcp01000E nh.jpg Provider AbbrevR Husar ImageDescriptionText PlatformAirplane GeoRegionNEVADA FeaturesDUST PLUME DateTime Lat36.75 Lat SQL Table <data_source service_url=" /> … see table left XML Example: Dust Plume Photo

DVOY State Maintenance This DVoyState data structure contains the state variables, which drive DVoy during browsing It is created by the DataCatalogWarpping service using the Catalog and Wrapping information User actions on Controllers modify the DVoyState structure directly but do not execute changes Actions are executed by managers (e.g. ConMan for connections) based on changes in DVoyState DVoyState resides on the client web page, hence it is unique for each Dvoy session The session state can be saved as a web page and can be recreated at load time Workbooks can be created from multiple pages of DVoyState (not yet implemented)

Add New Layer (New): Populate DVoyState.xml WSGetDatasetList DatasetList.xmlDVoyState.xml WSGetDatasetInfo DatasetInfo.xml DatasetSelector DVoy Catalog Database On LoadCatalogPage On AddLayer Init DVoyStateAdd layer/dataset_abbr to DVoyStateAdd Layer Description to DVoyState DVoyState.xml

Event Handling in DVoy

Applications - Examples

Quebec Fires, July 6, 2002 SeaWiFS, METAR and TOMS Index superimposed SeaWiFS satellite and METAR surface haze shown in the Voyager distributed data browser Satellite data are fetched from NASA GSFC; surface data from NWS/CAPITA servers

Trans-Atlantic Transport of Quebec Smoke July 11: Smoke approaching Europe July 10: Quebec smoke over Mid- Atlantic SeaWiFS Reflectance TOMS Absorbing Aerosol SeaWiFS Reflectance TOMS Absorbing Aerosol Spain E. US

Web Service Wrapper for TOMS Aerosol Index Fixed Geo-rectangle; Image Trim, daily TOMS Image Metadata Geo-rectangle (65, -180; -65, 180) Image Size (640, 480) Image Margins (40, 40, 30,30) Transparent Colors (0,0,255 ) Image Access Metadata URL template: :ftp://jwocky.gsfc.nasa.gov/pub/eptoms/images/aerosol/YYYYY/eaYYMMDD.gif StartDate, EndDate

Browsing of Distributed Data from HTTP/FTP Servers Land Reflectance from SeaWiFS Project, NASA GSFC AVHRR Oceanic Aerosol CAPITA, WashU, STL Fire Pixels, Jan 1997, ESA Ionia Project

Voyager Spatio-Temporal Data Browser

NRL Forecast Model for Dust, Smoke and Sulfate METAR Surface Haze Real-time model and surface observations are compared spatially and temporally Dust Sulfate Smoke METAR Haze Time Selector