-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Georeferencer truncates coordinates to 2 decimals #18892
Comments
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Miroslav Umlauf (@mirouml) Still happens in 2.6. I would say it is pretty high issue. For system in meters, precision to millimeters are sure fine for majority. But when using WGS 84 or any degrees, this is significant error and gives the user wrong result without any warning. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Miroslav Umlauf (@mirouml) Sorry, I did few more tests and this issue doesn't affect precision as far as the values cropped to two decimals were not updated/re-saved. Internally it keeps original values, including saving to GCP - points - file). |
Author Name: Nyall Dawson (@nyalldawson) Fixed in changeset "cecae9f107351404f202166237b3397735d4d9c2".
|
Author Name: ujaval gandhi (@spatialthoughts)
Original Redmine Issue: 10480
Affected QGIS version: 2.6.0
Redmine category:c++_plugins/georeferencer
When entering target coordinates in Georeferencer, the GCP table shows only 2 decimal values. I believe the full value is stored internally, but while transforming, the Georeferencer uses the truncated value. This is especially problematic if the GCP points are close by and truncating the coordinates to 2 decimal shifts the GCPs to a completely wrong location.
This was reported in the user list in 2011 and the issue still persists. http://lists.osgeo.org/pipermail/qgis-user/2011-December/014732.html
The text was updated successfully, but these errors were encountered: