There are some edge cases (i.e. custom header definitions out of spec) when default MDIO SEG-Y spec doesn't unpack some values into JSON and if it is exported, the data will be lost.
In those cases we can give a full SEG-Y spec based on the TGSAI/segy schema as a JSON environment variable: MDIO__SEGY__SPEC.
As long as the user has the JSON available at runtime; MDIO should be able to ingest/export files conforming to that spec.
IMPORTANT: Re-emphasizing that the files ingested with a custom JSON spec will ONLY be exportable if the spec is available. Or else default MDIO can't export it since it will be out of spec.
There are some edge cases (i.e. custom header definitions out of spec) when default MDIO SEG-Y spec doesn't unpack some values into JSON and if it is exported, the data will be lost.
In those cases we can give a full SEG-Y spec based on the
TGSAI/segyschema as a JSON environment variable:MDIO__SEGY__SPEC.As long as the user has the JSON available at runtime; MDIO should be able to ingest/export files conforming to that spec.
IMPORTANT: Re-emphasizing that the files ingested with a custom JSON spec will ONLY be exportable if the spec is available. Or else default MDIO can't export it since it will be out of spec.