You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've put up a service to allow retrieval of the fdsn data metrics. It has the same request parameters as the dataselect query but is outside the fdsn URL path. It will also include any files that have errors in the results. These are excluded from the data select results.
This is an experimental stage one. We can change this anyway as needed.
If no endtime is given it defaults to a period of one day? From my playing that seems to be the case.
Can I ask what constitutes a file error? If I ask for a site ABC, which I presume does not exist, nothing is returned?
This isn't intended as a tool to identify data gaps is it? ObsPy provides obspy-scan, which I have never used, but that seems to be only for data on disk. Is there a tool for gaps from FDSN? I'm not aware of one. Sorry, this is getting a bit off topic.
wrt to gaps etc - you're on the right track. Please view this service as very experimental while @nbalfour and the data team define what it should do.
Errors relates to whether the mSEED file in the archive could be read into the index at all. If there is an error in the metrics service then data for that file won't appear in the dataselect service at all.
I've put up a service to allow retrieval of the fdsn data metrics. It has the same request parameters as the dataselect query but is outside the fdsn URL path. It will also include any files that have errors in the results. These are excluded from the data select results.
This is an experimental stage one. We can change this anyway as needed.
https://beta-service.geonet.org.nz/metrics/fdsnws/dataselect/1/query?starttime=2016-01-09T00:00:00&endtime=2016-01-09T23:00:00&network=NZ&station=CHST&location=01
This chrome extension is useful for viewing JSON in a browser. https://chrome.google.com/webstore/detail/jsonview/chklaanhfefbnpoihckbnefhakgolnmc?hl=en
The text was updated successfully, but these errors were encountered: