The Location sensor has a function called "DistanceInterval to" ...the units are in meters. Another feature is one called "TimeInterval" - it sets the frequency the gps triggers an event. These controls probably can help you do what you want to do.
You might be able to use the info at the link Taifun provided by recording the start location and comparing it with present location. The Google Maps and Static Maps API's can be your friend. The biggest issue is the ability of the gps in phones/tablets can provide the precision required.
However, consider:
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 can (and cannot) do:
Sensor Controls
Ten meter sampling of your 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 (yeah, a lot of paces). You might do better to count the number of paces a runner takes using the Orientation.Sensor. It too is not very precise. It might be possible to record the shock of a footstep, but I doubt it.
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. What it may have is the same reading it had when the runner was 10 meters earlier into the run; if you do a calculation, his speed would be zero. better to possibly compare start time/location with present time/location at say two minute intervals and compare the distance to go with the distance traversed. you would need to store the data in a TinyDB with AI.
You can also compare your present location with your actual location just using start and present location coordinates and using the Haversine algorithm. However, I suspect there is a math issue when using that algorithm using AI2 block for determining very small distance changes like you would calculate, that is meters vs. kilometers. (I am trying to confirm there errors because the algorithm calculates zero rather than a correct answer of 10's of meters), although the algorithm is perfectly ok for distances of a few miles or so (It is not accurate for longer distances ... like America to Europe for example ... Vincenty's Algorithm is the most accurate in that instance).
Is this the type of info you are interested in?
Best of luck,
Steve
Assigned to steve....@gmail.com by taifu...@gmail.com
Taifun. 