[Realtime-feed-users] Event ids in cont_mi.json shakemaps

[Adam Kalachman]

Sounds like a reasonable approach. Thanks a lot for all the help.

On Thu, Dec 3, 2015 at 4:04 PM, Fee, Jeremy <jmfee at usgs.gov> wrote:

> 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).
>
>
> Thanks,
>
> Jeremy
>
>
> On Wed, Dec 2, 2015 at 3:34 PM, C. Bruce Worden <cbworden at usgs.gov> wrote:
>
>> Hi,
>>
>> 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.
>>
>> 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.)
>>
>> Bruce
>>
>> On Dec 2, 2015, at 1:34 PM, Fee, Jeremy <jmfee at usgs.gov> wrote:
>>
>> Hello,
>>
>> 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.
>>
>>
>> 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.
>>
>> 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".
>>
>>
>> Thanks,
>>
>> Jeremy
>>
>>
>> On Mon, Nov 23, 2015 at 9:08 AM, Adam Kalachman <akalachman at google.com>
>> wrote:
>>
>>> Hi,
>>>
>>> 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?
>>>
>>> Thanks,
>>> Adam
>>>
>>> --
>>>
>>> Adam Kalachman | Software Engineer | akalachman at google.com |
>>> 256-509-5336
>>>
>>> _______________________________________________
>>> Realtime-feed-users mailing list
>>> Realtime-feed-users at geohazards.usgs.gov
>>> https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users
>>>
>>>
>>
>>
>


-- 

Adam Kalachman | Software Engineer | akalachman at google.com | 256-509-5336
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/realtime-feed-users/attachments/20151203/3cacee3a/attachment.html>