Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QuakeML output for all cases #32

Open
claudiodsf opened this issue Mar 31, 2023 · 2 comments
Open

QuakeML output for all cases #32

claudiodsf opened this issue Mar 31, 2023 · 2 comments

Comments

@claudiodsf
Copy link
Member

This is a follow-up of the discussion started in #29.

It would be nice to be able to generate QuakeML in all cases, even if there is no QuakeML output.
Also, QuakeML output should be an option.

This will take quite some work, since we need to create an ObsPy Event() object (including location and picks) from scratch for cases when we don't have a QuakeML (parsed to Event() by ObsPy) as input.

So, I will leave it here for after releasing v1.7.

@krisvanneste, I would like to know if that's a feature you need, or it's just something that would be nice to have.

@krisvanneste
Copy link
Collaborator

krisvanneste commented Mar 31, 2023

I don't personally need this, it just seemed awkward compared to the other output options.

On the other hand, if you implement it, it would probably be best to do it at the beginning of the process flow. It could for instance eliminate the need for custom Pick and Hypo objects in ssp_read_event_metadata.py.

I have partly implemented creation of obspy Event and Pick objects, which may provide a good starting point:

@claudiodsf
Copy link
Member Author

Yes, good idea.

I'll look into that after releasing v1.7 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants