1) the gps in most phones is not precisely accurate, +/- 50 feet on average, perhaps as good as 5 feet on occasion.
2) phones do also use other information to determine location. It is not as accurate as the gps.
3) the gps receivers in phones are not very sensitive. They lose signals in buildings and are difficult in an urban environment. Buildings obscure their line of sight to the positional satellites.
4) not all phones have a gps. Those phones that do not have much reduced positional accuracy compared to those that have a gps.
4) there is an option in the location sensor to determine proximity to a destination. My experiments indicate it is not very accurate. +/- 50 feet reliable might be possible on a regular basis.
The following describes what the sensors in AI2 can (and cannot) do:
Sensor Controls Some of the functions they control are not available on all devices, so if a function does not seem to work, the Android version in use or the device might not have the capability.
Ten meter sampling of a location does not seem practical. A phone gps might only be able to resolve +/- 50 meters. See for your self, use the Location.Sensor.Accuracy block and sample it every minute and see what you get? Perhaps sample every 50 meters. .
Another issue is the frequency the gps will update the location. I think the default is 60 seconds; it can be reset, however, the simple gps receivers in phones take a bit to stabilize. There is no guarantee that after someone traverses 10 meters, the gps will update
Is this the type of info you are interested in?
Best of luck,
Steve