PR: NFSI OBS instrument updates for local fdsnws and vertical component naming #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adapt OrientPy to be compatible with NFSI data. (1) - allow selectable vertical component identifier. NFSI Data is 123, not 12Z (2) - split the waveform and catalogue clients to separate services, and allow for base_urls to be specified Signed-off-by: Andrew Schaeffer <[email protected]> 2025-03-27 17:20 PDT
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added ability to specify ZComp name (instead of just "Z"), to handle CH[124] data from NFSI.
Added ability to specify a local base_url for the fdsnws data_select, as well as a separate base_url for the fdsnws event selection.