-
This actually holds true for the current fdsn service as well. The below example uses the obspy fdsn client, which appears to pass arguments properly to urls:
```python
from obspy.clients.fdsn impor…
-
I have been playing with the station service and queries are broken in obspy, but not in the URL, but they return different things with the URL, but that is not surprising. Anyway, it summary I can't …
-
I've tried the station service with Swarm. I get the following error - so this is a client sending a request (we can't change it) is it sending a valid starttime? We should try to make this work on …
-
-
When querying Metadata (Text) via FDSNws for >1 data centers, the merged result (of different requests) includes 1 header line for each request.
See example of query result:
`
#Network|Station|…
-
Hi Howard,
obspy (a common FDSN client) always adds `&format=xml` to the station query URL e.g.,
```
curl "http://beta-service.geonet.org.nz/fdsnws/station/1/query?location=20&station=A*&forma…
-
In order to provide an overview of data holdings available from the service, a new endpoint: `/fdsnws/dataselect/1/extent` could be added that returns selected data channel extents from the `all_chann…
-
Use the same filenames as the DMC's service includes in the Content-Disposition.
-
Hi all
We are using `fdsnxml2inv` script to convert StationXML to
Inventory.
I noticed that converting a StationXML with Station and Channels
**restricted**, the output Inventory is not correctly ge…
-
Hello,
When using FDSN dataselect as data source, it seems the code is expecting data trimmed to the nearest sample. I noted that trying to perform orientationCheck and crossTalk metrics, where the…