Seems like this could get expensive in your example use cases vs avoiding the API and using pure application code?
@codefoster
3 жыл бұрын
I think you mean moving the map and the logic offline to the device to avoid cloud compute costs. That could be. I think a hybrid solution would be best to capture the benefits of doing it in the cloud while maintaining the low cost of doing it on the device.
@heiko3169
4 жыл бұрын
While I understand the "inaccurate GPS" claim, i do NOT understand why I need a buffer when it comes to the result of being inside or outside the polygone. Its a mathematical function to calculate whether a coordinate is within a defined polygone , or not. Thats not something special for GPS! There is absolutely no reason for a "buffer". Do I miss something here? ..oh now i got that. The buffer is there because the longitude/latitude being send to the API (from the IoT device) could be affected by the GPS inaccurance. OK, makes sense then to have the buffer as a margin to be not too strict. On the other hand, one could setup the Azure fence polygone just a bit wider or narrower to cover that buffer. Or?!
@codefoster
3 жыл бұрын
Yeah, I think the buffer makes it easy to "debounce" the location. Without it, your location may appear to be sporadically jumping in and out of the fence. I believe you could accomplish the same thing with a bit of application logic, but I suspect it could get difficult in more complicated geofences, so it's nice that it's in the SDK.
Пікірлер: 5