Archive "Bogus" Events

[emartinez-usgs]

We need a solution to archive "bogus" events from the index. Identifying what is particularly "bogus" is undermined. Potentially events without event parameters (latitude/longitude/time) could be considered bogus.

The situation has occurred where a product is received that specifies an eventSource and eventSourceCode, but not eventTime, eventLatitude, or eventLongitude properties. This leads to an event being created in the index without any event parameters by which the event (and its products) can be archived.

In the case this occurs for an old event that previously existed, the realtime system then begins to mask the ComCat data by instead of serving a "302" redirect to ComCat, the realtime server instead serves incomplete data (or potentially a 409 deleted message).

See:

• http://earthquake.usgs.gov/earthquakes/eventpage/us20005gsg
• http://earthquake.usgs.gov/earthquakes/feed/v1.0/detail/us20005gsg.geojson
• http://earthquake.usgs.gov/fdsnws/event/1/query?eventid=us20005gsg&format=geojson

[vinceq-usgs]

Did someone fix this manually or did it resolve automatically somehow?

[emartinez-usgs]

Unclear. I will look into this more on Monday.

On Friday, June 17, 2016, Vince Quitoriano notifications@github.com wrote:

Did someone fix this manually or did it resolve automatically somehow?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/usgs/pdl/issues/39#issuecomment-226823266, or mute the thread https://github.com/notifications/unsubscribe/ABpZHxqg0aHamGRe4lVCjRs3JIkOBIDMks5qMtHWgaJpZM4I3p54 .

[jmfee-usgs]

These have been fixed in the realtime systems, using the queries described in 41: https://github.com/usgs/pdl/issues/41#issuecomment-234393586