Multi-Format Export with Cryptographic Provenance
Export results in industry-standard formats with SHA-256 integrity verification and full processing lineage.
The Problem
Legacy tools lock processed seismic data in proprietary formats. Exporting to industry-standard formats requires expensive third-party converters that strip metadata, break spatial references, and lose the processing history. Regulatory submissions need provenance trails that most tools cannot provide. Without a cryptographic integrity hash, there is no way to verify that exported data has not been modified after delivery.
The Solution
Seismic Swift AI exports to every major industry format with full provenance metadata embedded directly in the output file. SHA-256 checksums, OSDU record IDs, processing parameters, and audit chain sequence numbers travel with the data — no separate metadata sidecar required. Regulatory-ready PDF reports are generated automatically. OSDU R3 publishing is native, not an afterthought.
Technical Specifications
Implementation details
| Format | Standard | Notes |
|---|---|---|
| SEG-Y | Rev 1 & Rev 2 | SEG Technical Standards Committee (2017). IEEE/IBM float (format codes 1–16), 32+ trace header fields (IL/XL/CDP/Source/Group/elevations/timestamps/gain/filter), EBCDIC textual headers per Barry (1975) convention, extended textual header blocks. |
| LAS | 2.0 & 3.0 | Canadian Well Logging Society (2012). All 16 mandatory ~W fields (STRT/STOP/STEP/NULL/COMP/WELL/FLD/LOC/PROV/CNTY/STAT/CTRY/SRVC/DATE/UWI/API), amplitude QC statistics in ~P survey geometry section, SHA-256 CHECKSUM provenance. |
| GeoTIFF | OGC 19-008r4 | CRS from EPSG code via rasterio, Affine transform (origin + pixel spacing), COG-ready tiling (blockxsize/blockysize), multi-band full-volume export, LZW/deflate compression, ARTIST + SOURCE_CHECKSUM + N_INLINES/N_XLINES/N_SAMPLES tags. |
| reportlab.platypus | 4-page report: (1) title + geographic metadata + CRS, (2) amplitude map with seismic LUT, (3) histogram + QC table, (4) diagnostics. Suitable for regulatory submission. SHA-256 embedded in PDF metadata. | |
| Provenance | SHA-256 / FIPS 180-4 | SHA-256 content hash embedded in every exported file immediately after write. Source filename, job ID, OSDU record ID, audit chain sequence number, and processing parameters travel with the data — no separate sidecar required. DOI |
| OSDU R3 | Native publishing | Records published to OSDU Storage Service (PUT /api/storage/v2/records) with validated schema conformance, ACL, legal tags (ISO 3166-1 country codes), and SeismicTraceData / Horizon / FaultSystem / WorkProduct entity kinds. DOI |
Format Comparison
Choose the right format for your workflow
| Format | Use Case | Max Volume | Provenance | Standard |
|---|---|---|---|---|
| SEG-Y Rev 2 | Full seismic volumes | Unlimited (streaming) | EBCDIC textual + SHA-256 | SEG 2017 |
| LAS 3.0 | Well log & attribute curves | All IL×XL traces | ~P CHECKSUM field | CWLS 2012 |
| GeoTIFF | Depth slices & attribute maps | Multi-band full volume | ARTIST + SOURCE_CHECKSUM tags | OGC 19-008r4 |
| Regulatory / executive reports | All depth slices | SHA-256 in PDF metadata | reportlab.platypus | |
| OSDU R3 | Data platform ingestion | Batch chunked | Native OSDU record ID + audit chain | The Open Group 2023 |
Quality Gates
Automated export validation
Every exported file passes a battery of structural and content checks before delivery. A failed gate aborts the export and surfaces the error with file offset and raw hex diagnostics.
Every exported file is hashed immediately after write and the checksum is verified against the in-memory value. Mismatch raises an error before the file is delivered.
All amplitude arrays are scanned for NaN and Inf values before encoding. Non-finite values are substituted with the configured null sentinel and flagged in the provenance block.
AmplitudeStatistics (mean, std, min, max, p5, p95) are computed and embedded in the export file. Values outside expected seismic ranges trigger a warning in the QC table.
SEG-Y exports verify that inline numbers are monotonically ordered and contiguous. Gaps or out-of-order traces are flagged before the file is finalised.
References
Industry standards and peer-reviewed foundations
- 1SEG Technical Standards Committee (2017). SEG-Y_r2.0: SEG-Y Revision 2.0 Data Exchange Format. Society of Exploration Geophysicists.
- 2Barry, K. M., Cavers, D. A. & Kneale, C. W. (1975). Recommended Standards for Digital Tape Formats. Geophysics 40(2), 344–352. DOI
- 3Canadian Well Logging Society (2012). LAS 3.0 Well Log ASCII Standard. CWLS Document Committee.
- 4OGC (2019). OGC GeoTIFF Standard, Version 1.1 (OGC 19-008r4). Open Geospatial Consortium.
- 5Yilmaz, Ö. (2001). Seismic Data Analysis: Processing, Inversion, and Interpretation of Seismic Data (2nd ed.). SEG Investigations in Geophysics No. 10. DOI
- 6The Open Group (2023). OSDU Data Platform — Storage Service API R3 M16. OSDU Forum.
- 7NIST FIPS 180-4 (2015). Secure Hash Standard (SHS). National Institute of Standards and Technology. DOI
Export your first project
All export formats are available on every plan. No additional fees for provenance embedding or OSDU registration.