This is not an app coding problem. I'm just calling toString on Location object. I can reproduce using Google Maps app on the emulator. Send emulator a known location (found using Google Maps web for example), and then use My Location on Google Maps app to see where it thinks that point is.
Guess what, its off by a few hundred yards. I run the same example on the setup on my PC and everything is fine. This is some weird issue either Mac SDK or 64 bit SDK, or maybe even Java runtime (new version was recently installed on my Mac). So its not my math that needs to be checked, but someone elses, basically somewhere some funky conversion is going on, but its nothing that I've written. Also I have found one other person who had the same issue, posted on Stack Overflow (I've also posted there but no response yet). Its not something a lot of people would pick up on. You have to be testing a location based app and you have to be sending known locations to the app and then verifying that the app shows the correct point. On Oct 23, 11:19 pm, Frank Weiss <[email protected]> wrote: > Carefully check your math. Also note that truncation occurs when a decimal > string is converted to a binary floating poit, and possibly also by internal > microdegree conversion. Another thing to take into consideration is that if > the original value has just two decimal digits of precision, 41.74, the > output value should also use that precision, the fourteen decimal digits. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
