Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: EE 1.3.1.GA_P01
-
Component/s: Containers
-
Labels:None
-
Environment:ICEmobile
Description
1. a single approximate value when the page is loaded
2. a current more accurate value when the user interacts
3. a history of locations
4. periodic update of current location at the server
1. and 2. are currently supported with the mobi:geolocation component. 3. can be implemented as a background task with a batch upload of the geolocation history. 4. deviates from the web model since the periodic update may be expected to occur even if the web browser is not active on the device.
However, some users may regard 4. as a privacy violation and be willing to provide location updates only when the web application is visible. This could be implemented with a periodic submit and the current mobi:geolocation component.
To provide continuous background updates would be a container feature and require investigation on each mobile platform.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
An initial prototype of a location service that can be accessed over cloud push mechanism has been developed. We must investigate if iOS and BB devices can provide a similar service.
mobi-alert has been updated to accept location updates from ICEmobile-SX.
Initial support for geospy has been added to android support, and checked in at svn 38033.
It supports parameter strategy=significant|continuous|stop.
For android these translate to:
significant = low accuracy, continuous, delta t = 1min, delta d = 100m
continuous = high accuracy, continuous, delta t = 15sec, delta d = 25m
These settings are somewhat arbitrary and should be configurable from the application level.
geoSpy on iOS now supports properties and duration:
<a id="track" type="button" class="whiteButton bridgeItBtn" onclick="bridgeit.geoSpy('tracker','handleSpy', {postURL: window.serviceHub + '/geospy', parameters: {strategy:'significant',duration:1,_jguid:jguid}});">Start Tracking</a>
Property names starting with _ will be added to the geoJSON POST with the _ removed. duration is specified in floating point hours.
geoJSON properties is a useful feature since the location service will not make use of sessions (but the properties can include a user ID).
The current demo assigns a GUID (named jguid) in the browser and maintains it in local storage for persistence. The only requirement of the native implementation is to detect _property and set properties
in the JSON POST.
Android implementation of jguid and duration parameters complete. svn 38293.
With the continuous nature of geospy, it will typically outlive the dispatch cycle of BridgeIt. This adds complications if multiple applications are attempting to use the feature at the same time, and with different configuration. BridgeIt need to be able to service multiple independent web apps. The initial plan is to support independent geospy services keyed on upload URL.
svn 38542: Android geospy support now uses independent location listeners based on upload URL. This means a single BridgeIt instance can support multiple web applications in parallel.
This feature is now required by the mobi:geotrack component in ICEfaces so must be added to the Android implementation:
- Property names starting with _ will be added to the geoJSON POST with the _ removed.
Marking as resolved.
Consider for ICEmobile 1.3.