[SEDONA-338] Fix RS_MakeEmptyRaster and make affine transformation parameters compliant with the GDAL/PostGIS convention
#940
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… the GDAL/PostGIS convention
Kontinuation
force-pushed
the
geo-referencing-cell-corner
branch
from
9671071
to
0404f69
Compare
jiayuasu
approved these changes
Aug 2, 2023
Kontinuation
added a commit
to Kontinuation/sedona
that referenced
this pull request
Oct 11, 2024
…parameters compliant with the GDAL/PostGIS convention (apache#940)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject.What changes were proposed in this PR?
RS_MakeEmptyRasterwork correctly by constructing the GridCoverage2D object directly from the affine transformation. Please refer to SEDONA-338 for details.How was this patch tested?
Add unit tests for geo-referencing related functions.
Did this PR include necessary documentation updates?