Web Services

Notifications, questions and comments related to using the DMC’s web services

webservices@lists.ds.iris.edu

Tags: Web Service
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June (1)
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December (1)
November
October
September
August
July
June
May
April
March
February (1)
January

Active Message Threads for July 2014

Dear All To trim, or not to trim, that is the question— Whether 'tis Nobler in the mind to suffer the spaces and dashes of outrageous parsers, or to take Arms against a Sea of spaces, and by opposing end them? ............. This comment from Joachim says it all >> The software changes are just one aspect. In fact, software changes are trivial compared to the nightmare of changing the existing metadata in databases, decades of SEED data, parametric data and so on.<< If it ain't broke don't... [more]
No replies
Chad Trabant
July 23, 2014, 10:30 a.m. - July 31, 2014, 10:13 a.m.
Hello WS users and developers, A recent discussion between FDSN data centers is centered on representation of empty location IDs in StationXML, the default format returned by the fdsnws-station web service. The DMC may be changing how it represents location ID in XML and text formats based on these discussions. We are asking for input as any such change will effect users of our metadata service. Some background: In the SEED channel naming scheme there is a hierarchy of network, station, ... [more]
Replies
Anthony, I agree entirely >> It seems to me that with modern languages a string that is empty or has 1-N spaces is the same thing.....A null string is not the same. So an empty or blank string is the same, valid location code, and null is undefined or uninitialized location code. >>With regards to the "--" pseudo for the location code, is this not needed because sometimes it is not possible or difficult to represent an empty string or even a string?... >>Just my 0.02EUR = $0.0268 What ev... [more]
No replies
John West
June 30, 2014, 4:34 p.m. - July 14, 2014, 2:18 p.m.
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
Replies
Chad Trabant
July 11, 2014, 1:24 p.m.
Hello WS users, The DMC has updated the fdsnws-station service to version 1.1.4: http://service.iris.edu/fdsnws/station/1/ Changes include: * The service will now return the correct media type in the Content-Type HTTP header when the format parameter is used in a POST request. * Matching of time series data availability, when matchtimeseries=true, has been fixed for some cases. This release is backwards compatible with all request tools. regards, IRIS DMC web services team
No replies
Chad Trabant
July 9, 2014, 5:40 p.m.
Hello WS users, The issue described in the notification below has been resolved. Unfortunately the original notification was misdirected and never made it to the list :( The short story is that the DMC’s fdsnws-dataselect web service will no longer accept HTTP HEAD requests, the response to such a request is now a 403 (Forbidden). In the future we may allow the HEAD method again when we can handle them elegantly, although they are minimally useful since we do not include any of the HTTP ... [more]
No replies