AR-Marker - Revision history

CWI at 12:34, 24 September 2025

2025-09-24T12:34:57Z

CWI at 13:11, 22 September 2025

2025-09-22T13:11:26Z

CWI at 10:02, 18 September 2025

2025-09-18T10:02:02Z

LGE: /* Grouped AR Marker {{Version/WinXSince|3.8}}{{Version/XamarinSince|1.1| Version_1.1_Xamarin}} */

2021-01-26T08:40:15Z

‎Grouped AR Marker {{Version/WinXSince|3.8}}{{Version/XamarinSince|1.1| Version_1.1_Xamarin}}

LGE at 10:51, 22 June 2020

2020-06-22T10:51:24Z

LGE at 10:51, 22 June 2020

2020-06-22T10:51:08Z

LGE at 10:41, 22 June 2020

2020-06-22T10:41:16Z

LGE at 12:33, 12 April 2019

2019-04-12T12:33:25Z

CHI at 10:01, 29 October 2018

2018-10-29T10:01:18Z

JKN at 07:08, 17 September 2018

2018-09-17T07:08:23Z

@@ Line 38: / Line 38: @@
 ** Geo AR markers.
 {{Hint|POI groups can be switched manually, but also via e.g. QR marker scanning. In fact, one can scan a QR marker and an AR marker at the same time to switch to a certain group and then display the AR marker object within that group.}}
 [[Category:Android|AR-Marker]]
@@ Line 45: / Line 55: @@
 [[Category:Version 3.8|AR-Marker]]
 [[Category:WinX|AR-Marker]]

@@ Line 41: / Line 41: @@
 [[Category:Android|AR-Marker]]
 [[Category:Client|AR-Marker]]
 [[Category:Version 1.1|AR-Marker]]
 [[Category:Version 3.8|AR-Marker]]
 [[Category:WinX|AR-Marker]]
-[[Category:Mobile|AR-Marker]]
+[[Category:Version 5.1|AR-Marker]]

@@ Line 44: / Line 44: @@
 [[Category:Version 3.8|AR-Marker]]
 [[Category:WinX|AR-Marker]]
-[[Category:Xamarin|AR-Marker]]
+[[Category:Mobile|AR-Marker]]

@@ Line 29: / Line 29: @@
 If marked with the [[SYSCLS_ARMARKER_GEO]] classification, AR-Markers can be used for calculating the device pose once they are detected in the [[POI_View|POI View ]] (see [[AR-Marker_Device_Pose_Estimation|AR-Marker Device Pose Estimation]])
-== Grouped AR Marker {{Version/WinXSince|3.8}}{{Version/XamarinSince|1.1| [[Version_1.1_Xamarin]]}}==
+== Grouped AR Marker {{Version/WinXSince|3.8}}{{Version/XamarinSince|1.1}}==
 For scenarios where more than 1024 markers are needed, {{UBIK}} provides the possibility to group AR markers just like with Geo POIs. This means:
 * Depending on the currently opened POI group, a scanned AR marker might not be displayed (if it's doesn't belong to that group);
@@ Line 42: / Line 42: @@
 [[Category:Client|AR-Marker]]
 [[Category:Version 1.1|AR-Marker]]
 [[Category:WinX|AR-Marker]]
 [[Category:Xamarin|AR-Marker]]

@@ Line 39: / Line 39: @@
 {{Hint|POI groups can be switched manually, but also via e.g. QR marker scanning. In fact, one can scan a QR marker and an AR marker at the same time to switch to a certain group and then display the AR marker object within that group.}}
 [[Category:Android|AR-Marker]]
 [[Category:WinX|AR-Marker]]
 [[Category:Xamarin|AR-Marker]]
-[[Category:Version 1.1|AR-Marker]]
+[[Category:Version 3.8|AR-Marker]]

