Skip to content

Fix out of bound segment index when reading over-buffered GeoTiff window - #2534

Merged
echeipesh merged 2 commits into
locationtech:masterfrom
echeipesh:fix/getIntersectingSegments
Jan 3, 2018
Merged

echeipesh merged 2 commits into
locationtech:masterfrom
echeipesh:fix/getIntersectingSegments

Conversation

@echeipesh

@echeipesh echeipesh commented Jan 3, 2018 •

Copy link
Copy Markdown
Contributor

Overview

GeoTiffSegmentLayout.getIntersectingSegments did not perform bound checking.
As a result if GridBounds parameter was outside of the bounds of segment layout an out of bounds index would be returned, resulting in failed segment lookup.

This issue was discovered in process of performing buffered window reads: raster-foundry/raster-foundry@49fe952

Checklist

  • docs/CHANGELOG.rst updated, if necessary
  • [-] docs guides update, if necessary
  • [-] New user API has useful Scaladoc strings
  • Unit tests added for bug-fix or new feature

@echeipesh echeipesh added the bug label Jan 3, 2018
@echeipesh
echeipesh force-pushed the fix/getIntersectingSegments branch from 3f2e4f6 to d33b392 Compare January 3, 2018 16:20
@echeipesh
echeipesh force-pushed the fix/getIntersectingSegments branch from 8ab0162 to e0a6205 Compare January 3, 2018 18:08
@echeipesh echeipesh added this to the 1.2 milestone Jan 3, 2018
@echeipesh
echeipesh merged commit 86ac40c into locationtech:master Jan 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant