Closed jstampa closed 5 years ago
Thanks for the feedback @jstampa ! I sent already messages to all people involved on this to solve it ASAP. Despite that we are reviewing everything, could you tell me 3-5 stations you are particularly missing? Just to start with something more concrete. Thanks again.
Hi,
no more Z3 data should be hosted at GFZ node, I think? All german Z3 stations were moved to LMU node, as far as I know.
Meanwhile I can confirm that Z3 stations are not accessible on ODC node: Neither metadata nor waveform data are currently available :-/ Not even with a direct (non-routed) request.
no more Z3 data should be hosted at GFZ node, I think? All german Z3 stations were moved to LMU node, as far as I know.
That's right.
Meanwhile I can confirm that Z3 stations are not accessible on ODC node: Neither metadata nor waveform data are currently available :-/ Not even with a direct (non-routed) request.
@jbienkowski : Could you please provide some details on this, please?
@jstampa Could you mention in particular just 3 to 5 stations from which data must be available and you are not receiving anything? I mean, all details to test the request, Namely, N.S.L.C and time window, as you have already provided the other details.
Hi, it's likely because ODC has some trouble synchronising the metadata from Z3 after stations were moved to LMU. Because of the missing inventory no metadata and waveforms can be downloaded from FDSNWS.
OK. Metadata seems to be already present and available at the ODC server. However, these routes are not present in the Routing Service. @jbienkowski and I are taking a look at this.
Hi everybody, sorry for delay , I was in holiday, now the error seems fixed; in any case I think that this module (fdsnws - auth) in our installation have some issue (dependencies? compatibility?...?) we cannot understand the point and, likely, we need some specialist help. For now, please let me know if also for you the webservice is ok.
Hi @massimo1962 ! Thanks a lot for fixing this!
Client: ObsPy 1.1.1, fdsn.RoutingClient, Python 3.5.3 Auth: eidatoken
Here is a station list i generated today with get_stations() from the RoutingClient. It seems that all the stations that are available through GFZ and ORFEUS nodes are missing. Requesting data from these stations individually also fails, giving a 'No data available for this request.' error message. The same is true for the stations hosted on INGV (the data is also unavailable), even though they appear in the station list.