Members of WG III
There were no changes in functionality requested by WGIII.
Chad has added some clarifications to the documentation of the various services motivated by comments received from the working group. The following items summarize these changes
2013/10/04 – 1.1 release candidate
1) Add description and clarification for the columns of the text formats for fdsnws-station and fdsnws-event.
2) Avoid ambiguity of required parameters by re-naming the appropriate column “Support” and changing the values to “Required” and “Optional”.
3) Add another example request to the fdsnws-event interface illustrating a query for text data and a portion of the response that might be expected.
Since there were no real changes in functionality, please have any comments back to the WG by next Monday 10/21/13. We will put this version up on the FDSN web site next
Monday assuming we hear of no objections.
Dr. Tim Ahern
FDSN Archive for Continuous Data
International Federation of Digital Seismograph Networks (FDSN)
c/o IRIS DMC
1408 NE 45th Street #201
Seattle, WA 98105
(206) 547-1093 FAX
fdsn-wg3-products mailing list
Comments on FDSN Web Service Specification version 1.1 RCI agree that such functionality is important, as this would effect every service I suggest we discuss this in the context of the specification after 1.1.
Doug Neuhauser, doug<at>seismo.berkeley.edu
1. For time series and catalog searches, I think it would be preferable
to specify a half-open time interval:
[start_time ... end_time)
start_time <= interval < end_time
start_time < interval <= end_time
Otherwise, there is no good way to specify non-overlapping time intervals.
2. For time specifications, I would recommend allowing ISO 8601 ordinalThese two time conventions are easily converted on either the server or client end. In my experience more-quickly-discovered errors and errors with less significant impact occur when leaving it on the client end. In this case the "syntactic sugar" is not worth it in my opinion. It would be interesting to hear perspectives from others on the working group.
in addition to the ISO 8601 calendar dates.
3. Table 1 is incomplete.Thanks for the careful read, I will remedy that in the specification.
"longestonly", "quality", minimumlength" used in fdsn-dataselect do
not appear in Table 1 (used in fdsn-dataselect).
Therefore, their types, allowable values, and defaults are never defined.
4. Text output (for fdsnws-event and fdsnws-station) is not well defined.You do not, any that exist in the metadata fields should be replaced with something else.
a. How do you include a vertical bar | in a field?
b. Is it permissible for any field (or all fields) to be empty?For the DMC's services yes.
c. In fdsnws-event, if format=text is specified, does this imply thatFor the DMC's services yes.
the following are invalid (or ignored)?
5. The meaning and use of "includeavailability" in fdsnws-0sstationIn StationXML the data availability extension includes the capability to specify either: details of specific segments and/or extents (min/max). This is left intentionally up to the data center regarding what level of detail is included, the reason being that each data center has different capabilities of reporting these details.
is not well defined.
a. Does this mean include detailed waveform availability for each
channel in the specified time, just a single min and max time for
any waveform in that time interval?
b. Can the waveform starttime be before the time inteval,Yes?
and can the waveform endtime be outside of the time interval?
b. Do you output this info only if "level=channel" is specified?Again, seems like a detail that might depend on data center capability and desires. StationXML is capable of reporting data availability at Channel, Station and Network levels.
c. Do you output this information for every discrete segment ofUp to the data center.
time series data for the channel?
d. How do you represent this info when "format=text" is specified?You do not.
6. What does "matchtimeseries" specify?Neither. The intent of matchtimeseries is: In addition to matching metadata based on selection criteria, the results will be further limited to metadata for which the criteria also match the existence of available time series data.
Need better definition of "where selection matches time series data
availability". Does this mean that you output a metadata segment
iff there is any time series data in that interval, or that you limit
the metadata interval to match each discrete time series segment?
- Doug N
Doug Neuhauser University of California, Berkeley
doug<at>seismo.berkeley.edu Berkeley Seismological Laboratory
Office: 510-642-0931 215 McCone Hall # 4760
Fax: 510-643-5811 Berkeley, CA 94720-4760
Remote: 530-752-5615 (Wed,Fri)
fdsn-wg3-products mailing list