The SACPZ web service allows users to retrieve instrument response information in SACPZ format.
NOTE: The sensitivity values for BK stations are slightly different from those produced via the NCEDC sacpz webservice. BK meta data is loaded from dataless provided by NCEDC. Due to a limitation of SEED, these values are rounded up when the dataless is written out.
Other options
The following options are available:
Examples:
POST Usage: Alternately, instead of providing parameters-value pairs in the URL, a file containing a selection list can be POSTed to this service. For the POST method, all parameters must be submitted as part of the POST body. POST requests should be sent as plain text and should not be formatted as applcation/x-www-form-urlencoded or multipart/form-data. Time and channel constraints parameters should be repeated as many times as necessary following this pattern:
NET |
STA |
LOC |
CHA |
STARTTIME |
ENDTIME |
NET |
STA |
LOC |
CHA |
STARTTIME |
ENDTIME |
NET |
STA |
LOC |
CHA |
STARTTIME |
ENDTIME |
All rules for parameters apply equally whether specified using the GET or POST methods with the exception of blank location IDs, which must be specified as "--" in the POST body due to spaces being used as the field separator. The parameters startbefore, startafter, endbefore, and endafter are NOT supported in POST. All other valid parameter-value pairs for GET queries are also valid for POST queries. Parameter-value pairs should be listed at the top of the file and are entirely optional. Below is a full list of service parameters and their usage.
Query: /scedcws/sacpz/1/query?[query-parameters] |
where query-parameters: |
net="network" |
Required |
Specify SEED network code, example net=CI. |
sta="station" |
Required |
Specify SEED station code, example sta=BAK. |
cha="channel" |
Required |
Specify SEED channel code mask, example: cha=BHE. Wildcards allowed. |
loc="location" |
Required |
Specify SEED location code mask, example: loc=00. substitute dash characters for white space, example: loc=--. Wildcards allowed. |
start=YYYY-MM-DDThh:mm:ss |
Optional |
Specify start of duration. All epochs that contain the provided value will be fetched. Maybe used in conjunction with end. When used in conjunction with end, all epochs that fall within end - start duration will also be fetched. |
end=YYYY-MM-DDThh:mm:ss |
Optional |
Specify end of duration. All epochs that contain the provided value will be fetched. Maybe used in conjunction with start. When used in conjunction with start, all epochs that fall within end - start duration will also be fetched. |
time=YYYY-MM-DDThh:mm:ss |
Optional |
Display epoch containing provided value. Cannot be used in conjuction with start or end parameters. |
nodata=204|404 |
Optional |
Specify which HTML status code is returned when no data is found (Default is 204). |
Note: Not specifying any temporal parameters will fetch current epoch. |