公告：所有在
2025 年 4 月 15 日之前注册使用 Earth Engine 的非商业项目都必须
验证是否符合非商业性质的资格条件，才能继续使用 Earth Engine。
Method: projects.locations.tables.create
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
创建一个可用于呈现“表格”数据的 ID。
此属性与 GetTableFeatures 结合使用。调用 tables.create 会提供一个表达式和一些输出选项。tables.create 的结果是一个 ID，表示表格，该表格是评估该表达式并应用这些选项的结果。随后，可以调用 GetTableFeatures 来获取整个生成表的表数据。该 ID 的有效期为中等时间（几小时）。
这对端点的最常见用例是通过 POST 向 tables.create 提供复杂表达式，然后通过 GET 向 GetTableFeatures 提取计算表。与 ComputeFeatures 相比，这种两步流程可在更多情况下使用。具体而言：- ComputeFeatures 的结果需要分页才能获取所有地图项。此外，系统只会返回单个 Feature。- ComputeFeatures 只能由已获授权的用户使用适当范围的 OAuth 令牌调用。tables.create 也存在相同的限制，但可以使用包含 API 密钥的网址调用 GetTableData，因此调用它的网址可以更广泛地使用。
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。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：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)."]]
