Unable to use VPS at my custom location – “Unavailable” in Geospatial Browser

Platform category:
Unity

Host machine & OS version:
Windows 10

ARDK version:
3.17

Description of the issue:
Hi Niantic Lightship Team,

I’m working on an AR project using Lightship ARDK in Unity, and I’m trying to use VPS at a location that shows as “Unavailable” in the Geospatial Browser.

My questions are:

  1. Is there any way for developers to scan a custom location and upload it to the Lightship VPS system, even if it currently shows as Unavailable?

  2. If direct uploading is not possible, do you have recommended alternatives for indoor or less-covered locations?

  3. Are there any best practices to make a location available for VPS testing in the future?

Any guidance would be greatly appreciated. Thank you for your support!

Hi Aya,

Could you share a link to the location that is showing up as unavailable? Or a screenshot of what you’re seeing on your end?

Hi Jesus,

Thanks for getting back to me.

I’ve attached a screenshot showing the location marked as Unavailable.
The place is a public road area directly in front of my office, and I’m trying to place AR content at a very specific real-world spot there.

My main question is:

  • If a location shows as Unavailable in the Geospatial Browser, is there any way for me to scan that area myself and upload it so it becomes usable for VPS / WPS?

  • Or is scanning and enabling coverage limited only to locations already supported by the Lightship system?

I’m trying to understand whether there’s a workflow that allows developers to contribute scans for currently unavailable areas, especially for precise outdoor placements.

What happens if you try pressing the Create Public Location option? The ‘address unavailable’ text likely just means that the system was not able to determine the address of the location but you should still be able to create a VPS location out of it.

Hi Aya,

Apologies for the delay. I noticed that you had replied but deleted the reply. Were you able to resolve the issue or is it still happening?