I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template mentioned
previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search
and
someone on the mobile dev team will take a look.
Best,
Will
···
On Tue, May 13, 2014 at 9:20 AM, Ameera Hamid wrote:
Hi Everyone,
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
Are there any plans to support "approximate" capture in CommCare?
···
On Tue, May 13, 2014 at 10:21 AM, William Pride wrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
Technically this would be trivial, the difficulty is in determining what
constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at all,
even if this was very approximate (the order of thousands of meters).
Meanwhile, if you wait for an exact location you might hang forever. The
solution we arrived at was to add an "acceptable" threshold with distinct
messaign in addition to the "exact" threshold that's seemed to work well in
general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective) Or maybe we want to make the
thresholds configurable via HQ?
Not sure this is the right forum to address these questions but I'm open to
hearing ideas and opinions
···
On Tue, May 13, 2014 at 12:30 PM, Cory Zue wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.com wrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
Technically this would be trivial, the difficulty is in determining what
constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at all,
even if this was very approximate (the order of thousands of meters).
Meanwhile, if you wait for an exact location you might hang forever. The
solution we arrived at was to add an "acceptable" threshold with distinct
messaign in addition to the "exact" threshold that's seemed to work well in
general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective)
Or maybe we want to make the thresholds configurable via HQ?
This makes the most intuitive sense to me, since each project may have
different requirements about how precise they need that number to be.
···
On Tue, May 13, 2014 at 1:05 PM, William Pride wrote:
Not sure this is the right forum to address these questions but I'm open
to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
I think making the threshold configurable would be a good idea and i see
that Amelia has posted a link for me to vote for that option. In the short
term is there anything that can be done abut it?
···
On Tue, May 13, 2014 at 7:05 PM, William Pride wrote:
Technically this would be trivial, the difficulty is in determining what
constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at all,
even if this was very approximate (the order of thousands of meters).
Meanwhile, if you wait for an exact location you might hang forever. The
solution we arrived at was to add an "acceptable" threshold with distinct
messaign in addition to the "exact" threshold that's seemed to work well in
general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective) Or maybe we want to make the
thresholds configurable via HQ?
Not sure this is the right forum to address these questions but I'm open
to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
Based on how many votes it gets we will plan to put it on a future mobile
release.
Thanks,
Amelia
···
On Tue, May 13, 2014 at 1:33 PM, Cory Zue wrote:
On Tue, May 13, 2014 at 1:05 PM, William Pride wpride@dimagi.com wrote:
Technically this would be trivial, the difficulty is in determining what
constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at
all, even if this was very approximate (the order of thousands of
meters). Meanwhile, if you wait for an exact location you might hang
forever. The solution we arrived at was to add an "acceptable" threshold
with distinct messaign in addition to the "exact" threshold that's seemed
to work well in general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective)
Or maybe we want to make the thresholds configurable via HQ?
This makes the most intuitive sense to me, since each project may have
different requirements about how precise they need that number to be.
Not sure this is the right forum to address these questions but I'm open
to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied it?
Based on how many votes it gets we will plan to put it on a future mobile
release.
Thanks,
Amelia
On Tue, May 13, 2014 at 1:33 PM, Cory Zue czue@dimagi.com wrote:
On Tue, May 13, 2014 at 1:05 PM, William Pride wpride@dimagi.com wrote:
Technically this would be trivial, the difficulty is in determining what
constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at
all, even if this was very approximate (the order of thousands of
meters). Meanwhile, if you wait for an exact location you might hang
forever. The solution we arrived at was to add an "acceptable" threshold
with distinct messaign in addition to the "exact" threshold that's seemed
to work well in general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective)
Or maybe we want to make the thresholds configurable via HQ?
This makes the most intuitive sense to me, since each project may have
different requirements about how precise they need that number to be.
Not sure this is the right forum to address these questions but I'm open
to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied
it?
which would evaluate that the accuracy was better than 100 meters, but this
would never allow the user to proceed if they couldn't acquire an accuracy
that was sufficient
-Clayton
···
On Wed, May 14, 2014 at 4:03 AM, Ameera Hamid wrote:
Thanks Amelia, will do so!
On Tue, May 13, 2014 at 8:44 PM, Amelia Sagoff asagoff@dimagi.com wrote:
Based on how many votes it gets we will plan to put it on a future mobile
release.
Thanks,
Amelia
On Tue, May 13, 2014 at 1:33 PM, Cory Zue czue@dimagi.com wrote:
On Tue, May 13, 2014 at 1:05 PM, William Pride wpride@dimagi.comwrote:
Technically this would be trivial, the difficulty is in determining
what constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at
all, even if this was very approximate (the order of thousands of
meters). Meanwhile, if you wait for an exact location you might hang
forever. The solution we arrived at was to add an "acceptable" threshold
with distinct messaign in addition to the "exact" threshold that's seemed
to work well in general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective)
Or maybe we want to make the thresholds configurable via HQ?
This makes the most intuitive sense to me, since each project may have
different requirements about how precise they need that number to be.
Not sure this is the right forum to address these questions but I'm
open to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied
it?
To clarify a bit because in retrospect this is a bit confusing:
In my workaround above: the constraint message there would show up after
the user has already confirmed to select Location Data. When they return to
the form with the "Capture Location" button, that screen would give them an
error that notifies them that their location is not accurate enough
(expressed through the validation condition message) and they would need to
click the button once again to try to receive a better location.
-Clayton
···
On Thu, May 15, 2014 at 12:32 PM, Clayton Sims wrote:
Ameera,
Until we've had a chance to update the UI:
The coordinates captured by CommCare are formatted as a space separated
list of values like
42.3331109 -71.0532241 0.0 769.0
The final value in that list should be the accuracy of the coordinate.
You could add a validation condition to the question reads the last item
and compares it to your minimum accuracy using the expression
which would evaluate that the accuracy was better than 100 meters, but
this would never allow the user to proceed if they couldn't acquire an
accuracy that was sufficient
Based on how many votes it gets we will plan to put it on a future
mobile release.
Thanks,
Amelia
On Tue, May 13, 2014 at 1:33 PM, Cory Zue czue@dimagi.com wrote:
On Tue, May 13, 2014 at 1:05 PM, William Pride wpride@dimagi.comwrote:
Technically this would be trivial, the difficulty is in determining
what constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at
all, even if this was very approximate (the order of thousands of
meters). Meanwhile, if you wait for an exact location you might hang
forever. The solution we arrived at was to add an "acceptable" threshold
with distinct messaign in addition to the "exact" threshold that's seemed
to work well in general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective)
Or maybe we want to make the thresholds configurable via HQ?
This makes the most intuitive sense to me, since each project may have
different requirements about how precise they need that number to be.
Not sure this is the right forum to address these questions but I'm
open to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in other
applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the GPS
question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied
it?
Thanks for the clarification. I will test it out in field and see how that
works with the project
Many thanks
Ameera
···
On 15 May 2014 9:58 PM, "Clayton Sims" wrote:
Ameera,
To clarify a bit because in retrospect this is a bit confusing:
In my workaround above: the constraint message there would show up after
the user has already confirmed to select Location Data. When they return to
the form with the "Capture Location" button, that screen would give them an
error that notifies them that their location is not accurate enough
(expressed through the validation condition message) and they would need to
click the button once again to try to receive a better location.
-Clayton
On Thu, May 15, 2014 at 12:32 PM, Clayton Sims csims@dimagi.com wrote:
Ameera,
Until we've had a chance to update the UI:
The coordinates captured by CommCare are formatted as a space separated
list of values like
42.3331109 -71.0532241 0.0 769.0
The final value in that list should be the accuracy of the coordinate.
You could add a validation condition to the question reads the last item
and compares it to your minimum accuracy using the expression
which would evaluate that the accuracy was better than 100 meters, but
this would never allow the user to proceed if they couldn't acquire an
accuracy that was sufficient
Based on how many votes it gets we will plan to put it on a future
mobile release.
Thanks,
Amelia
On Tue, May 13, 2014 at 1:33 PM, Cory Zue czue@dimagi.com wrote:
On Tue, May 13, 2014 at 1:05 PM, William Pride wpride@dimagi.comwrote:
Technically this would be trivial, the difficulty is in determining
what constitutes an "approximate" vs "exact" location. Before our last GPS
overhaul in 2.8 or so the main going concern was that question reported the
"Location Successfully Acquired" when you had any location read at
all, even if this was very approximate (the order of thousands of
meters). Meanwhile, if you wait for an exact location you might hang
forever. The solution we arrived at was to add an "acceptable" threshold
with distinct messaign in addition to the "exact" threshold that's seemed
to work well in general.
I suppose the question here is: do we want to dilute the value of
"acceptable" threshold by making it higher and including approximate
locations? Maybe we want to add a separate question type for approximate
locations instead of exact ones? (though again I think what constitutes an
approximate location is very subjective)
Or maybe we want to make the thresholds configurable via HQ?
This makes the most intuitive sense to me, since each project may have
different requirements about how precise they need that number to be.
Not sure this is the right forum to address these questions but I'm
open to hearing ideas and opinions
On Tue, May 13, 2014 at 12:30 PM, Cory Zue czue@dimagi.com wrote:
Are there any plans to support "approximate" capture in CommCare?
On Tue, May 13, 2014 at 10:21 AM, William Pride wpride@dimagi.comwrote:
Ameera,
Are the users able to precisely find their location via GPS in
other applications (like Whatsapp or Google Maps)? Its possible these
applications are only getting an approximate location via cellular
triangulation and CommCareODK will not "accept" these general locations. If
you determine that the device is able to get a precise GPS location in
other applications then please report a bug through the template
mentioned previouslyhttps://confluence.dimagi.com/display/commcarepublic/Bug+Reports?src=search and
someone on the mobile dev team will take a look.
I would just like to know from those of you who make use of the
GPS question in the form builder if you have also experienced problems with
finding a location when completing forms? My students are using the GPS to
verify their location at their clinical sites everyday on the commcare
logbook that i have created, however, many of them, despite having data and
turning the GPS on, have struggled to find locations. They are using the
Samsung Galaxy Tab 3 7" tablets. could it be a tablet problem? I
initially thought it could be a network problem (between vodacom, mtn and
cellc), however, all networks have experienced problems recording a
location using the commcare app. Surprisingly though, they are able to
send me their location on whatsapp without any hassles. I have looked at
the settings of the tablets to enable proper functioning of the GPS feature
in commcare and all the settings comply, so I am unable to figure out why
they are having troubling with this feature. This is a major concern as
this is an important component of the logbook for faculty members asnd has
also caused a low morale amongst students using the logbooks.
Has anyone experienced similar problems? and how have you remedied
it?