This document contains instructions for running application Catalog Merger within the EPISODES Platform. The application is a tool for merging two catalogs of the same type (e.g. Catalog, Ground Motion Catalog - see complete list of catalog types).

To obtain more general information about working with applications within the Platform, see Applications Quick Start Guide.

CATEGORY Reconstruction tools

KEYWORDS Data merging

CITATION If you use the results or visualizations retrieved from this application in a publication, then you must cite the data source as follows:
Orlecka-Sikora, B., Lasocki, S., Kocot, J. et al. (2020) An open data infrastructure for the study of anthropogenic hazards linked to georesource exploitation., Sci Data 7, 89, doi: 10.1038/s41597-020-0429-3.

Input files specification

The application requires exactly two files that are in the format of a Matlab catalog (type Data Catalog). These may be a Catalog (a seismic events catalog), Ground Motion Catalog or any other similar type - check other possible catalog data formats, including also catalogs that are produced by joining two different catalog types (products of the Parameters Catalog builder user guide). However, it is important that the two files are of the same type.

For the purpose of this guide, we use the seismic catalog (Catalog), but most of the functionality is the same for other types.

Figure 1. Application input files specification

Produced output

The result catalog is a sum of the input catalogs, with the contents sorted by time (if the time column is found in the catalog). If one of the catalogs contains fields (columns) that are not present in the other, the fields are added. In case there are new fields for the rows (e.g. events) already present in one of the catalogs, the row is supplemented by the additional values, where the same rows are identified by a unique ID characteristic to the specific catalog type (e.g. Event ID in case of a seismic catalog and Registration ID in case of Ground Motion Catalog).

The name of the resulting catalog is constructed from the two input catalog file names - e.g. in the case pictured in Figure 1, the resulting file name would be CZORSZTYN_catalog_part1_CZORSZTYN_catalog_part2.mat.

Figure 2. Result file visualization

Back to top