1 / 28

Conversion of SEED format to XML representation for a new standard of seismic waveform exchange

Conversion of SEED format to XML representation for a new standard of seismic waveform exchange. Seiji Tsuboi (IFREE/JAMSTEC) and Shin’ya Morino (Hakusan Corp.). What is SEED?. Widely used among global broadband seismograph networks as Standard for the Exchange of Earthquake Data (SEED)

jelani-underwood
Download Presentation

Conversion of SEED format to XML representation for a new standard of seismic waveform exchange

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conversion of SEED format to XML representation for a new standard of seismic waveform exchange Seiji Tsuboi (IFREE/JAMSTEC) and Shin’ya Morino (Hakusan Corp.)

  2. What is SEED? • Widely used among global broadband seismograph networks as Standard for the Exchange of Earthquake Data (SEED) • Designed in 1987 by Federation of Digital broadband Seismograph Network (FDSN), which is under the International Association of Seismology and Physics of the Earth’s Interior (IASPEI).

  3. SEED Format Organization • Control headers (formatted in ASCII) information about the volume, the station-channels, and the data • Time series (binary, unformatted) seismic waveform data

  4. Blockettes • Each control header is made up of a sequence of blockettes –data structures that contain a type identifier, length and sequence of data fields specific to the blockette type.

  5. Problems of SEED format • No major revision since 1993 • Each field has a fixed length, which makes it difficult to include new features in the format. • Huge amount of seismic waveform data are stored as mini-SEED format in data centers of broadband seismographic networks.

  6. XML Representation of SEED format • eXtensible Markup Language (XML) is a text-based language. • XML documents use `tags’ to establish hierarchical data structure and named values. • XML can be used for most of all major platforms. • XML is a basic technology for networking.

  7. Advantages of using XML • Header structure of SEED is modular, which can be easily represented by XML. • Data structure of XML is flexible, because length of any fields is not fixed. • XML has its schema language –XML-Schema, which can be used for validation of XML document.

  8. Design requirements of conversion of SEED to XML representation • Entities described in the current SEED headers should be identical to those described in XML representation. • Changes in structures of SEED headers should be as small as possible. • XML document should have structures that allow validation with XML-Schema language.

  9. Conversion of control header <?xml version="1.0" ?> <xseed> <volume_control_header> <!--For blockettes in volume control header --> </volume_control_header> <abbreviation_dictionary_control_header> <!--For blockettes in abbreviation dictionary control header --> </ abbreviation_dictionary_control_header > <station_control_header> <!--For blockettes in volume control header --> </station_control_header> <timespan_control_header> <!--For blockettes in volume control header --> </timespan_control_header> </xseed>

  10. Conversion of blockette Blockette will be represented as follows with blockette name as 'blockette_name', and blockette type as '555', <blockette_name blockette="555"> <!-- Fields to be inserted --> </blockette_name> 'Length' field is not required in XML representation.

  11. Example of conversions: Volume identifier blockette <volume_identifier blockette=”010”> <version_of_format >Trial</version_of_format> <logical_record_length>12</logical_record_length> <beginning_time>1992-01- 01T00:00:00.0000</beginning_time> <end_time>1992-01-02T00:00:00.0000</end_time> <volume_time>1993-01-29</volume_time> <originating_organization>IRIS_DMS</originating_organization> <label>Data for 1992-01-01</label> </volume_identifier>

  12. Data Records(1) Separated header file and data

  13. Data records(2) decoded in base64 <data_records> <data_record sequence_number="000001"> <data_header> header information </data header> <chunk data_record_length="4048"> 6AMAAAoBDAAAAAAAAAAAAAKpqqr egAIAREAXQBM/8H/FP/GALoAlxqpaqon </chunk> </data record> </data records>

  14. XML-SEED formatted data are now provided through Pacific21 Data Center • http://www.jamstec.go.jp/pacific21/xmlninja • Seismograms are formatted either in format1 (binary mini-seed) or format2 (bas64 encoded mini-seed) • Software to convert full-SEED volume to XML-SEED and to read XML-SEED volume are also provided through the Pacific21 Data Center

  15. Pacific21 Broadband Seismographic Stations

  16. seedconv • Converts full-SEED volume to XML-SEED volume based on our XML-SEED schema • There are two formats to represent seismograms: (1) format1: binary mini-SEED data follows after XML represented SEED header. (2) format2: base64 encoded mini-SEED data are represented in XML and follows after XML-SEED header. • Runs on Solaris8/SPARC platforms

  17. xrdseed • Reads XML-SEED volumes and output header information and seismograms. • Based on rdseed • Runs on Solaris8/SPARC platform.

  18. Future direction of XML-SEED • XML-SEED ver. 1.0 may implement - multiple data records in one logical record - other encoding scheme of data records, such as CM6 - complete and consistent XML-Schema, which may include new data fields (tags), such as data center

More Related