AreaTracker only supports AreaTarget trackables and it differs from the ObjectTracker because it can be used for indoor navigation and spatial awareness.
AreaTracker supports multiple active AreaTargets during runtime. You can load up to 255 AreaTargets in one session and activate them after each other. Consider that a very large space of maximum 1000m2 can consist of multiple smaller AreaTargets which have the benefit of freeing up memory as only one AreaTarget needs to be active at a certain position in the area. Then, a logic can be developed for switching between the targets.
NOTE: The DeviceTracker must be initialized and enabled before starting the AreaTracker.
NOTE: For both Native and Unity, ARKit or ARCore supported devices or a HoloLens headwear is required when deploying to a device.
NOTE: In order to cover a larger space with multiple Area Targets, you need to segment the regions already during scanning and create independent scans covering adjacent parts of the environment. The scans need to be converted individually to Area Targets. For a continuous experience and pose you will need to maintain an offset between parts on app level.
Multiple Target Types
Since AreaTarget is tracked and managed by the AreaTracker, it is necessary to involve the ObjectTracker for tracking other types of trackables in parallel to the AreaTarget. The use of multiple types is worth considering as it can be a source for aiding relocalization if the AreaTarget tracking becomes LIMITED. See the section below on Location Prior for more information. Another useful consideration is to combine Model Targets with Area Targets in situations where you want users to inspect objects up close.