For the complete documentation index, see llms.txt. This page is also available as Markdown.

Version 2.3.3

Public share links, geo-fences and localization by coordinate, declared coordinate reference systems on E57, MapSets built from a shared survey frame, and the OSCP GeoPose Protocol.

v2.3.3 19-September-2026

Added

  1. USDZ mesh export. Every map now exports its mesh as a USDZ file that can be used directly in NVIDIA Isaac Sim and Omniverse.

  2. Share links. Publish a map or map set to a public URL that needs no MultiSet account. Choose whether the splat and the 360° tour are included, set an expiry or make it one-time, and revoke it at any moment. Sharing Maps

  3. Geo-fences. A geo-referenced map now covers a known real-world area, so a coordinate can be resolved to the map that contains it. Geo-fence

  4. Localize by coordinate. Pass geoLocation on the query instead of a mapCode and the nearest map in range is resolved and queried for you. Map Query

  5. Find maps near a point. GET /v1/vps/map/nearby ranks the candidates around a coordinate, grouped by what you would actually query, so a client can resolve once per session and cache it. Geo-fence

  6. Declare the coordinate reference system of an E57. Send source.metadata.crs with an EPSG code, or a 7-parameter Helmert transform for a private site grid that has no EPSG code. Coordinate Reference System

  7. OSCP GeoPose Protocol. POST /v1/vps/map/geopose speaks Open AR Cloud's protocol, so an OSCP client can localize against MultiSet maps without MultiSet-specific code. OSCP GeoPose Protocol

  8. Build a MapSet from a shared survey frame. POST /v1/vps/map-set/from-georeference places maps from the survey frame they were captured in instead of a visual overlap job, so sections of a site that never see each other can still be merged. Maps can be added to such a set later, and its origin corrected. Merging Maps by Georeference

  9. VPS-2 and depth on multi-image and equirect queries. queryMode=vps-2 now runs the deep-search engine on the multi-image query and on imageType=equirect panoramas, not only on single pinhole frames, and both accept depth from 1 to 5 to widen the search on large maps. Query Mode

  10. mobile provider. Create a zip map with source.provider set to mobile, alongside unity. Map Upload

  11. Change a map's thumbnail. Replace the image shown for a map with Change thumbnail on its detail page in the Developer Portal, or with PUT /v1/vps/map/{mapCode}/thumbnail. JPEG, PNG, and WebP images up to 5 MB are accepted. Maps Map Operations

Changed (iOS Native SDK)

  1. The xcframework no longer contains AR code. ARKit, RealityKit, SwiftUI and CoreLocation code now ships as source in MultiSetAR/, added to your app target. Replace the framework and the folder together and remove MultiSetSDK.MultiSetARView references. The API is unchanged. iOS Swift Native

  2. MultiSet and MultiSetCallback are @MainActor. Call them from the main thread and create your callback object there. MultiSetCallback

  3. poseConsistencyCheck defaults to false (it was on in 1.16.0), and poseConsistencyThreshold is now a flat 1 to 15 metre limit, so re-tune it. MultiSetConfig

Fixed

  1. The satellite viewer places scans at the correct height. Scans are now shown at their ellipsoidal height. Earlier versions used the MSL (geoid) height, which left scans offset vertically by the local geoid separation.

  2. The iOS SDK sends the correct GPS height with geoHint. It previously sent CLLocation.altitude (mean sea level) and now sends CLLocation.ellipsoidalAltitude, so the hint is no longer offset vertically by the local geoid separation. GeoHint in Localization

Last updated

Was this helpful?