Method: projects.locations.tables.create

Stay organized with collections Save and categorize content based on your preferences.

Creates an ID that can be used to render "table" data.

This 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).

The 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 table.computeFeatures. In particular: - the result of table.computeFeatures requires pagination to get the entirety of the features. Additionally only individual Features are returned. - table.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.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Required. The parent of the location where the table will be created (e.g., "projects/*").

Query parameters



User supplied tag to track this computation.

Request body

The request body contains an instance of Table.

Response body

If successful, the response body contains a newly created instance of Table.

Authorization Scopes

Requires one of the following OAuth scopes:


For more information, see the Authentication Overview.