Workaround needed for ambiguous SEG Y channel identification
jpjones76 opened this issue · 1 comments
jpjones76 commented
SEG Y has six quantities that can identify a unique channel. Most don't translate cleanly to any subfield of a SEED-type ID (e.g., NN.SSSSS.LL.CCC, which SeisIO uses). Data in #55 (comment) use SEG Y channel number to identify new channels.
Original file posted by @tclements in #55 (comment)
jpjones76 commented
Planned workaround: new keyword in read_data that sets the location field of :id (boldface in NN.SSSSS.LL.CCC), using channel number from SEG Y trace header (Int32 starting 12 bytes from trace begin). To the best of my knowledge this will only work for SEG Y records with n <= 1296 channel numbers; as I recall, the only allowed location codes are "00" through "ZZ".