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

Inaccurate and asymmetric (North/South) transformation utm to lat lon #6

Open
camillechasset opened this issue Mar 18, 2024 · 6 comments

Comments

@camillechasset
Copy link

I think I found an error in the original python code. The issue is reported and analyzed here

Summary: because of a wrong parenthesis position here the transformation from UTM to lat/lon was not fully accurate. Error up to 8cm in Svalbard, 6.5cm in Norway, and 5mm at other places. Error can be reduced with a factor between 5 and 10 depending on the location.

@im7mortal
Copy link
Owner

Thank you @camillechasset !
Great explanation! I will change it immediately after the python version will be modified.
Feel free to remind me about it.

@im7mortal
Copy link
Owner

@camillechasset I see there still no any response on python version.

I still want that python and go version were exact match. I just want to notify you , that I follow this issue

@im7mortal
Copy link
Owner

I see there still no any response on python version.

It's possible to get version with this fix using this command

go get github.com/im7mortal/UTM@839439135257eeb116a1edb8af72911e5df6a998

@tvkn
Copy link

tvkn commented Dec 16, 2024

Hi @im7mortal,

The python code has now been updated (with 8394391), and the corresponding issue has been closed.

Is there anything else blocking from getting this into main? Can I help?

@im7mortal
Copy link
Owner

Thank you @tvkn !

I released v1.4.0.

If you could verify that the distortion disappeared, it would be great!

Otherwise feel free to close the issue.

@tvkn
Copy link

tvkn commented Jan 2, 2025

I reviewed your code change and it looks good (and in line with the Python fix).

I can't close the issue as I don't own it, but OK for me to close based on the above.

Thanks & happy new year!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants