-
Notifications
You must be signed in to change notification settings - Fork 46
The readEvents() function
The readEvents() function is used to read event metadata (origin time, lon, lat, depth, mag etc.) from various different data sources such as IRIS DMC, and catalog formats such as those produced by Seisan, Antelope, hypoinverse, hypoellipse etc., into a Catalog object.
The aim is to support the same name-value parameter pairs supported by irisFetch.m. Currently supported are:
- startTime
- endTime
- eventId
- fetchLimit
- magnitudeType
- minimumLongitude
- maximumLongitude
- minimumLatitude
- maximumLatitude
- minimumMagnitude
- maximumMagnitude
- minimumDepth
- maximumDepth
And the two convenience parameters:
- radialcoordinates, which is a vector [centerLatitude, centerLongitude, maximumRadius]
- boxcoordinates, which is a vector [minimumLatitude maximumLatitude minimumLongitude maximumLongitude]
Calls to readEvents() are like:
>> catalogObject = readEvents(dataformat, 'param1', value1, ..., 'paramN', valueN)
dataformat may be:
- 'iris' (for IRIS DMC, using irisFetch.m),
- 'antelope' (for a CSS3.0 Antelope/Datascope database)
- 'seisan' (for a Seisan database that uses the "Nordic" REA/YYYY/MM/ directory structure)
The aim is to also add support to read from other FDSN data centers and from other catalog formats, such as hypoinverse, hypoellipse, hypocenter, hypo71 etc.
The plan is also to optionally load arrival data too, from dataformat's that contain that information.
Code | Wiki | Tutorials | Website | Mailing list | Getting started | Reporting problems
- What is GISMO?
- Who uses it?
- Historical Development
- Getting started
- Getting and using the develop branch
- GISMO data types
- * Tutorials *
- * Workflow examples *
- * Applications *
- The GISMO Users Group
- Reporting errors, bugs, issues
- Contributing to GISMO
- * SUGGESTED CITATION *
- News
- Future Development
- Links