Invalid video info when no image chip is available#585
Merged
rwgdrummer merged 1 commit intolocationtech:0.9.0-RC1-mergefrom Jan 21, 2016
Merged
Invalid video info when no image chip is available#585rwgdrummer merged 1 commit intolocationtech:0.9.0-RC1-mergefrom
rwgdrummer merged 1 commit intolocationtech:0.9.0-RC1-mergefrom
Conversation
…frame number) when an image chip is not available.
rwgdrummer
added a commit
that referenced
this pull request
Jan 21, 2016
Invalid video info when no image chip is available
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
2 participants
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.
This pull request fixes an issue with a track point's video info (pixel column, pixel row and frame number) when an image chip is not available.
Prior to this fix, none of the video information for a track point or motion point was being populated if an image chip was not available. The pixel row, pixel col and frame number was being stored in GeoWave as -1.
An NPE was being thrown and caught when the imageChip was not populated causing the population of the other fields to be bypassed.