[Kwiver-users] Bounding Box Issues

[Matt Leotta]

On Mon, Mar 11, 2019 at 11:59 AM Matt Brown <matt.brown at kitware.com> wrote:

> You should not hit this case.  This is a bounding box, not a polygon.  You
>> should warp the corners of this box (or other data within) and then compute
>> a new bounding box on the warped points.
>>
> Maybe this is contrived, but as an example, let's say you are working with
> orbiting WAMI data and you warp a raw-image bbox from one side of the orbit
> to a raw image from the other side of the orbit. The top/left and
> bottom/right corners may get inverted so that top/left > bottom/right. If
> you naively generated a new bbox with that top/left and bottom/right
> specification, the new bbox encodes empty. Is it the detection-warping-code
> implementer's responsibility to manage this accordingly?
>
> The right way to do this is to warp all four corner points and then add
them to a new empty box with the "extend()" function to recompute the new
box.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/kwiver-users/attachments/20190311/37e5342b/attachment.html>