You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating an app that has backup VPS systems in the case that an area lacks accurate Geospatial API coverage (inside buildings, private land, etc).
However during testing I have found that the Geospatial API will sometimes return horizontal accuracy of < 1.5 meters, even if I'm covering the camera with my hand or there is zero streetview coverage of an area. In these tests the coordinates returned by the Geospatial API are of course not accurate and are usually 5-10 meters off (usual GPS accuracy).
Is this a bug?
It would be nice if we could get an idea of if Geospatial is basing its position on streetview or only GPS.
The text was updated successfully, but these errors were encountered:
Hi @mechpil0t that does sound like a bug, the accuracy should not be so low without utilizing VPS localization. Could you share a video showing this behavior, using e.g. the sample app as it shows live altitude and heading accuracy readings.
I am creating an app that has backup VPS systems in the case that an area lacks accurate Geospatial API coverage (inside buildings, private land, etc).
However during testing I have found that the Geospatial API will sometimes return horizontal accuracy of < 1.5 meters, even if I'm covering the camera with my hand or there is zero streetview coverage of an area. In these tests the coordinates returned by the Geospatial API are of course not accurate and are usually 5-10 meters off (usual GPS accuracy).
Is this a bug?
It would be nice if we could get an idea of if Geospatial is basing its position on streetview or only GPS.
The text was updated successfully, but these errors were encountered: