Skip to content
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

Open
simplywing opened this issue Jul 6, 2017 · 18 comments
Open

Geolocation acting strange #54

simplywing opened this issue Jul 6, 2017 · 18 comments

Comments

@simplywing
Copy link

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.
bildschirmfoto 2017-07-06 um 21 58 59

@tananaev
Copy link
Member

tananaev commented Jul 6, 2017

Possibly it's network location, which can be very inaccurate. Then GPS fixes the signal, so you start receiving precise location.

@simplywing
Copy link
Author

Is there a way to fix this and only take the GPS-Location?

@tananaev
Copy link
Member

tananaev commented Jul 6, 2017

Unfortunately not for iOS, but it should be reporting accuracy along with location.

@simplywing
Copy link
Author

simplywing commented Aug 9, 2017

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

@tananaev
Copy link
Member

tananaev commented Aug 9, 2017

Looks like it's not implemented on iOS yet. Android app definitely reports it.

@simplywing
Copy link
Author

@tananaev
Copy link
Member

Maybe I have some changes locally. I definitely remember implementing it. Anyway, it's in plans to include it.

@simplywing
Copy link
Author

simplywing commented May 7, 2018

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?

@tananaev
Copy link
Member

tananaev commented May 7, 2018

It should be available in iOS as well.

@simplywing
Copy link
Author

It clearly is not:
https://github.com/traccar/traccar-client-ios/blob/master/TraccarClient/ProtocolFormatter.swift

I used Wireshark to be sure. It really does not report the accuracy, no matter which accuracy mode is chosen.

@tananaev
Copy link
Member

tananaev commented May 8, 2018

I definitely worked on it. Possibly I haven't pushed it to the GitHub yet for some reason.

@simplywing
Copy link
Author

Would be super nice if you could push these changes.

@tananaev
Copy link
Member

Added accuracy:

471d786

@LNFWebsite
Copy link

LNFWebsite commented Jul 13, 2018

@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!

@tananaev
Copy link
Member

I don't think we released a new version with this functionality yet.

@LNFWebsite
Copy link

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.

@tananaev
Copy link
Member

It will be included with next release.

@LNFWebsite
Copy link

Okay, thanks man!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants