Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Developer Wilayah Ekonomi Eropa (EEA)
Jika Anda tidak dapat menyertakan produk rendering pihak ketiga ke dalam solusi, Anda mungkin harus membuat perender Petak 3D sendiri. Pendekatan
ini mengharuskan Anda mempertimbangkan faktor-faktor penting berikut:
Saat menayangkan Petak 3D Fotorealistik, Map Tiles API menampilkan URI untuk
tileset turunan. URI tileset ini bukan URL biasa. URI ini hanya mencakup komponen jalur dan parameter. Header tersebut tidak berisi kunci API Anda, yang diperlukan untuk mengizinkan permintaan Anda. Untuk mengetahui informasi selengkapnya, lihat
Spesifikasi Petak 3D.
Permintaan dan respons
Berikut beberapa contoh permintaan dan respons Ubin 3D Fotorealistik. Anda dapat memeriksanya menggunakan Chrome Developer Tools.
Anda harus melampirkan parameter apa pun yang muncul di URI set petak, bersama dengan kunci API Anda, saat Anda membuat permintaan petak berikutnya. 3D Tiles API
menyediakan dua parameter berikut:
session
ID bawaan untuk sesi pemuatan 3D. ID ini dibuat secara otomatis
oleh API. Harus dilampirkan oleh perender saat membuat permintaan
petak berikutnya.
key
Kunci API yang Anda gunakan untuk mengakses layanan 3D Tiles. Anda harus melampirkannya ke
semua permintaan petak berikutnya.
Menampilkan atribusi
Atribusi berarti mengakui sumber petak peta dan merupakan persyaratan untuk
penggunaan API ini - hal ini mencakup atribusi merek Google (logo) serta
atribusi data. Logo Google tersedia untuk Anda di halaman
Kebijakan Map Tiles API. Informasi atribusi data ditampilkan di setiap respons kartu. Cari di
petak glTF, di bagian
asset, copyright.
{"asset":{"version":"2.0","generator":"draco_decoder","copyright":"Data SIO, NOAA, U.S. Navy, NGA, GEBCO;Landsat / Copernicus"}}
Anda harus menggabungkan, mengurutkan, dan menampilkan informasi ini dalam satu baris teks,
biasanya di bagian bawah rendering. Hal ini memerlukan langkah-langkah berikut:
Ekstrak semua informasi hak cipta dari semua kartu yang terlihat.
Pisahkan beberapa sumber hak cipta dengan titik koma.
Urutkan informasi berdasarkan jumlah kemunculan.
Tampilkan sumber hak cipta di layar, diurutkan dari yang paling sering muncul hingga yang paling jarang, mirip dengan cara Google Earth melakukannya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eWhen building your own renderer for Photorealistic 3D Tiles, you need to handle content URLs, requests, and responses, and display attributions correctly.\u003c/p\u003e\n"],["\u003cp\u003eContent URLs for tilesets returned by the API are relative and require your API key to be added for subsequent requests.\u003c/p\u003e\n"],["\u003cp\u003eRequests for tiles must include both your API key and a session parameter provided in the initial tileset response.\u003c/p\u003e\n"],["\u003cp\u003eData attribution information is included in each tile's \u003ccode\u003easset.copyright\u003c/code\u003e property within the glTF and must be aggregated, sorted, and displayed appropriately in your application.\u003c/p\u003e\n"],["\u003cp\u003eYou are required to display both the Google logo and aggregated data attributions, similar to how Google Earth displays them, for compliance with API usage policies.\u003c/p\u003e\n"]]],[],null,["# Work with your own 3D Tiles renderer\n\n**European Economic Area (EEA) developers** If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google\n| Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. [Learn more](/maps/comms/eea/faq). In addition, certain content from the Map Tiles API will no longer be returned. [Learn more](/maps/comms/eea/map-tiles).\n\nIf you're not able to incorporate a third-party rendering product into your\nsolution, then you might have to create your own 3D Tiles renderer. This\napproach requires that you consider the following important factors:\n\n- [Content URLs](#content_urls)\n- [Requests and responses](#requests-and-responses)\n- [Display data attributions](#display-attributions)\n\nContent URLs\n------------\n\nWhen serving Photorealistic 3D Tiles, the Map Tiles API returns URIs for\nchildren tilesets. These tileset URIs are not regular URLs. They include only\nthe path and parameters component. They don't contain your API key, which is\nrequired to authorize your request. For more information, see the\n[3D Tiles Specification](https://docs.opengeospatial.org/cs/18-053r2/18-053r2.html#23).\n\nRequests and responses\n----------------------\n\nHere are some examples of Photorealistic 3D Tiles requests and responses. You\ninspect them by using the Chrome Developer Tools.\n\nSample root tileset request: \n\n https://tile.googleapis.com/v1/3dtiles/root.json?key=YOUR_API_KEY\n\nSample tileset response URI: \n\n /v1/3dtiles/datasets/CgA/files/UlRPVEYuYnVs.json?session=CIqhrPOFvdHSYg\n\nSample tile request URLs used by renderers: \n\n https://tile.googleapis.com/v1/3dtiles/datasets/CgA/files/UlRPVEYuYnVs.json?session=CIqhrPOFvdHSYg&key=YOUR_API_KEY\n\n https://tile.googleapis.com/v1/3dtiles/datasets/CgA/files/UlRPVEYubm9k.glb?session=CIqhrPOFvdHSYg&key=YOUR_API_KEY\n\nYou should attach any parameters that appear in the tileset URI, together with\nyour API key, when you construct the subsequent tile requests. The 3D Tiles API\nprovides the following two parameters:\n\n`session`\n: A built-in identifier for a 3D loading session. It's automatically generated\n by the API. It must be attached by the renderer when constructing the subsequent\n tile requests.\n\n`key`\n: The API key that you used to access 3D Tiles service. You must attach it to\n all subsequent tile requests.\n\nDisplay attributions\n--------------------\n\nAttribution means acknowledging the source of map tiles and is a requirement for\nuse of this API - this includes the Google brand attribution (logo) as well as\ndata attribution. The Google logo is available to you on the\n[Map Tiles API Policies](/maps/documentation/tile/policies) page. Data\nattribution information is returned in every tile response. Look for it in the\n[glTF tile](https://github.com/KhronosGroup/glTF), under\n`asset`, `copyright`. \n\n {\n \"asset\": {\n \"version\": \"2.0\",\n \"generator\": \"draco_decoder\",\n \"copyright\": \"Data SIO, NOAA, U.S. Navy, NGA, GEBCO;Landsat / Copernicus\"\n }\n }\n\nYou must aggregate, sort, and display this information on a line of text,\nusually at the bottom of the rendering. This entails the following steps:\n\n1. Extract all of the copyright information from all of the tiles in view.\n\n2. Separate multiple copyright sources with a semicolon.\n\n3. Sort the information based on the number of occurrences.\n\n4. Display the copyright sources on-screen, ordered from most occurrences to the\n least, similar to the way\n [Google Earth](https://earth.google.com)\n does it."]]
