GTC-2027 (part 2) - give useful error when input geometry is not Polygon/MultiPolygon #504
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.
GTC-2027 (part 2) - give useful error when input geometry is not Polygon/MultiPolygon
This is to fix for a bunch more "tuple index out of range" 500 errors that are showing up. Someone is submitting zonal statistic queries on geometries which are not Polygons. This is the same as my previous fix for normal queries.
Since zonal statististics are on the way out (eventually), I didn't add a new test for this particular error case.