Open SrNetoChan opened 5 years ago
The error is not in the processing algorithm, but looks like a precision issue in the library
I can do it manually and get the same result
c = toWgs("02HLB") toMgrs(*c) '02HKB0000000000'
This can be seen in other converters as well, so might be a problem with that conversion in general
See: http://www.earthpoint.us/Convert.aspx
entering 02HLB, the roundtrip returns a different one as well. And changing the precision makes it change. Probably there will always be that kind of problems with low resolution coordinates, such as the ones used in the test data
I guess this can be closed
Ways to replicate:
Run the "Test add MGRS field algorithm" from the tester plugin. (it's in #13 )
Or:
Using the MGRS coordinates panel, and entering values from the problematic features, it seems that the MGRS_1 field values zoom to the correct place, while the new MGRS field vlaues doesn't.