Open segburg opened 3 years ago
thanks @segburg
future discussion and work in Geonet/tickets: https://github.com/GeoNet/tickets/issues/7736
Finalisation here - when understood and done
@segburg would you mind to precise the entire time window of investigation you worked on in order to identify if this could be associated to a unique period of time ? thanks a lot
I was looking at 2012-2020
There is also this event with an origin id but nothing else: https://service.geonet.org.nz/fdsnws/event/1/query?eventid=2019p431888. Quakesearch returns more complete information though: 2019p431888,earthquake,2019-06-09T19:10:11.104Z,2019-06-09T19:13:33.266Z,176.2471619,-38.20523834,3.188777932,142.2965698,M,,LOCSAT,confirmed,manual,iasp91,47,41,75,0.05085235834,46.94885254,0.5494196773,0
Below is a list of a few more event xmls with MLv station magnitudes but missing MLv amplitudes and no network MLv: 2012p318469 2012p449454 2012p478269 2013p289288 2013p416398 2013p434263 2013p437956 2013p706831 2018p818207 2019p109870
HNY @segburg !
okay for t 2012-2020
it looks like an an occasional feature. Will llook at these specific conditions
and follow up as in https://github.com/GeoNet/help/issues/78#issuecomment-747723060
There is also this event with an origin id but nothing else: https://service.geonet.org.nz/fdsnws/event/1/query?eventid=2019p431888. Quakesearch returns more complete information though: 2019p431888,earthquake,2019-06-09T19:10:11.104Z,2019-06-09T19:
@segburg this is looking a different issue but interesting. I ll look at it - Check that the sc3xml is existing as opposed to the fdsnxml
you can find the corrected file here: https://github.com/GeoNet/tickets/files/5890112/2019p431888_AssOrigin.xml.txt
thanks @segburg
* [x] Detail the missing bits of amplitude information * [x] Investigate the reason(s) * [x] Track if it is a systematic feature and list the affected other events -->> occasional cause to detail ( event list as in [Quake Catalogue - Occasional amplitude information missing from the event xml #78 (comment)](https://github.com/GeoNet/help/issues/78#issuecomment-756532665) ) * [ ] Test if the actual ampliude measurement can be restored * [ ] Address the event update mechanism in AWS and if updating the event archive with completed information is relevant FYI @elidana @JonoHanson
future discussion and work in Geonet/tickets: GeoNet/tickets#7736
Finalisation here - when understood and done
This still needs to be finalized
I encountered a few event xml files for which amplitude informations are missing. Contributing station magnitudes are included, and refer to Mlv amplitude Ids, which are missing.
The publicids with missing amplitude informations are below, but there could be more: 2013p545297.xml 2014p051690.xml 2014p052015.xml 2014p052498.xml 2014p354109.xml 2014p004933.xml 2014p051854.xml 2014p052055.xml 2014p242353.xml 2014p008685.xml 2014p051920.xml 2014p052137.xml 2014p258757.xml