1 | initial version |
It is not a bug, it's a feature. :) The reason why keypoint.octave
has a weird value is because it carries the information on:
octave
in the least significant byte of the keypoint.octave
fieldlayer
of that octave in the second least significant byte of the keypoint.octave
fieldkeypoint.octave
gets unpacked into the variables octave
, layer
, and scale
(scale
is just 1/2^octave
) with the method unpackOctave
(see OpenCV implementation).
To get a visual understanding of variables octave
and layer
, this image might help:
(I've explained this in an answer on Stack Overflow.)