<p>Very good idea..<br>
Implementing a known problems per release seems possible to me. But it can only be a webpage cause at the time of release you mostly are not aware of the problems..<br>
Regards<br>
Werner</p>
<div class="gmail_quote">Am 17.12.2011 21:07 schrieb "Agustin Lobo" <<a href="mailto:alobolistas@gmail.com">alobolistas@gmail.com</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Many thanks Manuel.<br>
No hurry for including the patch, once the problem is identified and<br>
you even provide a simple way to circumvent it.<br>
What is needed is to have users know of these potential problems, ie. through<br>
a note of "Known Problems" included in the release mentioning that<br>
"the Georeferencer plugin requires users to check that their files do<br>
not include<br>
an implicit geotransform and use e.g.<br>
"gdal_translate -co "PROFILE=BASELINE" -of GTiff Ilerfly125v2.tif<br>
Ilerfly125v2-nogeotrans.tif"<br>
to remove it in case this is actually needed".<br>
In other words, once the problem is identified and warned, users can<br>
rely on using the software for the rest of cases.<br>
The question is thus that, in addition of the excellent developers<br>
already involved,<br>
we need a team of users and a battery of tests to be regularly performed.<br>
Agus<br>
<br>
<br>
<br>
<br>
<br>
<br>
2011/12/17 Manuel Massing <<a href="mailto:m.massing@warped-space.de">m.massing@warped-space.de</a>>:<br>
> Hi Agustin,<br>
><br>
><br>
>> The points are correct (therefore the errors etc), but the<br>
><br>
>> georeferenced image is shifted. May be the datum is not taken into<br>
><br>
>> account<br>
><br>
>> when the georeferenced image is created.<br>
><br>
><br>
> I did a clean checkout, and could finally reproduce the problem:<br>
><br>
> it stems from the fact that your input file has a geotransform,<br>
><br>
> which flips the yaxis of the local coordinate system and changes the<br>
><br>
> origin. As the geotransform plugin does not handle geotransform<br>
><br>
> info correctly, this results in the shift you have observed.<br>
><br>
><br>
> Removing the geotransform (e.g. using "gdal_translate -co "PROFILE=BASELINE"<br>
> -of GTiff Ilerfly125v2.tif Ilerfly125v2-nogeotrans.tif") should give you<br>
><br>
> a file which the georeferencer can handle correctly (you may have to delete<br>
> the accompanying .aux file, if gdal uses this to keep the geotransform).<br>
><br>
><br>
> I had a local patch in the georeferencer which handles geotransform<br>
><br>
> information, so this is why I couldn't reproduce the problem (talk about a<br>
><br>
> mixture of good and bad luck :-)). I will see what is required to make my<br>
><br>
> local changes ready for submission, so we can avoid such subtle problem with<br>
><br>
> georeferenced/pseudo-georeferenced files in the future. As I already<br>
><br>
> mentioned, due to an important deadline at work, I have little time to<br>
><br>
> dedicate to this atm, so it may take a few day... is there a release in the<br>
><br>
> pipeline?<br>
><br>
><br>
> cheers,<br>
><br>
><br>
> Manuel<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>