Workflow and Limitations
A quick look at our SDK.
The process to enable persistent AR in a space can be divided into two main parts.
- Mapping a location.
- Finding the device position and orientation (localizing) within the location using the constructed map.
Our SDK provides functions for both mapping and localizing.
When mapping a space with our SDK, the images are sent to our servers for map construction.
After construction, the map can be downloaded from our servers. You can either download and embed the map into your app for full offline use or download the maps at runtime.
Localization can be done on device or on our servers depending on your needs.
When mapping with the Immersal Mapper app, images are temporarily stored on the device and queued for uploading to the Cloud Service. The
In Queuevalue in the workspace info panel tells you how many images are stored on the device, waiting to be uploaded.
After images are uploaded to the Cloud Service, they are stored in what we call a workspace. The workspace is a container for all the input data the maps are constructed from. The
Uploaded Imagesvalue in the workspace info panel tells you how many images have been uploaded and stored in the workspace.
After you have captured the necessary images, you then submit the workspace content for map construction. At this point, the data is copied and a new map construction job is created. You can then see the map construction job appear on the map list in the Immersal Mapper app or the Developer Portal. When the map construction job has been created, you can safely delete the images from the workspace and start mapping a new location.
You can restore data from existing map construction jobs to the workspace. This is useful when you want to update or expand existing maps.
The Mapping App also includes a mode to test and visualize constructed maps.
Screenshot of the Mapping App's Visualize mode. The blue dots are the point cloud preview of the map.