use location and proximity to adjust location polling frequency
Maybe this is a little bit out there, but if you know a person's location, their defined locations, and the maximum speed they're likely to travel, then you can guess whether they're likely to come in range of a location-based profile anytime soon.
Example: all of my location-based profiles are in Toronto, but I travel in about a 50km radius of Toronto all the time. If I'm 50km away from the nearest defined location and I can't realistically travel more than 120km/h, why check my location 10 minutes later (or however long the refresh interval is currently)? It'll take me at least 25 minutes to get there.
I mostly just thought this was a cool idea. But it might improve battery life a little bit.
Billy Barnes
shared this idea
Locale does dynamically adjust frequency a little bit, but the maximum amount of time between location checks is fixed.
We’ve found that location data can be inaccurate, and that frequent polling is necessary to ensure that Locale updates your situations properly. For example, in certain spots within the city of Boston, Google often tells me that I’m 60 miles outside of Boston. If all my locations are in Boston and Locale assumes that I won’t enter any of them for half an hour, then that causes problems because I’m actually right next to them. (The real problem is bad location data from Google)
