Fix Affine matrix multiplication warnings - #939
be-student wants to merge 11 commits into
Conversation
|
With this change, will need to pin rasterio>=1.5.1 and affine>=3. |
Keep all nine coefficients and the existing NumPy comparison precision when validating Affine 3 transforms. Document the comparison pattern for future tests.
|
I suggest focusing only on affine matrix multiplication. If more than that is added, it could cause the PR merge to be delayed or blocked. |
|
Thanks for the guidance. I narrowed the branch back to the affine matrix multiplication change and the requested At head |
|
AppVeyor build I am keeping the branch affine-only as requested and am not reintroducing shutdown hooks or a CI wrapper that accepts the native crash. The complete hosted log is available in AppVeyor build 54750988. |
Summary
Fixes the
PendingDeprecationWarningraised by Affine 3 when rioxarray uses*for matrix multiplication. Pixel-center and recalculated transforms now use@, while coordinate-array transforms use explicit coefficient arithmetic so rectilinear and rotated/sheared results remain unchanged.The compatible dependency floors are now explicit:
rasterio>=1.5.1affine>=3Validation
2 passed.30 passed.git diff --check: passed.Exact tested head:
127d5af29d000608a9575a62bd4de4d3651459de.Issue linkage
rioxarray.open_rasteriostarting to emit warning from affine #937.AI assistance disclosure
OpenAI Codex assisted with implementation, test design, and preparation of this pull request text. The validation results above were run against the exact head listed in this description.
rioxarray.open_rasteriostarting to emit warning from affine #937docs/history.rst