Hello,
I encountered an event where a 3D scan of a VPS in Niantic Wayfair Beta was successfully uploaded but was not reflected anywhere.
The case in which this event occurs is in a slightly dark environment after dark or at night. The scan takes about 1 minute. The scan itself completes successfully and the upload completes successfully. However, the number of times scanned is still not counting up when checked in Niantic Wayfair Beta.
Are there cases where a 3D scan is successfully uploaded but not registered as data as a result? If so, please tell us in what cases this occurs.
It is a situation where the upload is even successful, but in fact it is failing, but since we cannot detect that failure, we are unable to determine the cause and take countermeasures.
Much of Niantic is currently away on winter holiday break, so it may take some additional time to investigate this issue on your behalf. We will post additional information here as it becomes available. Thank you for your patience!
This may occur when uploading additional scans to a wayspot that has already been VPS-activated. At this time, we have to file a request to update the wayspot to include the additional scans. Has the wayspot this is occurring at already been activated? If so, we will need the name of the wayspot, its coordinates, the wayspot ID, and the email associated with your account – which can be sent via direct message if you prefer.
I am currently VPS activated, but when this event occurred, it occurred for both VPS activated and VPS unactivated. As stated in the first post, it occurred when scanning at night. When scanned during the day, i.e. on a sunny day, the data seemed to register correctly.
It is possible that scans for public wayspots can be rejected due to a variety of reasons, including insufficient lighting. Scans for public wayspots may also be rejected for other reasons such as poor scan quality, too much blur, or the scan featuring too much of the ground rather than the scan target. Please keep in mind that these limitations do not apply to private scans.
Additionally, you may also find that scans originating from a LIDAR-enabled device have a higher success rate in lower-light situations due to the increased tracking stability and device sensors.
You can read more tips for generating successful VPS scans in the Scanning Best Practices section of the Lightship documentation.
It is possible that scans for public wayspots can be rejected due to a variety of reasons, including insufficient lighting. Scans for public wayspots may also be rejected for other reasons such as poor scan quality, too much blur, or the scan featuring too much of the ground rather than the scan target. Please keep in mind that these limitations do not apply to private scans.
My hope is to have a system judge the quality at the completion of the scan.
I can uncover problems early and proceed to resolve them sooner.
As I have asked below, 110 scans were performed and only 36 were accepted. As a result, the quality was Low.
I am using an iPhone 12 Pro with LiDAR.
Let me ask an additional question.
For Wayspot that is determined to be Low, an additional scan is performed and uploaded. If I then request activation again, will the quality ever change from Low to Production?
Thank you for your feedback, @Sadao_Tokuyama! I’ve filed a feature request with the team on your behalf in regards to receiving immediate scan quality feedback.
To answer your question, it is possible that a wayspot’s localizability quality can change after reactivation with additional scans, but it’s not a guarantee. For example, it’s possible that older scans could be removed during this process if the subject target has sufficiently been altered between the time of the original scans and the time of the updated scans.