Difference between revisions of "CSEP 2 CATALOG FORMAT"
From SCECpedia
Jump to navigationJump to search| Line 13: | Line 13: | ||
== Summary == | == 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<br> | + | 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:<br><br> |
<code> | <code> | ||
longitude, latitude, '''M''', epoch_time (time in millisecond since Unix epoch in GMT), depth, +x-offset, +y-offset, catalog_id, event_id | longitude, latitude, '''M''', epoch_time (time in millisecond since Unix epoch in GMT), depth, +x-offset, +y-offset, catalog_id, event_id | ||
</code> | </code> | ||
| + | |||
| + | <code>longitude</code> | ||
| + | <code>latitude</code> | ||
| + | <code>'''M'''</code> | ||
| + | <code>epoch_time</code> | ||
| + | <code>depth</code> | ||
| + | <code>+x-offset</code> | ||
| + | <code>+x-offset</code> | ||
| + | <code>catalog_id</code> | ||
| + | <code>event_id</code> | ||
Revision as of 05:51, 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
latitude
M
epoch_time
depth
+x-offset
+x-offset
catalog_id
event_id
