The 3D context is Google Photorealistic 3D Tiles — the same data as
Google Earth Pro. It needs a Google Maps Platform key with Map Tiles API enabled. Address search additionally needs
Maps JavaScript API and Geocoding API — both of them.
What this is costing
Google charges per root tileset request — one each time the 3D
context loads, covering up to three hours. Panning, zooming and the tiles themselves are
free and don't count. This counter is what this browser asked for; the billing
figure for everyone is in the Cloud console under Metrics.
Daily cap is already set to match Blink's Google project
(3D Tiles root requests per day = 200, down from Google's default of 10,000).
Only change it if that figure changes in the console.
The free allowance belongs to the Google project, not to you — five people
at 200 each have used it up, and none of them would see a number near 1,000. So the warning
measures against your share: the allowance divided by however many of you are testing.
An estimate, but it fires at roughly the right time instead of never.
The key is kept in this browser only (local storage) and never goes into a
project file. Without one the tool falls back to a flat OpenStreetMap globe, which is enough
to learn the controls but no use for judging a view.
