ESM Dataset Selection Web-Service

Sample requests

Data can be obtained using any program supporting the HTTP-GET method, e.g. your favourite web browser:

Restricted Data (authenticated users only)

ESM Administrators and users with special authorizations can access data intended for internal use and/or embargoed.
Data can be obtained using any program supporting the HTTP-POST method, e.g. CURL:

Query options

HTTP-POST variables (required)

Option Description Default
messageThe clearsign token obtained from the generate-signed-message authentication webservice or from EIDA authentication webpage.

URL format

Option Description Default
eventidESM event ID. Supported wildcard are or '*' (matches zero or more characters) or '?' (matches just one character).'*'
starttimeLimit to events on or after the specified start time. Allowed formats: 'YYYY-MM-DDTHH:MM:SS' and 'YYYY-MM- DD'.'1900-01-01T00:00:00'
endtimeLimit to events on or before the specified end time. Allowed formats: 'YYYY-MM-DDTHH:MM:SS' and 'YYYY-MM- DD'.'2100-01-01T00:00:00'
minmagLimit to events with a magnitude larger than the specified minimum.0
maxdistLimit to stations with epicentral distance smaller than the specified maximum.3000
networkESM network code (i.e. FDSN network code). Supported wildcard are or '*' or '?'.'*'
stationESM station code (SEED station code or data center defined code). Supported wildcard are or '*' or '?'.'*'
instrumentInstrument code. Supported wildcard are or '*' or '?'.'*'
unprocessed{true,false} Include unprocessed data.true
discarded{true,false} Include manually discarded data.true
automatic{true,false} Include automatically processed data.true
manual{true,false} Include manually processed data.true
standard{true,false} Include data processed with default/standard ESM method (Paolucci et al. 2011 aka ITACA) as preferred, both manual and automatic modes.true
ebasco{true,false} Include data processed with eBASCO method (Schiappapietra et al. 2021) as preferred, both manual and automatic modes.true
processing-filter-logic{preferred,available} Specify a criterion for filter on processing scheme. Available types are: 'available' (the processing scheme specified by manual/automatic + standard/ebasco options is available for selected waveforms.), 'preferred' (the processing scheme specified by manual/automatic + standard/ebasco options is the preferred scheme for selected waveforms.).preferred
best{true,false} Include data classified as 'best quality'.true
good{true,false} Include data classified as 'good quality'.true
bad{true,false} Include data classified as 'bad quality'.true
undef{true,false} nclude data classified as 'undefined'.true
quality-reasonSelect 'all' or one or more quality reason codes (see table below for description). Multiple codes are comma-separated.all
format{json} Specify format of result, currently only 'json' is supported.'json'
offsetPagination offset. NOTE: setting offset=0 and limit=0 disables pagination.0
limitPagination limit. NOTE: setting offset=0 and limit=0 disables pagination.0
indent{true,false} Prettifies output setting a 4 spaces indentation style. Valid only in combination with 'json' format.false
 

Quality reason codes for option 'qr'

 
Code Description Quality class
1High Signal to Noise RatioBEST
2PGA > 2gGOOD
3one component more than twice the other (ACC)GOOD
4unreliable P-wave arrivalGOOD
5more events detectedGOOD
6restricted frequency passbandGOOD
7too short duration for one or more componentsBAD
8one zero componentBAD
9cannot_compute_zeroes_percentBAD
10one or more quasi zero componentBAD
11auto trigger failedBAD
12auto PS phase picking failedBAD
13Low Signal to Noise RatioBAD
14Anomalous Signal to Noise RatioBAD
15very restricted frequency passbandBAD
16missing one componentUNDEF
17one empty componentUNDEF
18Undefined Quality IndexUNDEF

 


Backend Python software used by this web service is developed and maintained by Russo E. and Felicetta C.