A Guide for Uploading Compatible Seismic Data to the Cloud Platform
Our platform supports the upload, preview, and metadata extraction of seismic data stored in the SEG-Y (.sgy) format. To ensure a smooth experience, your files should comply with the SEG-Y standard and contain the required headers and trace data.
What Is a SEG-Y File?
A .sgy (or .segy) file is a binary format defined by the Society of Exploration Geophysicists (SEG) for storing seismic reflection data. It is commonly used in geophysical surveys and oil and gas exploration.
A SEG-Y file typically contains:
A 3200-byte textual header
A 400-byte binary header
A sequence of trace headers and trace data
Supported SEG-Y Versions
Version | Status | Notes |
Rev 0 (1975) | Supported | Original SEG-Y standard |
Rev 1 (2002) | Supported | Supports modern extensions |
Rev 2 | Supported | Supports modern extensions |
We recommend using SEG-Y Revision 2 for maximum compatibility.
File Requirements
To be compatible with our preview and metadata extraction pipeline, ensure your .sgy file meets the following:
Required Components
Section | Size | Required | Description |
Textual Header | 3200 bytes | Yes | ASCII or EBCDIC encoded metadata |
Binary Header | 400 bytes | Yes | Contains key survey info |
Trace Headers | 240 bytes per trace | Yes | Includes coordinates, elevation, offset, etc. |
Trace Data | Variable | Yes | The actual recorded seismic data |
Coordinate Reference System (CRS)
The SEG-Y format does not require a CRS, but to enable map-based Trace preview, your file must:
Store X and Y coordinates in each trace header
Clearly define coordinate scaling factors
Optionally include EPSG code in extended headers
Key Binary Header Fields
Offset | Field | Notes |
3217–3218 | Sample format code | Must match the encoding of trace data |
3221–3222 | Number of samples per trace |
|
3225–3226 | Sample interval in microseconds |
|
Use of IEEE floating point (code 5) or IBM float (code 1) is recommended for trace data.
Required Trace Header Fields
To display a map footprint, each trace must contain:
Offset | Field | Required | Notes |
73–76 | X coordinate | Yes | In UTM or geographic units |
77–80 | Y coordinate | Yes | In UTM or geographic units |
71–72 | Coordinate scaling | Yes | Positive = multiplier, negative = divisor |
81–84 | Elevation | Optional |
|
37–40 | Inline number | Optional |
|
41–44 | Crossline number | Optional |
|
Make sure the coordinates are in a consistent, known system (e.g., UTM Zone 32N = EPSG:32632).
Unsupported Scenarios
We currently do not support:
Files missing X/Y coordinates in trace headers
Files with zero or constant coordinate values
Files using nonstandard header lengths or encodings
Rev 2 features (e.g., extended trace headers)
Proprietary format variants (e.g., P1/90, SEGD)
Upload Checklist
Before uploading your .sgy file:
File is in SEG-Y Rev 0 or Rev 1 format
Textual and binary headers are present
Each trace includes valid X and Y coordinates
Coordinates use a consistent projection (UTM or lat/lon)
File size is below the current upload limit (e.g., 5 GB)
Format References
Resource | Link |
SEG-Y Rev 1 Specification (PDF) |