[Realtime-feed-users] Delayed feeds and/or events (1+ hours)

[Matt Keller]

Eric,

Sorry for the delay. Just got off work. The most recent example was a quake
this morning at 11:25 AM CST that didn't hit the feeds until around 4:37 PM
CST. The quake's ID is usb000rrac and the URL is
http://earthquake.usgs.gov/earthquakes/eventpage/usb000rrac#summary.

The following quakes are ones that i know missed the past hour feed but
don't have more specific info (like when they hit the feed) because i
wasn't monitoring the past day feed. All i know is that they missed the
past hour feed and my app didn't pick them up.

usc000rpls
usc000rplj
usc000rpye
usc000rqbx
usc000rqwg
usc000rr7z
usb000rr2b

Scott, The URL I'm accessing is
http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_hour.geojson.
My app hits that URL every couple of minutes and checks for new events that
meet certain criteria. (In my case, the Oklahoma City metro area) If it
sees a new event meeting the criteria, the event is parsed, tweeted, and
then added to a database so i don't tweet it out again.

Thanks for everyone's help.


On Wed, Jul 9, 2014 at 8:35 AM, Martinez, Eric <emartinez at usgs.gov> wrote:

> Hi Matt,
>
> If you can reference a few recent, specific instances (event IDs) where
> the event skipped the past hour feed due to latency, I'd be happy to look
> into it. We have not noticed this on our end. The timely reporting of
> earthquake information is important to us, so if it is a problem on our
> end, we would like to fix it.
>
> Regards,
>
> Eric Martinez
> Application Developer
> U.S. Geological Survey
> emartinez at usgs.gov
>
>
> On Wed, Jul 9, 2014 at 6:42 AM, Scott Smurthwaite <smurth at mangolabs.com>
> wrote:
>
>> Matt,
>>
>> I use the feed and have not noticed a lag.
>>
>> which url are you using for the json feed?
>>
>> Scott
>>
>> ----- Original Message -----
>> From: "Matt Keller" <mattrk at mattrk.com>
>> To: realtime-feed-users at geohazards.usgs.gov
>> Sent: Wednesday, July 9, 2014 12:47:35 AM
>> Subject: [Realtime-feed-users] Delayed feeds and/or events (1+ hours)
>>
>>
>>
>> Realtime-feed-users,
>>
>>
>> I've noticed that for the last month or so, earthquakes are showing up
>> later and later after they happen. My app focuses around Oklahoma which
>> doesn't have automatic posting like California. (Not sure why, but i assume
>> that's a $$ issue) Recently I've noticed that a lot of the quakes happening
>> in Oklahoma aren't even hitting the "Past Hour" feed because they are
>> taking 1+ hours to get posted. Since my app (A twitter bot) hits the feed
>> regularly to check for new quakes, I've found the past hour feed to be the
>> most efficient. (Much less data to download and parse) However, with these
>> quakes showing up so late, I'm missing a lot of them. Because of this I'm
>> probably going to have to switch to the "Past Day" feed so i can be sure to
>> catch everything.
>>
>> Does anyone have any idea why this is happening? I'm not really informed
>> enough to know how exactly the entire system works from the waves in ground
>> to the json feed but i would love if someone else more knowledgeable might
>> be able to fill in the blanks for me. Is this something that can be "fixed"
>> or is it just a "that's how it is" type of situation?
>>
>> _______________________________________________
>> Realtime-feed-users mailing list
>> Realtime-feed-users at geohazards.usgs.gov
>> https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users
>> _______________________________________________
>> Realtime-feed-users mailing list
>> Realtime-feed-users at geohazards.usgs.gov
>> 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/20140709/c2886bf7/attachment.html>