09:26 <Loqi> http://twitter.com/Thomas_Wendt :: @farman Not really, just played around a bit. But Geoloqi has a geonotes feature that I've used. Works pretty well.

15:47 <nmelo> Hey everyone! I'm working on a geoloqi enabled app that's using geofences to keep tabs on the user location in regular intervals. Have you ever seen a case where geofence triggers don't fire at high speeds, (~80mph)?

15:53 <aaronpk> if the geofences aren't big enough it's possible that you won't record any points inside the fence if you're moving that fast

15:59 <nmelo> we set up both 250m and 3km fences... often, the 3km fence doesnt fire. the fence is set up around the person... so there's never really an "entrance." it's always exits only.

16:00 <aaronpk> 3km is certainly big enough. 250m may be on the edge if you're going that fast

16:00 <aaronpk> the trigger won't fire unless they enter it, however. so they need to go outside then back in in order to trigger

16:01 <nmelo> hmm... i thought if a geofence were created around you, you'd still get an exit trigger firing.

16:01 <nmelo> i've done that other times

16:01 <nmelo> you can have exit triggers and entrance triggers, no?

16:02 <aaronpk> yes, they are separate kind of triggers

16:02 <aaronpk> but again, the exit trigger will only fire at the moment they leave

16:03 <aaronpk> if you're trying to just get a general idea of where they are all the time, you can use the "rough" profile in the SDK which records locations regardless of the triggers nearby

16:03 <nmelo> yup. that's acceptable...in your opinion, traveling at that speed with a 3km geofence, should we always get at least an exit trigger?

16:03 <nmelo> we ran an experiment... we set up a geofence with a 500m radius, drove through it at 80mph. no entrance trigger, no exit trigger.

16:04 <aaronpk> yes you definitely should get an exit trigger for the 3km geofence if you're driving and leave the area of the fence

16:05 <nmelo> thanks. what about 500 m?

16:05 <aaronpk> 500m should be big enough as well

16:06 <nmelo> what if you "show up" outside it, e.g., you've been in a long tunnel for 10 km, for example. (subway, or whatever). is it the act of passing the boundary that fires the trigger? or the device detecting that you're outside the boundary?

16:13 <aaronpk> you have to cross the boundary for it to run the trigger. the server needs to see the device outside the trigger and if it was previously inside it will run the trigger

16:15 <nmelo> @aaronpk: thanks. that's great.

16:16 <nmelo> i was wondering more about waking the device from the background. if the device is getting location data in the background, only an exit trigger will wake it up

16:16 <nmelo> or entrance trigger

16:16 <nmelo> ?

16:17 <aaronpk> ah, there are a couple things that could wake up the app in the background. one is the exit trigger, but we put in a few other hooks to have a better chance of it being woken up at a good time

16:20 <nmelo> great :) any good advice to debug that 80mph geofence skip issue we're seeing?

17:45 <se7h> hey there, is the 'extra' property not supposed to be returned when fetching a list of layers?

18:15 <se7h> debug webpage is now showing any requests

18:16 <aaronpk> thanks. we are working on it.

18:17 <se7h> maybe you guys can have a look at this too: https://community.geoloqi.com/discussion/102/invalid-error-returned-when-creating-a-user-that-already-exists#Item_1

18:21 <aaronpk> se7h: api debugger shoudl be back now

18:22 <se7h> let me check

18:22 <se7h> aaronpk: yes it is

18:23 <aaronpk> great

18:24 <se7h> this api doc page doesnt exist http://developers.geoloqi.com/api/group/leave/:token

18:26 <se7h> I'll be posting on the community forum issues i find

18:26 <se7h> but that invalid error is really critical since the app has no clue what happend

18:59 <bringo> hey caseorganic are you there?

19:00 <caseorganic> bringo: hello!

19:00 <caseorganic> how are you?

19:00 <bringo> howdy! Hey this URL keeps loading empty for me… no layers shown: http://developers.geoloqi.com/account/layers

19:00 <bringo> is that an el Bug?

19:01 <bringo> hey, I'm doing good, happy hour at Bye and Bye with Rafa so good times. :)

19:09 <bringo> caseorganic: this is what I'm seeing: https://www.dropbox.com/s/m5a5u50d664f5o0/Your%20Layers%20-%20Geoloqi%20Developers.png

19:21 <patrickarlt> bringo that will show layer that belong to applications you have created if you are looking for the list of layers for the app that is here http://geoloqi.com/layers

19:21 <bringo> patrickarlt: ohhhh!

19:24 <bringo> yeah I find the nav sometimes a little bit confusing. but that makes sense. Thanks!

20:01 <se7h> could the layers be 'public' only to app users ?

20:03 <aaronpk> the current API doesn't treat layers that way unfortunately

20:04 <se7h> aaronpk: are there any plans to add the functionality ?

20:05 <aaronpk> the second version of the API will effectively work that way, but we don't have a specific release date set yet

20:09 <se7h> aaronpk: same thing for layers?

20:10 <se7h> i'm trying to find a way to get s list of layers or groups in the app

20:10 <aaronpk> is the code running on a phone or on a server?

20:11 <aaronpk> if it's on a server, you can use the application access token and use layer/list to get a list of layers teh app made

20:11 <aaronpk> also layer/nearby?application_id=XX will return nearby layers created by the given application

20:13 <aaronpk> I have to run! hopefully that is helpful!

20:17 <se7h> aaronpk: layers/list only gives me layers created on the site

20:17 <se7h> layers created by users are no returned

20:18 <se7h> tho nearby returns everything given the app_id

20:18 <se7h> everything nearby i mean