Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify meaning of level=response #7

Open
crotwell opened this issue Feb 25, 2022 · 3 comments
Open

clarify meaning of level=response #7

crotwell opened this issue Feb 25, 2022 · 3 comments

Comments

@crotwell
Copy link

Current spec says:

The ​ level​ parameter controls the amount of detail included in the returned FDSN StationXML results
with the following hierarchy: ​ network​, ​ station​, ​ channel​ and ​ response​ . For example, if the ​ station​ level
is requested the Station elements will be included in the results but not Channel or Response related
information.

but does not clarify StationXML output of the <Response> element when level=response vs level=channel. Current implementations, I think, use:

  • level=channel means include the <Response> element and <InstrumentSensitivity> or <InstrumentPolynomial> if exists, but do not include any <Stage> elements.
  • level=response means include above, as well as all <Stage> elements.

The current wording kind of makes it seem like level=channel should not include any response information, but including the scalar response is useful, easy and matches current practice.

@calum-chamberlain
Copy link

Kia ora all - related to this, it would be helpful to clarify what is expected if level=response (or any more detailed level), but no response information is available. This is related to this issue at GeoNet, where we have some legacy stations that have minimal metadata (station location) but no response information is available.

@crotwell
Copy link
Author

crotwell commented Aug 2, 2022

See here for how to represent unknown or missing response in StationXML:
http://docs.fdsn.org/projects/stationxml/en/latest/reference.html#response

In cases where the response is unknown, for example really old channels, or where a response is not applicable, like textual log channels, it is preferred that an empty response element be used, <response></response>, to positively indicate that no response exists.

@calum-chamberlain
Copy link

Thanks @crotwell that is really helpful - ignore the above comment then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants