I've done work with SEGY files, and the fixed length headers with ignored fields were an issue. Also, endian issues.
You have to remember SEGY is the present exchange and archiving standard. That's a good thing.
The issue is that SEGY was designed for tape, so it's a single file.
In this day and age, that may not be a good thing. It might be better to ...
The Elsevier service Geofacets "is designed to search for, and extract, maps, sections and other geographically-referenced geoscientific data from a very large and growing volume of published content", and as such is perhaps relevant -- though it focusses on georeferenced data rather than on scientific articles.
Two-way time (ms)
Line type (2=2D, I=inline, X=crossline)
2D line name or 3D survey name
The format allows for a column between 8 and 9, for amplitude value — not present in this example.
This is a formatted layout to specific columns. So there is ...
The advantage of SEGY is also it's main problem; It's been around for very long. I've been struggling to open a decade old word document correctly, whiles one can actually still access a SEGY from the 70's or 80's. It's also an advantage that all program packages can, somehow, import and export the files.
I agree with David, that the headers doesn't need ...
One thing that already exists is the ph5 format from the PASSCAL group: https://www.passcal.nmt.edu/content/ph5-what-it
It is essentially a port of the SEG Y format that removes some restrictions and adds a bunch of new meta information. It is based on HDF5 and is currently mainly intended as an archival format although I don't see why it could not also be ...
The SEG has a sitting committee for SEG-Y revision 2, which has debated the need to adopt changes to SEG-Y since the last revision that are needed (such as removing trace length limits for continuous data, formats for passive data, etc.). If you want to do something about what SEG-Y for the future should look like, You should join the SEG and volunteer for ...