barsch/seishub.plugins.seismology

Seismology package for SeisHub.

seishub.plugins.seismology's Issues

Multichannel files not compatible with apply_filter option

QuakeML validation issue

Hi again Robert,

I'm receiving a validation error for a set of QuakeML files I'm attempting to upload to my SeisHub db and was wondering if you'd be able to shed some light on a possible reason.

The files all follow the format of the attached xml file (.txt extension to appease GitHub) and wont validate against the RelaxNG schema for 'event' in the seismology plugin.

I assume this is an issue with the .xml files I am feeding seishub but am unsure how to go about troubleshooting this. The files are readable by Obspy's readQuakeML() and readEvents(). Calling isQuakeML() returns 'True' (although I'm unsure how relevant that might be).

Attempting to upload the file yields the following:

chet@chet-Dell-Precision-M3800:~$ curl -v --data-binary @/home/chet/data/GeoNet_catalog/2012p000867.xml -u admin:admin -X POST http://localhost:8080/xml/seismology/event/
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
* Server auth using Basic with user 'admin'
> POST /xml/seismology/event/ HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.35.0
> Host: localhost:8080
> Accept: */*
> Content-Length: 44468
> Content-Type: application/x-www-form-urlencoded
> Expect: 100-continue
> 
< HTTP/1.1 100 Continue
< HTTP/1.1 409 Resource-validation against schema 'seismology_event_QuakeML-1.2-merged.rng' failed. (Could not validate document. (Element quakeml has extra content: eventParameters, line 2))
< Transfer-Encoding: chunked
< Date: Tue, 17 Nov 2015 04:13:14 GMT
< Access-Control-Allow-Origin: *
* Server SeisHub 1.4.0 is not blacklisted
< Server: SeisHub 1.4.0
* HTTP error before end of send, stop sending
< 
* Closing connection 0

Any advise is very much appreciated,

Chet

2012p000867.xml.txt

Stop using pickle

I just noticed that SeisHub (and ObsPy) use pickle to communicate some things. Since this is a networked service, there are no guarantees that data may not be corrupt (accidentally or maliciously). There's even a great big red warning on the module documentation page for pickle about it.

fetching unavailable data from arclink should be controllable in the configuration

..and should default to False, IMO.