Location accuracy expands when opening/saving location

Platform: Android

App version number: 1.20.14 (445) but it’s been happening for several versions

Screenshots:

EXAMPLE 1

  1. I create an observation and set the location with accuracy 268m.

Screenshot_20200913-082914|250x500

  1. After tapping the checkmark to save the location, it’s set to this, with accuracy 269m. (In this example it changed only very slightly but other times it has changed a lot, sometimes nearly doubling.)

Screenshot_20200913-082923|250x500

  1. Opening the location picker again to fix it displays the location accuracy as 269 but the actual circle is much larger…

Screenshot_20200913-082931|250x500

  1. … and tapping the checkbox again saves the expanded radius of 526:

Screenshot_20200913-082941|250x500

  1. Opening the location picker again has the radius expand even further:

Screenshot_20200913-083041|250x500

EXAMPLE 2

  1. I made a new observation and pinned its location, with accuracy of 299, which changed to 300 when I left the location picker:

Screenshot_20200913-083808|250x500

Screenshot_20200913-083830|250x500

  1. In a new observation, I picked the pinned location. It still displays the accuracy as 299, but the circle is much larger:

Screenshot_20200913-083945|250x500

  1. Saving the location and going back to the observation, the accuracy has been saved as 526.

Screenshot_20200913-083954|250x500

Description of problem: Location accuracy data doesn’t get saved as what I actually set it to, but saves as something larger, sometimes significantly so. This happens whether I set the location manually on the map or whether I pick a pinned location from the list. Opening and re-saving the location multiple times without changing it causes it to balloon outward exponentially.

This has been an issue for quite a while, through several updates and cache clearings on my end, but I didn’t report it because it was such a glaring issue that I assumed someone else had noticed and reported it and it was getting fixed, but searching the bug reports forum didn’t seem to have any matching results so I guess it wasn’t?

Anyway, thank you for your time

4 Likes

I’ve experienced this as well.

2 Likes

I can replicate, I’ve filed a bug report: https://github.com/inaturalist/iNaturalistAndroid/issues/903

2 Likes

I think this has been fixed - working OK for you?

https://github.com/inaturalist/iNaturalistAndroid/commit/e09ab0ea6d9fac0eab03f8e08537659e2420887a

Something like this has been happening to me lately with the Android app. I select a correct pinned location and it accepts it. On reopening the observation, however, the location has expanded to cover half the United States. Reselecting the pinned location reverts it to correct.
Edit: Actually, it doesn’t accept it the first time. It zooms to the correct location but the accuracy in numbers is way off. Sometimes it varies by insignificant amounts too.

After original upload.

After reselecting pinned location.

Which version of the app are you using?

I’m using 1.28.10 (563) version.

i can reproduce this, but not consistently. using the steps below, i can reproduce maybe one out of every three attempts:

  • check to make sure you don’t have any unsynced observations.
  • close the app completely
  • turn off location services in Android, but make sure you have an internet connection
  • open the app again
  • start a new observation
  • tap the location input box to edit it. this should start you at lat 0 long 0, with a large accuracy circle.
  • choose your pinned location
  • if you encounter the error situation, at this point, should see the preview map zoomed to your location, and you should see a location description that matches your pinned location but coords and accuracy that match the lat 0 long 0 default location.
  • if you accept this location, you will get coords and location description matching your pinned location, but accuracy will reflect the large value from the lat 0 long 0 default.

UPDATE: for what it’s worth, i looked at my app logs, and i don’t see anything obvious that would shed light on what’s going on. here’s a snippet of the part of the log that i believe captures a case where the problem is manifested:

datetime message
2023-08-05 18:28:49 INaturalistApp.applyLocaleSettings():1055: INAT: Application: applyLocaleSettings - en / en / en_US
2023-08-05 18:28:59 LocationChooserActivity.updateLocationBasedOnMap():757: LocationChooserActivity: mOriginalZoom = null; current zoom = 3.000000
2023-08-05 18:28:59 LocationChooserActivity.updateLocationBasedOnMap():762: LocationChooserActivity: Meters per radius = 1519730.375
2023-08-05 18:30:06 LocationChooserActivity.updateLocationBasedOnMap():757: LocationChooserActivity: mOriginalZoom = 15.686739; current zoom = 15.686739
2023-08-05 18:30:06 ObservationEditor.onActivityResult():2769: INAT: ObservationEditor: onActivityResult: 103:-1:Intent { (has extras) }

It’s not consistent for me either, and probably not for anyone, I’m guessing.