search

FDSN / StationXML

The FDSN StationXML schema and related documents
https://docs.fdsn.org/projects/stationxml/
12 stars 16 forks source link

FDSN StationXML for arrays and array stations #68

Open peacocks opened 3 years ago

peacocks commented 3 years ago

We're writing software to write StationXML for our array stations for ease of use in beamforming programs, but can't see how to (a) relate a particular station/channel to an array (e.g. EKR9 to EKA), and (b) store array station offsets (x/y/z in km not degrees) from the array centre. Happy to discuss these outside this forum if this is not the appropriate place for them.

rcasey-earthscope commented 2 years ago

For experiment data with arrays of receivers, we use the following conventions.

The Channel element contains attributes using the 'iris' namespace that are specially used to designate array numbers, component numbers, and receiver IDs.

<Channel code="DPZ" locationCode="" startDate="2021-05-30T18:31:57" endDate="2021-06-27T01:46:41" restrictedStatus="closed" iris:PH5Array="001" iris:PH5Component="1" iris:PH5ReceiverId="1"> I am not aware that these special attributes are documented anywhere, so that is a future issue to address. However, these do get encoded into the PH5 volumes at the PASSCAL data center, so there must be some method to the madness.

In each Array, there are a sequence of ReceiverIds (which are synonymous with stations and may use the same ID), each of which has a sequence of Components. The progression for a query on network XE for arrayid=001 looks something like:

https://service.iris.edu/ph5ws/station/1/query?net=XE&level=channel&arrayid=001&nodata=404
    PH5Array    PH5Componenet   PH5ReceiverId
    001     1 - DP1     100
    001     2 - DP2     100
    001     3 - DPZ     100
    001     1       101
    001     2       101
    001     3       101
    001     1       102
    ...etc...

Note that these attributes are only visible in XML format, not in text output format.