Today Dale and I took the Samsung out for a tour of Williamstown. The GPS tracking was quite smooth and we didn't encounter any problems.
We soon discovered that the order the questions had been provided in did not generate a circuit track but rather had us zig zagging back and forth between Williamstown and Newport.
We were sure to enable the tracking application before we left the office but discovered upon our return that when switching between the Mobile Geo location Application and the Google Maps application, the tracking data would stop being transmitted.
We have now been left to consider the best approach for mapping, the current options include an analogue paper based map, Google Maps/Latitude or an integrated map built into the application mitigating the need to minimise the browser.
We had the distinct pleasure of demoing the application to Howard from Flexible learning who was sporting a new Motorola Android device and a lovely red sweater. In configuring his device for the journey we learned that setting your default web browser to Opera can make using the application rather difficult as Opera takes over regardless of the web browser the address was entered from. Since the Opera browser lacks support for the JQuery Mobile framework we have utilised we were unable to use his device.
Below is a screenshot of the built in tracking which helps to illustrate our adventure. The Sony Xperia demonstrated a near perfect line tracing our journey from location to location. The Motorola running Opera traced a faint line outside our office before disappearing from the game altogether. The strangest of all was the line traced by the Samsung Galaxy which continuously defaulted to an obscure point in the distance every time it lost the satellite reception signal.
We also found once again that metal roofs interfere with the GPS signal, some phone faring better than others. The Samsung’s response can be seen above. This resulted in interesting jumps in suggested distance from the location as we drew closer. The Sony had a steady decline updating every few seconds, the Samsung lagging behind and surprising us with spikes of hundreds of meters.
We soon discovered that the order the questions had been provided in did not generate a circuit track but rather had us zig zagging back and forth between Williamstown and Newport.
We were sure to enable the tracking application before we left the office but discovered upon our return that when switching between the Mobile Geo location Application and the Google Maps application, the tracking data would stop being transmitted.
We have now been left to consider the best approach for mapping, the current options include an analogue paper based map, Google Maps/Latitude or an integrated map built into the application mitigating the need to minimise the browser.
We had the distinct pleasure of demoing the application to Howard from Flexible learning who was sporting a new Motorola Android device and a lovely red sweater. In configuring his device for the journey we learned that setting your default web browser to Opera can make using the application rather difficult as Opera takes over regardless of the web browser the address was entered from. Since the Opera browser lacks support for the JQuery Mobile framework we have utilised we were unable to use his device.
Below is a screenshot of the built in tracking which helps to illustrate our adventure. The Sony Xperia demonstrated a near perfect line tracing our journey from location to location. The Motorola running Opera traced a faint line outside our office before disappearing from the game altogether. The strangest of all was the line traced by the Samsung Galaxy which continuously defaulted to an obscure point in the distance every time it lost the satellite reception signal.
No comments:
Post a Comment