Turbo87
commented
11 years ago Fixed by https://github.com/Turbo87/utm/commit/d6c0cb88dffef13d566c56e3684c7e10215e6104
I would be cautious about the potential precision loss during the conversion. There are quite a few very large and very small numbers involved in the conversion which could potentially lead to a small precision loss depending on the algorithm. I've found my results to be sufficiently correct though for my use cases.
Right now the conversion functions round UTM coodinates (via a cast to
int) but the coordinates should be retained with greater precision -- if someone sends on high-precision coordinates, they likely don't want to know the UTM position rounded to the nearest meter.