Location Manager - Revision history

CWI at 12:12, 24 September 2025

2025-09-24T12:12:29Z

2025-09-23T13:54:09Z

2025-09-18T13:42:42Z

2025-09-18T10:18:30Z

2022-05-06T09:31:24Z

2022-05-06T08:27:12Z

‎WinX

2022-04-14T13:02:45Z

‎WinX

2022-04-13T12:59:51Z

‎Possible Positioning Modes

2017-09-19T13:43:36Z

‎Working Principle

2017-09-19T13:43:24Z

‎Best Practices

@@ Line 2: / Line 2: @@
 The Location Manager controls the different positioning services that are available for mobile devices.
-== PoseFusion ==
+== PoseFusion {{Version/MobileSince|5.1}} ==
 There is a toggle for using the Posefusion functionality.
-== Possible Positioning Modes ==
+== Possible Positioning Modes {{Version/MobileSince|5.1}} ==
 There are three different modes available for the Location Manager. The names and defined behaviors of the three modes are:
@@ Line 81: / Line 81: @@
 [[Category:Mobile|Location Manager]]
 [[Category:WinX|Location Manager]]

@@ Line 1: / Line 1: @@
-=Android=
+=UWP/WinX/Mobile=
 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:
@@ Line 50: / Line 71: @@
 In indoor environments and environments with strong magnetic fields the [[Compass]] and [[GPS]] Pose Estimation Systems should be deactivated. [[Routing-Graph Snapping]] should only be activated and configured where the user is in the proximity of the graph (e.g. on corridors).
@@ Line 82: / Line 81: @@
 [[Category:Mobile|Location Manager]]
 [[Category:WinX|Location Manager]]

@@ Line 53: / Line 53: @@
-=UWP/WinX/Xamarin=
+=UWP/WinX/Mobile=
 The Location Manager controls the different positioning services that are available for mobile devices.
@@ Line 80: / Line 80: @@
 [[Category:Android|Location Manager]]
 [[Category:Client|Location Manager]]
 [[Category:Mobile|Location Manager]]

← Older revision		Revision as of 10:18, 18 September 2025
Line 79:		Line 79:

	[[Category:Android\|Location Manager]]		[[Category:Android\|Location Manager]]
−	~~[[Category:WinX\|Location Manager]]~~
−	~~[[Category:Xamarin\|Location Manager]]~~
	[[Category:Client\|Location Manager]]		[[Category:Client\|Location Manager]]
		+	[[Category:WinX\|Location Manager]]
		+	[[Category:Mobile\|Location Manager]]

@@ Line 43: / Line 43: @@
 [[File:EKF.png|700 px|center|thumb|alt=Extended Kalman Filter|Extended Kalman Filter]]
-[[Category:Android|Location Manager]]
-[[Category:WinX|Location Manager]]
 == Best Practices ==
@@ Line 50: / Line 50: @@
 In indoor environments and environments with strong magnetic fields the [[Compass]] and [[GPS]] Pose Estimation Systems should be deactivated. [[Routing-Graph Snapping]] should only be activated and configured where the user is in the proximity of the graph (e.g. on corridors).
-[[Category:Android|Location Manager]]
-[[Category:WinX|Location Manager]]
 =UWP/WinX/Xamarin=
@@ Line 81: / Line 81: @@
 [[Category:WinX|Location Manager]]
 [[Category:Xamarin|Location Manager]]

@@ Line 57: / Line 57: @@
 == Possible Positioning Modes ==
-There are three different modes available for the Location Manager. The names and defined behaviors are:
+There are three different modes available for the Location Manager. Additionally there is a Toggle for using the Posefusion functionality.
 {| class="wikitable sortable"
@@ Line 69: / Line 70: @@
 | BEACON_PROXIMITY_MODE || class="centeredCell" | {{bullet_empty}} || class="centeredCell" | {{bullet_full}} || class="centeredCell" | {{bullet_full}}
 |}
 <headertabs/>

@@ Line 34: / Line 34: @@
 == Working Principle ==
-Internally the Location Managers uses an Extended Kalman Filter to combine and filter pose estimation systems, based on their probabilistic error levels. Each Pose Estimation System is therefore associated with a variance level (squared standard deviation), describing the expected uncertainty. Precise systems, such as [[AR-Markers]], are associated with a lower variance than inaccurate systems such as [[GPS]].
+Internally the Location Managers uses an Extended Kalman Filter to combine and filter pose estimation systems, based on their probabilistic error levels. Each Pose Estimation System is therefore associated with a variance level (squared standard deviation), describing the expected uncertainty. Precise systems, such as [[AR-Marker]], are associated with a lower variance than inaccurate systems such as [[GPS]].
 The Kalman Filter keeps track of the current device pose (= best estimate) and the associated uncerctainty. The operation is subdivided into two stages: Prediction and Correction.

@@ Line 47: / Line 47: @@
 == Best Practices ==
-[[AR-Marker]] and [[Gyroscope]] are the most precise pose estimation systems. Thus it is adviced to activate them in any case. Especially in the proximity of POIs [[AR-Markers]] should be deployed, to provide a good AR-experience. Furthermore it is recommended to activate the [[Step-Detector]] in scenarios, where the mobile device points into walking direction (i.e. the operator is not expected to walk sideward).
+[[AR-Marker]] and [[Gyroscope]] are the most precise pose estimation systems. Thus it is adviced to activate them in any case. Especially in the proximity of POIs [[AR-Marker]] should be deployed, to provide a good AR-experience. Furthermore it is recommended to activate the [[Step Detector]] in scenarios, where the mobile device points into walking direction (i.e. the operator is not expected to walk sideward).
-In indoor environments and environments with strong magnetic fields the [[Compass]] and [[GPS]] Pose Estimation Systems should be deactivated. [[Routing-graph]] snapping should only be activated and configured where the user is in the proximity of the graph (e.g. on corridors).
+In indoor environments and environments with strong magnetic fields the [[Compass]] and [[GPS]] Pose Estimation Systems should be deactivated. [[Routing-Graph Snapping]] should only be activated and configured where the user is in the proximity of the graph (e.g. on corridors).
 [[Category:Android|Location Manager]]