You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
jawooll
added a commit
to KIT-GPI-AI/obspy
that referenced
this issue
Jan 27, 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.
The text was updated successfully, but these errors were encountered: