Differences

This shows you the differences between two versions of the page.

--- software:stitching [2012/02/12 21:43] – mcmaster
+++ software:stitching [2025/08/04 21:23] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 IC image stitching as a basic level is similar to stitching together a large number of scanned images.  Depending on how you collect the images though you also might have to (at least want to) correct lens defects, roll/pitch, and other parameters.  Additionally, due to the very large sizes involved you may find that software breaks down as you start approaching the gigapixel (GP) image size.
-Pr0ntools (https://github.com/JohnDMcMaster/pr0ntools/) has image processing routines to help with the sort of tasks you'll want to do.  Its setup for the tool flow that I (JM) use but should be modular enough that others can get it to fit their needs.  This page will refer to the Hugin/panotools toolchain unless otherwise specified.
+This page primarily focuses on Hugin / libpano
-====== Basic stitching ======
+Tutorials
+  * Hugin
+    * Hugin scanner tutorial
+    * https://github.com/whitequark/groupxiv#bonus-image-stitching-with-hugin
+    * Ken S (FIXME: link)
+  * prawntools (libpano / Hugin core)
-Follow the Hugin scanner tutorial
-====== Gathering control points ======
+====== prawntools ======
-The best open source way to do these is probably autopano-sift-c (or the surf version if you are commercial).  However, I've found that Andrew Jenny's free but closed source version tends to do a lot better.  I suspect that its related to point validation but don't really know.  pr0nstitch takes cares of the hoops you'd need to go through to get the latest version of it working well through WINE.
+https://github.com/JohnDMcMaster/prawntools/
-====== Lens correction ======
+I (JM) use this to stitch my images.  Its intended to help automate overall workflow and accelerate large stitch jobs.
-TODO: add a section on this
+====== Gathering control points ======
+The best open source way to do these is probably autopano-sift-c (or the surf version if you are commercial).  However, I've found that Andrew Jenny's free but closed source version tends to do a lot better.  I suspect that its related to point validation but don't really know.  prawnstitch takes cares of the hoops you'd need to go through to get the latest version of it working well through WINE.
 ====== Google maps view ======
-See some examples here http://siliconpr0n.org/map/
+Some options:
+  * prawnmap, part of prawntools
+  * whitequark tool (FIXME: link)
+See some examples here http://siliconprawn.org/map/
 People tend no to like to download huge image files and some people won't have the computer hardware to open them.  Google maps view breaks the huge images into many smaller tiles so that they can be accessible to a wider audience (and save server bandwidth too!).
-pr0ntools provides tools to convert an existing image to Google maps (pr0nmap) as well as directly stitching a panotools .pto project to tiles.  In practice this tends to be faster than stitching to a full sized image and then breaking out because it avoids creating large intermediate images that tend to eat cache / RAM for breakfast.
+prawntools provides tools to convert an existing image to Google maps (prawnmap) as well as directly stitching a panotools .pto project to tiles.  In practice this tends to be faster than stitching to a full sized image and then breaking out because it avoids creating large intermediate images that tend to eat cache / RAM for breakfast.