obspy/obspy — pull request #425 by mbyt (2012-10-12 18:41:15+00:00)
Title: Mseed timing quality

# Adding support for timing quality and configuration info in mseed

This pull requests is a basic implementation of the feature requested
by R.S (2012-09-07):

```
As I mentioned the collection of large amounts of data may become
a bottleneck at some point. In case a user can extract certain information
(qc parameters) from the requested data before transfering the data itself
(by ArcLink or webservices) it may help him/her (or a tool) to do a
selection prior to the transfer. I guess this requires the data center to
run obspy (with modules to provide qc parameters) but also a kind of
client/server relation in obspy.

The extraction of qc information as time series from the data (mini-SEED)
is useful anyway. As an example, I sometimes would like to monitor the
stability of the timing quality over time (which requires the presence of
blockette 1001 I believe). Also, looking for data which includes a
calibration signal (one of
the 3?? blockettes) is useful. As this information is available in each
header of a miniSEED record, and usually the records have different time
lengths, it will produce a non-uniform sampled time series. Can ObsPy
currently handle that ?
```

Features:
* only retrieved on request, when adding details flag
* works also for headonly
* when details are specified timing quality and configuration info are added to the condition to split in contiguous segments
* test added for timing quality, could not find a mseed file containing configuration info