Stay organized with collectionsSave and categorize content based on your preferences.
Creates an ID that can be used to render "table" data.
This is used in conjunction withtables.getFeatures. A call totables.createprovides an expression and some output options. The result oftables.createis an ID that represents a table that is the result of evaluating that expression and applying those options. Subsequently, calls totables.getFeaturescan be made to get the table data for the entire resulting table. The ID will be valid for a moderate period (a few hours).
The most common use case for this pair of endpoints is to provide a complex expression via a POST totables.create, and then fetch the computed table via a GET totables.getFeatures. This two-part process allows for use in more situations thanComputeFeatures. In particular: - the result ofComputeFeaturesrequires pagination to get the entirety of the features. Additionally only individualFeatures are returned. -ComputeFeaturescan only be called by an authorized user, using a properly-scoped OAuth token.tables.createhas the same restriction, butGetTableDatacan be invoked with a URL containing an API key, so URLs invoking it can be used more broadly.
HTTP request
POST https://earthengine.googleapis.com/v1alpha/{parent=projects/*}/tables
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-06 UTC."],[[["\u003cp\u003e\u003ccode\u003etables.create\u003c/code\u003e generates a temporary ID representing a table derived from a provided expression and output options.\u003c/p\u003e\n"],["\u003cp\u003eThis ID can be used with \u003ccode\u003etables.getFeatures\u003c/code\u003e to retrieve the entire table data, enabling complex expressions and broader access compared to \u003ccode\u003eComputeFeatures\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves a POST request to \u003ccode\u003etables.create\u003c/code\u003e with the expression and a subsequent GET request to \u003ccode\u003etables.getFeatures\u003c/code\u003e using the generated ID.\u003c/p\u003e\n"],["\u003cp\u003eAuthorization is required for \u003ccode\u003etables.create\u003c/code\u003e but \u003ccode\u003etables.getFeatures\u003c/code\u003e can be accessed with an API key for wider usage.\u003c/p\u003e\n"],["\u003cp\u003eThis approach addresses limitations of \u003ccode\u003eComputeFeatures\u003c/code\u003e like pagination and restricted access.\u003c/p\u003e\n"]]],[],null,["# Method: projects.tables.create\n\nCreates an ID that can be used to render \"table\" data.\n\nThis is used in conjunction with `tables.getFeatures`. 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 `tables.getFeatures` 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 `tables.getFeatures`. 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/v1alpha/{parent=projects/*}/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/v1alpha/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/v1alpha/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)."]]
