Annotation to World coordinates
Class KnownMetadata allows for several ways of specifying the annotation to world coordinate conversion. Simple Origin/ISpacing/XSpacing, or IJK with any 3d affine transform, or 4 control points, or XYZ unconverted.
Is there a single method in the API that an application can use to get this transform?
Failing that, are there usage rules when writing files that makes it simpler to read them later? For example there might be a rule that if the 4-point style (GridPoint0 etc.) is used, the simple origin and spacing must also be provided.
IJK origin and step is a superset of the simple 2d origin and step, so a seismic cube might be stored as IJK with K pointing straight down. But does that make sense? Or put differently: Should a program that only reads poststack 3d seismic need to be able to process a file with IJK coordinate information as long as K is vertical?