PRISM Information Integration System

The “Bloodstream”

Miles Logsdon

Bruce Campbell

Harvey Greenberg

Sarah Rodda

Initial Boundary

NCEP

Interpolation

Coordinate TransformationInterpolation PRISM

Domain

LandCover

Soils

FlowRouting

MM5

48hr WeatherForecasts Surface Field

to SoundCirculation

3-D FieldsWEB

DHSVM

River FlowBasin Sums

WEBVisuals

SST

• Short- & Long-wave• Precipitation• Temperature• Humidity• Wind Speed• Surface pressure

DRIVERS MODELS OUTPUT

Surface FieldUrbanModel

Tidal Elevation

Current

Temperature

WEBVisuals

• Short- & Long-wave• Precipitation• Temperature• Humidity• Wind Speed• Surface pressure

Surface Boundary

Initial Conditions

•Temperature•Salinity•Bathymetry

Lateral Boundary

•Tidal Elevation•River Flow•River Temp.

SoundCirculation

POM

Salinity

Mixing

LandConversion

Resources Use

Emissions

WEBVisuals

P. S. Template (biophysical)

•Topography•Climate•Soils

••••

••••

••••

HouseholdsIncomeSizeEthnicityEducation

BusinessesSIC# of EmployeesOutputIncome

Land UseTypeLot size# of UnitsValue

Impervious Surface

WaterDemand

• # of people•Birth rate•Migration

Demographics

Economic• Regional Trends• Input-Output

Political• Growth Mgmt.• Zoning• Environmental Laws

Infrastructure•Transportation•Energy•Water & Sewer

UrbanSim & CRYSTAL

Hunter Hadaway & CEV

Soils -•3 layers•Surface & Subsurface Process

Snow -2 layers

Vegetation•2 canopies•density•LAI

Wind Stress

Evaporation Precipitation

•Runoff•Erosion

Mixing

CloudsEvapotransporations

Biomass

Atmosphere•32 layers

Sea•30 layers•Tides•Temp. & Salinity

River network•Routing•Chemistry

Urbanization•Growth•Land cover & use•Emissions

Radiation

We started drawing arrows

CoastalZone

Habitat

Hillslope

Continuos R

eal-time M

onitoring Stations

Land Processes.Hydrology

DHSVM

Climate & AtmosphericForcing

MM5

Water ResourceAllocation

CRYSTAL

Human DimensionUrban Sim

Sea Circulation& CompositionPOM & EFDC

Landsat TM

SeaWiFs

AVHRR

LandcoverMapping

UrbanWatershed

Shorelines

Wastetreatment

urbdp467

BioticResources

More Arrows

PRISM – Information Integration System Architecture:“the Bloodstream”

•Fewer Arrows•Less lines•A “circle”!

Key Points

It’s about Data Integration and Data Sharing

Everyone is either one or more of these:1. A data source

2. An Occasional default data sink (proactive)

3. A hardwired data sink (proactive)

4. A query sink (retroactive)

We’ve begun: Relay Node – plasmus.ocean.washington.edu Wiring for example sink and source services Default source and sink services Investigation of 39 program languages suited for XML-RPC services

Design Basis: a framework that simplifies all aspects of scientific data networking, allowing simple access to data

DODS

Distributed

Oceanographic

Data

System

Built upon the design principles of:

•Division of Atmospheric Sciences (ATM) of the National Science Foundation (NSF) NSF UNIDATA program, and the Internet Data Distribution (IDD ) system, and

•The NASA Earth Science Information Partners (ESIP) Federation

Design Principle

Data are most appropriately described updated and distributed by those that develop them;

Users desire access ready for their existing application/software;

It isn’t the scientists job to responding to data request;

Users want access to data from anywhere that is served by the PRISM project regardless of its native format

Multiple SOURCES: Data can be injected into the BLOODSTREAM from multiple sources where SOURCE SERVICES have been installed.

Data recognition SINKS: Through a data recognition mechanism, users select from the available data only those needed for their needs.

Reliable data delivery RELAYS: Reliable transport protocols ensure data accuracy at all sites. A queuing system buffers data flows at relays, preventing losses from network congestion and short outages.

Load distribution: designed to avoid excessive concentration of network traffic. Generally, metadata flows with data. Only new data flow when needed.

Data SOURCE servicesData RELAY servicesData SINK services

What is XML-RPC?

A specification and a set of implementations that allow software running on disparate operating systems, running in different environments to make procedure calls over the Internet.

Remote procedure calling services using HTTP as the transport and XML as the encoding. XML-RPC is designed to be as simple as possible, while allowing complex data structures to be transmitted, processed and returned.

XML-RPC Implementations AOL Server client/server Apache client/server AppleScript client ASP client/server Axapta client/server C/C++ client/server C client/server Cold Fusion client/server COM client/server Delphi/Kylix client/server Dylan client/server Eiffel client/server Flash client Frontier client/server Guile client/server Internet Expolrer client J2ME client Java client/server JavaScript client K client/server KDE client/server Lingo client Lisp client/server Macintosh OS X client/server

Microsoft .NETclient/server

Mozilla client Objective C client/server Perl

client/server PHP

client/server Pike server Python

client/server REALBasic client Rebol

client/server Ruby

client/server Scheme client Tcl

client/server Tintware client/server WebObjects client/server Zope

client/server

Default Sink Client (available 11/15/2002)

Data Access Methods:

• Web via URL

• FTP via anonymous FTP

• Email via request form

• Database Query

• Other methods required by us

Query results of latest catalog entries

Status Updates

Applet or Application

Filtering Available based on XML hierarchy

Default Source Client (available 11/15/2002)

Applet or Application

For Querying and Filtering

Miles’ Parting Shots

Remember: We’re trying to say:

Collaboration begins with sharing information Each of our projects is both a data source and data

sink within the PRISM program By “communicating” through our data and

information, we reduce the need for numerous solutions to similar tasks of data distribution, formatting, archiving, and retrieval tasks

Have Fun!