- Slides: 16
PRISM Information Integration System The “Bloodstream” Miles Logsdon Bruce Campbell Harvey Greenberg Sarah Rodda
DRIVERS MODELS Interpolation MM 5 Initial Boundary NCEP 48 hr Weather Forecasts SST Coordinate Transformation Interpolation PRISM Domain Land Cover Soils Flow Routing • Short- & Long-wave • Precipitation • Temperature • Humidity • Wind Speed • Surface pressure DHSVM OUTPUT Surface Field Urban Model Demographics • # of people • Birth rate • Migration Surface Field to Sound Circulation Economic • Regional Trends • Input-Output 3 -D Fields WEB River Flow Basin Sums WEB Visuals Surface Boundary Tidal Elevation • Short- & Long-wave • Precipitation • Temperature • Humidity • Wind Speed • Surface pressure Salinity Initial Conditions • Temperature • Salinity • Bathymetry Lateral Boundary • Tidal Elevation • River Flow • River Temp. Sound Circulation POM Current Mixing Temperature WEB Visuals Political • Growth Mgmt. • Zoning • Environmental Laws P. S. Template (biophysical) • Topography • Climate • Soils Urban. Sim & CRYSTAL Households • • Income • Size • Ethnicity Education • Businesses • SIC • # of Employees • Output Income • Land Use • Type • Lot size • # of Units Value Infrastructure • Transportation • Energy • Water & Sewer Land Conversion Impervious Surface Resources Use Water Demand Emissions WEB Visuals
Hunter Hadaway & CEV
We started drawing arrows Radiation Atmosphere • 32 layers Evapotransporations Vegetation • 2 canopies • density • LAI Clouds Biomass Urbanization • Growth • Land cover & use • Emissions Snow -2 layers Evaporation Precipitation • Runoff • Erosion Wind Stress Soils • 3 layers • Surface & Subsurface Process River network • Routing • Chemistry Mixing Sea • 30 layers • Tides • Temp. & Salinity
Sea. Wi. Fs Sea Circulation & Composition POM & EFDC Waste treatment Coastal Zone AVHRR Continuos Real-time Landsat TM Climate & Atmospheric Forcing MM 5 Land Processes. Hydrology DHSVM urbdp 467 Monitoring Stations Human Dimension Urban Sim Water Resource Allocation CRYSTAL Urban Watershed Hillslope Landcover Mapping Habitat Biotic Resources Shorelines More Arrows
PRISM – Information Integration System Architecture: “the Bloodstream” • Fewer Arrows • Less lines • A “circle”!
Key Points l It’s about Data Integration and Data Sharing l Everyone is either one or more of these: 1. 2. 3. 4. A data source An Occasional default data sink (proactive) A hardwired data sink (proactive) A query sink (retroactive) We’ve begun: l l Relay Node – plasmus. ocean. washington. edu Wiring for example sink and source services Default source and sink services l Investigation of 39 program languages suited for XML-RPC services l l
Design Basis: a framework that simplifies all aspects of scientific data networking, allowing simple access to data 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 DODS Distributed Oceanographic Data System
Design Principle l l 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
Data SOURCE services Data RELAY services Data SINK services l l 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.
What is XML-RPC? l 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. l 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 l l l l l l AOL Server Apache Apple. Script ASP Axapta C/C++ C Cold Fusion COM Delphi/Kylix Dylan Eiffel Flash Frontier Guile Internet Expolrer J 2 ME Java. Script K KDE Lingo Lisp Macintosh OS X client/server client/server client/server client/server client client/server client/server l l l l Microsoft. NET Mozilla Objective C Perl PHP Pike Python REALBasic Rebol Ruby Scheme Tcl Tintware Web. Objects Zope client/server client/server client/server client/server
Default Sink Client (available 11/15/2002) Filtering Available based on XML hierarchy Applet or Application Query results of latest catalog entries Data Access Methods: • Web via URL • FTP via anonymous FTP • Email via request form • Database Query • Other methods required by us Status Updates
Default Source Client (available 11/15/2002) Applet or Application For Querying and Filtering
Miles’ Parting Shots Remember: We’re trying to say: l l l 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