[GH-3260] Preserve M and ZM in Python GeometryUDT serialization - #3265
Draft
jiayuasu wants to merge 1 commit into
Draft
[GH-3260] Preserve M and ZM in Python GeometryUDT serialization#3265jiayuasu wants to merge 1 commit into
jiayuasu wants to merge 1 commit into
Conversation
This file contains hidden or 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
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 ticket?
[GH-XXX] my subject.Part of #3260.
What changes were proposed in this PR?
GEOSHasM_rAPI while retaining compatibility with older supported GEOS versions.This is the first PR in the #3260 stack and is based on
master.How was this patch tested?
git diff --check, passed.Did this PR include necessary documentation updates?