2 ms·

Cool idea, can only use 2D at the moment. Looks like the 3D tile quota is exhausted: "message": "Quota exceeded for quota metric '3D Tiles root requests' and li

Cool idea, can only use 2D at the moment. Looks like the 3D tile quota is exhausted: "message": "Quota exceeded for quota metric '3D Tiles root requests' and limit '3D Tiles root requests per day' of service 'tile.googleapis.com' for consumer 'project_number:1016378558728'." https://tile.googleapis.com/v1/3dtiles/root.json?key=AIzaSyBdLna6MLOzCVRmK6qxm0-1u2GGUVhYdto https://tile.googleapis.com/v1/3dtiles/root.json?key=AIzaSyB...

lukehollis 1y ago
Asking for a quota increase with support! Will build in bring-your-own-key
- mkbehbehani 1y ago
  Random thing worth I ran into once, you may have already handled this but sharing just in case: May want to confirm the map renderer is making its requests using the URL with both the session and API key instead of only the API key. If your API requests are base key only, every refresh client-side might be unexpectedly consuming one of your root quota units, rather than each user getting a session of unlimited tile loads for 3 hours. If you're seeing network traffic in the console from your renderer out to the API without the session token in the query string along with the API token, or if you see the session token is totally different after refreshing, that might be a sign of something wonky causing quota depletion. Example URL for a tile fetch with both params: https://tile.googleapis.com/v1/3dtiles/datasets/CgA/files/UlRPVEYuYnVs.json?session=SESSION_TOKEN&key=YOUR_API_KEY Examples: https://developers.google.com/maps/documentation/tile/create-renderer#requests-and-responses A quick check would be to see how far apart your google analytics for unique users are vs. your API console usage data. If way less than 10,000 unique users depleted the 10,000 unit quota it may be another indicator of something in token/session setup.
- lukehollis 1y ago
  Okay back online in 3d too!

lukehollis 1y ago

Asking for a quota increase with support! Will build in bring-your-own-key

mkbehbehani 1y ago
Random thing worth I ran into once, you may have already handled this but sharing just in case: May want to confirm the map renderer is making its requests using the URL with both the session and API key instead of only the API key. If your API requests are base key only, every refresh client-side might be unexpectedly consuming one of your root quota units, rather than each user getting a session of unlimited tile loads for 3 hours. If you're seeing network traffic in the console from your renderer out to the API without the session token in the query string along with the API token, or if you see the session token is totally different after refreshing, that might be a sign of something wonky causing quota depletion. Example URL for a tile fetch with both params: https://tile.googleapis.com/v1/3dtiles/datasets/CgA/files/UlRPVEYuYnVs.json?session=SESSION_TOKEN&key=YOUR_API_KEY Examples: https://developers.google.com/maps/documentation/tile/create-renderer#requests-and-responses A quick check would be to see how far apart your google analytics for unique users are vs. your API console usage data. If way less than 10,000 unique users depleted the 10,000 unit quota it may be another indicator of something in token/session setup.
lukehollis 1y ago
Okay back online in 3d too!