I know it's not the most efficient way, but I use "Refresh Cache Data" to get my 9000+ record database up to date. I can filter it one way to get 3050 or so records, then a second way to get an additional 2600 or so. I'm left with a daily balance of 330 or so caches to download. This refresh was complete last night prior to midnight local (US-CST). This morning, at about 8:15 local, I start a refresh on the remaining 3000-odd caches, and walk away. When I return, I find that the refresh has aborted because I have reached my daily limit. What the --?
I realize this is not a GSAK problem, but an API issue. Still, I thought I'd stand a better chance at a response here, rather than at geocaching.com. I'm guessing the API uses a different time zone for when to reset the download balance. UTC, I'm thinking? Certainly not US-PST, as that would have worked even more in my favor than US-CST.
I realize this is not a GSAK problem, but an API issue. Still, I thought I'd stand a better chance at a response here, rather than at geocaching.com. I'm guessing the API uses a different time zone for when to reset the download balance. UTC, I'm thinking? Certainly not US-PST, as that would have worked even more in my favor than US-CST.