International Federation of Digital Seismograph Networks

FDSN Working Group III

FDSN Working Group III on Coordination of Products, Tools and Services

This group was established at the 2007 FDSN meeting in Perugia Italy.

FDSN WGIII will identify standard products that may be produced by FDSN data centers. It will advocate product uniformity and methods of production for FDSN products. It will advocate development and distribution of standard software tools that will support the production of FDSN products.

The goal of FDSN WGIII is to coordinate the creation of uniform products at participating FDSN data centers. It will also attempt to standardize services and share tools that produce FDSN approved products.

fdsn-wg3-products@lists.fdsn.org

August
July
June
May
April
March
February
January
December
November
October
September
August (6)
July (11)
June (14)
May
April (1)
March (15)
February
January
December
November
October
September
August
July (1)
June (2)
May (2)
April
March (1)
February (6)
January (1)
December
November
October
September
August (1)
July
June
May
April
March
February
January
December
November
October
September
August
July
June (2)
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 (1)
December
November
October
September
August
July
June (4)
May
April
March
February
January
December
November
October
September (1)
August (1)

Active Message Threads for March 2017

Philip Crotwell
March 10, 2017, 2:22 p.m. - March 20, 2017, 10:04 p.m.
Hi all If/when there is a revision to the FDSN ws spec, I think it should allow the appending of a Z to signify UTC to all input time parameters. Currently there is no timezone on the times and they are limited to: YYYY-MM-DDTHH:MM:SS.ssssss YYYY-MM-DDTHH:MM:SS YYYY-MM-DD This would change to time parameters being expressed as one of these, with the first 2 being preferred. YYYY-MM-DDTHH:MM:SS.ssssssZ YYYY-MM-DDTHH:MM:SSZ YYYY-MM-DDTHH:MM:SS.ssssss YYYY-MM-DDTHH:MM:SS YYYY-MM-DD The reaso... [more]
Replies
Tim Ahern
March 10, 2017, 10:50 a.m. - March 10, 2017, 12:06 p.m.
Hello members of FDSN WG III. As we start preparing for the FDSN meetings in Kobe (July 30-August 4) I would like to have members of WG III submit topics they would like to have considered for the FDSN WG III Agenda. Please send your ideas to me by the end of March and I will produce a draft agenda. I do not have an indication of when the WG meeting will be at this time but I am sure we will know sometime in the next few months. Thanks for your help in this small issue. Dr. Tim Ahern ... [more]
Replies
Philip Crotwell
March 10, 2017, 11:48 a.m.
Hi all I would like to propose that the eventid query param in the FDSN Event web service be deprecated and in its place a new "service method" be created for getting a single event by its publicID. It would look something like this: http://service.example.org/fdsnws/event/2/publicid/<identifier>?<parameters> The parameters for this service method would be limited to nodata, format, includeallorigins, includeallmagnitudes and includearrivals. The event identifier is not a parameter but is ... [more]
No replies
Philip Crotwell
March 1, 2017, 11:45 a.m. - March 6, 2017, 3:52 p.m.
Hi all A common access pattern is to first do an initial wide but shallow query, and then return to do a deep but narrow query. For example asking an fdsn-station ws for stations in a box, displaying those on a map, and then only going back to ask for channels or response for stations as the user clicks on them. Another example would be to query an fdsn-event web service for earthquakes, and then return using things like includeallorigins=true and includearrivals=true to get more detailed in... [more]
Replies
Jeremy Fee
March 3, 2017, 1:12 p.m. - March 6, 2017, 11:54 a.m.
Hello, I'm writing to see if FDSN has interest in adding a JSON output format to the FDSN Event Web Service specification. The JSON format (and specifically GeoJSON) are very useful for integrating data into web applications and other programming languages. USGS has already implemented GeoJSON FeatureCollection (many events) and GeoJSON Feature (one event) outputs for our FDSN end point and near-real time feeds, which is described on this page and could be a starting point for standardiza... [more]
Replies