Migrating from VPS to VPS2

1. Geospatial Browser → Scaniverse Web

The Geospatial Browser (GSB) used to search for and active VPS locations is being shut down. Scaniverse Web should be used instead. See the From Setup to First Localization guide to be walked through how to create a Scaniverse Web account and manage your scanned locations.

If you have saved payloads from VPS locations found on the GSB, those can still be used for localization. However, the VPS Coverage API can still be used at runtime to query for VPS location and anchors near the user, but will be replaced by a new unified Sites API in the near future

2. VPS + WPS Sessions → VPS2 Session

All* the functionality from VPS and WPS (and more) is now accessible through the VPS2 APIs. See the VPS2 feature page to learn what VPS2 provides on top of VPS and WPS.

*The on-device mapping featureset from the original VPS is not yet available with VPS2, as of NSDK version 4.0 beta 1.

Anchor Management: The VPS2 functions and logic for creating, tracking, getting updates for, and removing anchors remains nearly identical with their VPS counterparts. VPS2 anchor updates have an additional "update type" field and surface (low-accuracy) poses even when not localized to a map. You can read more about in the guide for Placing Virtual Content with VPS2.

Getting Geolocation: The functions for converting a local AR pose into a geolocation in both VPS and WPS are replaced by using the VPS2 transformer. See Getting VPS2 Geolocation to learn more.