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
Are there plans to integrate RTK to Geospatial API?
At the moment, Geospatial API addresses most accuracy issues, provided Google has prior knowledge (through VPS) to said area.
However, if a project desires centimeters to millimeters accuracy, I believe an RTK fixed base station could be set up and use Geospatial API functionalities (such as adding geospatial anchors that subscribes to the RTK fixed base station instead) within areas where Google would have difficulties detecting via its VPS. Would this make sense to include RTK functionalities in the future? or will the workload required to make this outweigh the benefits?
I am open to alternative suggestions for ways to obtain accuracies in areas with not so good VPS coverage.
Much thanks in advance!
The text was updated successfully, but these errors were encountered:
We don't have any plans currently for adding that feature. If an area does not have VPS scanning the area for Cloud Anchors might be useful. ARCore's device pose accuracy may not be accurate enough to utilize higher accuracy external sensors.
Are there plans to integrate RTK to Geospatial API?
At the moment, Geospatial API addresses most accuracy issues, provided Google has prior knowledge (through VPS) to said area.
However, if a project desires centimeters to millimeters accuracy, I believe an RTK fixed base station could be set up and use Geospatial API functionalities (such as adding geospatial anchors that subscribes to the RTK fixed base station instead) within areas where Google would have difficulties detecting via its VPS. Would this make sense to include RTK functionalities in the future? or will the workload required to make this outweigh the benefits?
I am open to alternative suggestions for ways to obtain accuracies in areas with not so good VPS coverage.
Much thanks in advance!
The text was updated successfully, but these errors were encountered: