I have two BLU 7.0 II Phablets that are running the same CommCare App with
the same configurations. One had a local sim card and the other one doesnt.
I noticed that when I capture a GPS point, if I stay in one area and let it
continue to try to capture the accuracy with change and generally decrease.
-On the GSM connected tablet the field is automatically collected after
the accuracy drops below 10m
-On the tablet without GSM (not connected to Wi-Fi or any other system)
the field is automatically collected after the accuracy drops below 5m
How can I adjust this buffer and why is it different between the GSM tablet
and non-GSM tablet?
I assume this is something within CommCare since it is the actual auto
capture of the point at a certain accuracy.
Again these are the same application so the validation conditions are the
same in CommCare
Best,
Nishant
Found it in
src: remove need for revalidate action · dimagi/commcare-android@324e01f · GitHub
Seems that it is a version issue (2.28 vs 2.29) with GOOD_ACCURACY changing
from 5 to 10.
Do you recommend converting all devices to the 2.28 application to ensure
5m auto collection or is there a better option? I really would like the
accuracy to be under 5. With the current config it would never get there.
···
On Friday, August 26, 2016 at 11:53:44 AM UTC-5, Nishant Kishore wrote:
>
> I have two BLU 7.0 II Phablets that are running the same CommCare App with
> the same configurations. One had a local sim card and the other one doesnt.
>
> I noticed that when I capture a GPS point, if I stay in one area and let
> it continue to try to capture the accuracy with change and generally
> decrease.
>
> -On the GSM connected tablet the field is automatically collected
> after the accuracy drops below 10m
>
> -On the tablet without GSM (not connected to Wi-Fi or any other
> system) the field is automatically collected after the accuracy drops below
> 5m
>
> How can I adjust this buffer and why is it different between the GSM
> tablet and non-GSM tablet?
>
> I assume this is something within CommCare since it is the actual auto
> capture of the point at a certain accuracy.
>
> Again these are the same application so the validation conditions are the
> same in CommCare
>
> Best,
>
> Nishant
>
Hi Nishant,
As you found on GitHub, between CommCare 2.28 and 2.29 we changed the max
needed accuracy for GPS auto-capture from 5 meters to 10 meters. This is
because in rural areas we found that often a GPS reading with 5 meters of
accuracy could never be achieved, so GPS capture would run for several
minutes, until timing out, heavily draining the device's battery.
It sounds like you would like to be able to set the capture accuracy of GPS
auto-capture to something even more accurate than the old 5 meter value. Is
this the case? I imagine this functionality is probably a capability that
many of our users would find useful.
I will look into allowing users to manually set the 'max needed GPS
accuracy' value in their app settings via CommCare HQ. No promises that
this will get done, so if you need this now you should probably downgrade
to 2.28.4. That said, I will be sure to follow up on this thread if it does
get released.
Hey Phillip,
Thanks for the response. You're right it would be great to be able to set
the "good accuracy" field directly since this changes depending on location
and resources. In our case we need to get down to below 5 as we will be
naviating back to these points at a later date and there is decent housing
density. I'll go ahead and switch this to 2.28 for our project.
Best,
Nishant
Nishant Kishore
Data Manager | Malaria Zero: The Alliance for a Malaria-free Haiti | CDC
RPCV: Nicaragua 2011-2014
nish.kishore@gmail.com
M: +18044371312
Skype: nishant.kishore
···
On Fri, Aug 26, 2016 at 2:08 PM, Phillip Mates wrote:
Hi Nishant,
As you found on GitHub, between CommCare 2.28 and 2.29 we changed the max
needed accuracy for GPS auto-capture from 5 meters to 10 meters. This is
because in rural areas we found that often a GPS reading with 5 meters of
accuracy could never be achieved, so GPS capture would run for several
minutes, until timing out, heavily draining the device's battery.
It sounds like you would like to be able to set the capture accuracy of
GPS auto-capture to something even more accurate than the old 5 meter
value. Is this the case? I imagine this functionality is probably a
capability that many of our users would find useful.
I will look into allowing users to manually set the 'max needed GPS
accuracy' value in their app settings via CommCare HQ. No promises that
this will get done, so if you need this now you should probably downgrade
to 2.28.4. That said, I will be sure to follow up on this thread if it does
get released.
--
You received this message because you are subscribed to a topic in the
Google Groups "commcare-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/commcare-users/r-7KTbx2M8o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Nishant and other interested in this issue,
We have just released CommCare 2.30. In this release it is possible to
configure the accuracy value at which GPS auto-capture stops looking for a
more accurate reading.
At this point the configuration requires some advanced, but straightforward
steps. Please reach out to me directly if you are interested in the
instructions. In the future we hope to have this setting to be more easily
configurable on HQ.
···
On Fri, Aug 26, 2016 at 2:25 PM, Nishant Kishore wrote:
Hey Phillip,
Thanks for the response. You're right it would be great to be able to set
the "good accuracy" field directly since this changes depending on location
and resources. In our case we need to get down to below 5 as we will be
naviating back to these points at a later date and there is decent housing
density. I'll go ahead and switch this to 2.28 for our project.
Best,
Nishant
Nishant Kishore
Data Manager | Malaria Zero: The Alliance for a Malaria-free Haiti | CDC
RPCV: Nicaragua 2011-2014
nish.kishore@gmail.com
M: +18044371312
Skype: nishant.kishore
On Fri, Aug 26, 2016 at 2:08 PM, Phillip Mates pmates@dimagi.com wrote:
Hi Nishant,
As you found on GitHub, between CommCare 2.28 and 2.29 we changed the max
needed accuracy for GPS auto-capture from 5 meters to 10 meters. This is
because in rural areas we found that often a GPS reading with 5 meters of
accuracy could never be achieved, so GPS capture would run for several
minutes, until timing out, heavily draining the device's battery.
It sounds like you would like to be able to set the capture accuracy of
GPS auto-capture to something even more accurate than the old 5 meter
value. Is this the case? I imagine this functionality is probably a
capability that many of our users would find useful.
I will look into allowing users to manually set the 'max needed GPS
accuracy' value in their app settings via CommCare HQ. No promises that
this will get done, so if you need this now you should probably downgrade
to 2.28.4. That said, I will be sure to follow up on this thread if it does
get released.
--
You received this message because you are subscribed to a topic in the
Google Groups "commcare-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/commcare-users/r-7KTbx2M8o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.