14.12.2014 Evaluation

[ppyordanov]

I just completed another evaluation session of the Android client and the server.

The evaluation lasted about 2 hours again, from just before 7 am to around 9 am in the morning to avoid stares from passers-by.

My aim today was to try and walk with relatively constant speed in the first half hour and then start to vary it in order to see how the data is being visualized on the server. The goal was to test how the newer (v6.1) version of the Android application with better geo-location accuracy and timely updates would behave.

Some observations that need to be documented:

• although the GPS sensor needs to be constantly on while tracking in order to improve accuracy, surprisingly, it does not noticeably affect battery life, at least in the short term (in my view, an hour of constant tracking should give an idea of power consumption). I can include some Android apps statistical data from my device. In conclusion, at most 5-10 % battery was consumed, considering I was constantly connected to the portable hotspot. In comparison, the previous configuration of the application (turning on the GPS sensor only every N seconds /where N is the size of the temporal window/) was not nearly as accurate, as can be seen on the screenshot below. The new routes (from this evaluation) are clearly very accurate (window used: 30 000 ms) compared to the ones from the last experiment:

• here is the route data list on the device; however, most of the routes are missing as I accidentally deleted them from the local device storage after uploading them to the server:

Route points (rough representation):

• walking along Great Western Road
• tracking from G. W. Road to Stevenson Gym
• walking from University Library to Boyd Orr
• Hillhead High School to Main Gate
• Main Gate to GUU
• GUU to G. W. R.
• Byres/ G. W. R. to Hetherington Building

Below are some photos I took to capture the whole data-generation process. I constantly monitored the data received from the device to verify that there is stable network access and data is being updated on regular time intervals. I also confirmed that each route gets aggregated on the server after tracking completion:

• Nexus 7 connection was active during the whole experiment duration
• Data updates were successfully transmitted:

• Probing information:

• Server data aggregation check:

• Final server desktop view:

After this evaluation there is enough information to serve as a base for further feature development.

Live changes can be checked on the website: http://ugmap.me/

[ppyordanov]

Here is how many data readings are in the database at this time (some data might have been lost when the map was reset):

[ppyordanov]

This task has been completed and can be closed now.