Feature request:
As a developer integrating 3DTiles data into a three.js / A-Frame app using the A-Frame 3DTiles Component, I would like to be able to have a simple mechanism to specify a latitude, longitude, radius and of course, a Google Maps API key, to retrieve 3D Tiles in my A-Frame scene where 0 0 0 XYZ coordinates correspond to the specified lat / long and the 3dtiles scene bounds correspond to the radius value in meters.
For comparison, this is already possible via Cesium ION and this component for custom photogrammetry. As a user I can upload a GLTF/GLB of a custom generated photogrammetry scene, generate 3D Tiles via Cesium ION, localize the photogrammetry via Cesium ION UI (specifying a lat / long), and then fetch those tiles where XYZ coordinates 0 0 0 in the 3D scene is the Lat / Long as specified in Cesium UI. (There is no radius bound needed since that is effectively determined by the size of the photogrammetry GLTF/GLB provided.)
kfarr
commented
8 months ago
Google Maps introduced the ability for third-party applications to request 3D tiles, theoretically in the same compliant format as this component can parse. Their example uses Cesium JS but ideally this component could support loading 3dtiles as well: https://cloud.google.com/blog/products/maps-platform/create-immersive-3d-map-experiences-photorealistic-3d-tiles
Feature request: As a developer integrating 3DTiles data into a three.js / A-Frame app using the A-Frame 3DTiles Component, I would like to be able to have a simple mechanism to specify a latitude, longitude, radius and of course, a Google Maps API key, to retrieve 3D Tiles in my A-Frame scene where 0 0 0 XYZ coordinates correspond to the specified lat / long and the 3dtiles scene bounds correspond to the radius value in meters.
For comparison, this is already possible via Cesium ION and this component for custom photogrammetry. As a user I can upload a GLTF/GLB of a custom generated photogrammetry scene, generate 3D Tiles via Cesium ION, localize the photogrammetry via Cesium ION UI (specifying a lat / long), and then fetch those tiles where XYZ coordinates 0 0 0 in the 3D scene is the Lat / Long as specified in Cesium UI. (There is no radius bound needed since that is effectively determined by the size of the photogrammetry GLTF/GLB provided.)
I have filed a ticket with Google Maps team as well to see if they have recommended solution: https://issuetracker.google.com/issues/282768831