<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div>Hi John,</div><div><br></div><div>Sounds like it’s mostly cleared up now (thanks Philip).</div><div><br></div><div>If you really want the data base in 1-day traces for processing, storage, etc. you can always make individual queries. Alternatively you could do the logic to split up multi-day segments on your end.</div><div><br></div><div>Chad</div><div><br></div><div><div>On Jul 14, 2014, at 11:35 AM, John D. West <<a href="mailto:john.d.west@asu.edu">john.d.west@asu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Thanks, Philip! I didn't realize that. Since I am reading the returned file with ObsPy, presumably that it what is assembling the data into contiguous sections. <div class="gmail_extra"><br clear="all"><div>
-- John</div>
<br><br><div class="gmail_quote">On Mon, Jul 14, 2014 at 11:18 AM, Philip Crotwell <span dir="ltr"><<a href="mailto:crotwell@seis.sc.edu" target="_blank">crotwell@seis.sc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<br>
Just one thought that might help clarify things. There is no notion in<br>
miniseed of a "trace" or even a "large contiguous set of data". It is<br>
just a whole bunch of 512 or 4096 byte data records whose begin/end<br>
times might or might not line up to form contiguous data. Any "trace"<br>
that you are seeing is an artifact of whatever you are reading the<br>
miniseed with. The segmentation you are seeing is probably caused by<br>
gaps, and the trace is the longest contiguous section of data.<br>
<br>
If what you want is miniseed files that correspond 1:1 with the lines<br>
of the request, then it would most likely have to be some other<br>
service that returned maybe a tar flle containing miniseed files for<br>
example.<br>
<br>
$0.02<br>
<span class="HOEnZb"><font color="#888888">Philip<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Mon, Jul 14, 2014 at 1:40 PM, John D. West <<a href="mailto:john.d.west@asu.edu">john.d.west@asu.edu</a>> wrote:<br>
> Hi, Chad.<br>
><br>
> Maybe "block" is the wrong term, sorry if it was confusing.<br>
><br>
> I assemble a post request containing 100 lines. In general, each line<br>
> represents one channel of broadband data for one station for one day, from<br>
> 00:00:00 to 23:59:59.9999.<br>
><br>
> My expectation was to get back a miniseed file containing 100 one-day<br>
> traces. Instead, contiguous traces are combined so I get some lesser number<br>
> of traces, many of which are longer than one day. I am not in principle<br>
> opposed to this behavior, but I can envision times when it may cause<br>
> problems, e.g., if I have some processing that has limits on the length of<br>
> the trace to which it can be applied. It seems to me that optimum behavior<br>
> would be a flag set by the user controlling whether you combine traces or<br>
> not.<br>
><br>
> Example: A request containing the following POST data is asking for 100 days<br>
> of data. It returns 27 traces of varying length.<br>
><br>
> POST text:<br>
> quality=B<br>
> TA G06A -- BHE 2008-03-15T00:00:00 2008-03-15T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-14T00:00:00 2008-03-14T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-13T00:00:00 2008-03-13T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-12T00:00:00 2008-03-12T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-11T00:00:00 2008-03-11T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-10T00:00:00 2008-03-10T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-09T00:00:00 2008-03-09T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-08T00:00:00 2008-03-08T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-13T00:00:00 2008-03-13T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-12T00:00:00 2008-03-12T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-11T00:00:00 2008-03-11T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-10T00:00:00 2008-03-10T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-09T00:00:00 2008-03-09T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-08T00:00:00 2008-03-08T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-07T00:00:00 2008-03-07T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-06T00:00:00 2008-03-06T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-05T00:00:00 2008-03-05T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-04T00:00:00 2008-03-04T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-03T00:00:00 2008-03-03T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-02T00:00:00 2008-03-02T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-01T10:23:45 2008-03-01T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-20T00:00:00 2008-03-20T22:22:22.9999<br>
> TA G06A -- BHZ 2008-03-19T00:00:00 2008-03-19T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-18T00:00:00 2008-03-18T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-17T00:00:00 2008-03-17T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-16T00:00:00 2008-03-16T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-15T00:00:00 2008-03-15T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-14T00:00:00 2008-03-14T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-13T00:00:00 2008-03-13T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-12T00:00:00 2008-03-12T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-11T00:00:00 2008-03-11T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-10T00:00:00 2008-03-10T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-09T00:00:00 2008-03-09T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-08T00:00:00 2008-03-08T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-07T00:00:00 2008-03-07T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-06T00:00:00 2008-03-06T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-05T00:00:00 2008-03-05T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-04T00:00:00 2008-03-04T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-03T00:00:00 2008-03-03T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-02T00:00:00 2008-03-02T23:59:59.9999<br>
> TA G06A -- BHZ 2008-03-01T10:23:45 2008-03-01T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-20T00:00:00 2008-03-20T22:22:22.9999<br>
> TA F18A -- BHN 2008-03-19T00:00:00 2008-03-19T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-18T00:00:00 2008-03-18T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-17T00:00:00 2008-03-17T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-16T00:00:00 2008-03-16T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-15T00:00:00 2008-03-15T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-14T00:00:00 2008-03-14T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-13T00:00:00 2008-03-13T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-12T00:00:00 2008-03-12T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-11T00:00:00 2008-03-11T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-10T00:00:00 2008-03-10T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-09T00:00:00 2008-03-09T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-08T00:00:00 2008-03-08T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-07T00:00:00 2008-03-07T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-06T00:00:00 2008-03-06T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-05T00:00:00 2008-03-05T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-04T00:00:00 2008-03-04T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-03T00:00:00 2008-03-03T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-02T00:00:00 2008-03-02T23:59:59.9999<br>
> TA F18A -- BHN 2008-03-01T10:23:45 2008-03-01T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-20T00:00:00 2008-03-20T22:22:22.9999<br>
> TA G06A -- BHE 2008-03-19T00:00:00 2008-03-19T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-18T00:00:00 2008-03-18T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-17T00:00:00 2008-03-17T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-16T00:00:00 2008-03-16T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-07T00:00:00 2008-03-07T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-06T00:00:00 2008-03-06T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-05T00:00:00 2008-03-05T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-04T00:00:00 2008-03-04T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-03T00:00:00 2008-03-03T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-02T00:00:00 2008-03-02T23:59:59.9999<br>
> TA G06A -- BHE 2008-03-01T10:23:45 2008-03-01T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-20T00:00:00 2008-03-20T22:22:22.9999<br>
> TA G16A -- BHZ 2008-03-19T00:00:00 2008-03-19T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-18T00:00:00 2008-03-18T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-17T00:00:00 2008-03-17T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-16T00:00:00 2008-03-16T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-15T00:00:00 2008-03-15T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-14T00:00:00 2008-03-14T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-13T00:00:00 2008-03-13T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-12T00:00:00 2008-03-12T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-11T00:00:00 2008-03-11T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-10T00:00:00 2008-03-10T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-09T00:00:00 2008-03-09T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-08T00:00:00 2008-03-08T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-07T00:00:00 2008-03-07T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-06T00:00:00 2008-03-06T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-05T00:00:00 2008-03-05T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-04T00:00:00 2008-03-04T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-03T00:00:00 2008-03-03T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-02T00:00:00 2008-03-02T23:59:59.9999<br>
> TA G16A -- BHZ 2008-03-01T10:23:45 2008-03-01T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-20T00:00:00 2008-03-20T22:22:22.9999<br>
> TA F10A -- BHN 2008-03-19T00:00:00 2008-03-19T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-18T00:00:00 2008-03-18T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-17T00:00:00 2008-03-17T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-16T00:00:00 2008-03-16T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-15T00:00:00 2008-03-15T23:59:59.9999<br>
> TA F10A -- BHN 2008-03-14T00:00:00 2008-03-14T23:59:59.9999<br>
><br>
> Thanks!<br>
><br>
> -- John<br>
><br>
><br>
> On Thu, Jul 10, 2014 at 7:08 PM, Chad Trabant <<a href="mailto:chad@iris.washington.edu">chad@iris.washington.edu</a>><br>
> wrote:<br>
>><br>
>><br>
>> Hi John,<br>
>><br>
>> Can you provide a bit more detail about what you mean by getting the data<br>
>> back in blocks? In a nutshell, if the data is continuous in the archive,<br>
>> what you get should be continuous as long as you have requested continuous<br>
>> segments.<br>
>><br>
>> In the archive, the internal blocking of the miniSEED data (referred to as<br>
>> records) are sometimes truncated at UTC day boundaries and other times there<br>
>> are records that cross the UTC day boundaries. For the TA data in<br>
>> particular, the R quality data that arrived in real time generally does not<br>
>> include records that cross the day boundaries (it has been cut to perfectly<br>
>> fit within days). But the Q quality data (a preferred copy) that arrives<br>
>> many months after real time does have records that cross day boundaries. On<br>
>> top of this, by default the dataselect service will trim the data requested<br>
>> to the time window specified by the user.<br>
>><br>
>> I think if you can clarify what you are mean by blocking and perhaps<br>
>> provide some example requests we might be able to give you a better answer.<br>
>><br>
>> Chad<br>
>><br>
>> On Jun 30, 2014, at 4:34 PM, John D. West <<a href="mailto:john.d.west@asu.edu">john.d.west@asu.edu</a>> wrote:<br>
>><br>
>> > Hi.<br>
>> ><br>
>> > I'm requesting continuous broadband data from (mostly) TA stations using<br>
>> > the POST usage of the dataselect web service.<br>
>> ><br>
>> > When I request multiple successive one-day blocks in the same POST<br>
>> > request, I sometimes get the data back in 1-day blocks and sometimes it is<br>
>> > combined into longer multi-day blocks.<br>
>> ><br>
>> > What controls this behavior? Is it possible to force the data to be<br>
>> > returned in single-day traces without resorting to sending multiple<br>
>> > individual requests, one per day?<br>
>> ><br>
>> > Thanks!<br>
>> > -- John<br>
>> > _______________________________________________<br>
>> > webservices mailing list<br>
>> > <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
>> > <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> webservices mailing list<br>
> <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
> <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
><br>
</div></div></blockquote></div><br></div></div>
_______________________________________________<br>webservices mailing list<br><a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>http://www.iris.washington.edu/mailman/listinfo/webservices<br></blockquote></div><br></body></html>