Assembleddata webservice

  The assembleddata webservice provides access to the pre-assembled RAP and RESIF events archives. It allows to retrieve waveforms in SAC and ASCII formats.

Output format

  Three formats are supported:

  1. archive format: The events satisfying the request are returned in zip format. The zip file contains SAC and ASCII waveforms.
  2. text format: return the events inventory as follows : collector| event_name | latitude | longitude | depth | magnitude | magtype |description| agency | pga
  3. json format: return inventory as above, but in json format

Overview of request parameters

The request parameters for the service are summarized in tables below. Events can be retrieved either by specifying the name of the event or by applying a filter:

To obtain a particular event, you must specify its name

Parameter Description Default Required Format
name Event name YES
format Response output format text NON text/json/archive


Several archives can be retrieved depending on the filters applied for a maximum one month.

Parameter Description Default Required Format
collector Event collector RAP and RESIF NO RAP/RESIF
after The minimum date NO YES ''YYYY-MM-DDTHH:MM:SS.ssssss'', ''YYYY-­MM-DDTHH:MM:SS'', ''YYYY­‐MM-­DD ''
before The maximum date NO YES ''YYYY-MM-DDTHH:MM:SS.ssssss'', ''YYYY-­MM-DDTHH:MM:SS'', ''YYYY­‐MM-­DD ''
minlatitude Events with latitude larger or equal to the specified limit NO NO [-90,90]
maxlatitude Events with latitude smaller or equal to the specified limit NO NO [-90,90]
minlongitude Events with longitude larger or equal to the specified limit NO NO [-180,180]
maxlongitude events with longitude smaller or equal to the specified limit NO NO [-180,180]
minmagnitude Events with magnitude larger or equal to the specified limit NO NO
maxmagnitude events with magnitude smaller or equal to the specified limit NO NO
mindepth Events with depth larger or equal to the specified limit NO NO
maxdepth events with depth smaller or equal to the specified limit NO NO
agency The organization that located the event NO NO NO
format output format text NO text/json/archive

HTTP status codes

Table below givesa list of status codes returned by the webservice. These codes should be used by end-user to check if a request was successful.

Code Description
200 Successfull request
201 Request was properly formatted and submitted but no data match the selection.
400 Bad request due to improper specification, unrecognized parameter, etc.
203 Request resulted in too much data being returned or the request itself is too large.
500 Internal Server Error

Examples