waleedAhmad1 / google-glass-api

Automatically exported from code.google.com/p/google-glass-api
0 stars 0 forks source link

Geofences that change location update frequency #70

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I'm developing Glassware that subscribes to location updates, but if a user is 
staying in a relatively small area, I will generally be ignoring the updates 
until they have moved a minimum amount (~1 mile). I would love to be able to be 
able to set (and potentially, tweak later) the minimum distance between 
updates. This would minimize what my app will have to process as well as cut 
down on traffic between it and the Mirror servers.

As this would need to be somewhat flexible as my glassware evolves, I would 
also need the ability to update that threshold for each of my users.

Original issue reported on code.google.com by kel...@gmail.com on 23 May 2013 at 1:53

GoogleCodeExporter commented 9 years ago

Original comment by mimm...@google.com on 23 May 2013 at 7:13

GoogleCodeExporter commented 9 years ago
I would like to add to this request - not only the ability to set the distance 
threshold, but also the frequency of the location update.  Unfortunately for my 
app, getting an update at 10 minute intervals won't be often enough.  I'm 
developing a travel/trip journal app that geo tags media as users are on the 
move.  If the media is tagged from 10 minutes ago, that location won't 
necessarily be accurate and negate the purposes of the tagging.

Original comment by parkbsu on 23 May 2013 at 12:41

GoogleCodeExporter commented 9 years ago
Isn't this just a request for a circular geofence?

Original comment by russnel...@gmail.com on 25 Jun 2013 at 8:25

GoogleCodeExporter commented 9 years ago
Nope, it is kinda the opposite. I do not want updates until the user has moved 
*outside* that circular fence, then the fence would change to surround the new 
point based on my supplied threshold.

The internal workings may behave similar to geo fencing, but the API would not 
be defining a specific fence, but rather the distance threshold between 
updates. Essentially sending the update out if the user is X away from the last 
time the update was sent.

Original comment by kmerr...@mercuryintermedia.com on 25 Jun 2013 at 9:15

GoogleCodeExporter commented 9 years ago

Original comment by mimm...@google.com on 22 Jul 2013 at 11:25

GoogleCodeExporter commented 9 years ago

Original comment by mimm...@google.com on 30 Jul 2013 at 1:50