Difference between revisions of "CSEP 2 CATALOG FORMAT"
| Line 31: | Line 31: | ||
* comcat: eg., 'ci0000000' | * comcat: eg., 'ci0000000' | ||
* ucerf3: eg., fault-system solution of supraseismogenic | * ucerf3: eg., fault-system solution of supraseismogenic | ||
| + | |||
| + | == Example Catalog == | ||
Revision as of 06:13, 19 May 2020
Catalog Format
Catalog properties:
1. User friendly (easy for non-developers to work with) 2. Self-consistent and Independent 3. Extensible 4. Easy represented in other formats
Considerations:
1. File format 2. Catalogs per File 3. Contents of File
Summary
The catalog will initially be defined as an ASCII .csv format where each row corresponds to a single event. This file will have the following headers:
longitude, latitude, M, epoch_time (time in millisecond since Unix epoch in GMT), depth, +x-offset, +y-offset, catalog_id, event_id
longitude: longitude in decimal degrees [-180,180]
latitude: latitude in decimal degrees [-90,90]
M: magnitude arbitrary units
epoch_time: time since unix epoch [-inf, inf]
depth: hypocenter depth in (km) [0, inf]
+x-offset: east-west offset from lon/lat in (m) [-inf, inf]
+y-offset: north-south offset from lon/lat in (m) [inf,inf]
catalog_id: indicates type of catalog
- observed: -1
- simulated: [0,n_cat-1]
event_id: used to indentify events beyond the basic properties
- comcat: eg., 'ci0000000'
- ucerf3: eg., fault-system solution of supraseismogenic