iris services initiative
DESCRIPTION
IRIS Services Initiative. Improving Data Access and Integration for the GeoSciences. Linus Kamb, Joanna Muench, Tim Ahern IRIS Data Management Center. IRIS Data Management Center. About 1100 stations in real time Nearly 50TB of seismic data. Growing currently at ~9TB / year - PowerPoint PPT PresentationTRANSCRIPT
IRIS Services Initiative
Improving Data Access and Integration for the GeoSciences
Linus Kamb, Joanna Muench, Tim AhernIRIS Data Management Center
2
IRIS Data Management Center
• About 1100 stations in real time• Nearly 50TB of seismic data• Growing currently at
~9TB / year
• EarthScope contribution raises to ~20TB / year
• Station and instrument metadata
3
Historical Access Methods
• Request methods– Email requests
• BREQ_FAST• NetDC
– Web-based request tools• WILBER, BUD tools
• Delivery methods– Tapes– FTP
4
DHI
• CORBA-based system• Available since 2001• Standard data access interfaces• Core services:
– Network (metadata) server– Event (earthquake info) server– Data (waveform) server
5
DHI Implementations
• Server implementations at:– IRIS, South Carolina, CalTech, Berkeley,
Orfeus, Geofon
• Example client applications:– Vase, JWeed, SOSA, GEE, SOD– SAC, Matlab, GEON SynSeis– EarthMotionMonitor
6
JWeed
7
DHI 2.0
8
New Directions for IRIS
• Mandate to provide data to broader geosciences community
• Provide access to data and data products through web services
• Expand range of services provided– Computational workflows– Added value services
9
IRIS Services Initiative• Develop a Service Oriented Architecture to complement and
enhance core access services
• Internally and externally available components
• Components include:– data access
– pre- and post-processing, filters, transformations
– plotting and mapping
• Move some standard computation to the data
• Provide access methods appropriate to a wider variety of users
• Get useful and usable information to the end user
10
Characteristics of SOA
• Services have contracts• Provides information about itself• Establishes agreement between provider and requestor
• Services are loosely coupled• Can operate together or independently• Changes to one implementation should not break another
• Services are composable• Multiple services can be linked together as workflows• Implies contracts are compatible
• eg. raw data seismogram = processed seismogram
11
Current and Planned Services
SOA Registry
12
Workflows
• Structure and order of a series of tasks
• Movement of data inputs and outputs through computational steps
• Composed of service components – Must be logical composition
• Can be expressed, saved, revised, and re-executed
13
Record Section Plot
14
Workflow Example
15
Workflow Example
16
Workflow Example
17
Workflow Example
18
Workflow Example
19
Workflow Example
20
SPADE
• Searchable Product Archive and Discovery Engine• Archive arbitrary XML data products
– Hypocenters, CMTs, historic data, PGV maps, etc.– As yet unknown data products
• Interface to search by product-specific metadata• Query across products by common fields
– Geospatial, Time, Other (eg., Dublin Core, keywords, ... )
21
SPADE Overview
22
Query - Select Product
23
Query - Enter Filters
24
Query - Results
25
Query - Common Metadata
26
Query - Results
27
IRIS Services Architecture
• Core data access services
• Enhanced data tools
• Wider range of products and services
• Enable scientific workflows
• Increased value and service to the broader geosciences community
28
Challenges
• Service– Description, Registration, Discovery
• Process composition and orchestration– Data management– Value extraction
• Data type coordination– Controlled vocabularies
• Interface-level independence
29
Community Value
• Improve quality and maintainability of IRIS core services
• Enable customization of user experience• Integrate into other organizations’
computational programs through improved accessibility to IRIS data and products
• Support a broader geosciences services architecture