Support maxdecimaldigits option by geometry type #7166
Merged
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.
Description of change
Adds support of PostGIS
maxdecimaldigits
option. The value comes from the existingprecision
option. Currently, it isn't possible, so the precision is always 9, therefore small, detailed elements either overlap or cannot be found using ST_Intersects, ST_Overlaps, etc. By default, PostGIS rounds all decimal places beyondmaxdecimaldigits
, which causes precision issues/ruins searching. This PR makesprecision
not only affectdouble
butgeometry
types as well.Fixes #7165
Pull-Request Checklist
master
branchnpm run lint
passes with this changenpm run test
passes with this changeFixes #0000