-
-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geolocation acting strange #54
Comments
Possibly it's network location, which can be very inaccurate. Then GPS fixes the signal, so you start receiving precise location. |
Is there a way to fix this and only take the GPS-Location? |
Unfortunately not for iOS, but it should be reporting accuracy along with location. |
Is there a documentation available for the accuracy reporting? According to the protocol formater, the accuracy is not reportet: https://github.com/tananaev/traccar-client-ios/blob/master/TraccarClient/TCProtocolFormatter.m |
Looks like it's not implemented on iOS yet. Android app definitely reports it. |
Maybe I have some changes locally. I definitely remember implementing it. Anyway, it's in plans to include it. |
Hi, I revisited this topic since the Android app now nicely reports the location accuracy. Cool! Is it planned to be implemented in IOS soon? |
It should be available in iOS as well. |
It clearly is not: I used Wireshark to be sure. It really does not report the accuracy, no matter which accuracy mode is chosen. |
I definitely worked on it. Possibly I haven't pushed it to the GitHub yet for some reason. |
Would be super nice if you could push these changes. |
Added accuracy: |
@tananaev Thanks for working on the ability to change accuracy so as not to drain battery. Unfortuately though, the accuracy radius is not being reported when in low accuracy mode. Is this known behavior of the app? (I'm on latest App Store version) Thanks ahead! |
I don't think we released a new version with this functionality yet. |
Oh okay. Yeah, an accuracy radius would be really helpful information if it's possible to gather. In the low accuracy mode, you can't distinguish between super inaccurate locations by cell triangulation from locations gathered by WiFi or GPS. Thanks anyway. |
It will be included with next release. |
Okay, thanks man! |
I recognized it a few times now that the first one or two location points are very far off the real point. After that it seems to recover. (Screenshot) This only seems to happen on IOS and not on Android.
The text was updated successfully, but these errors were encountered: