<div dir="ltr">Some of the larger events that have been deleted are described on this page:<div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><a href="http://earthquake.usgs.gov/earthquakes/errata.php">http://earthquake.usgs.gov/earthquakes/errata.php</a><br></div></blockquote><br></div><div><br></div><div>Thanks,</div><div><br></div><div>Jeremy</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 26, 2016 at 10:43 AM, Adam Kalachman <span dir="ltr"><<a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Interesting. Of these non-seismic events, what is the typical range of magnitudes?<div><br></div><div>Thanks,<br>Adam</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 26, 2016 at 9:39 AM, Fee, Jeremy <span dir="ltr"><<a href="mailto:jmfee@usgs.gov" target="_blank">jmfee@usgs.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>The most commonly deleted events are automatic location/magnitudes that turn out not to be a seismic event. In general, we recommend networks leave valid events in their catalogs and accurately represent the quality/uncertainty of the solution.</div><div><br></div><div>Event IDs should not be reused once issued. An event may be undeleted after further review.</div><div><br></div><div><br></div><div>Thanks,</div><div><br></div><div>Jeremy</div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 22, 2016 at 3:35 PM, Adam Kalachman <span dir="ltr"><<a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Jeremy,<div><br></div><div>Thanks, that's helpful. We have a solution for dealing with updates to old events, but I want to know more about deleted events.</div><div><br></div><div>Under what circumstances are events deleted? Are they eventually replaced by other events with the same id?</div><div><br></div><div>Thanks,</div><div>Adam</div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 15, 2016 at 2:30 PM, Fee, Jeremy <span dir="ltr"><<a href="mailto:jmfee@usgs.gov" target="_blank">jmfee@usgs.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Adam,<div><br></div><div>The short answer is there are a couple issues with using feeds to build a catalog:<br></div><div><br></div><div>1) Deleted events are not included in feeds.</div><div><br></div><div>2) Events are only included during the feed lifetime. For example, if you monitor a 1 day feed you won't see any updates to events more than one day old.</div><div><br></div><div><br></div><div>The longer answer is it depends on what you're trying to do with the data. Happy to discuss further.</div><div><br></div><div><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Jeremy</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 13, 2016 at 3:10 PM, Peter Schmidt <span dir="ltr"><<a href="mailto:peter.schmidt@geo.uu.se" target="_blank">peter.schmidt@geo.uu.se</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Adam<br>
<br>
Sorry for intervening on this thread, but speaking from personal
experience, one complication of building a catalog based on feeds
is that from time to time feeds will be issued for spurious
events, hence a minimum requirement is a mechanism to track these
down and remove them from the catalogue. <br>
<br>
Not using GeoJSON feeds from USGS but rather tapping into their
implementation of the FDSN web service I'm not sure how big of a
problem this is for GeoJSON, but at least for the FDSN-WS we have
seen a few of these per year although they seem to have become
less frequent the last year or so (if I remember correctly most of
the spurious events have been issued by the Pacific Tsunami
Warning Seismic System, pt). <br>
<br>
<br>
regP<div><div><div><div><br>
<br>
<br>
On 2016-04-13 20:52, Adam Kalachman wrote:<br>
</div></div></div></div></div><div><div><div><div>
<blockquote type="cite">
<div dir="ltr">Hi Jeremy,
<div><br>
</div>
<div>Can you clarify why building a catalog from the feeds is
not recommended? Presumably having data pushed to us means we
can get it slightly faster, but beyond that, are there other
concerns with using the feed in this manner?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Adam</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Apr 11, 2016 at 11:00 AM, Fee,
Jeremy <span dir="ltr"><<a href="mailto:jmfee@usgs.gov" target="_blank">jmfee@usgs.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Hello,
<div><br>
</div>
<div>The ids in the feeds are "eventually consistent"
because they run on distributed systems that may have
different information at different times. Generally, we
recommend using the feature "id" attribute and when
processing a previously unseen id checking the "ids"
list to see if the system has already processed the
event under a different id.</div>
<div><br>
</div>
<div><br>
</div>
<div>As an alternative to building a catalog from the
feeds (not recommended), and for push access to our
information, you can use our java data distribution
software to build/update the catalog; and trigger
external processing as changes are made.</div>
<div>
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div><a href="https://github.com/usgs/pdl" target="_blank">https://github.com/usgs/pdl</a><br>
</div>
</blockquote>
<br>
</div>
<div>An example configuration of the "indexer" is
available on github:</div>
<div>
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div><a href="https://github.com/jmfee-usgs/pdl-client-examples/tree/indexer" target="_blank">https://github.com/jmfee-usgs/pdl-client-examples/tree/indexer</a><br>
</div>
</blockquote>
<br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Jeremy</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>On Fri, Apr 8, 2016 at 5:12 PM, Adam
Kalachman <span dir="ltr"><<a href="mailto:akalachman@google.com" target="_blank"></a><a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div>
<div dir="ltr">Hi,
<div><br>
</div>
<div>I have a couple of questions regarding id
stability in the GeoJSON earthquakes feed. The
'ids' field appears to specify the id of each
contributing network, but is there any
consistency to the ordering of this field?
Best I can tell, it's neither chronological
nor alphabetical.</div>
<div><br>
</div>
<div>Assuming the order is arbitrary, is there
some way that a stable record id, independent
of any individual sensor networks, could be
added to the GeoJSON schema?</div>
<div><br>
For example, say the feed reports an
earthquake with ids ak000, us001, and nc002,
and preferred id us001. Then a client of the
feed might've seen ak000 and nc002 previously,
and it's the responsibility of the client to
track down those earthquake summaries and
replace or merge them with the new data. If,
however, all three were assigned a single
stable id, say, eq0003, then each updated
summary could more easily replace its previous
versions.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Adam</div>
<span><font color="#888888">
<div>
<div><br>
</div>
-- <br>
<div>
<div dir="ltr"><br>
<div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif;font-size:small"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Adam
Kalachman |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Software
Engineer |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:akalachman@google.com" target="_blank"></a><a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> <a href="tel:256-509-5336" value="+12565095336" target="_blank">256-509-5336</a></span></div>
</div>
</div>
</div>
</font></span></div>
<br>
</div>
</div>
_______________________________________________<br>
Realtime-feed-users mailing list<br>
<a href="mailto:Realtime-feed-users@geohazards.usgs.gov" target="_blank">Realtime-feed-users@geohazards.usgs.gov</a><br>
<a href="https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users" rel="noreferrer" target="_blank">https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr"><br>
<div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif;font-size:small"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Adam
Kalachman |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Software
Engineer |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:akalachman@google.com" target="_blank"></a><a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> <a href="tel:256-509-5336" value="+12565095336" target="_blank">256-509-5336</a></span></div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Realtime-feed-users mailing list
<a href="mailto:Realtime-feed-users@geohazards.usgs.gov" target="_blank">Realtime-feed-users@geohazards.usgs.gov</a>
<a href="https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users" target="_blank">https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users</a>
</pre>
</blockquote>
<br>
<br>
</div></div></div></div><span><font color="#888888"><span><font color="#888888"><pre cols="72">--
********************************************************************************
Peter Schmidt Tel: <a href="tel:%2B46-18-4717104" value="+46184717104" target="_blank">+46-18-4717104</a>
Swedish National Seismological Network (SNSN) Mobile: <a href="tel:%2B46-73-3190975" value="+46733190975" target="_blank">+46-73-3190975</a>
Dept. of Earth Sciences:geophysics e-mail: <a href="mailto:peter.schmidt@geo.uu.se" target="_blank">peter.schmidt@geo.uu.se</a>
Uppsala University
Villavagen 16
SE-75236 Uppsala
********************************************************************************
</pre>
</font></span></font></span></div><span>
<br>_______________________________________________<br>
Realtime-feed-users mailing list<br>
<a href="mailto:Realtime-feed-users@geohazards.usgs.gov" target="_blank">Realtime-feed-users@geohazards.usgs.gov</a><br>
<a href="https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users" rel="noreferrer" target="_blank">https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users</a><br>
<br></span></blockquote></div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><br><div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif;font-size:small"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Adam Kalachman |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Software Engineer |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> <a href="tel:256-509-5336" value="+12565095336" target="_blank">256-509-5336</a></span></div></div></div>
</div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><br><div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif;font-size:small"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Adam Kalachman |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Software Engineer |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:akalachman@google.com" target="_blank">akalachman@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> 256-509-5336</span></div></div></div>
</div>
</div></div></blockquote></div><br></div>