Web Services

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

Email address
webservices@lists.ds.iris.edu
Type
Subscribers
321
Moderated by
Chad Trabant, Robert Casey, gillian@iris.washington.edu, Gillian Sharer, Rob Casey
Related tags
Web Service
Login to manage your subscriptions
March
February
January
December (2)
November (3)
October (3)
September
August
July
June
May (8)
April
March
February (2)
January
December
November
October
September
August (1)
July (1)
June
May (4)
April
March (3)
February (19)
January (4)
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 October 2011

Philip Crotwell
2011-10-28 22:51:58
I suppose I can fix it on the client side, but if the time window has the same start and end day, no result is returned even if there really was a channel in existence on part of that day. For example, the start time for PAULI is <StartDate>2011-04-26T15:00:00</StartDate>, but asking for the resp for one of its channels on that day with this URL http://www.iris.edu/ws/station/query?net=CO&sta=PAULI&loc=00&chan=HHZ&timewindow=2011-04-26,2011-04-26&level=resp gives: <Response><Status><code>404… [more]
No replies
Philip Crotwell
2011-10-28 18:28:17
Hi For the resp level output from this URL: http://www.iris.edu/ws/station/query?net=CO&sta=PAULI&loc=00&chan=HHN&level=resp The Stage 2 response consists of just a <StageSensitivity> which has a empty <GainUnits/> element. All of the other stages also have sensitivities with the <GainUnit> but it is filled in with the same value as the <InputUnits> of the stage. <Response stage="2"> <StageSensitivity> <SensitivityValue>1</SensitivityValue> <GainUnits/> <Frequency>.05</Frequency… [more]
Replies
Philip Crotwell
2011-10-27 19:20:15 - 2011-10-27 22:43:58
HI Time has gotten away from me, but I will try and read the new schema more carefully soon and send in any more comments I have. But do have three so far. First is, please consider some sort of versioning in the schema. I believe I posted a comment some time back about this, but for an xml schema to be useful, you need to be able to pair an instance XML document with the schema that it uses. My understanding is that this is usually accomplished by adding a version of some kind to the namespa… [more]
Replies
Philip Crotwell
2011-10-20 20:40:38 - 2011-10-21 18:29:28
Hi So two of the three stationXML examples on the SCEC website are invalid. IMHO, a lot of the value of having a schema is lost if it isn't used for validation, at least occasionally. I have to say that writing code to deal with StationXML is made more complicated than it needs to be when the documentation, the xschema, and the examples+web services are all slightly incompatible. It would be really nice if the agreement between these three could be tightened up a bit, especially if stationxml… [more]
Replies
Philip Crotwell
2011-10-21 17:57:33
Hi Small issue, but here is another place where the documentation and the schema don't line up. <!-- Positive integers used as counters for stage numbers, component numbers, etc. --> <xs:simpleType name="CounterType"> <xs:restriction base="xs:integer"> <xs:minInclusive value="0"/> </xs:restriction> </xs:simpleType> The docs seems to indicate that CounterType should start with 1 but the schema says it starts with 0. The use in the stage number of a response, using stage=0 to denote … [more]
No replies
Philip Crotwell
2011-10-20 17:50:25 - 2011-10-21 17:21:06
Hi I am looking into pulling responses via the stationXML XML web service, and am getting a <Response> that contains only a <StageSensitiviy> but the docs in the xschema it should have one of <PolesZeros>, <Coefficients>, etc. From the xschema: <xs:documentation>Choose one of these responses. There should be one response per stage.</xs:documentation> </xs:annotation> An example is <Response stage="2"> in: http://www.iris.edu/ws/station/query?net=II&sta=AAK&loc=00&cha=BH1&timewindow=1990-… [more]
Replies
Philip Crotwell
2011-10-20 18:25:11 - 2011-10-21 17:18:32
HI The "Channel" field in the station URL builder puts "cha" in the query parameters, but from the docs it should be "chan". The result is that if you use the query builder and specify "BHZ" you end up getting all active channels at that station instead of just the one you wanted. For example: http://www.iris.edu/ws/station/query?net=II&sta=AAK&loc=00&cha=BH1&timewindow=1990-11-30%2C1990-11-30&level=resp Philip
Replies
Philip Crotwell
2011-10-20 18:16:49 - 2011-10-20 19:00:57
Hi The schema says that the <Gain> element within a channel <Epoch> "Corresponds to SEED blockette 58 for stage 0." but the xml from the web service does not include a <Gain> element and instead includes a <Response stage="0"> that only contains a <StageSensitivity>. Seems like using stage=0 is a SEED convention that really shouldn't be used in stationXML??? This section of StationXML also seems pretty confusing as there are 4 different places you could put the overall gain, <InstrumentSensit… [more]
Replies
Chad Trabant
2011-10-19 18:29:41
Hello web service users, The DMC's primary storage system that contains the archive will be undergoing maintenance today at 2:00pm Pacific time. We expect the maintenance to take no longer than 30 minutes. This means that the web services that return time series data will not be able to return anything from the archive, data from the real-time buffers should remain accessible. All other services should not be effected. Thanks for your patience, IRIS DMC
No replies
Philip Crotwell
2011-10-19 17:08:01
Hi This URL generates a large number of duplicate <stationEpoch> elements for each station. Oddly, if anything, including a *, is put in the "sta" query item, then the duplicate stationEpoch elements are not there. Deleting the timewindow also removes the duplicate entries. Not sure, but wonder if it is picking up a stationEpoch for each channel? http://www.iris.edu/ws/station/query?net=II&timewindow=1997-06-07%2C2011-06-07&level=sta thanks, Philip
Replies
Robert Casey
2011-10-17 16:02:26
FYI for our web services users. Begin forwarded message: > > We need to shut down the Oracle database for a network interface > switch. This should be a relatively short process. I'll send out > an email when all is back up. > > Sue Schoch > IRIS Data Management Center > _______________________________________________ > dhi-servers mailing list > dhi-servers@iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/dhi-servers
No replies
Chad Trabant
2011-10-06 20:15:28
Hello web service users, The DMC database maintenance is complete and all services are working again. Please let us know if you observe any unexpected behavior. DMC web services team
No replies
Chad Trabant
2011-10-06 18:20:01
Hello web service users, The DMC's database will be down for maintenance starting at 12:00pm Pacific time today. We anticipate no more than an hour of down time. During this time most of the DMC's web services will not work. We will post another message when the services are back in working order. DMC web services team
No replies
Yazan Suleiman
2011-10-05 18:05:06
Hello webservice users, The DMC is pleased to announce the release of the ws-event webservice (version 1.1.0). http://www.iris.edu/ws/event/ The event web service returns event information in the QuakeML format (schema 1.2 RC3). As with most of our other webservices, ws-event accepts simple HTTP GET query parameters. Events may be selected based on location, time, catalog, contributor and internal identifiers. The IRIS DMC receives earthquake location and magnitude information primarily fr… [more]
No replies
Chad Trabant
2011-10-03 16:53:54
Hello web service users, The DMC is experience some internal system troubles that are effecting DMC services. The services will be working intermittently until we can resolve the issues. Our apologies. Web services team
No replies
10:04:25 v.01697673