<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">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<br>
      <br>
      <br>
      On 2016-04-13 20:52, Adam Kalachman wrote:<br>
    </div>
    <blockquote
cite="mid:CAMRE77PzZPr7kgApApA9LroLs556P_L0TLwEN=QVQyU5cuA2fw@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <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 moz-do-not-send="true"
              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 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 moz-do-not-send="true"
                      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 moz-do-not-send="true"
                      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 class="h5">On Fri, Apr 8, 2016 at 5:12 PM, Adam
                    Kalachman <span dir="ltr"><<a
                        moz-do-not-send="true"
                        href="mailto:akalachman@google.com"
                        target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:akalachman@google.com">akalachman@google.com</a></a>></span>
                    wrote:<br>
                  </div>
                </div>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <div>
                    <div class="h5">
                      <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
                                        moz-do-not-send="true"
                                        href="mailto:akalachman@google.com"
                                        target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:akalachman@google.com">akalachman@google.com</a></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
                                        moz-do-not-send="true"
                                        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 moz-do-not-send="true"
                    href="mailto:Realtime-feed-users@geohazards.usgs.gov"
                    target="_blank">Realtime-feed-users@geohazards.usgs.gov</a><br>
                  <a moz-do-not-send="true"
                    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 class="gmail_signature">
          <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
                  moz-do-not-send="true"
                  href="mailto:akalachman@google.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:akalachman@google.com">akalachman@google.com</a></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>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Realtime-feed-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Realtime-feed-users@geohazards.usgs.gov">Realtime-feed-users@geohazards.usgs.gov</a>
<a class="moz-txt-link-freetext" href="https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users">https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
********************************************************************************
Peter Schmidt                                      Tel: +46-18-4717104
Swedish National Seismological Network (SNSN)   Mobile: +46-73-3190975
Dept. of Earth Sciences:geophysics              e-mail: <a class="moz-txt-link-abbreviated" href="mailto:peter.schmidt@geo.uu.se">peter.schmidt@geo.uu.se</a>  
Uppsala University
Villavagen 16
SE-75236 Uppsala
******************************************************************************** 
</pre>
  </body>
</html>