-
This will require quite some changes and we should think through the use cases before we make a change.
- We need to decide which SOH channels
- We then need to include those channel codes in the…
-
StationXML with a Polynomial first stage should have a InstrumentPolynomial with the same number of coefficients.
Also, each coefficient in the InstrumentPolynomial should be the corresponding val…
-
dear all,
Luděk and me noticed that for temporary stations installed by our group in various countries, the PaZ stage is empty and some stages are missing when StationXML is downloaded from EIDA, whi…
-
Assuming the FDSN identifiers will be used in the new data format (please discuss this in #4) how should the network code be expanded (or not) and what conventions should be adopated (if any)?
-
Assuming the FDSN identifiers will be used in the new data format (please discuss this in #4) how should the location code be expanded (or not) and what conventions should be adopated (if any)?
-
Assuming the FDSN identifiers will be used in the new data format (please discuss this in #4) how should the channel code be expanded (or not) and what conventions should be adopated (if any)?
-
### Problem
We have `client.get_waveforms(..., attach_response=...)` mechanism to automatically fetch metadata for each trace (using `client._attach_responses()` private method) and attach it to each…
-
Here
https://github.com/iris-edu/mseed3-evaluation/commit/058dd8d4d0f58be0e6ff4ea9cf18005abc6ecc31
is a first try at a json schema for the extra headers based on Chad's list of things, my grouping…
-
I see that there is a note regarding Channel types being removed in the future.
https://github.com/FDSN/StationXML/blob/7ccd7ddaf3082f242a09591a8d6f5ffa88b6213b/docs/level-channel.rst#type
Where…
ghost updated
2 years ago
-
Need to pull docs from json schema into rst.
> Related to changing the documentation of extra headers: I realized that the canonical documentation for each field is not displayed in the specificati…