I'm finding wrong, distorted results with qgis 2.0 georeferencer. We've tried
with the same set of gcp's in envi and the same method (polynomial deg 2) and
there the results are correct, but with
qgis the result is very distorted. Actually, the errors represented by
the red segments in the
Hi!
We are using the Georeferencer tool and the resulting image is shifted,
please see the screenshot here:
https://sites.google.com/site/filestemp2/home/error_georef.jpg?attredirects=0
We've tried polynomia of order 1 and 2 and Helmert, with very similar results.
I think this is a bug, but I'm
Hi Paolo,
Warning: Object::connect: No such signal
QgsGCPListWidget::replaceDataPoint( QgsGeorefDataPoint*, int )
in
/home/paolo/build/qgis/qgis_unstable/src/plugins/georeferencer/qgsgcplist
w idget.cpp:70 All the best.
apart from this warning (which shouldn't have any side effects), I
Il giorno sab, 29/01/2011 alle 14.17 +0100, Manuel Massing ha scritto:
found anything which explains the bad_alloc you are getting. I
suspect
it is a build issue, or the exception is thrown from somewhere else
(e.g.
the plugin loader).
I think you're right: I spotted the same popup on
Il giorno mar, 25/01/2011 alle 23.12 +0100, Manuel Massing ha scritto:
I can't reproduce either of the bugs (not the bad_alloc() nor the
transform failure). Do you have any specifics?
Yes:
- it happens only at the startup of the georeferencer
- it happens on a machine, not on another
- the
Hi al.
I keep on getting:
std::bad_alloc
when opening the georeferencer (Debian unstable, qgis trunk).
After that, it seems to work fine.
Can anyone confirm?
All the best.
--
Paolo Cavallini: http://www.faunalia.it/pc
___
Qgis-developer mailing list
And under Ubuntu today we seemed to find no situation in which it
would actually allow the transform to be carried out...
Regards
Tim
On Tue, Jan 25, 2011 at 2:18 PM, Giovanni Manghi
giovanni.man...@gmail.com wrote:
Hi,
Can anyone confirm?
not under Ubuntu/qgis trunk. Here no error
Hi,
And under Ubuntu today we seemed to find no situation in which it
would actually allow the transform to be carried out...
I can't reproduce either of the bugs (not the bad_alloc() nor the
transform failure). Do you have any specifics?
cheers,
Manuel
