Show picks for all events in QuakeML between given starttime & endtime #50
Conversation
|
Our use case is to have one event per QuakeML file, that's why it's implemented this way, and also inside obspyck current event data is stored as a Catalog object with a single Event and a single Origin/Magnitude. What's your use case? Just plot all the picks and don't modify existing picks or add new picks? |
|
Well actually my idea was simply to review the events one by one to check the picks, for the moment I don't want to re-pick events, just look at them. |
|
I'm a bit unsure about this one, this would be a pretty big change.. maybe it's an option for you to split up the QuakeML file into multiple files (e.g. using obspy) with one event each and use those in separate obspyck runs? |
|
Another thought.. you could try to merge those events into a single event and use that in obspyck, it should be possible to plot all picks then when using the new setting introduced by b88897a. |
|
The problem with splitting the xml and launching obspy for each event is pretty long as it fetches the station xml each time. The best idea would be indeed to have all picks in one event but then I can't use the relocations plugins... |
|
Well, I can add another magic switch that combines all data into one single event at obspyck startup.. just be aware that this will only be useful for displaying and any modifications on picks etc. will be totally haphazard.. that work for you? |
|
Yes I think it might be useful for other people just wanting to check for picks. |
|
This is now a PR, let me know if it works for you like this. |
reding from QuakeML/fetching from server
Hi,
Currently it is possible to plot the picks for one single event (the first one) of the quakeml file. Shall we consider the idea of plotting all the picks associated to multiple events (if t0 of all events are between starttime and endtime given in command line)? Is that out of scope of obspyck's philosophy?
Thanks,
Christian