Spatial Constructors

Components that given the specifications in the input generate new sets of spatial data; those being points, line, polygons and even tilesets.

BBOX from Values

Description

This component creates a new table containing a 'geom' column and a single row containing a geography that represents a bounding box as defined by the input min/max values.

Inputs

• Minimum X [Number]

• Minimum Y [Number]

• Maximum X [Number]

• Maximum Y [Number]

Outputs

• Result table [Table]

BigQuery reference

Clip with Polygons

Description

This component creates a new table containing the geographies of the input table clipped to the combined boundary of the geographies in another table. Geographies in this second table must be of type polygon.

Inputs

• Table to clip [Table]

• Polygons table [Table]

• Geo column in table to clip [Column]

• Geo column in polygons table [Column]

Outputs

• Result table [Table]

Create Grid

Description

This component creates a new table containing points distributed in a regular grid, according to a given interval. Point geographies are stored in a column named 'geo'. The extent to cover is defined by an ancillary table with geographies.

Inputs

• Reference table (used for extent) [Table]

• Geo column [Column]

• Interval (degrees) [Number]

Outputs

• Result table [Table]

Create Isolines

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component computes isolines.

Inputs

• Source table

Settings

• Geo column: select a column that contains points that will be the origin point of the isoline.

• Mode: Select a mode of transport for the isoline calculation.

• Type of range: Select between time or distance for the isoline calculation.

• Range value (seconds/meters): Input a numeric value that represent seconds if time was selected or meters if distance was selected.

Provider-specific settings:

CARTO makes use of different isoline providers. The default one is TravelTime, but TomTom and HERE are also available. Please contact the team at [email protected] for more information.

TravelTime:

• Departure time: Take into account historical traffic conditions to generate the isoline. Accepted values are now or a timestamp in this format: YYYY-MM-DDThh:mm:ss, for example: 2024-01-31T09:30:00

• Single shape (default true): Force the resulting isoline to be a single polygon.

TomTom

• Departure time: Accepted values are any, now or a timestamp in this format: YYYY-MM-DDThh:mm:ss, for example: 2024-01-31T09:30:00

• Use traffic information if available: Check this option to take into account historical traffic conditions to generate the isoline.

HERE

• Arrival Time: any, now or timestamp (YYYY-MM-DDThh:mm:ss). Not compatible with Departure Time

• Departure Time: any, now or timestamp (YYYY-MM-DDThh:mm:ss). Not compatible with Arrival time

• Optimize for: balanced (default), quality, performance.

• Routing mode: fast (default), short

• Origin radius (m): Consider any position in the radius of the origin point as origin.

Advanced Options:

• Isoline Options: A JSON object that can contain other provider specific options, for example: {"option1":"value", "option2": 123}. Check each provider documentation for a complete reference of available options in the External links section below.

Outputs

• Result table: The component generates a table that contains the following columns:

  • All columns from input table.

  • An orig_geom column that contains the original point geometry in the selected geo column.

  • A geom column that contains the generated isoline.

  • A carto_isoline_metadata column that can contain additional information. Usually details if the isoline failed for some reason. In most scenarios it will be null if the isoline was generated correctly.

External links

• TravelTime API reference

• HERE API reference

• TomTom API reference

Create H3 Isolines

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

This component requires the TravelTime LDS provider. If your organization uses a different isolines provider, the component will raise an error.

Description

This component computes H3 isolines (isochrones represented as H3 cells) from given origin points. Unlike the standard Create Isolines component which returns polygon geometries, this component returns H3 cells with travel time information for each cell, enabling more efficient spatial analysis and aggregation operations.

Inputs

• Source table

Settings

• Geo column: select a column that contains points that will be the origin point of the H3 isoline.

• Mode: Select a mode of transport for the H3 isoline calculation. Available modes for TravelTime: walk, car, bike, public_transport, coach, bus, train, ferry.

• Type of range: Currently only time is supported for H3 isolines.

• Range value (seconds): Input a numeric value in seconds. Valid range: 60-14400 (1 minute to 4 hours).

• H3 Resolution: Select the H3 resolution level for the output cells. Valid range: 1-8. Lower values produce larger cells covering more area, while higher values produce smaller, more detailed cells.

TravelTime-specific settings:

• Departure time: Take into account historical traffic conditions to generate the H3 isoline. Accepted values are now or a timestamp in this format: YYYY-MM-DDThh:mm:ssZ, for example: 2024-01-31T09:30:00Z

Advanced Options:

• H3 Isoline Options: A JSON object that can contain other TravelTime-specific options. Check the TravelTime documentation for available options. Check the External links section below to understand better the advanced options.

Outputs

• Result table: The component generates a table that contains the following columns:

  • All columns from input table (except the original geo column).

  • An h3 column that contains the H3 cell index.

  • An h3_min column with the minimum travel time in seconds to reach this H3 cell.

  • An h3_max column with the maximum travel time in seconds to reach this H3 cell.

  • An h3_mean column with the average travel time in seconds to reach this H3 cell.

  • A carto_isoline_metadata column that can contain additional information. Usually details if the isoline failed for some reason. In most scenarios it will be null if the H3 isoline was generated correctly.

External links

• TravelTime H3 API reference

• BigQuery reference

• Snowflake reference

• Redshift reference

• Databricks reference