← Older revision		Revision as of 10:51, 22 June 2020
Line 38:		Line 38:
	** Geo AR markers.		** Geo AR markers.
	{{Hint\|POI groups can be switched manually, but also via e.g. QR marker scanning. In fact, one can scan a QR marker and an AR marker at the same time to switch to a certain group and then display the AR marker object within that group.}}		{{Hint\|POI groups can be switched manually, but also via e.g. QR marker scanning. In fact, one can scan a QR marker and an AR marker at the same time to switch to a certain group and then display the AR marker object within that group.}}
		+
		+	[[Category:Client\|AR-Marker]]
		+	[[Category:Android\|AR-Marker]]
		+	[[Category:WinX\|AR-Marker]]
		+	[[Category:Xamarin\|AR-Marker]]
		+	[[Category:Version 1.1\|AR-Marker]]

@@ Line 16: / Line 16: @@
 An additional [[SYSCLS_ARCONTENTREFERENCE]] {{Version/WinXSince|3.4.0}} can be used to specify an UBIK Object that should be rendered instead of the detected AR-Marker. This enables Multi AR-Marker Rendering whereby one an the same UBIK object can be rendered in relation to multiple AR-Markers.
 == Direct Augmentation ==
@@ Line 26: / Line 28: @@
 == AR-Marker Device Pose Estimation ==
 If marked with the [[SYSCLS_ARMARKER_GEO]] classification, AR-Markers can be used for calculating the device pose once they are detected in the [[POI_View|POI View ]] (see [[AR-Marker_Device_Pose_Estimation|AR-Marker Device Pose Estimation]])

@@ Line 7: / Line 7: @@
 == Marker Creation ==
