Similar to the POI view on our other UBIK^® clients, the Xamarin version displays Points of Interest (POIs) based on the current location of the mobile device. A typical POI view consists of a real time camera view and a number of floating POIs.

As a classic example of Augmented Reality, UBIK^® enhances the camera view with additional information about POIs. A POI is presented as a billboard which is sometimes also referred to as a bubble. By default, it visually contains some information about the object it represents. For example, the name, the description, and the status color.

We mention "by default" because the POIs can be customized to your liking.

There are several types of POIs.

Geo POI

For all objects carrying Geo coordinates, a POI is displayed at the respective coordinates.

The app calculates the object's position relative to the user's and shows a POI approximately where the user would see the actual object through the camera, taking the following into account:

• The closer/further an object is, the bigger/smaller the POI gets;
• Once too far away, the POI is not shown;
• Those that are behind/above/below the user/device are not shown.

The look and feel of these POIs can be customized in UBIKWorldViewItemArea.xamlx.

Optical marker POI

Some objects are associated with certain optical codes, e.g. QR codes. The app displays POIs for such objects whenever the corresponding optical markers are detected/scanned. The POIs are always positioned close to the markers.

Simple optical marker POI

Such optical codes include barcode, QR code and OCR text - OCR is short for "Optical Character Recognition", meaning the app's ability to recognize text in images - which then can be associated with UBIK^® objects and POIs automatically.

The UI of these POIs can be customized in UBIKDisplayViewItemArea.xamlx.

AR marker POI

Compared to other simple optical markers, AR (Aruco) marker POIs can make use of the additional information detected from the markers, namely the marker's relative distance and orientation to the device. Also, the placement of the POIs is more flexible and can be tailored. For details of such POIs, please refer to AR-Marker.

The UI of these POIs can be customized in UBIKCameraViewItemArea.xamlx.

In addition to the displayed information on POIs, you can also interact with them. A single tap on a POI selects or deselects it. Once a POI gets selected, several options become available on the right side of the POI view.

Buttons for Selected POIs

1. Open the selected POI group or building; (only visible if the selected POI represents such types)
2. Use the Geo location of the selected POI object; (also enters the respective POI group or building)
3. Browse to the selected POI object;
4. Show a route to the selected POI object. See screenshots below for examples.

• 

  Turn Around

• 

  Turn Left

Buttons for Entered Building

To make a large number of POIs appear more structured and not cluster the view too much, POI groups are introduced. POI groups aggregate the contained POIs and display only one POI as a substitute for all of them until the POI group is expanded ("entered"). A POI group can be entered so that only those POIs that belong to that group are displayed. The only exceptions are those that don't belong to any group, which are displayed all the time. A building is a special type of POI group which consists of several building levels. Each level itself behaves similar to a group in the sense that multiple POIs can belong to it and, therefore, are only displayed when the level is active. Once a POI group or a building is entered, some additional options become available on the left side of the POI view.

1. Displays the name and description of the entered group or building, click to exit;
2. A list of buttons, each representing a building level, click to switch to that level.

When you execute the NavigateToPOIPageCommand from a context object (e.g. ContentViewModel, ContentPageViewModel, ContentListItemViewModel, etc.), the POI view will be opened with that context object. This includes:

• Entering necessary POI groups, buildings or building levels so that the context object is visible (of course the camera still has to face the right direction);
• Taking the geo location of the context object as the current location;
• Selecting the POI for the context object automatically. (Once you start interacting with other POIs, the selected states will most likely change.)

Unlike executing the NavigateToPOIPageCommand from a place without a context object, doing so with one will additionally check the validity of that object, namely if it at least has geo information. If not, the command will be disabled.