search

GeoNet / help

An issues repo for technical help questions.
6 stars 3 forks source link

FDSN_Client problems with get_events #57

Open iceseismic opened 5 years ago

iceseismic commented 5 years ago

FDSN get_events fails multiple times, without explanation, only succeeding after trying ca 9 times ( with no code changes) : So it succeeds, but only after many unsuccessful attempts...

image

image

francovm commented 5 years ago

Dear @iceseismic,

I tried the same request using obspy.clients.fdsn, and it works well:

from obspy.clients.fdsn import Client as FDSN_Client

client = FDSN_Client("GEONET")

starttime = "2018-11-01 00:00:00.000"
endtime = "2019-07-01 00:00:00.000"
cat = client.get_events(starttime=starttime, endtime=endtime,minlatitude=-39.70,maxlatitude=-37.5
                        ,minlongitude=175.0,maxlongitude=177.5
                        ,minmagnitude=2.5
                        ,mindepth=0.1,maxdepth=32.9)

print(cat)

Also using the URL query (will take a tiome to generate a QuakeML)

https://service.geonet.org.nz/fdsnws/event/1/query?starttime=2018-11-01T00:00:00&endtime=2019-07-07T00:00:00&maxlatitude=-37.5&minlongitude=175.0&maxlongitude=177.5&minlatitude=-39.7&minmag=2.5&mindepth=0.1&maxdepth=32.9

This is one is much quicker, since is retrieving a list of event:

https://service.geonet.org.nz/fdsnws/event/1/query?starttime=2018-11-01T00:00:00&endtime=2019-07-07T00:00:00&maxlatitude=-37.5&minlongitude=175.0&maxlongitude=177.5&minlatitude=-39.7&minmag=2.5&mindepth=0.1&maxdepth=32.9&format=text

salichon commented 5 years ago

@francovm Close this one ?

iceseismic commented 5 years ago

Hi,

I still hit timing problems with get_events when using Geonet client ; but can bypass sometimes by using the IRIS client

I still think you have a problem

cheers

From: jerry notifications@github.com Sent: Thursday, 22 August 2019 10:19 To: GeoNet/help help@noreply.github.com Cc: Stephen Bannister S.Bannister@gns.cri.nz; Mention mention@noreply.github.com Subject: Re: [GeoNet/help] FDSN_Client problems with get_events (#57)

@francovmhttps://github.com/francovm Close this one ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/GeoNet/help/issues/57?email_source=notifications&email_token=AAGK7QE6KIJDSNBSBJ2QQNTQFW5OFA5CNFSM4H4BQAL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD43JONY#issuecomment-523671351, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAGK7QDON3LPYGCDKIRL6ALQFW5OFANCNFSM4H4BQALQ.

Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents.

salichon commented 5 years ago

Hello @iceseismic , Stephen! Thanks a lot for this Hmm I m usually not using python to fetch the quakeml indeed. How long or painful is it ? We have to reproduce your queries i reckon to track this (while in peace time), Can you send us a problematic request ?

Thanks a lot FYI @francovm Cheers Jerome

iceseismic commented 5 years ago

We have to reproduce your queries i reckon to track this (while in peace time), Can you send us a problematic request ? Yes – will do ; just have to replicate one

From: jerry notifications@github.com Sent: Thursday, 22 August 2019 10:53 To: GeoNet/help help@noreply.github.com Cc: Stephen Bannister S.Bannister@gns.cri.nz; Mention mention@noreply.github.com Subject: Re: [GeoNet/help] FDSN_Client problems with get_events (#57)

Hello @iceseismichttps://github.com/iceseismic , Stephen! Thanks a lot for this Hmm I m usually not using python to fetch the quakeml indeed. How long or painful is it ? We have to reproduce your queries i reckon to track this (while in peace time), Can you send us a problematic request ?

Thanks a lot FYI @francovmhttps://github.com/francovm Cheers Jerome

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/GeoNet/help/issues/57?email_source=notifications&email_token=AAGK7QBEDU6A4QAOO5XCKETQFXBNFA5CNFSM4H4BQAL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD43LRGY#issuecomment-523679899, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAGK7QG53YP6IRLJW2PMR3DQFXBNFANCNFSM4H4BQALQ.

Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents.

salichon commented 5 years ago

Hi @nbalfour I reckon this could be useful for our FDSN services bench marking. I talked briefly to Stephen Bannister about it today. And we ll get a typical request on which we can test-proof the issue.

Cheers Jerome

salichon commented 2 years ago

While we are thinking FDSN services work plan @elidana perhaps this one may worth to be put back on investigation for our 2022 services. as fas as i undertand we need to check for: FDSN get_events fails multiple times, without explanation perhaps difficult to reproduce without more context. cf: https://user-images.githubusercontent.com/831424/60312146-3f7c9800-99ae-11e9-898d-27ded0f83ca8.png which is : The HyperText Transfer Protocol (HTTP) 504 Gateway Timeout server

Should you experience this query feature still @iceseismic ?

staylorofford commented 2 years ago

@salichon this possibly relates to maximum query / transfer size. When I have tried to pull large parts of our EQ catalogue I have had errors that are not explicit, i.e., the code fails without any information as to why.

salichon commented 2 years ago

Kia Ora @iceseismic Would you, time allowing, check if this issue still persists on your end in light of the updates in the fdsn services over time ?

thank you :)