THIS PROJECT HAS BEEN ARCHIVED
Please see [https://code.usgs.gov/ghsc/neic/utilities/earthquake-processing-formats)
The US Geological Survey (USGS) National Earthquake Information Center (NEIC) defines a number of data exchange formats to communicate seismic event processing information between seismic data services and/or algorithms. These formats are defined using objects as defined in the JSON standard.
The purpose of this project is to:
- Define formats to hold data required for various types of seismic event processing algorithms.
- Store the format definitions in a source controlled manner.
- Host libraries used to generate and parse the formats
- Location Request Format - A format for for requesting an updated location from a location algorithm
- Location Result Format - A format for for a result from a location algorithm
- Pick Format - A format for pick data from a waveform arrival time picking algorithm or human analyst.
- Travel Time Request Format - A format for requesting travel time data
- TravelTimeSession Format - A format for setting up a travel time session
- Error Elllipse Object - An object that contains information about travel time data returned as part of a travel time request.
- Hypocenter Object - An object that contains information about a hypocenter.
- Site Object - An object that defines the station used to create a pick.
- Source Object - An object that defines the creator/source of a pick, request, or result.
- Travel Time Data Object - An object that contains information about travel time data returned as part of a travel time request.
- Travel Time Plot Data Object - An object that contains information about travel time plot data returned as part of a travel time request.
- Travel Time Plot Data Branch Object - An object that contains information about travel time plot data branch returned as part of a travel time request.
- Travel Time Plot Data Branch Object - An object that contains information about travel time plot data sample returned as part of a travel time request.
Currently a library written in C++11, a Java 1.7 jar file, and a Python 3.6 implementation exist to generate and parse these formats.
- See the C++ README.
- See the Java README.
- See the Python README.