Figure 8.4 - Remote recognition, recognition and composition
According to the MAR component classification scheme in Clause 7, this system class has the following characteristics:
Pure sensors – visual
Real world capturer – visual, 2D video
Recognizer – image patch, recognition event, remote
Tracker – image patch , spatial event, remote
Space mapper - spatial
Event mapper - visual
Execution engine – remote, 2D + t
Renderer - visual
Visual display – 2D mono
8.2 MAR Class G: Points of Interest (POI)—GNSS-based Systems
8.2.1 Content-embedded POIs
MAR Execution Engine is used by the end-user to open a MAR file containing (locally in the scene) POIs from a specific region. The POIs are filtered with respect to user preferences as follows: Either the engine has access to a local resource (file) containing predefined POI-related user preferences or the engine exposes an interface allowing users to choose (on the fly) their preferences. The POIs corresponding to the user selections/preferences are displayed. The MAR content also describes how the POIs are displayed, either on the map or in AR view, by creating “Map Marker” instances and using the metadata provided by the POIs. The content specified in the Information viewpoint is:
POI data.
The Map Marker shape (representation) referenced by the MAR Execution Engine.
User preferences (optional).
Figure 8.5 - Content-embedded POI
According to the MAR component classification scheme in Clause 7, this system class has the following characteristics:
Pure sensors – GNSS
Real world capturer – visual, 2D video
Recognizer – location, recognition event, local
Tracker – earth reference , spatial event, local
Space mapper - spatial
Event mapper - location
Execution engine – local, 2D + t
Renderer - visual
Visual display – 2D mono
Aural display - mono
8.2.2 Server-available POIs
A MAR Execution Engine is used by the end-user to open an MAR file. One or multiple URLs to POI providers are specified in the MAR content. The POIs are filtered with respect to user preferences as follows: Either the engine has access to a local resource (file) containing predefined POI-related user preferences or the engine exposes an interface allowing users to choose (on the fly) their preferences. The POIs corresponding to user selections/preferences are requested from the specified URLs and displayed. The MAR content describes how POIs are displayed, either on the map or in AR view, by creating MapMarker instances and using the metadata provided by the POIs. The content specified in the Information viewpoint is:
URLs of the POI providers.
The MapMarker shape/representation.
In addition, a communication protocol should be established between the MAR Execution Engine and the POI Provider.
Share with your friends: |
