[webservices] continuous data with dataselect service

[Chad Trabant]

Hi John,

Can you provide a bit more detail about what you mean by getting the data back in blocks?  In a nutshell, if the data is continuous in the archive, what you get should be continuous as long as you have requested continuous segments.

In the archive, the internal blocking of the miniSEED data (referred to as records) are sometimes truncated at UTC day boundaries and other times there are records that cross the UTC day boundaries.  For the TA data in particular, the R quality data that arrived in real time generally does not include records that cross the day boundaries (it has been cut to perfectly fit within days).  But the Q quality data (a preferred copy) that arrives many months after real time does have records that cross day boundaries.  On top of this, by default the dataselect service will trim the data requested to the time window specified by the user.

I think if you can clarify what you are mean by blocking and perhaps provide some example requests we might be able to give you a better answer.

Chad

On Jun 30, 2014, at 4:34 PM, John D. West <john.d.west at asu.edu> wrote:

> Hi.
> 
> I'm requesting continuous broadband data from (mostly) TA stations using the POST usage of the dataselect web service.
> 
> When I request multiple successive one-day blocks in the same POST request, I sometimes get the data back in 1-day blocks and sometimes it is combined into longer multi-day blocks. 
> 
> What controls this behavior? Is it possible to force the data to be returned in single-day traces without resorting to sending multiple individual requests, one per day?
> 
> Thanks!
>      -- John
> _______________________________________________
> webservices mailing list
> webservices at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/webservices