OVER_QUERY_LIMIT & map losing bearing

Fergus Flanagan shared this question 10 months ago
Answered

Okay I'm still having a problem with intermittently getting this message OVER_QUERY_LIMIT which appears if I shift focus to another app and return to Locus, or after the calculating message appears on screen. So do I have to keep on erasing my temporary files in settings > miscellaneous > clear temporary data and restart Locus or is there a fix for this? As I have set Brouter as the default router period.


When Brouter is set as the default router (route computing) and I'm online (3/4G) will Locus try and use an online source such as mapquest instead or will it stick with Brouter all the time?


When I used the rotate map to point map in the direction I was travelling on occasions the map would behave as if it was having a seizure by going left and right manically. Any idea why or what?


Thanks

Comments (20)

photo
1

Good day Fergus,

I've read that first major troubles are already solved, that's fine. Let's tune it little bit more.


Error message you see > I have no idea where it comes from and why it happen. It is definitely not directly from Locus. Anyway only solution I see now, is creating error log, right after this error happen, with hope, there will be something useful. How to create a log is wrote here.


If BRouter is set as default, then it will be used everytime, no fallback to another routing engine.


Rotation of map > isn't this problem happen only in moments, you leave track for longer distance then defined in settings > navigation > advanced > maximum allowed deviation? Because in this moment, Locus Map should not be anymore stick to navigation track and also rotation of map starts to be defined by gps/compass (as you have defined) and not track itself.

photo
1

  1. Rotation of map > isn't this problem happen only in moments, you leave track for longer distance

Hi Menion,Well the weird thing was it was doing this when I was actually on the route. I can only assume there maybe was a glitch with the gps and Loucs thought I was off route. Maybe I will just turn off the max allowed deviation for now.


  1. Anyway only solution I see now, is creating error log, right after this error happen, with hope, there will be something useful. How to create a log is wrote here.

Yes I will have a look at doing this when I get an opportunity to get out on a ride next. It would be great to get to the bottom of this.

One more thing on my rides I noticed even though I was on the planned route the "Calculating" message would appear periodically on screen for a few seconds. Is this normal?

photo
1

Really ("Calculating" message)? Hmm, I found this problem as well few weeks ago with previous version. Issue was, that by accident, Locus reported GPS location and network (wi-fi, cell-id), both at once.

Anyway it should be already fixed in new 3.19.0 version. Maybe this was also cause of previous mentioned problems. Give please new version a try during your rides and you will see. Thanks!

photo
1

Will do. Will be a while before I'm out on the bike next but will report back any problems when I do manage to get out :)

photo
1

Perfect Fergus, thank you very much and enjoy your bike rides!

photo
1

Good day Fergus,

Uwe, I've merged your problem to this topic, as both of you see same error message "over_query_limit". Unfortunately this message is not produced by Locus, but by any service that has this problem. Any idea, why which service you use that may cause it?

photo
1

I do not use any external services.

All service settings are by locus default.

photo
1

Some additional information:

Whenever I get this popup error message, the advertising banner on top is stuck.

photo
1

Are you sure you do not use any external services by default ?

AFAIK, Locus by default uses online external MapQuest navigation/routing service.

photo
1

I didn't change any of locus' default service settings.


How can I get this topic back into "my topics" ?


After the merging it disappeared there and is more difficult to follow for me.

photo
1

For testing purpose, I've enabled advertisements also for my Locus version, so we will see if this will cause any troubles.

About following a topic ... there should be no difference for you. Both topics has same problems so it is a lot easier, to discuss both in one topic, thanks for understanding.

If you find anything useful, like "error happen only when I do this and this", please let me know.

photo
1

Will a screenshot help?


But I don"t have this in "my topics" anymore.


I always have to retype it in search, whenever it scrolled out of recent topics.


How can I follow it easier after the merge?

photo
1

Unfortunately this message is not produced by Locus, but by any service that has this problem.


I'm lost what do you mean by this? Can you give examples so I can eliminate them one by one!


I'm guessing what you may mean as one example of a service is the navigation data source?


Mine is currently set to BRouter, will send photos when google get's it act together and doesn't take all day to sync a couple of photos to my desktop!!

photo
1

Take a look at these screenshots to confirms offline service is being used.

photo
1

Thank you for your screenshots Fergus. I was not saying that it have to be a problem of navigation.

Sorry for using word "service" ... to technical :).

What about something different, like "dynamic elevation"? This service, in case you do not have downloaded special offline data, use internet connection to Google server. As I'm checking, here we do now use paid plan so there is a limit that may be reached since more and more people use Locus.

photo
1

"dynamic elevation"

Wasn't aware of the types of services such as this. Could you list those that would likely cause this error message?


Okay I have disabled dynamic elevation. Is there anything else I should be looking out for?

photo
1

Fergus, I do not even know how many of similar services exists in Locus ... well ... many :).

Locus has quite stupid reporting system so in most cases, it is not clear, from which service error comes. It is improved step by step for every service separately. So there is currently nothing you may do. Check next version and let me know, if problem remains. If issue was thanks to this "Dynamci elevation", it will be fixed in next version.

photo
1

OVER_QUERY_LIMIT is related to dynamic altitude from my experience. Google only allows a certain number of requests per ip and then fails with this message if i remember correctly.

photo
1

Perfect joeloc, thank you! Then consider this issue as solved. I've switched from Free access to Paid access where are limits a lot higher, so this problem should not appear again.

photo
1

Thanks folks sounds promising :)

photo