Hello Aron,
If I understand hugin and the undelying panotools correctly, then the
maths direction is already in the direction you require. In the output
image, equirectangular, you already have theta and phi angle in 3D for
each pixel. Distance to object is missing of course. With this (x,y)
which in equirectangular projection is (phi,theta) hugin, well
panotools needs to know which camera pixel it needs to look at.
So one way would be to look up the formulas in the source code.
I presume that output coordinates are first transformed into focal
plane coordinates using standard lense formula and for this the hfov
number is used. Then a new radius is computed from the a,b,c plus d
formula. Of course after that correction for a non-square input image
the hfov angle is not the real horizontal angle as captured with the
sensor. I would cling to points at h/2 radius as these are not
affected by the a+b+c+d correction. Given that your input images have
a know aspect ratio, for the maths to start I would convert the hfov
value into a vfov value which survives the correction unchanged.
Hope that helps
Klaus
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQTo post to this group, send email to
hugin-ptx@...
To unsubscribe from this group, send email to
hugin-ptx-unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/hugin-ptx-~----------~----~----~----~------~----~------~--~---
