[webservices] Earth-unit Conversion Issue with LDO/BDO Channel Data in timeseries product?

[Robert Weekly]

Hi Alex,

We have identified the underlying issues related to this problem and have recently released new versions of the impacted software.  You should find that the query you included now works properly.

Thank you for bringing this issue to our attention and for your continued support of the IRIS DMC web services.

Cheers,
Robert

_______________________________
Robert Weekly
Quality and Deployment System Engineer
[e] rtweekly<at>iris.washington.edu


> On Dec 1, 2014, at 7:58 AM, Alex Jacques <alexander.jacques at utah.edu> wrote:
> 
> Hello Support,
> 
> Thank you for providing such a great suite of web service products, they have been extremely useful for my research which examines the atmospheric pressure data collected by the US Transportable Array (TA).  For my work, the timeseries product has been immensely helpful, however I've run into a bit of a snag over the last week when attempting to query data from the LDO/BDO channels for the TA and N4 networks (pressure data from the Setra 278 sensors).  I'm able to query and see the "integer count" data just fine as shown in the plotting tool example below...
> 
> http://service.iris.edu/irisws/timeseries/1/query?net=TA&sta=N63A&loc=EP&cha=LDO&start=2014.330T12:00:00&end=2014.331T12:00:00&output=plot
> 
> However, when I attempt to apply the instrument correction argument (correct=true) to get the data into earth units, which is the actual pressure reading, I receive an internal server error.
> 
> http://service.iris.edu/irisws/timeseries/1/query?net=TA&sta=N63A&loc=EP&cha=LDO&start=2014.330T12:00:00&end=2014.331T12:00:00&output=plot&correct=true
> 
> It appears that perhaps the internal conversion function is not understanding the conversion string information properly, but that is just a cursory look from my end based on the information provided to me from the error display.  Would it be possible for someone to take a look at this?  I do use other channels that contain atmospheric data as well (LDM/BDM for example) and those appear to be working properly, I'm unclear on if this issue is occurring with any other channels or networks.
> 
> Thanks for taking a look into this.
> 
> Alexander Jacques
> Ph.D. Candidate - Atmospheric Sciences
> Programming Support - MesoWest
> University of Utah
> INSCC Rm. 484
> (801) 581-4362
> Alexander.Jacques at utah.edu
> _______________________________________________
> webservices mailing list
> webservices at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/webservices