Thread: MUSTANGBETA Questions/Comments

Started: 2014-04-23 19:05:49
Last activity: 2014-04-23 19:05:49
Topics: Web Services
Lion Krischer
MUSTANGBETA Questions/Comments
2014-04-23 19:05:49
Dear all,

I am trying out the MUSTANG Beta web service. Great job!

Apologies if this is not the right place to post this.


I have an issue with the value constraints. It is possible to use, e.g. "value_lt=3” and it will select those measurements with a value of less then 3. The problem arises when querying multiple metrics at once. In that case the constraints are applied to all metrics simultaneously and it does not appear to be possible to restrict it only to one metric.

The following toy query illustrates the problem:

http://service.iris.edu/mustangbeta/measurements/1/query?station=ANMO&channel=BHZ&startafter=2012-10-01&endbefore=2012-10-20&metric=sample_median&metric=max_stalta&value_lt=20


A way out of this would be to prefix the value constraints with the name of the metric, e.g. “max_stalta_value_lt=20”. Then it would be possible to build up fairly complex queries which I imagine being very useful.

Geographical queries would be another nice-to-have feature, e.g. use latitude/longitude bounds instead of/in addition to the currently available SNCLQ filters. Then it would be possible to query for all channels in a certain region that satisfy a list of requirements and directly feed the result to the dataselect FDSN service.


All the best!

Lion

  • Robert Casey
    Re: MUSTANGBETA Questions/Comments
    2014-04-23 15:25:30

    Thank you for the supportive feedback, Lion. I'll note this down as a feature request. This issue makes sense.

    -Rob

    On Apr 23, 2014, at 3:05 AM, Lion Krischer wrote:

    Dear all,

    I am trying out the MUSTANG Beta web service. Great job!

    Apologies if this is not the right place to post this.


    I have an issue with the value constraints. It is possible to use, e.g. "value_lt=3” and it will select those measurements with a value of less then 3. The problem arises when querying multiple metrics at once. In that case the constraints are applied to all metrics simultaneously and it does not appear to be possible to restrict it only to one metric.

    The following toy query illustrates the problem:

    http://service.iris.edu/mustangbeta/measurements/1/query?station=ANMO&channel=BHZ&startafter=2012-10-01&endbefore=2012-10-20&metric=sample_median&metric=max_stalta&value_lt=20


    A way out of this would be to prefix the value constraints with the name of the metric, e.g. “max_stalta_value_lt=20”. Then it would be possible to build up fairly complex queries which I imagine being very useful.

    Geographical queries would be another nice-to-have feature, e.g. use latitude/longitude bounds instead of/in addition to the currently available SNCLQ filters. Then it would be possible to query for all channels in a certain region that satisfy a list of requirements and directly feed the result to the dataselect FDSN service.


    All the best!

    Lion
    _______________________________________________
    webservices mailing list
    webservices<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/webservices



SAGE Facility has been certified as a trustworthy data repository by the CoreTrustSeal Standards and Certification Board
23:25:32 v.22510d55