FDSN Event Service - Lost event information during conversion from SC3ML to QuakeML

[segburg]

Here is an instance where all picks, arrivals, amplitudes, magnitudes,... were lost during the conversion from Seiscomp3ML to QuakeML. I can't attach the xml files but here is what I entered in the browser line:
https://service.geonet.org.nz/fdsnws/event/1/query?eventid=2019p431888
http://seiscompml07.s3-website-ap-southeast-2.amazonaws.com/2019p431888.xml

[salichon]

Hi @segburg thanks for this
Is there more than this one-off case ?
The origin might be somewhere around these geonet repos:
seiscompml-to-quakeml
OR
fdsn)
Although need confirmation which is the one active (most likely the latest fdsn)

Issue: The original sc3xml for this event is truncated from detailed information in its quakexml content.

@junghao Can you reproduce the quakeml truncation and track the origin of the issue?
is it a bug and non-unique?
thanks :)
Cheers
jerome

[salichon]

the information content of the event page looks ok as opposed to the quakeml file. https://www.geonet.org.nz/earthquake/technical/2019p431888

[segburg]

I am sure that I have encountered a few f this kind, but I have lost track of the publicids. Often just the amplitudes are missing instead. It seems to be something particular about this sc3xml that doesn't get converted properly, but what?

[segburg]

Another event file having lost all info https://service.geonet.org.nz/fdsnws/event/1/query?eventid=2014p231806
compared to the seiscomp3ML http://seiscompml07.s3-website-ap-southeast-2.amazonaws.com/2014p231806.xml

[salichon]

• Would require to re-update the FDSN event DB at least partially