GEOCPSET("1")

🦋 geocpset — the girl who adds control points by ✨vibes and geometry✨

okay so first things first, bestie: the header up top says GEOCPSET("1") and the manual section is HUGIN — that's literally the whole family tree, iykyk. Now let's get into it 💅

---

🌸 NAME 🌸

geocpset — adds control points based on geometric position. that's it, that's the whole personality 🫶

---

✨ SYNOPSIS ✨

geocpset [-o output.pto] input.pto

short and iconic. love that for us.

---

💖 DESCRIPTION 💖

okay so picture this: you've got panoramas full of featureless images — think sky images, the most gorgeous boring thing ever, literally nothing but blue. and in those images, a control point detector finds nothing. zero. nada. it's giving "empty group chat" 😭

that's where geocpset comes in and honestly? she ate. she analyses the positions of the images in project files, then she adds control points to these images which are not connected by control points.

and here's the important part, the part you can NOT skip (this is the vibe check of the whole manpage): those control points are set only by the geometric positions of the images and not by the image content. so geocpset should only be used with projects which have assigned rough image positions. like, no positions assigned? she has nothing to work with. it's giving ✨no cap✨

---

🎀 USAGE 🎀

geocpset -o output.pto input.pto

if the --output/-o switch is missing then the suffix _geo is added to the filename. cute little auto-nickname, honestly 🥰

and here's the indented workflow — the main character sequence, step by step, do not skip steps bestie:

#1 first create project file

pto_gen -o project.pto *.jpg

#2 then assign rough positions to images

pto_var --set y=i*20-40,p=0,r=0 -o project.pto project.pto

#3 now run a "normal" control point detector, e.g. only on overlapping images

cpfind --prealigned -o project.pto project.pto

#4 and finally connect all unconnected images

geocpset -o project.pto project.pto

see how it all comes together?? the way that workflow just works 🔥

---

🧚 OPTIONS 🧚

• -o|--output output.pto — Output a pto file with the given filename. If not given it will append _geo to the input filename. 💖
• -e|--each-overlap — By default geocpset adds only control points to unconnected images. With this switch you can force to add a geometric control point to each overlap, which is not connect by control points or linked with image positions. she's thorough like that ✨
• --min-overlap=NUM — By default geocpset takes only image pairs into account which overlap more than 10 %. If you have very narrow overlaps you can decrease this value to take also such small overlaps into account, e.g. --min-overlap=1. tiny overlap? no problem, she sees you 👀
• -h|--help — Display help. the classic "please explain yourself" button 🫶

---

👑 AUTHORS 👑

geocpset was written by Thomas Modes. This manpages was generated by converting the wiki-page on <http://wiki.panotools.org/> to pod-format by Andreas Metzler. legends, both of them, fr fr 🌈

---

lowkey a reminder before you go: geocpset only works off geometry, not image content — so make sure your project already has rough image positions assigned, or she's just guessing (and not in a fun way) 💀

---

and that's the whole page, bestie — signed off with Version: 2025.0.1, dated 2026-09-22, and yes that's the same GEOCPSET("1") we opened with, coming back around like the main character she is 🎀✨