The IRIS DMC provides data to users in several different formats. The following data formats are described here:
The Standard for the Exchange of Earthquake Data (SEED) is a data format intended primarily for the archival and exchange of seismological time series data and related metadata. The format is maintained by the International Federation of Digital Seismograph Networks and documented in the SEED Manual (PDF format). Originally designed in the late 1980s, the format has been enhanced and refined a number of times and remains in widespread use.
A so-called full SEED volume is the combination of time series values along with comprehensive metadata. In essense a full SEED volume is the combination of miniSEED with a matching dataless volume in a single file.
SEED volumes are not designed for data processing and are commonly converted to other formats prior to data processing. The IRIS DMC’s rdseed software can convert full SEED volumes to many different output formats.
Data identification nomenclature ¶
The SEED format uses 4 name components to uniquely identify a time series and provide attribution to the owner of the data:
- Network code: a 1 or 2 character code identifying the network/owner of the data. These codes are assigned by the FDSN to provide uniqueness to seismological data, new codes may be requested.
- Station code: a 1 to 5 character identifier for the station recording the data.
- Location ID: a 2 character code used to uniquely identify different data streams at a single station. These IDs are commonly used to logically separate multiple instruments or sensor sets at a single station.
- Channel codes: a 3 character combination used to identify the 1) band and general sample rate 2) the instrument type and 3) the orientation of the sensor. A convention for these codes has been established and is documented in Appendix A of the SEED Manual.
Another field, referred to as the Quality Indicator, is commonly used to logically separate versions of the same time series. For example, the raw recorded time series and a quality controlled copy (e.g. with timing corrections applied).
Dataless SEED ¶
A dataless SEED volume is the metadata counterpart to miniSEED that contains the geographic coordinates and instrument response information often needed to process the time series data. A dataless can contain a complete and comprehensive history of metadata for one or many networks and stations. A dataless volume does not contain any time series values.
A dataless volume is commonly used to populate a metadata database or in combination with miniSEED to convert time series to an alternate format (using the IRIS DMC’s rdseed software).
A modern alternative to dataless SEED volumes to exchange seismological metadata is the FDSN’s StationXML schema.
Getting a Dataless SEED File ¶
- Generate a request for a dataless using the online form
- Submit a BREQ_FAST style request to email@example.com from your mail client.
- Get a dataless from the BUD Query Interface.
- Download network dataless SEED files from the IRIS FTP site.
miniSEED is the subset of the SEED standard that is used for time series data. Very limited metadata for the time series is included in miniSEED beyond time series identification and simple state-of-health flags. In particular, geographic coordinates, response/scaling information and other information needed to interpret the data values are not included.
Time series are stored as generally independent, fixed length data records which each contain a small segment of contiguous series values. A reader of miniSEED is required to reconstruct longer, contiguous time series from the data record segments. Common record lengths are 512-byte (for real time streams) and 4096-byte (for archiving), other record lengths are used for special scenarios.
A “file” or “stream” of miniSEED is simply a concatenation of data records. Depending on the capabilities of the intended reader the data records for multiple channels of data may be multiplexed together.
More than one programming library exists to support easy reading and writing of miniSEED data without knowing the details of the format, the libmseed library is supported and used extensively by the IRIS DMC.
Getting a MiniSEED File ¶
Submit a BREQ_FAST style request to firstname.lastname@example.org from your mail client.
Submitting MiniSEED data to the DMC ¶
For non-realtime data the DMC is providing a
miniseed2dmc client to data suppliers (available at http://www.iris.edu/pub/programs/). This client runs at the remote suppliers site and sends Mini-SEED records to a server at the DMC. The supplier specifies either files containing records or directories containing files with records and which server at the DMC to submit data to. It is important to emphasize that the client does not send files (just records) so the DMC has no idea of what the submitters’ files were organized or named, etc. The DMC receives a stream of Mini-SEED records.
The sender can ship files that are >2Gb with this, since
miniseed2dmc will turn the files into packet confetti, but on the receiving end, you must make sure that you do not write large files if the operating system doesn’t support it. The manual page for
miniseed2dmc is included in the distribution in the doc directory as a man page.
On the DMC side we run a
ringserver process to catch the streaming data sent by
miniseed2dmc and write it out into file denominations of our choosing. In practice the DMC will run one ringserver process for each supplier. Each ringserver process will “listen” for connections on a network (TCP) port, so each supplier should be assigned a port number.