Web service portal for seismic data
and
KML generator for seismic tomography model
Seiji Tsuboi1, Hiroyuki Yamaji2,
Yasuko Yamagishi1, Hiroshi Yanaka2
1:IFREE, JAMSTEC
2:Fujitsu Ltd.
2008/11/13
0
NINJA
• Seismic data distribution system
• Data center which is operating NINJA
– OHP data center in ERI
– Pacific21 data center in IFREE/JAMSTEC
2008/11/13
1
NINJA Portal
• Data center portal for digital broadband seismograms.
• It can access two data centers at the same time. • Using the technology of Web Service.
2008/11/13
2
Web Service Interface(1)
• It offers a common interface in another data center.
• Interface information is defined in the WSDL and the Data type Schema.
• The standardization of the interface can be achieved by providing for the WSDL and the Data type Schema.
2008/11/13
3
Web Service Interface(2)
NINJA Portal
WSDL
Schema
HTTP
enter
parameters
User
SOAP
Web
Browser
Pacific21
Web service
interface
receive data
OHP
Web service
interface
Web service interface
Web service interface
2008/11/13
User Interface
HTTP
Standard interface
information
SOAP Message
Reference from
・QuakeML
・XML Seed
Logic
Service Proxy
Pacific21
Web service
interface
OHP
Web service
interface
SOAP
Internet
SOAP Message
Reference from
・QuakeML
・XML Seed
SOAP
SOAP
Web view
interface
Web service interface
Cont
Event
Station
data
data
info
Pacific21 NINJA
Data
Controller
Data
Wrapper
Web view
interface
Web service interface
Cont
Event
Station
data
data
info
OHP NINJA
Data
Controller
Data
Wrapper
4
Web Service Interface(3)
Developing Flow
1. Define the WSDL & Schema.
Standard interface
information
WSDL
3. Set in the Datacenter interface.
Datacenter interface
mapping logic
Schema
data
data
Datacenter B
2. Generate the module of interface.
Portal
interface
Datacenter interface
Interface
Generator
2008/11/13
4. Set in the Portal interface.
Portal
Logic
Service Proxy
Portal
interface
5
Web Service Interface(4)
Portal
HTTP
HTTP
enter
parameters
User
User Interface
Developing Flow
SOAP
Logic
Service Proxy
Portal
Portal
interface
interface
A
B
SOAP
Web
Browser
Internet
receive data
SOAP
SOAP
Web view
interface
2008/11/13
Datacenter interface
Cont
Event
Station
data
data
info
Datacenter A
Data
Controller
Data
Wrapper
Web view
interface
Datacenter interface
Cont
Event
Station
data
data
info
Datacenter B
Data
Controller
Data
6
Wrapper
WSDL(1)
• WSDL defines the service of Data Center.
• NINJA Portal assumes three WebServices.
– Database Query service
– Seismic event waveform request service
– Seismic continuous data request service
2008/11/13
7
WSDL(2)
„
Database Query service
service
DBQueryService
operation
parameter
requestSession
getFERegionName
return
sessionResult
latitude
FERegionName
longitude
2008/11/13
searchEventData
eventDataQuery
eventParameters
getContinuousAvailability
continuousDataQuery
continuousData
searchStations
stationQuery
stationList
8
WSDL(3)
„
Seismic event waveform request service
service
SeismicEventWaveform
RequestService
operation
parameter
return
requestSession
sessionResult
getEventLicense
eventLicense
authenticEventLicense
eventLicense
authenticationResult
sessionID
setUserInformation
userInformation
result
sessionID
requestEventWaveform
2008/11/13
eventWaveform
Request
requestResult
sessionID
requestID
getEventWaveformRequestStatus
sessionID
dataStatusList
cancelEventWaveformRequest
sessionID
requestResult
requestID
9
WSDL(4)
„
Seismic continuous data request service
service
SeismicContinuousData
RequestService
operation
parameter
return
requestSession
sessionResult
getContinuousLicense
continuousLicense
authenticContinuousLicense
continuousLicense
authenticationResult
sessionID
setUserInformation
userInformation
result
sessionID
requestContinuousData
2008/11/13
continuousData
Request
requestResult
sessionID
requestID
getContinuousRequestStatus
sessionID
dataStatusList
cancelContinuousRequest
sessionID
requestResult
requestID
10
Data type Schema(1)
• Data type Schema defines the metadata.
• NINJA Portal is using the following Data type Schema.
– QuakeML for parametric data
(by ETH Zurich)
– XML‐SEED for waveform data
(by IFREE/JAMSTEC)
2008/11/13
11
Data type Schema(2)
„
XML-SEED
Data Name
XML-SEED
Attribute
volume_index_control_header
abbreviation_dictionary_control_header
station_control_headers_model_type(Multi)
timespan_control_header
data_records
2008/11/13
Refer to next
page for details.
12
Data type Schema(3)
Data Name
station_control_headers_type
Attribute
station_identifier
station_call_letters
latitude
longitude
elevation
site_name
network_code
station_comment(Multi)
channel_identifier(Multi)
channel_identifier
sample_rate
response_poles_and_zeros(Multi)
response_coefficients(Multi)
reponse_list(Multi)
generic_response(Multi)
decimation(Multi)
channel_sensitivity_gain(Multi)
channel_comment(Multi)
FIR_response(Multi)
2008/11/13
13
Conclusion (1)
• The standardization of the interface can be achieved by providing for the WSDL and the Data type Schema.
• Please try NINJA Portal from following URL.
http://www.jamstec.go.jp/pacific21/
2008/11/13
14
Conversion from seismic tomography model data to KML
• Original tomography model data
– Grid point data of layered model
– File for each depth
• KML
– A Polygon having a rectangle shape for a grid point data
– Grid point coordinate (longitude, latitude, depth) ‐> Coordinate for Polygon’s corners (longitude, latitude, altitude)
– Seismic velocity anomaly ‐> Color of the polygon
Conversion of depth scale to altitude scale
• The Earth’s interior is invisible on Google Earth
• Cross section of the seismic tomography model must be displayed outside of the Earth
• Depth scale ‐> altitude scale
Proposal for vertical cross section
• Earth’s surface ‐> 3,000 km in altitude
• 3,000 km in depth ‐> 0 km
Coordinates of polygon corners
(horizontal cross section)
longitude, latitude
altitude
• On the surface
– altitude = 0
– <clampedToGround> tag
• In the sky
– Earth’s surface ‐> 3,000 km in altitude
– 3,000 km in depth ‐> 0 km – altitude = 3,000 km – depth of the model
– <relativeToGround> tag
Coordinates of polygon corners
(vertical cross section, lon., lat.)
longitude, latitude
• Start and end points of the profile of the model
• New grid point
• New grid point interval < Original grid point interval
• Seismic velocity anomaly of new grid point = that of nearest original grid point
Coordinates of polygon corners
(vertical cross section, altitude)
altitude
• Earth’s surface ‐> 3,000 km in altitude
• 3,000 km in depth ‐> 0 km
Color of polygon
• Three colors at maximum, minimum, and zero seismic velocity anomaly
– C(dV/Vmax), C(dV/Vmin), C(dV/Vzero)
• RGB color space
– C(R(dV/V), G(dV/V), B(dV/V))
• Functions R(dV/V), G(dV/V), B(dV/V) – Quadratic equations
Example Example 2
Example 3
Conclusion (2)
We developed KML generating tool for seismic tomography model. We propose that for vertical cross section;
• Earth’s surface ‐> 3,000 km in altitude
• 3,000 km in depth ‐> 0 km
Please try our KML generetor from following URL.
http://www.jamstec.go.jp/pacific21/
2008/11/13
24