In the track recording profile, the value "Required accuracy" is less than 10m is not set

Igor Magellan shared this problem ago

Solved

The SET button does not work at values less than 10.

This is useful when writing a track with frequent calls inside the premises.

The same problem 0

Replies (2)

Libor Poutnik Striz ●

Accuracy <10 may lead to many missing points even outdoors.

URL

Igor Magellan ●

This is a specific profile for a smartphone with a good GPS. I do not need "a blot" in the track when I enter, for example, into the store. I noticed that on the street the accuracy of my GPS is always 3m, and it immediately increases to 6 inside the room, I would be helped by a profile with a precision value of 5m, so as not to create track points that do not make any sense. My GPS picks up satellites even through the windows of rooms and does not stop trying to record a track with asterisks.

On walks in the forest, I have other profiles - 10m or more, the tracks are very good.

URL

Libor Poutnik Striz ●

It is rather for smartphone with strong Kalman filtering, or averaging of static like positions, not accuracy of Gps.

With HDOP 1.0, Gps accuracy is typically 2-7 m. In bad signal conditions or satellite geometry, it can be several times worse.

Filtering can produce false feeling of accuracy.

URL

Menion ●

Hi guys,

thanks for a discussion.

Limit to 10 metres has it's historical reason to protect users who sometimes select non-sense values. Agree that values below 10 metres may have sense in this days, so I'll reduce this limit to half.

Anyway as Libor wrote, please keep in mind that accuracy 10 m does not means that all recorded locations will be equal or more precise then this value. Accuracy used in all devices say only probability that location will be in certain range. In case of Android, it usually say that there is 68% probability that location is in circle with defined accuracy.

But, because same "kind" of value is received from GPS and also same "kind" of value is used in recording profile, it make sense to allow also little lower values.

URL

Igor Magellan ●

Thank you, Menion

To protect users who do not know about the danger of small accuracy values, you can display the red popup warning -"Warning! The selected value is too small for most cases!" when you tap "Set", but giving to do it.

OR something like this:

18350bbf93afcde6ccae9ea569865b7d

URL

Menion ●

Thanks Igor, I'll try to improve it.

URL