agenda fdsn wg2 3 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Agenda FDSN WG2+3 PowerPoint Presentation
Download Presentation
Agenda FDSN WG2+3

Loading in 2 Seconds...

play fullscreen
1 / 7

Agenda FDSN WG2+3 - PowerPoint PPT Presentation


  • 93 Views
  • Uploaded on

Agenda FDSN WG2+3. SEED issues Order of FIR filter coeff (bl 54) QC flag indicating M for merged data Est. delay and corr. Applied fields bl 57 Minor SEED manual changes Real time data exchange—protocols and methods Standard interface to link distributed data centers Redistribution of data

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Agenda FDSN WG2+3


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
agenda fdsn wg2 3
Agenda FDSN WG2+3
  • SEED issues
    • Order of FIR filter coeff (bl 54)
    • QC flag indicating M for merged data
    • Est. delay and corr. Applied fields bl 57
    • Minor SEED manual changes
  • Real time data exchange—protocols and methods
  • Standard interface to link distributed data centers
  • Redistribution of data
  • XML developments (QuakeML)
  • Proposal station codes (Shapira, Buland, Bossu)
standard interface to link distributed data centers
Standard interface to link distributed data centers
  • Existing interfaces are e.g. arclink, DHI and NINJA. New developments include the use of web services.
  • Existing connection between DHI and arclink.
  • Small community of knowledgeable people
  • Need for a standard schema for web services (connects to XML)
  • Action: bring experts together to discuss further
seed issues
SEED issues
  • Blockette 57, new wording proposed for ‘estimated delay’ and ‘correction applied’;clarification-> Accepted
  • Specification of the order of coefficients (time forward order); clarification in the description-> Accepted
    • Remark: list of dataloggers with generic response is worthwhile
    • Remark: add minimum phase for non-symmetric filters
  • Introduce flag M as header/quality indicator (ext. of D,R&Q) ->Accepted
    • Remark: not for users, but for network operators
  • SEED manual change; correction ->Accepted
  • Proposal for fixed header reserve bit-> will be send around
real time data exchange protocols and methods
Real-time data exchange; protocols and methods
  • There is a need to identify a standard RT data exchange protocol
    • Tsunami: SEED accepted (FDSN format), no RT exchange standard. Seedlink as de-facto standard?
    • More protocols are available. Davis will email document. What are requirements for an evaluation? How many real protocols are there? Start of a discussion.
    • Action: make a list of protocols and its usage and further discuss an evaluation over email.
redistribution of data
Redistribution of data
  • Basic idea: truly open access to data
  • Problem: standardized reporting on the usage of the data
  • Data request from a portal, where it is important that the data is served from distributed centres.
xml developments quakeml
XML developments (QuakeML)
  • Winfried presented an overview of QuakeML developments (copy will be distributed)
  • Web services development within Earthscope
    • QuakeML was late in the ES developments
    • How rigid is the current design?
  • First version of the software will be released soon
  • IRIS is happy to embrace it, but with possible modifications
  • In Japan they have their own developments, mainly interest in XML for waveform exchange.
station codes
Station codes
  • Problem: present station codes are not sufficient (Registry problem)
  • Recent (June) proposal different from earlier one. Needs clarification.
  • proposal looks attractive, but
  • careful to make changes, it effects DC operations
  • Impact on user requests?