Here's me redo of it, with steps, output image and PTO.
Steps (just to make sure I remembered what I did).
1. Select the 4 images in my file manager, right click, select "Open
With ... Hugin PTO generater.
2. Open the PTO in Hugin.
3. Run Create control points option "Hugins CPFind + Celest (slower, but
no CPS on clouds).
4. Optimize geometric (incremental, starting from anchor). My run
reported this:
Results:
average control point distance: 22.408888
standard deviation: 77.171264
maximum: 339.069320
5. Cleaned control points. That removed 7.
6. Crop all images from this lens to remove the notched corner.
7. Optimize geometric Positions, View and Barrel (y,p,r,v,b).
8. Preview panorama in Fast Panorama Preview window. While there, set
projection to Rectilinear. On Move/Drag tab, click Center button.
9. Optimize geometric positions: Everything without translation.
10. In Fast Panorama Preview, click Center button again to re-center. On
the Crop tab in Fast Panorama Preview, click Autocrop. Close Fast
Panorama Preview.
11. Click calculate optimize size. Gave me 27012 width, 60777 height.
12. Save pano and stitch.
NOTE: Didn't run vertical lines search. Vertical lines make no sense for
these images. I think vertical lines here could really screw things up.
Didn't optimize exposure at all. First time I tried this, I tried
optimizing exposure, and it came out all overexposed and wrong. So I
decided to go without it.
Also, after you mentioned the source of these images (scanned film from
some unknown aerial camera) and that it was professionally shot, I
decided that they would have shot them all at the same exposure. If they
were also professionally scanned, I'm pretty sure they're all the same
exposure. So I left the exposure as it was, without optimization.
Link for the image and PTO file:
http://clanjones.org/david/porirtestpano/LMI-Kort-J36-J-8500-LMI-Kort-J36-J-8503.tif
http://clanjones.org/david/porirtestpano/LMI-Kort-J36-J-8500-LMI-Kort-J36-J-8503.pto
The TIF is 748.8MB, 48bit TIFF. 24736 wide, 10515 height. 82.5" by 35"
at 300 dots per inch in the USA's archaic measurement system.
Let me know when you get them.
A quick look through showed me a few artefacts: minor jogs in a house
and a street at a few places. Those might originate in the geometric
optimization process. Maybe optimizing for translation, too, would help,
since these were shot from a moving airplane so the camera was moving.
I'm not familiar with using translation. Other folk on the list would be
better helpers with that.
What do you think?
On 4/27/19 5:45 AM, Kameldýrið wrote:
hugin1.PNG
hugin0.PNGHi again.
I tried a procedure silmilar to one that you described
I ended up with an image with farly much over-exposure and and artefacts.
Is there anything that I am doing wrong that I can do to improve my results?
Could you perhaps upload your result image?
Thanks.
Þórir.
On Sunday, 21 April 2019 07:51:12 UTC, GnomeNomad wrote:
Hey, thanks for sharing the pictures. Loved them, big and sharp. :)
Very big - 446.8MB per image! What kind of drone/camera did you use?
The focal length Hugin PTO Generator came up with was 34.607 with a
multiplier of 1.
I stitched all 4 of them, full sized, in Hugin on my Linux laptop.
First
ran the Hugin PTO Generator. Then opened the PTO in Hugin, ran the
CPFind + Celeste option on it. Ran the Positions Incremental geometric
otpimization. Cleaned the control points. On the Masks tab, masked out
the corner notch and the black borders on the images. Ran the Positions
and Barrel Distortion (yp4b) geometric optimization. Went to the Fast
Preview, set it to Rectilinear projection. Clicked the Center button on
Move/Drag tab, then Autocrop. On the Stitcher tab, I clicked Calculate
Optimal Size. I experimented with various photometric optimizations and
finally decided to just leave it untouched.
Saved the PTO and ran the stitch. Stitching took 4 minutes on my 2.4GHz
i7 processor.
Memory usage peaked at 10.8GB (my laptop has 16GB). That could affect
things on machines with less memory or other operating systems. My
office laptop with Windows 7 Enterprise and 8GB of memory uses just
about 4GB of memory for Windows and the assorted enterprise-mandated
security applications. So I suspect the fact that stitching stopped and
produced a corrupted file on your computer means your computer ran out
of memory and something didn't respond well to using swap space.
I ended up with a 932.9MB 48-bit TIFF file. Ran the stitch again to
output a JPG and got a 345.3MB file.
Thank you again for the pictures. I currently shoot mere 6Mpixel 48-bit
TIFF and plan to move to a 42-45Mpixel camera in the future. Nice to
know that my present set up can handle large images!
On 4/17/19 8:30 AM, Wirz wrote:
> Hi,
>
> I think there is nothing wrong with your pictures. I gave the first
> first two a try and they stitch fine
> (http://78.46.190.157:8080/first-two.jpg
<http://78.46.190.157:8080/first-two.jpg>).
>
> Mostly that is, because there is a conceptual problem with aerial
> pictures: You can either stitch photos of any scene (with all the
photos
> taken from the same point), or of a flat surface (with almost
arbitrary
> camera positions). Given that Iceland is not flat, and airplanes
are
> not stationary, neither approximation is perfect. But if some
artefacts
> are acceptable you can assume that the ground is flat enough and the
> result won't be too bad.
>
> cheers, lukas
>
>
>
> On 17/04/2019 17:48, Kameldýrið wrote:
>> The focal length is 151,78 mm on those
>>
>> On Wednesday, 17 April 2019 14:40:05 UTC, Kameldýrið wrote:
>>>
>>> Hi Terry.
>>> Whenever hugin stitches them together it stops responding and
results in a
>>> corrupt file.
>>> I dont know if its due to their size (they're fairly large
tiffs) or to my
>>> computers limitations.
>>> The tiff files of the 4 photos can be downloaded if you would
like to
>>> recreate. (500
>>>
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8500
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8500>>,
>>> 501
>>>
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8501
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8501>>,
>>> 502
>>>
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8502
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8502>>,
>>> 503
>>>
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8503
<https://atlas.lmi.is/getfile/tif_loftmynd.php?id=/mnt/loftmvolmc/loftmvolm8/loftm_vol_8/J36-J-8503>>
>>> )
>>>
>>> Thanks for responding
>>>
>>> On Wednesday, 17 April 2019 02:50:51 UTC, Tduell wrote:
>>>>
>>>> On Wed, 17 Apr 2019 06:48:01 +1000, Kameldýrið
>>>> <[email protected]> wrote:
>>>>
>>>>> Hi. I'm new to hugin an I wanted to know if there's a way to
stitch
>>>>> aerial
>>>>> photos.
>>>>> I have 4 photos I'd like to stich together but I don't know how.
>>>>> Any help is appreciated.
>>>>>
>>>>
>>>> Have you read the tutorials ?
>>>> <http://hugin.sourceforge.net/tutorials/index.shtml
<http://hugin.sourceforge.net/tutorials/index.shtml>>
>>>> Assuming that your images have a reasonable amount of overlap,
I'd
>>>> suggest
>>>> you have a try and if you run into difficulties, then come
back here with
>>>>
>>>> details of your problems.
>>>>
>>>> Cheers,
>>>> --
>>>> Regards,
>>>> Terry Duell
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/d0113379-b8da-4edf-5f89-b5270b4da476%40gmail.com.
For more options, visit https://groups.google.com/d/optout.