[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["The Streetscape Geometry APIs utilize Google Street View data to provide 3D geometry of terrain and buildings for use in AR experiences."],["Developers need to enable both the Geospatial API and Streetscape Geometry mode in their ARCore session configuration."],["`StreetscapeGeometry` objects contain mesh data, pose information, and quality level for representing the geometry."],["AR content can be attached to Streetscape Geometry using Geospatial Depth hit-tests or by creating anchors directly on the geometry."],["Geospatial Depth enhances depth data by combining Streetscape Geometry with sensor input, potentially improving pose accuracy."]]],["Geospatial Anchors place 3D content in the real world using latitude, longitude, and altitude. Types include WGS84, Terrain, and Rooftop anchors, each with specific altitude references and creation APIs. Anchors can be created using dedicated APIs or hit-tests. Latitude/longitude can be determined via Geospatial Creator, Google Maps, Google Earth, or a physical location. Terrain and Rooftop anchors are created asynchronously and are resolved to the terrain or building. WGS84 anchors have specific altitude determination methods. The rotation of the anchors is done with a quaternion.\n"]]