You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that high precision GNSS receivers are supported (as per #65), the ability for the user to set the arrival threshold is more important.
Consider this a refinement of #3. Some examples are:
If a user has a receiver that as an accuracy of 1m, and they are searching for a manhole in an open field - an arrival threshold of 1m is a reasonable expectation.
if a user in a city environement, using either an external receiver or internal position source and looking for a light pole (ie: something obvious), then an arrival threshold of 10-20m is reasonable.
The text was updated successfully, but these errors were encountered:
accuracy threshold should go in the settings section called destination (under longitude) - not a new section of its own - and display the units that are selected below it eg: (m) or (ft) to be clear that even when degrees are used for the coordinates the accuracy will always be entered / shown in m or ft.
Now that high precision GNSS receivers are supported (as per #65), the ability for the user to set the arrival threshold is more important.
Consider this a refinement of #3. Some examples are:
The text was updated successfully, but these errors were encountered: