Creating points with MGRS gives wrong positions

Boris K shared this problem ago

Solved

Dear all,

I encounter the following problems with Locus Map Pro for Android (3.14.2) concerning the MGRS format

Set the position format to MGRS. Now I want to communicate the position of a previously created point to a friend. In the point's details view, I tap and hold on the coordinates text-field. Locus copies the position to the clipboard. Now I paste the string into a message to my friend. It is "32UMV 45260 02922" (without the quotes, but with the blanks), a small rescue outpost in the northern Black Forest in Germany. My friend copies this data to his clipboard, creates a new point in Locus, taps on the position field in order to edit, chooses MGRS and pastes the sting into the text-field. After saving the point, one can notice that the newly created point has a DIFFERENT position. In my case, it is "32UMV 45261 02929", which is not correct. This behavior can be reproduced every time. The blanks in the position string seem to be the problem: If you omit the blanks and enter "32UMV4526002922" into the MGRS text-field, it ALMOST works (see problem b). In my opinion this is a severe bug: If I needed rescue and Locus itself copies my position to the clipboard with blanks, it should be capable of reading this exact string. Furthermore, the rescuer doesn't get an error while pasting the position (like: "wrong format"). So he won't find me. In this example, the offset created by Locus is not huge, but I encountered the same problem in another case where (if I remember correctly) it has been like a hundred meters (or so).

In general, Locus seems to dislike some MGRS positions. I create a new point and enter the following string in the MGRS text-field: "32UMV4517002908" (without quotes), this is the "Predigtstuhl" rock. After hitting ok, Locus now immediately changes the position to "32UMV4516902907". OK, the offset is 1m south and 1m west, but that is not what I gave you, Locus! WHY?! Maybe the position is converted internally back and forth. There is a workaround: I convert the position (using a web service) to Lat/Lon and then enter it as Lat/Lon. With MGRS set as position format, it will now display the "correct" MGRS position (with ...70 ...08).

I really love Locus Map Pro for its features and most of all, for being able to handle MGRS/UTM-REF. Please continue the good work and kick the bug's asses. Especially problem a) is really critical.

Boris