<div dir="ltr"><div>Hello,</div><div><br></div><div>Some of the "lag" is from the time it takes for seismic waves to propagate. Some is due to network reporting thresholds. Small, dense networks issue automatic solutions for local events within seconds or minutes after an event. NEIC only issues reviewed solutions, typically 15 minutes after an event to give time for enough station data to arrive. As analysts further review seismic data, new events may be located and existing events updated or removed.</div>
<div><br></div><div>Realtime feeds and the Catalog web service provide snapshots of contributed data, but it is important to keep in mind that the underlying data is changing as these review processes continue. Our latest earthquake and event page applications display the current contents of feeds and search results ( <a href="http://earthquake.usgs.gov/earthquakes/map/">http://earthquake.usgs.gov/earthquakes/map/</a> ).</div>
<div><br></div><div>If you are trying to build a catalog based on feed snapshots, it is simpler to run our catalog software locally (or use our catalog web service). PDL can be downloaded from <a href="http://ehppdl1.cr.usgs.gov/" target="_blank">http://ehppdl1.cr.usgs.gov/</a> , and several examples are available on github at <a href="https://github.com/jmfee-usgs/pdl-client-examples" target="_blank">https://github.com/jmfee-usgs/pdl-client-examples</a> . PDL also triggers configurable processing as data arrives and/or events are updated.</div>
<div><br></div><div><br></div><div>Thanks,</div><div><br></div><div>Jeremy</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jul 12, 2014 at 4:35 AM, David Loring <span dir="ltr"><<a href="mailto:dloring@eircom.net" target="_blank">dloring@eircom.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-IE" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1f497d">Thinking about it the provision of, or changing to, a 2 hour file would resolve virtually all lags. Probably worth considering.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1f497d"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Realtime-feed-users [mailto:<a href="mailto:realtime-feed-users-bounces@geohazards.usgs.gov" target="_blank">realtime-feed-users-bounces@geohazards.usgs.gov</a>] <b>On Behalf Of </b>David Loring<br>
<b>Sent:</b> 12 July 2014 11:09<br><b>To:</b> 'Matt Keller'; 'Harold Lemon'</span></p><div class=""><br><b>Cc:</b> <a href="mailto:realtime-feed-users@geohazards.usgs.gov" target="_blank">realtime-feed-users@geohazards.usgs.gov</a><br>
<b>Subject:</b> Re: [Realtime-feed-users] Delayed feeds and/or events (1+ hours)<u></u><u></u></div><p></p></div></div><div class=""><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><i>For example, if the event occurs at 1pm, and is posted at 1:30pm, the event would fall off the feed at 2pm thus only staying on the feed for 30 minutes.<u></u><u></u></i></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Yup, exactly what happens. This should not be a problem if you are accessing every 5 minutes Matt, except where a quake does not make it to the short list inside one hour as does happen.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">David<span style="font-size:11.0pt;color:#1f497d"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Realtime-feed-users [<a href="mailto:realtime-feed-users-bounces@geohazards.usgs.gov" target="_blank">mailto:realtime-feed-users-bounces@geohazards.usgs.gov</a>] <b>On Behalf Of </b>Matt Keller<br>
<b>Sent:</b> 12 July 2014 01:18<br><b>To:</b> Harold Lemon<br><b>Cc:</b> <a href="mailto:realtime-feed-users@geohazards.usgs.gov" target="_blank">realtime-feed-users@geohazards.usgs.gov</a><br><b>Subject:</b> Re: [Realtime-feed-users] Delayed feeds and/or events (1+ hours)<u></u><u></u></span></p>
</div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal" style="margin-bottom:12.0pt">Harold, <br><br>I'm glad to know I'm not the only one experiencing this issue. With regard to events not staying on the feed for an hour, I always assumed that the "Past Hour" meant that it only showed events that actually occurred within the last hour. For example, if the event occurs at 1pm, and is posted at 1:30pm, the event would fall off the feed at 2pm thus only staying on the feed for 30 minutes. I think this is why my app was missing so many events. The event would be posted 1+ hours after it occurred so it was only hitting the Past Day and longer feeds. Though i could be wrong. <u></u><u></u></p>
</div></div></div></div><br>_______________________________________________<br>
Realtime-feed-users mailing list<br>
<a href="mailto:Realtime-feed-users@geohazards.usgs.gov">Realtime-feed-users@geohazards.usgs.gov</a><br>
<a href="https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users" target="_blank">https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users</a><br>
<br></blockquote></div><br></div>