<div dir="ltr">Since the ShakeMap ids are inconsistent, the best bet is probably to store the id from the GeoJSON feed and ignore any ids embedded in Shakemap files (other than to detect ShakeMap id/version changes).<div><br><div><br></div><div>Thanks,</div><div><br></div><div>Jeremy</div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 2, 2015 at 3:34 PM, C. Bruce Worden <span dir="ltr"><<a href="mailto:cbworden@usgs.gov" target="_blank">cbworden@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 style="word-wrap:break-word">Hi,<div><br></div><div>The Regional Seismic Networks (northern California, southern California, Nevada, Utah, etc.) typically don’t prepend their event IDs with their own network ID when generating ShakeMaps, so the ShakeMap products they create don’t have the fully-qualified event IDs embedded within them. </div><div><br></div><div>To complicate matters, the global ShakeMap system, which covers the rest of the US and global earthquakes does prepend the network ID, so those products have embedded event IDs that are consistent with the USGS event IDs. (Though, to complicate matters further, we’ve only been doing that for a year or so, so older maps will have the old style event IDs, without the network ID prepended.)</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Bruce</div></font></span><div><div class="h5"><div><br><div><blockquote type="cite"><div>On Dec 2, 2015, at 1:34 PM, Fee, Jeremy <<a href="mailto:jmfee@usgs.gov" target="_blank">jmfee@usgs.gov</a>> wrote:</div><br><div><div dir="ltr">Hello,<div><br></div><div>Are there specific contributors that have this problem? It may be a misconfiguration, I've added Bruce Worden to the email so he can comment and/or help those contributors fix the problem.</div><div><br></div><div><br></div><div>An event with multiple contributors _may_ have multiple ids, but always has a preferred id. Because of the distributed nature of creating earthquake information, any of the ids from any contributor can be used to access that information. The preferred id is determined by the id assigned by the network with the preferred location ("origin" type product); often the authoritative network for that location.</div><div><br></div><div>These ids appear in the GeoJSON format. The preferred id is the feature id attribute, and a comma separated list of all associated ids as the property "ids".</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><div class="gmail_quote">On Mon, Nov 23, 2015 at 9:08 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">Hi,<div><br></div><div>I've noticed that sometimes the event id in the cont_mi.json shakemap doesn't match the event id of the corresponding earthquake; in particular, the event id sometimes leaves out the catalog id. How is the event id listed in the shakemap determined? Is there a pattern for when catalog is included in the id?</div><div><br></div><div>Thanks,</div><div>Adam<span><font color="#888888"><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>
</font></span></div></div>
<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></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></div></blockquote></div><br></div>