-Currently {{UBIK}} is using the standard dictionary, allowing the creation of 1024 unique AR-Marker IDs. Markers can be created using the provided Aruco Marker Creation tool from the release portal [[https://80.243.175.50/Release/download/modules/Plugins/tools/ArucoMarkerGenerator.rar Aruco Marker Creation Tool]]. Once the tool is extracted, the ArucoMarkerGenerator.htm can be opened to configure the ID and side length. After clicking Generate Marker, the AR-Marker can be printed.
+Currently {{UBIK}} is using the standard dictionary, allowing the creation of 1024 unique AR-Marker IDs. Markers can be created using the provided Aruco Marker Creation tool from the release portal [https://release.augmensys.at/download/modules/Plugins/tools/ArucoMarkerGenerator.rar Aruco Marker Creation Tool]. Once the tool is extracted, the ArucoMarkerGenerator.htm can be opened to configure the ID and side length. After clicking Generate Marker, the AR-Marker can be printed.
 {{Hint|Note when printing AR-Markers the physical side length has to correlate with the AR-Marker side length property (see [[AR-Marker#Classifications|Classifications]]).}}

← Older revision		Revision as of 10:01, 29 October 2018
Line 15:		Line 15:
	The most important classification is the [[SYSCLS_ARMARKER]], containting the identifier and the AR-Marker side length. Two additional classifications [[SYSCLS_ARMARKER_DIRECTAR]] and [[SYSCLS_ARMARKER_GEO]] inherit from the above classiciation and are used to distinguish between the two use-cases of [[AR-Marker#Direct_Augmentation\|Direct Augmentation]] and [[AR-Marker#AR-Marker Device Pose Estimation\|Device Pose calculation]].		The most important classification is the [[SYSCLS_ARMARKER]], containting the identifier and the AR-Marker side length. Two additional classifications [[SYSCLS_ARMARKER_DIRECTAR]] and [[SYSCLS_ARMARKER_GEO]] inherit from the above classiciation and are used to distinguish between the two use-cases of [[AR-Marker#Direct_Augmentation\|Direct Augmentation]] and [[AR-Marker#AR-Marker Device Pose Estimation\|Device Pose calculation]].

		+	An additional [[SYSCLS_ARCONTENTREFERENCE]] {{Version/WinXSince\|3.4.0}} can be used to specify an UBIK Object that should be rendered instead of the detected AR-Marker. This enables Multi AR-Marker Rendering whereby one an the same UBIK object can be rendered in relation to multiple AR-Markers.

	== Direct Augmentation ==		== Direct Augmentation ==

@@ Line 1: / Line 1: @@
 [[File:ArucoMarker.PNG|250 px|right|thumb|alt=AR-Marker|AR-Marker]]
 AR-Markers are square fiducial markers composed by a wide black border and a inner binary matrix which determines its identifier (ID). These markers are detected in the camera stream of the [[POI_View|POI View]] and can be used for [[AR-Marker#Direct_Augmentation|Direct Augmentation]] or [[AR-Marker#AR-Marker Device Pose Estimation|Device Pose calculation]].
-The AR-Marker ID is defined as an integer value between zero and the maximum dictionary size (see [[AR-Marker#Marker Creation|Marker Creation]]). Once a marker is detected, the ID is used to gather additional information from the associated UBIK® object (see [[AR-Marker#Classifications|Classifications]]).
+The AR-Marker ID is defined as an integer value between zero and the maximum dictionary size (see [[AR-Marker#Marker Creation|Marker Creation]]). Once a marker is detected, the ID is used to gather additional information from the associated {{UBIK}} object (see [[AR-Marker#Classifications|Classifications]]).
 The four corner points of an AR-Marker are extracted to calculate the relative pose (position and orientation) between the camera and the AR-Marker, which serves as a basement for the above stated use-cases. For that, the camera of the mobile device has to be calibrated (see [[Camera_Calibration|Camera Calibration]]) and the AR-Marker side length has to be known.
@@ Line 7: / Line 7: @@
 == Marker Creation ==
-Currently UBIK® is using the standard dictionary, allowing the creation of 1024 unique AR-Marker IDs. Markers can be created using the provided Aruco Marker Creation tool from the release portal [[https://80.243.175.50/Release/download/modules/Plugins/tools/ArucoMarkerGenerator.rar Aruco Marker Creation Tool]]. Once the tool is extracted, the ArucoMarkerGenerator.htm can be opened to configure the ID and side length. After clicking Generate Marker, the AR-Marker can be printed.
+Currently {{UBIK}} is using the standard dictionary, allowing the creation of 1024 unique AR-Marker IDs. Markers can be created using the provided Aruco Marker Creation tool from the release portal [[https://80.243.175.50/Release/download/modules/Plugins/tools/ArucoMarkerGenerator.rar Aruco Marker Creation Tool]]. Once the tool is extracted, the ArucoMarkerGenerator.htm can be opened to configure the ID and side length. After clicking Generate Marker, the AR-Marker can be printed.
 {{Hint|Note when printing AR-Markers the physical side length has to correlate with the AR-Marker side length property (see [[AR-Marker#Classifications|Classifications]]).}}
@@ Line 17: / Line 17: @@
 == Direct Augmentation ==
-If marked with the [[SYSCLS_ARMARKER_DIRECTAR]] classification, AR-Markers can be directly augmented once they are detected in the [[POI_View|POI View ]]. Per default a Billboard, representing the classified UBIK® object, will be shown directly on the AR-Marker. Additional classifications ([[SYSCLS_ARCONTENTTRANSLATION]], [[SYSCLS_ARCONTENTROTATION]], [[SYSCLS_ARCONTENTSCALE]]) can be used to translate, rotate and scale the Billboard in relation to the detected AR-Marker. Furthermore it is possible to render multiple UBIK® objects in relation to the same physical AR-Marker.
+If marked with the [[SYSCLS_ARMARKER_DIRECTAR]] classification, AR-Markers can be directly augmented once they are detected in the [[POI_View|POI View ]]. Per default a Billboard, representing the classified {{UBIK}} object, will be shown directly on the AR-Marker. Additional classifications ([[SYSCLS_ARCONTENTTRANSLATION]], [[SYSCLS_ARCONTENTROTATION]], [[SYSCLS_ARCONTENTSCALE]]) can be used to translate, rotate and scale the Billboard in relation to the detected AR-Marker. Furthermore it is possible to render multiple {{UBIK}} objects in relation to the same physical AR-Marker.
 Depending on the computational capacities of a mobile device, AR-Markers can be directly augmented in realtime (25 Hz).