[Realtime-feed-users] North Korea earthquake data not showing on 2.5_week.geojson

[Fee, Jeremy]

Hi Tony,

Can you provide the API url example you are trying to use that is hanging?

Sometimes queries across long time spans do not run quickly, and need to be
broken into multiple API requests for better performance.  A minimum
magnitude threshold is also useful to improve performance.  For example,
this API request is for all explosions above magnitude 2.5 since January 1,
2017.  I chose the GeoJSON output format, which is recommended for most
programmatic uses:

https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson&starttime=2017-01-01&minmag=2.5&eventtype=explosion



Thanks,

Jeremy


On Mon, Sep 11, 2017 at 11:03 AM, Tony Anecito <adanecito at yahoo.com> wrote:

> Hi Jeremy,
> Ok I am almost happy. I try to filter by eventtype but the query just
> seems to hang. Where can I find an example query using eventtype? Is there
> some test script somewhere I can look at for that? BTW this is really cool.
>
> Many Thanks,
> -Tony
>
>
> ------------------------------
> *From:* Tony Anecito <adanecito at yahoo.com>
> *To:* "Fee, Jeremy" <jmfee at usgs.gov>
> *Cc:* "realtime-feed-users at geohazards.usgs.gov" <realtime-feed-users@
> geohazards.usgs.gov>
> *Sent:* Monday, September 11, 2017 10:12 AM
>
> *Subject:* Re: [Realtime-feed-users] North Korea earthquake data not
> showing on 2.5_week.geojson
>
> Hi Jeremy,
> Ok I looked at the API and I am wondering how far back in time I can go.
> The data I am looking for is not frequent so maybe a handful if that over a
> period of months.
>
> Best Regards,
> -Tony
>
>
> ------------------------------
> *From:* Tony Anecito <adanecito at yahoo.com>
> *To:* "Fee, Jeremy" <jmfee at usgs.gov>
> *Cc:* "realtime-feed-users at geohazards.usgs.gov" <realtime-feed-users@
> geohazards.usgs.gov>
> *Sent:* Monday, September 11, 2017 10:02 AM
> *Subject:* Re: [Realtime-feed-users] North Korea earthquake data not
> showing on 2.5_week.geojson
>
> Thanks, I did not want to assume that but noticed the testing code of that
> service had those listed.
>
> Best Regards,
> -Tony
>
>
> ------------------------------
> *From:* "Fee, Jeremy" <jmfee at usgs.gov>
> *To:* Tony Anecito <adanecito at yahoo.com>
> *Cc:* "realtime-feed-users at geohazards.usgs.gov" <realtime-feed-users@
> geohazards.usgs.gov>
> *Sent:* Monday, September 11, 2017 9:56 AM
> *Subject:* Re: [Realtime-feed-users] North Korea earthquake data not
> showing on 2.5_week.geojson
>
> Hello,
>
> The valid combinations for realtime feeds are listed on the GeoJSON
> Summary page:
>
> https://earthquake.usgs.gov/earthquakes/feed/v1.0/geojson.php
>
>
> All magnitudes, M1.0+, M2.5+, and M4.5+.
>
>
> You can also query the API directly, however results are cached for 15
> minutes (realtime feeds are only cached for 1 minute for up to 7 days, one
> month feeds are also cached for 15 minutes):
>
> https://earthquake.usgs.gov/fdsnws/event/1/
>
>
> Thanks,
>
> Jeremy
>
>
>
>
> On Mon, Sep 11, 2017 at 9:39 AM, Tony Anecito <adanecito at yahoo.com> wrote:
>
> Thanks Jeremy.
> I left later messages indicating I figured that out and something else I
> found. Mainly now I am looking for info regarding what range of values are
> valid for the request url since I discovered 2.5_month (in the url) returns
> geojson but not 2.0_month. The examples do not indicate that limitation so
> that is why I was wondering where there might be info about that. Else the
> developers have to request all the earthquakes for the hour or day or week
> or month then filter the resultant geojson response based on magnitude.
>
> Best Regards,
> -Tony
>
>
> ------------------------------
> *From:* "Fee, Jeremy" <jmfee at usgs.gov>
> *To:* Tony Anecito <adanecito at yahoo.com>
> *Cc:* "realtime-feed-users@ geohazards.usgs.gov
> <realtime-feed-users at geohazards.usgs.gov>" <realtime-feed-users@
> geohazards.usgs.gov <realtime-feed-users at geohazards.usgs.gov>>
> *Sent:* Monday, September 11, 2017 9:26 AM
> *Subject:* Re: [Realtime-feed-users] North Korea earthquake data not
> showing on 2.5_week.geojson
>
> Hello,
>
> This is likely related to when you accessed the feed.  The
> event us2000aert occurred at 2017-09-03T03:30:01.940Z, and currently
> appears in the M2.5+ month geojson feed; so it would have been included in
> the M2.5+ week geojson feed until 2017-09-10T03:30:01. 940Z.
>
> If you accessed the feed before this time and the event was not included,
> please provide any details for us to troubleshoot further.
>
>
> The GeoJSON summary format is described on this page, and there links to
> related information in the left navigation:
>
> https://earthquake.usgs.gov/ earthquakes/feed/v1.0/geojson. php
> <https://earthquake.usgs.gov/earthquakes/feed/v1.0/geojson.php>
>
>
>
> Thanks,
>
> Jeremy
>
>
>
>
>
>
> On Sun, Sep 10, 2017 at 12:28 PM, Tony Anecito <adanecito at yahoo.com>
> wrote:
>
> Hi All,
>
> I noticed the N. Korean earthquake data does not show up on the
> 2.5_week.geojson request. Anyone know why? It does show up on the
> all_month.geojson request.
>
> Also, where can I find the listing for the API?
>
> Thanks!
> -Tony
>
> ______________________________ _________________
> Realtime-feed-users mailing list
> Realtime-feed-users@ geohazards.usgs.gov
> <Realtime-feed-users at geohazards.usgs.gov>
> https://geohazards.usgs.gov/ mailman/listinfo/realtime- feed-users
> <https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users>
>
>
>
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/realtime-feed-users/attachments/20170913/472d57fe/attachment-0001.html>