<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Michael,<div class=""><br class=""></div><div class="">By “orthomosaicing” are you just looking for a 2D orthographic mosaic image or are you looking for dense 3D (or 2.5-D, like a DSM)?</div><div class=""><br class=""></div><div class="">Either way the answer is "we have done that, but it needs to be better integrated”. Integrating these things is conceptually on our roadmap, but this integration work is not actively being funded by anyone at the moment, so it may take some time before it happens.</div><div class=""><br class=""></div><div class="">There is code [1] in the VIBRANT project that will take a homography file produced by the MAP-Tk feature tracker or the VIBRANT stabilization process and produce a mosaic image. However, the mosaic is not necessarily in meaningful ground plane coordinates. Alternatively we can extract homographies from the cameras and point cloud produced by MAP-Tk [2] to get a sequence of homographies that mosaics images on the ground plane.</div><div class=""><br class=""></div><div class="">On the other side, we have developed code [3] to take the camera calibration and point cloud (e.g. from MAP-Tk) and estimate a dense 2.5-D height map (aka DSM). This work was done in a separate experimental repository (not as well tested/maintained/documented) for an earlier project that pre-dates MAP-Tk.</div><div class=""><br class=""></div><div class="">We would very much like to integrate these features within KWIVER more cleanly, but it will take a bit of work since each of these projects (VIBRANT, MAP-Tk, Super3D) came about more or less independently under different funding. If anyone is interested in volunteering to help or willing to fund this work, please let us know.</div><div class=""><br class=""></div><div class="">—Matt</div><div class=""><br class=""></div><div class="">[1] <a href="https://github.com/Kitware/vibrant/blob/master/tools/warp_video.cxx" class="">https://github.com/Kitware/vibrant/blob/master/tools/warp_video.cxx</a></div><div class="">[2] <a href="https://github.com/Kitware/maptk/blob/master/scripts/krtd_and_ply_to_homog.py" class="">https://github.com/Kitware/maptk/blob/master/scripts/krtd_and_ply_to_homog.py</a></div><div class="">[3] <a href="https://github.com/Kitware/super3d/tree/master/super3d/depth" class="">https://github.com/Kitware/super3d/tree/master/super3d/depth</a></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 11, 2015, at 2:09 PM, Michael Rosen <<a href="mailto:michael.rosen@gmail.com" class="">michael.rosen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">With an eye toward a a non-gpl tool chain to do orthomosaicing of overlapping aerial imagery, I'd like to ask about planned support for or suggested options for dense reconstruction.<div class=""><br class=""></div><div class="">Given, say, a bundle.out file (or something equivalent generated by MapTK), how can we create a dense reconstruction like CMVS? Is this something that Kwiver / MapTK expects to support?</div><div class=""><br class=""></div><div class="">msr</div></div>
_______________________________________________<br class="">Kwiver-users mailing list<br class=""><a href="mailto:Kwiver-users@public.kitware.com" class="">Kwiver-users@public.kitware.com</a><br class="">http://public.kitware.com/mailman/listinfo/kwiver-users<br class=""></div></blockquote></div><br class=""></div></body></html>