[Realtime-feed-users] Id stability in the GeoJSON feed

[Fee, Jeremy]

Hello,

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.


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.

https://github.com/usgs/pdl


An example configuration of the "indexer" is available on github:

https://github.com/jmfee-usgs/pdl-client-examples/tree/indexer



Thanks,

Jeremy


On Fri, Apr 8, 2016 at 5:12 PM, Adam Kalachman <akalachman at google.com>
wrote:

> Hi,
>
> 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.
>
> 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?
>
> 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.
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/realtime-feed-users/attachments/20160411/efbe8ac3/attachment.html>