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

Add warning when writing non-compatible stream metadata to MSEED #2971

Open
jawooll opened this issue Jan 26, 2022 · 0 comments · May be fixed by #2972
Open

Add warning when writing non-compatible stream metadata to MSEED #2971

jawooll opened this issue Jan 26, 2022 · 0 comments · May be fixed by #2972

Comments

@jawooll
Copy link

jawooll commented Jan 26, 2022

When writing stream objects to MSEED, the network, station, location, channel code, each string can be up to 11 bytes long. With fields > 11 bytes raising an appropriate ValueError.

Then reading the same stream back in, these fields are then cut to the first 2, 5, 2, and 3 characters for the network, station, location, channel respectively. Whilst this point has been raised previously (#2588), should an appropriate warning should be logged to the user from obspy when they try to write metadata fields > required length?

As a bit of background, this is something we are encountering when attempting to write out probabilistic CFs as stream objects, with the label information encoded in the channel string see here.

@jawooll jawooll linked a pull request Jan 27, 2022 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants