Difference between revisions of "Location Manager"
(→Android) |
|||
| Line 1: | Line 1: | ||
=Android= | =Android= | ||
| − | The Location Manager aims to calculate the device pose (position and orientation) as accurate as possible using various input sources. The performance of pose | + | The Location Manager aims to calculate the device pose (position and orientation) as accurate as possible using various input sources. The performance of pose estimation can be characterised by the following measures: |
• Accuracy --> describes the average offset between real and estimated device pose | • Accuracy --> describes the average offset between real and estimated device pose | ||
| Line 27: | Line 27: | ||
| Routing-Graph Snapping || Position || none | | Routing-Graph Snapping || Position || none | ||
|} | |} | ||
| + | |||
| + | Besides the stated systems, the user can utilize the position of GEO-Objects by clicking the {{key press|Use Location}} button in the [[UBIK Client Basics#Context Menu|Context Menu]]. Pose estimation is started once the device pose is requested by another part of the application (e.g. [[POI_View|POI View]], [[Map_View|Map View]], [[UBIK_Client_Basics#Content Browser|Content Browser]]). If the specific device does not possess the required sensor technology of an active pose estimation system, a notification is shown. | ||
| + | |||
| + | [[Category:Android|Location Manager]] | ||
| + | [[Category:WinX|Location Manager]] | ||
=WinX= | =WinX= | ||
Revision as of 11:29, 19 September 2017
Android
The Location Manager aims to calculate the device pose (position and orientation) as accurate as possible using various input sources. The performance of pose estimation can be characterised by the following measures:
• Accuracy --> describes the average offset between real and estimated device pose
• Standard Deviation --> describes to which extend the estimated pose “jumps” around the real device pose
• Update Rate --> describes how often the device pose can be updated.
To maximise the performance, the Location Manager combines and filters estimated poses from various Pose Estimation Systems based on their estimated error levels. Pose Estimation systems can be activated and deactivated using the Pose Estimation Systems Setting. Currently the following pose estimation systems are available:
| Name | Estimated Quantity | Required Sensor Technology! |
|---|---|---|
| AR-Marker | Position and Orientation | Camera |
| Beacon Proximity | Position | Bluetooth Low Energy (Blue-tooth 4.0) |
| Compass | Orientation | Accelerometer and Magne-tometer |
| GPS | Position | GPS Sensor |
| Object Proximity | Position | none |
| Step Detector | Position | Step Detector Sensor |
| Routing-Graph Snapping | Position | none |
Besides the stated systems, the user can utilize the position of GEO-Objects by clicking the Use Location button in the Context Menu. Pose estimation is started once the device pose is requested by another part of the application (e.g. POI View, Map View, Content Browser). If the specific device does not possess the required sensor technology of an active pose estimation system, a notification is shown.
WinX
The Location Manager controlls the different positioning services that are available for mobile devices.
Possible Positioning Modes
There are three different modes available for the Location Manager. The names and defined behaviors are:
| Mode | GPS | LLA | iBeacon Proximity |
|---|---|---|---|
| USE_ALL |  |
|
|
| LLA_ONLY_MODE | |
|
|
| BEACON_PROXIMITY_MODE | |
|
|
