Transform order should be the same as in GDAL

[felixcremer]

Why is the ordering of the transform parameters not following the same standard as in GDAL?

I would argue, that there are more packages in other languages apart from python which would interact with GDAL rather than with the python Affine library.

[kylebarron]

In my view of the ecosystem, I don't see GDAL transform ordering as being the standard.

The ordering used here, which is the same as what Python's Affine uses, is the standard matrix algebra notation. That's pervasive among the entire Python ecosystem I'm aware of.

Looking at the ecosystem, I don't know of any formats/libraries other than GDAL that use GDAL's ordering:

• In STAC spec, which is language-agnostic, proj:transform uses Affine ordering.
• Rust's geotiff library uses Affine ordering

I can look for more examples in the ecosystem.

At the end of the day the ordering doesn't matter as long as it's consistent and documented, and I would strongly argue that choosing GDAL ordering would cause more confusion, not less.