公告：凡是在
2025 年 4 月 15 日前註冊使用 Earth Engine 的非商業專案，都必須
驗證非商業用途資格，才能繼續存取 Earth Engine。
Method: projects.locations.tables.create
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
建立可用於轉譯「table」資料的 ID。
此選項會與 GetTableFeatures 搭配使用。呼叫 tables.create 會提供運算式和一些輸出選項。tables.create 的結果是代表資料表的 ID，該資料表是評估該運算式並套用這些選項的結果。接著，您可以呼叫 GetTableFeatures，取得整個結果資料表的資料表資料。ID 的有效時間為數小時。
這組端點最常見的用途，是透過 POST 將複雜運算式提供給 tables.create，然後透過 GET 將計算表擷取至 GetTableFeatures。這個兩階段程序比 ComputeFeatures 更適合用於更多情況。具體來說：ComputeFeatures 的結果需要分頁才能取得完整的功能。此外，系統只會傳回個別的 Feature。- ComputeFeatures 只能由已授權的使用者使用適當範圍的 OAuth 權杖呼叫。tables.create 有相同的限制，但 GetTableData 可透過含有 API 金鑰的網址叫用，因此叫用它的網址可更廣泛地使用。
HTTP 要求
POST https://earthengine.googleapis.com/v1beta/{parent=projects/*/locations/*}/tables
這個網址使用 gRPC 轉碼語法。
路徑參數
| 參數 |
parent |
string
必要欄位。要建立資料表的位置的父項 (例如「projects/*」)。
|
查詢參數
| 參數 |
workloadTag |
string
使用者提供的用於追蹤這項運算的代碼。
|
回應主體
如果成功，回應主體會包含新建立的 Table 例項。
授權範圍
需要下列其中一種 OAuth 範圍：
https://www.googleapis.com/auth/earthengine
https://www.googleapis.com/auth/earthengine.readonly
https://www.googleapis.com/auth/cloud-platform
https://www.googleapis.com/auth/cloud-platform.read-only
詳情請參閱 OAuth 2.0 Overview。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eThe \u003ccode\u003etables.create\u003c/code\u003e endpoint generates a temporary ID representing a table derived from a provided expression and output options.\u003c/p\u003e\n"],["\u003cp\u003eThis ID can then be used with \u003ccode\u003eGetTableFeatures\u003c/code\u003e to retrieve the entire table data, enabling complex expressions and broader access via API keys.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003etables.create\u003c/code\u003e offers advantages over \u003ccode\u003eComputeFeatures\u003c/code\u003e by avoiding pagination for complete results and allowing data access with API keys in \u003ccode\u003eGetTableFeatures\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAuthorization is required for \u003ccode\u003etables.create\u003c/code\u003e, using OAuth scopes similar to \u003ccode\u003eComputeFeatures\u003c/code\u003e, but \u003ccode\u003eGetTableFeatures\u003c/code\u003e allows access via URLs containing API keys for wider usage.\u003c/p\u003e\n"]]],["`tables.create` generates an ID representing a table from an expression and output options. `GetTableFeatures` then retrieves the table data using this ID. This method is advantageous over `ComputeFeatures` because it allows full table retrieval without pagination and can be accessed via an API key. The process involves a POST request to `tables.create`, providing the expression. The ID is valid for a limited duration, and an authorized user or a public API key is needed to make calls to `GetTableFeatures`.\n"],null,["# Method: projects.locations.tables.create\n\nCreates an ID that can be used to render \"table\" data.\n\nThis is used in conjunction with `GetTableFeatures`. A call to `tables.create` provides an expression and some output options. The result of `tables.create` is an ID that represents a table that is the result of evaluating that expression and applying those options. Subsequently, calls to `GetTableFeatures` can be made to get the table data for the entire resulting table. The ID will be valid for a moderate period (a few hours).\n\nThe most common use case for this pair of endpoints is to provide a complex expression via a POST to `tables.create`, and then fetch the computed table via a GET to `GetTableFeatures`. This two-part process allows for use in more situations than `ComputeFeatures`. In particular: - the result of `ComputeFeatures` requires pagination to get the entirety of the features. Additionally only individual `Feature`s are returned. - `ComputeFeatures` can only be called by an authorized user, using a properly-scoped OAuth token. `tables.create` has the same restriction, but `GetTableData` can be invoked with a URL containing an API key, so URLs invoking it can be used more broadly.\n\n### HTTP request\n\n`POST https://earthengine.googleapis.com/v1beta/{parent=projects/*/locations/*}/tables`\n\nThe URL uses [gRPC Transcoding](https://google.aip.dev/127) syntax.\n\n### Path parameters\n\n| Parameters ||\n|----------|------------------------------------------------------------------------------------------------------|\n| `parent` | `string` Required. The parent of the location where the table will be created (e.g., \"projects/\\*\"). |\n\n### Query parameters\n\n| Parameters ||\n|---------------|-------------------------------------------------------|\n| `workloadTag` | `string` User supplied tag to track this computation. |\n\n### Request body\n\nThe request body contains an instance of [Table](/earth-engine/reference/rest/v1beta/projects.locations.tables#Table).\n\n### Response body\n\nIf successful, the response body contains a newly created instance of [Table](/earth-engine/reference/rest/v1beta/projects.locations.tables#Table).\n\n### Authorization scopes\n\nRequires one of the following OAuth scopes:\n\n- `https://www.googleapis.com/auth/earthengine`\n- `\n https://www.googleapis.com/auth/earthengine.readonly`\n- `\n https://www.googleapis.com/auth/cloud-platform`\n- `\n https://www.googleapis.com/auth/cloud-platform.read-only`\n\nFor more information, see the [OAuth 2.0 Overview](/identity/protocols/OAuth2)."]]