Create Routes

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component creates routes between origin and destination points stored in a table.

Inputs

• Source table [Table]

Settings

• Origin column [Column]

• Destination column [Column]

• Name for column with routes [String]

• Mode [Selection]

Outputs

• Result table [Table]

External links

BigQuery reference

Create Routing Matrix

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component computes the routing matrix between a set of origins and destinations and return their distances and duration until arrival.

Inputs

• Origin table: A table that contains points with the origin points for the routes.

• Destination table: A table that contains points with the destination points for the routes.

Settings

• Type of transport: Select the type of transport for the route computation. The available options will depend on the provider. See the 'External links' reference for a full description of the options.

• Departure time: (Optional) Set the departure time for the route computation. Date-time as "<YYYY-MM-DD>T<hh:mm:ss>" . Default is "now" or "any" if your provider is TomTom.

• Travel time: (Not available with TomTom) The maximum time allowed for the route calculation. If a set of origin/destination produces a route that is longer that this setting (in seconds) it won't be computed.

• Advanced settings: a free-text input that supports a JSON formatted string with advanced options. See 'External links' section below for a list of additional options supported on each provider.

Advanced settings is preset with carto_origins_batch_size and carto_destinations_batch_size configurations. Together they define the size of the batches that will be made to optimize calls to the external provider. You can configure these settings to adapt to the shape of your matrix. For example, rectangular (fewer origins than destinations) or square (same number of origins and destinations) matrices. Please refer to the 'External links' section below for more details. NOTE: The product of both origins and destinations batch sizes can't be greater than 10000.

Outputs

• Result table: This component generates a table that is the cartesian product of both input tables with additional columns for the route computation.

External links

• BigQuery

• Snowflake

• Redshift

Create Tileset

On July, 17th 2024 this component was deprecated in favor of the components in the Tileset Creation category.

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component creates a tileset.

Inputs

• Source table [Table]

• Geo column [Column]

• Tileset name [String]

• Tileset description [String]

• Minimum zoom [Number]

• Maximum zoom [Number]

• Minimum zoom column [Column]

• Maximum zoom column [Column]

• Maximum tile size (KB) [Number]

• Tile feature order [String]

• Drop duplicates [Boolean]

Outputs

External links

BigQuery reference

Point from Static LatLon

Description

This component creates a new table containing a single row with a single point geography. The point is stored in a column named 'geo'.

Inputs

• Longitude [Number]

• Latitude [Number]

Outputs

• Result table [Table]

Remove Holes

Description

This component generates a new geo column with polygons without holes.

Inputs

• Source polygons table [Table]

• Geo column [Column]

Outputs

• Result table [Table]

Spatial Process

Description

This component performs high-level spatial object editing from a simple, single component. You can combine multiple objects or cut the spatial objects of the input table.

With this component you can combine objects, cut 1st from 2nd, cut 2nd from 1st, create the intersection object or create the inverse intersection object. Define the action that you want to do using the “Action” field.

Inputs

• source table [Table]

• 1st Spatial Field [Column]

• 2nd Spatial Field [Column]

• Action [Selection]

Outputs

• Result table [Table]

ST Boundary

Description

This component adds a new column with the boundary of the input geography.

Inputs

• Source table [Table]

• Geo column [Column]

Outputs

• Result table [Table]:

External links

BigQuery reference

Redshift reference

ST Bounding Box

Description

This component creates a new column containing rectangles that represents the bounding box of each geometry.

Inputs

• Source table [Table]

• Geo column [Column]

Outputs

• Result table [Table]

External links

BigQuery reference

Snowflake reference

Redshift reference

PostgreSQL reference

ST Extent

Description

This component creates a new table containing a 'geom' column and a single row containing a geography that represents the bounding box of the input table.

Inputs

• Source table [Table]

• Geo column [Column]

Outputs

• Result table [Table]

External links

BigQuery reference

ST Generate Points

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component generates a table with a specified number of random points within a extent.

The extent is specified using a table with polygons.

Inputs

• Source table [Table]

• Geo column [Column]

• Number of points [Number]

Outputs

• Result table [Table]

External links

BigQuery reference

ST Geocode

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component geocodes an input table.

It generates a new table with an additional column named 'geo' containing the geocoded addresses.

Inputs

• Source table [Table]

• Column with addresses [Column]

• Country [Selection]

Outputs

• Table with geocoded rows [Table]

• Table with rows that could not be geocoded [Table]

External links

BigQuery reference

ST Make Line

Description

This component creates a new table with an additional column with line geographies. Geographies are created based on another column containing arrays of points.

Inputs

• Source table [Table]

• Points column [Column]

Outputs

• Result table [Table]

External links

BigQuery reference

PostgreSQL reference

ST Make Polygon

Description

This component creates a new table with an additional column with polygon geographies. Geographies are created based on another column containing polylines.

Inputs

• Source table [Table]

• Polylines column [Column]

Outputs

• Result table [Table]

External links

BigQuery reference

Snowflake reference

Redshift reference

PostgreSQL reference

ST Polygonize

This component requires the CARTO Analytics Toolbox installed in the chosen connection to build the workflow.

Description

This component adds a new column with polygons, created from a column containing arrays of lines representing polygon edges.

Inputs

• Source table [Table]

• Geo column [Column]

Outputs

• Result table [Table]

External links

BigQuery reference