Support for Geofences?

[maurizi]

Is there any intention to add support for Geofences and the Geofence API?

[ecgreb]

Geofencing is definitely on the roadmap.

Currently we are working on adapting the project to use the new location APIs introduced in Google Play services 4.2.

#11 implements some of the methods in FusedLocationProviderApi and adds a skeleton for the new GeofencingApi.

Pull requests are always welcome 😄

[friesenkiwi]

I am currently trying to port OwnTracks from PlayServices to LOST (owntracks/android#88). It looks good so far, but missing Geofencing would be a dealbreaker, since it is a feature many users of it heavily rely upon.
For the current development state, I added some try/catch for the "not yet implemented" RuntimeExceptions to at least not crash the app.
But we would still like to switch and thus "need" GeoFencing support in LOST. Are there any recent considerations of implementation or forseeable progress?
Thinking about it, it might be not too complicated to add it? As far as I can see, it would be implementing the three methods addGeofences(List, PendingIntent), removeGeofences(List), removeGeofences(PendingIntent) in GeofencingApiImpl.java
and implement the Geofence.java interface, is that correct? Also, of course, the actual detection of transitions needs to be implemented. But since there are only circular Fences, that should be quite straightforward, right?
I found https://code.google.com/p/openmap/source/browse/src/openmap/com/bbn/openmap/geo/Intersection.java
or
http://www.codeproject.com/Articles/62482/A-Simple-Geo-Fencing-Using-Polygon-Method
as a start, but they seem to be eben a little bit too complex.
And I'd say, a minimal set of features would already be desireable, no need to implement all features at once? (Loitering, Dwelling, Responsiveness, GeofencingRequest etc.)

[broakenmedia]

Hows this going? Any sign of addProximityAlert methods?

[friesenkiwi]

Hey, there. Sorry I had to drop my first work on this last year, but I am right now looking into it again. I see @ecgreb you are working on it as well? How far is the progress? Would it be any helpful if I joined in?
Is the schedule for 2.0 very tight? Because I would love to see this feature in a release soon, so it can be used over at owntracks, and I would be very happy to help, if that's of interest.

[ecgreb]

Hi @friesenkiwi. Its all good. Help is always appreciated. Here is what I have so far:

#86

As you can see in the description things are not quite working yet. Also once inital support is in place there will be more work needed including registering multiple geofences, removing geofences, and triggering geofences via mock locations. Plus likely some other things I am overlooking.