Hi Patty,
I have not worked with Event objects very much, but it looks like you can access the attributes you want in this way:
Your EVTs object is a list of events (in this case, there is only one in the list).
To create an object with just this event in it, and see its attributes, I did this:
In [11]: myevent.origins[0][‘latitude’]
Out[11]: 37.001
So it looks like each Event can have a list of different origins associated with it (though again, there is only one for this event). You could do a similar thing to get the longitude, time, and depth. The “magnitudes” attribute also seems to be structured in a similar way:
If you are puzzled by the setup of all the event related objects, I can
recommend a look at the QuakeML standard. It is quite complex,
admittedly, but it makes sense and the ObsPy Event structure is modeled
pretty closely around it (as QuakeML is the standard Event/Catalog
exchange format right now).