[Metadata] ORFEUS stations HYP02, HYP03, HYP04 require correct epoch time bounds

[rcasey-earthscope]

(original thread indicated below)

Current user contacted IRIS to address an issue with three stations (6A.HYP02, 6A.HYP03, 6A.HYP04) showing up on their temporary experiment (Teno Valley Seismic Network - 2017-2018) when doing a station-level scan.

http://service.iris.edu/irisws/fedcatalog/1/query?net=6A&start=2017-01-01&end=2018-12-31&format=text&includeoverlaps=true&nodata=404&level=station

Because the channel level metadata is confined to the (Acoustic Ground Coupling Experiment, University of Vienna) 2019 experiment epoch, many tools such as MDA do not exhibit this cross-over issue. However, the above use case shows that this can happen at the station level.

The effect carries over to the IRIS Fed Catalog: http://service.iris.edu/irisws/fedcatalog/1/query?sta=HYP02&format=text&includeoverlaps=true&nodata=404&level=station

Requesting that the station epochs for these three channels be reviewed and revised.

Thanks. Rob Casey IRIS Data Services

On Jan 4, 2022, at 10:39 AM, Adam Clark <adam@iris.washington.edu> wrote:

This looks like an issue with the ORFEUS metadata.

ORFEUS has the HYP02/HYP03/HYP04 stations listed as 1980-01-01 - (open):
http://service.iris.edu/irisws/fedcatalog/1/query?net=6A&start=2017-01-01&end=2018-12-31&format=text&includeoverlaps=true&nodata=404&level=station

Confirmed in their service:
http://www.orfeus-eu.org/fdsnws/station/1/query?net=6A&level=station&format=text&nodata=404&start=2017-01-01&end=2018-12-31

This appears to be limited to the station level only -- the dates at the network and channel levels (and our fedcatalog versions of these) appear correct:
http://service.iris.edu/irisws/fedcatalog/1/query?net=6A&start=2017-01-01&end=2018-12-31&format=text&includeoverlaps=true&nodata=404&level=channel

Cheers,
Adam

----------------------
Adam Clark
Web Application Developer
IRIS Data Management Center
adam@iris.washington.edu

Begin forwarded message:

From: "Hammond, James" <j.hammond@ucl.ac.uk>
Subject: Seismic Network 6A (2017-2018)
Date: January 4, 2022 at 6:15:48 AM PST
To: "webmaster@fdsn.org" <webmaster@fdsn.org>
Cc: "Sanchez De La Muela Garzon, Almudena" <almudena.muela.16@ucl.ac.uk>

Hi,

I note that 3 infrasound stations in Austria are listed as belonging to our seismic network (6A, Eno Valley Seismic Network), I just thought I would mention it as they should not be.  Thanks for hosting the data!

Kind regards

James

James Hammond
Reader in Geophysics

Director, Mount Paektu Research Centre
Assistant Dean, Recruitment and Retention, School of Science

Department of Earth and Planetary Sciences
Birkbeck, University of London
Malet Street
WC1E 7HX
+44 (0)20 3926 1795

Website: http://www.bbk.ac.uk/geology/our-staff/james-hammond
Mount Paektu Research Centre website: https://themprc.org

[petrrr]

Looks like 1980-01-01 is some default, maybe in seiscomp? Especially for temporary networks we should check (ideally systematically), if ...

1. start/end times of networks are aligned with FDSN assignments;
2. all stations (start / end) remain within the network declared time span;
3. all channel epochs remain within the station declared time span;