ARCore Geospatial API connects augmented reality to real-world locations

The API combines sensors, GPS and VPS to position content at an urban scale. Understand anchor types, coverage, accuracy, and privacy.

VPS fixes GPS ambiguity

Images and visual geometry help locate the device in relation to the environment. Accuracy still varies with coverage, light, visibility and movement.

Each anchor solves a problem

WGS84 uses absolute altitude; Terrain considers the soil; Rooftop positions in relation to the top of the building. The choice must follow the physical object and the acceptable margin of error.

Coverage must be tested before the campaign

A supported city does not mean uniform quality on every street. Remote verification and on-site testing avoid launching an experiment that fails right at the point of use.

Location and camera are sensitive data

Explain why they are needed, reduce retention, limit telemetry, and provide an alternative when the user does not grant access.

Nexus Reading

Geospatial AR creates a digital layer over public operations and spaces. Value depends on measured accuracy, useful content, and a fallback that preserves the task when tracking degrades.

FAQ

Does the API only work with GPS?

No. It combines GPS, sensors and VPS to estimate a geospatial pose.

Is any address covered?

No. VPS availability must be checked for project locations.

Which anchor to use on a building?

It depends on the case: Rooftop can serve the top, Terrain the ground and WGS84 at a defined altitude, always with local testing.

Essential guides to delve deeper into the decision