Restricting fake location application while collecting gps points with Collect android app

Features
#1

App versions:

ODK Collect v1.27.3 also KoBoCollect v1.27.3

Problem description:

Enumerators are able to use fake location application while collecting gps points with Collect android app.

Steps to reproduce the problem:

  • Enable the fake location app.
  • Collect gps data in Collect android app.
  • You are able to collect fake gps location.

Expected behavior

While collecting data with Collect android app would it be possible to disable the fake location app that generates fake location?

Other information:

For details, please have a look at the community forum for the detailed discussion:

#2

Hi @Lama
welcome to the forum! Please introduce yourself here!

While collecting data with Collect android app would it be possible to disable the fake location app that generates fake location?

It is doable. Location class we use provides isFromMockProvider() so we could easily check it and ignore such results.

Is that a real problem you faced?

1 Like
#3

Hi @Grzesiek2010,

Thank you for getting back on the query! Great to hear that it's doable. Yes its a problem faced by our users where the enumerators seems to manipulate location by installing Fake GPS applications in their Android phones.

Thank you!

#4

Ok so wee need to figure out how to handle that issue.
We can:

  1. Ignore locations that come from fake providers at all
  2. Add an option in admin settings that would disable it (enabled by default).
  3. Do that on a form level, adding an appearance for example.

Personally I would consider first two options. @LN @seadowg any thoughts?

2 Likes
#5

Yeah if isFromMockProvider() can indeed filter out results from the fake GPS apps I'd probably go for option 2. This would allow people to still use fake GPS apps for testing things out or development.

#6

Hi Everyone

is there any update on this ,How we can disable this fake location activity

#7

Hi @caneeraj
we haven't implemented any changes so far to address this issue. @LN we were talking about it during v1.29 planning have you maybe thought about this issue?