-
Notifications
You must be signed in to change notification settings - Fork 54
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
How to read latitude/longitude or xcoordinate/ycoordinate information?? #90
Comments
|
Hi, Thank you, |
@keerthigajee It's difficult to say what the problem is unless you can share your SEG-Y file in some way. You can see the header field names in the code here Line 257 in d39b89c
|
So I'm having the same issue I believe it may have something to do with the size of the trace header. I get this when I simply try to see the header Mine is in a 2D data file with what looks like non standard cdp_x and cdp_y bit locations but I'm not sure that is the issue. Also is there a way to easily override the offset for those fields so that it will read the traces correctly? |
After a lot of tracking down, I found an issue between the segy file I had and the format for the trace header, this may be related to the original problem and my not. solution for me was to edit the trace_header.py to say class Correlated(IntEnum): Seems like sometimes segy files include 0 for this field |
Hi, I also run into the same issue: EOFError: Trace header truncated when reading from position 3600 with packer BijectiveHeaderPacker(TraceHeaderRev1). I am trying to (1) read in a 2D seismic segy using create_reader [create_reader(segy_in_file, dimensionality=2)] and then (2) write it out into a new segy file using write_segy [write_segy(segy_out_file, seg_y_dataset, endian='>')]. The read-in step is fine while the error message occurs during the write-out step. I zip the public segy file and attach it here. Kindest regards, John |
I’m on vacation currently. I’ll take a look next week.
…On Sat, 20 Apr 2019 at 18:19, InnoKaleid ***@***.***> wrote:
Hi,
I also run into the same issue: EOFError: Trace header truncated when
reading from position 3600 with packer
BijectiveHeaderPacker(TraceHeaderRev1).
I am trying to (1) read in a 2D seismic segy using create_reader
[create_reader(segy_in_file, dimensionality=2)] and then (2) write it out
into a new segy file using write_segy [write_segy(segy_out_file,
seg_y_dataset, endian='>')]. The read-in step is fine while the error
message occurs during the write-out step.
I zip the public segy file and attach it here.
3X_75_PR.zip
<https://github.com/sixty-north/segpy/files/3100354/3X_75_PR.zip>. I was
wondering if someone can help me with it?
Kindest regards,
John
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAH65KN46ACGTDRYRL6UWSTPRM7ADANCNFSM4GSK2U3A>
.
|
Hi rob-smallshire, Thank you and have a great vacation. John |
@InnoKaleid Best of Luck ` def getpoint(segydata, i, j = None):
filePath = "tmp/3X_75_PR.SGY" fileHandle = open(filePath, 'rb') imax = max(segyData.cdp_numbers()) for i in np.arange(imin, imax, 10): print(points) ` |
Hi Aaron, Thank you for your help. It seems work well and have a great weekend. John |
John |
Hi Aaron, Thank you very much and your answer is very helpful. Happy Easter! John |
Hi, I too have the same error: any thoughts how this can be fixed in the pip distro module? |
my fork should work for this. Aaron |
what is the use of progress in the reader and writer module and how to use it ???? |
Hello @rob-smallshire, I tried to check the field names, but the EOFError issue persists. What to do with a 3D seismic file if x, y co-ordinates are required? Kindly help!. Regards, |
The EOF error is pretty common. |
Hi,
I need to know how to read latitude/longitude or xcoordinate/ycoordinate information from a .sgy file instead of inline/xline? I need to know the field names for extraction.
Thank you.
Regards,
Soumi
The text was updated successfully, but these errors were encountered: