Skip to content

Improve detection of gdal ordering of proj:transform#1570

Open
soxofaan wants to merge 2 commits intomasterfrom
issue1557-gdal-transpose-detection
Open

Improve detection of gdal ordering of proj:transform#1570
soxofaan wants to merge 2 commits intomasterfrom
issue1557-gdal-transpose-detection

Conversation

@soxofaan
Copy link
Member

@soxofaan soxofaan commented Mar 2, 2026

  • xOrigin or yOrigin should can be any value (also zero), so we must be more careful when considering it
  • also add option to consider the data to have YX orientation
  • added more test coverage to further harden the implementation and scope

@soxofaan soxofaan marked this pull request as ready for review March 2, 2026 14:13
@soxofaan
Copy link
Member Author

soxofaan commented Mar 2, 2026

@JeroenVerstraelen
this is proposal to improve the detection of gdal ordering of proj:transform

problem I encountered is that detection would go wrong if xOrigin or yOrigin is zero, which can happen at equator, or e.g. in the center meridian in UTM zones

@soxofaan
Copy link
Member Author

soxofaan commented Mar 2, 2026

related to and triggered from

@soxofaan soxofaan force-pushed the issue1557-gdal-transpose-detection branch 4 times, most recently from 82857a1 to 33b85fa Compare March 3, 2026 09:55
- xOrigin or yOrigin can be any value (also zero), so we must be
  more careful when considering them
- also add option to consider the data to have YX orientation
- added more test coverage to further harden the implementation and
  scope
@soxofaan soxofaan force-pushed the issue1557-gdal-transpose-detection branch from 33b85fa to 7bcfd14 Compare March 4, 2026 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant