Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion flat mosaic stitching (scans etc) and field of view
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
torger  
View profile  
 More options Feb 1 2012, 9:45 am
From: torger <tor...@ludd.ltu.se>
Date: Wed, 1 Feb 2012 06:45:37 -0800 (PST)
Local: Wed, Feb 1 2012 9:45 am
Subject: Re: flat mosaic stitching (scans etc) and field of view
On Jan 31, 11:34 am, kfj <_...@yahoo.com> wrote:

> Having many CPs allows you to calculate lens distortion coefficients,
> which are essential. And you might surprise yourself by just how
> accurate a fit you can get from a field of, say, 100 automatically
> generated CPs per pair. cpfind is really very good, give it a shot.

I've tried it and it works ok, although film grain can confuse it a
bit.

I have no problems with Hugin when doing normal panorama work using my
panorama head, the stuff Hugin is designed for. This application
introduces non-linear issues though, possibly micro-variations in film
curl etc, the micro-metric scale makes it hard to provide "error-free"
input, and on top of that the grainy structure makes seams in slightly
mismatching low contrast areas visible.

As said in the previous post, I now think it is hard to solve this
problem without having a rubber-sheeting or similar non-linear
correction model to handle residual errors. A software designed for
stitching aerial photographs for maps may be the thing, still
searching for something suitable and that works on a tight budget
though.

The trick I did with yaw/pitch corrections and small FOV was just a
"hack" to deal with residual errors the yaw/pitch that the optimizer
finds is not real, but sometimes it works and improves matching
without bad side effects. At first I thought it almost always worked,
but now after more testing I've been forced to change my mind.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.