Skip to content
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

Closed
qgib opened this issue Jun 5, 2014 · 5 comments
Closed

Georeferencer truncates coordinates to 2 decimals #18892

qgib opened this issue Jun 5, 2014 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins

Comments

@qgib
Copy link
Contributor

qgib commented Jun 5, 2014

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

@qgib
Copy link
Contributor Author

qgib commented Jun 29, 2014

Author Name: Jürgen Fischer (@jef-n)


  • category_id was changed from C++ Plugins to C++ plugins/Georeferencer

@qgib
Copy link
Contributor Author

qgib commented Nov 23, 2014

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.

@qgib
Copy link
Contributor Author

qgib commented Nov 23, 2014

Author Name: Giovanni Manghi (@gioman)


  • version was changed from 2.2.0 to 2.6.0

@qgib
Copy link
Contributor Author

qgib commented Nov 24, 2014

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).

@qgib
Copy link
Contributor Author

qgib commented Jun 19, 2015

Author Name: Nyall Dawson (@nyalldawson)


Fixed in changeset "cecae9f107351404f202166237b3397735d4d9c2".


  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins labels May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins
Projects
None yet
Development

No branches or pull requests

1 participant