<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Hi Anthony,</div><div><br></div><div>In the background the same "extent" (earliest and latest data) information is used by both services, the availability service simply trims it down to your request time window. It is important to note that this does not mean that time series are guaranteed to exist in that window (there could be gaps that are not represented in our quick-to-query extent information). We are looking towards being able to provide more granular data coverage information, it is a challenging problem.</div><div><br></div><div>If you only want to match your request window to the availability times our fdsnws-station service will already do that for you. The <b>matchtimeseries</b> parameter limits results to channels where the availability intersects with your starttime and endtime selection. In short, add matchtimeseries=true to your request and you do not need to do your own availability checking.</div><div><br></div><div>Regarding the response size, unless you really like XML or need the details included in that format you might consider using the text output (format=text) which is much more compact and easily parsed:</div><div><br></div><div><a href="http://service.iris.edu/fdsnws/station/1/query?starttime=2013-01-01T00:00:00&endtime=2013-01-01T01:00:00&sta=CMB&cha=BHZ&level=channel&matchtimeseries=true&format=text">http://service.iris.edu/fdsnws/station/1/query?starttime=2013-01-01T00:00:00&endtime=2013-01-01T01:00:00&sta=CMB&cha=BHZ&level=channel&matchtimeseries=true&format=text</a></div><div><br></div><div>best regards,</div><div>Chad</div><div><br></div><br><div><div>On Jul 3, 2013, at 12:46 AM, Anthony Lomax <<a href="mailto:alomax@free.fr">alomax@free.fr</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
The European High Schools are using directly the
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
IRIS DMC Web Services for data hosted at IRIS and local
implementations of a subset of these services for other data.<br>
<br>
One local tool we have developed uses an iris type availability ws
to check for data available around the origin time of an earthquake
for a list of networks/stations. The old iris availability service
(deprecated) returns a compact response (even in XML!) for such a
request, e.g.<br>
<blockquote><a class="moz-txt-link-freetext" href="http://www.iris.edu/ws/availability/query?&starttime=2013-01-01T00:00:00&endtime=2013-01-01T01:00:00&sta=CMB&cha=BHZ&output=xml">http://www.iris.edu/ws/availability/query?&starttime=2013-01-01T00:00:00&endtime=2013-01-01T01:00:00&sta=CMB&cha=BHZ&output=xml</a><br>
</blockquote>
<blockquote><StaMessage><Source>IRIS-DMC</Source><SentDate>2013-07-03T07:31:57</SentDate><Station
net_code="BK"
sta_code="CMB"><Lat>38.03455</Lat><Lon>-120.38651</Lon><Elevation>697.0</Elevation><Channel
chan_code="BHZ" loc_code="00"><br>
<Availability><Extent start="2013-01-01T00:00:00"
end="2013-01-01T01:00:00"/></Availability><br>
</Channel></Station></StaMessage><br>
</blockquote>
while the replacement , e.g.<br>
<blockquote><a href="http://service.iris.edu/fdsnws/station/1/query?starttime=2013-01-01T00:00:00&endtime=2013-01-01T01:00:00&sta=CMB&cha=BHZ&level=channel&includeavailability=true">service.iris.edu/fdsnws/station/1/query?starttime=2013-01-01T00:00:00&endtime=2013-01-01T01:00:00&sta=CMB&cha=BHZ&level=channel&includeavailability=true</a><br>
</blockquote>
returns a monster response (attached!) including:<br>
<blockquote><DataAvailability><Extent
start="2010-12-17T19:52:43"
end="2013-07-02T12:00:00"/></DataAvailability><br>
</blockquote>
Note that besides the huge size of the response (we need to make
multiple requests for a list of stations), the
<DataAvailability><Extent in the two responses are
different - the first confirms a data window within our requested
time span (exactly the response we want), while the second seems to
present to total time of data available, which we would have to
further process to confirm that our time window of interest is
available.<br>
<br>
Is all of the above behaviour and the differences between the two
responses correct? Is there any way or any plans to get the more
compact, old-style availability response?<br>
<br>
Thanks,<br>
<br>
Best regards to all,<br>
<br>
Anthony<br>
<br>
<div class="moz-signature">-- <br>
Sent from my iClayTablet <br>
<br>
<hr style="position:absolute; left:0px; width:70%;"> <br>
<b style="color:darkred; font-size:larger">Anthony Lomax</b> <br>
<b style="color:dimgray;">161 Allée du Micocoulier, 06370
Mouans-Sartoux, France</b> <br>
<b style="color:dimgray;"> tel: +33 (0)4 93 75 25 02
e-mail: <a href="mailto:anthony@alomax.net">anthony@alomax.net</a>
web: <a href="http://www.alomax.net/">http://www.alomax.net</a>
</b> <br>
<br>
<b style="color:darkgreen;">Science & Special Topics: </b>
<b style="color:dimgray;"><a href="http://www.alomax.net/science">http://www.alomax.net/science</a></b>
<br>
<b style="color:darkgreen;">Software: </b> <b style="color:dimgray;"><a href="http://www.alomax.net/software">http://www.alomax.net/software</a></b>
<b style="color:darkgreen;"> - updates: </b> <b style="color:dimgray;"><a href="https://twitter.com/ALomaxNet">https://twitter.com/ALomaxNet</a></b>
<br>
<hr style="position:absolute; left:0px; width:50%;"> </div>
</div>
<span><fdsnws-station_2013-07-03T07_33_01.xml></span>_______________________________________________<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>