Compatibility Mode
Components to facilitate the migration to CARTO of workflows built with other similar tools, such as for example Alteryx.
Description
This component performs a cartesian join.
In a Cartesian join, every row from one table is joined to every row of another table. For example, if table A has 100 rows, and table B has 10,000 rows, the Cartesian join of these two tables results in 1,000,000 rows.
Inputs
Main table [Table]Secondary table [Table]
Outputs
Result table [Table]
Description
This component takes any polygon or polyline spatial object and expands or contracts its extents by a user-specified value.
Inputs
Source table [Table]Spatial Field [Column]Distance [Number]Units [Selection]Include Original Spatial Field in Output [Boolean]
Outputs
Result table [Table]
Description
This component extracts tabular information about the spatial object. Attributes like area, spatial object, number of parts, number of points, and centroid Latitude /Longitude coordinates can be revealed.
Inputs
Source table [Table]Spatial Object Field [Column]Area (Square Kilometers) [Boolean]Area (Square Miles) [Boolean]Bounding Rectangle as Points [Boolean]Bounding Rectangle as Polygon [Boolean]Bounding Rectangle as X and Y Fields [Boolean]Centroid as Spatial Object [Boolean]Centroid as X and Y Fields [Boolean]End Points as Spatial Object [Boolean]End Points as X and Y Fields [Boolean]Length (Kilometers) [Boolean]Length (Miles) [Boolean]Number of Parts [Boolean]Nunber of Points [Boolean]Spatial Object Type [Boolean]
Outputs
Result table [Table]
Description
This component creates a point-type spatial object by specifying input fields containing the X coordinate (Longitude) and the Y coordinate (Latitude). This is usually done to prepare the input data for spatial processing using components like the A Spatial Match, the A Distance or the A Trade Areas.
Inputs
Source table [Table]X Field (Longitude) [Column]Y Field(Latitude) [Column]
Outputs
Result table [Table]
Description
This component calculates the ellipsoidal direct point-to-point, point-to-edge, or the drive distance between two sets of spatial objects.
There are three types of distance calculation relationships available:
- 1.Point-to-point: The Distance tool calculates the distance between two sets of point type spatial objects. An example is calculating the distance from records in a customer data table (point type) to records in a store data table (point type).
- 2.Point-to-edge (line): The Distance tool calculates the distance between a set of point type spatial objects and the closest edge of a set of line type spatial objects. An example is calculating the distance from the records in a customer data table (point type) to the nearest interstate highway (edge of line spatial type).
- 3.Point-to-edge (polygon): The Distance tool calculates the distance between a set of point type spatial objects and the closest edge of a set of polygon type spatial objects.
- When the points are contained within the polygons, you can choose one of two options: Return a distance of zero, or Return the distance to the nearest edge. If the point is located inside of a polygon the A_DISTANCE component returns a negative number for the distance to the edge of the containing polygon.
- When the points are contained outside of the polygons, you can also choose to have the A_DISTANCE component calculate the Nearest Interior point within the nearest edge of a polygon.
- While this method of calculating distance takes the curvature of the Earth into consideration, it is not a routing routine and does not follow street patterns or honor physical barriers such as bodies of water.
Inputs
Source table [Table]Point or centroid source [Column]Point, line or polygon destination [Column]When a point is inside a polygon [Selection]Create nearest interior point inside of the polygon [Boolean]Output direction in degrees [Boolean]Output cardinal direction [Boolean]Units [Selection]
Outputs
Result table [Table]
Description
This component identifies the shortest distance between spatial objects in one table and the objects in a second table.
There are many use cases for this component. For example, to find the closest store locations to consumers in the customer file (both point tables), identify the closest cell towers (point tables) to LATAs (polygon tables), or select congressional districts (polygon tables) within 50 miles of a major thoroughfare (line table).
Inputs
Targets [Table]Universe [Table]Target Spatial Object Field [Column]Universe Spatial Object Field [Column]Id column in target table [Column]Id column in universe table [Column]Maximum Distance [Number]Units [Selection]
Outputs
Result table [Table]
Description
This component decreases the number of nodes that make up a polygon or polyline, making a simpler rendition of the original spatial object. Polygons are generalized using the Ramer-Douglas-Peucker algorithm.
Inputs
Source table [Table]Spatial Field [Column]Threshold [Number]Units [Selection]
Outputs
Result table [Table]
Description
This component combines two input tables based on common fields between the two tables. You can also Join two tables based on record position.
Inputs
Left table [Table]Right table [Table]Join By [Selection]Column in Left Table [Column]Column in Right Table [Column]
Outputs
Table with unjoined rows from left table [Table]Table with unjoined rows from right table [Table]Joined table [Table]
Description
This component takes a group of spatial point objects and draws a polygon or polyline in a specific sort order to represent that group of points.
This component can also be used for spatial layer development by translating a collection of GPS data into polygon or polyline objects, where a polygon is a simple bounded region, such as a state boundary, and a polyline contains multiple line segments with any number of points between its start and endpoints, such as a river or road.
Inputs
Build Method [Selection]Source table [Table]Source Field [Column]Source Field [Column]Sequence Field [Column]
Outputs
Result table [Table]
Description
This component splits polygon or polyline objects into their component point, line, or region objects.
This is a very specialized component used for spatial layer development. A typical use of this component is to disaggregate complex regions that may contain more than one polygon or to separate a polyline into its individual nodes.
Inputs
Source table [Table]Spatial Field [Column]Split To [Selection]
Outputs
Result table [Table]
Description
This component establishes the spatial relationship (contains, intersects, touches, etc.) between two sets of spatial objects. The component accepts a set of spatial objects from the Target Input and a set of spatial objects from the Universe Input. At least one input stream should contain Polygon type spatial objects.
Inputs
Targets [Table]Universe [Table]Target Spatial Object Field [Column]Universe Spatial Object Field [Column]Type of Spatial Match [Selection]Output Intersection Object (Intersects Only) [Boolean]
Outputs
Result table [Table]
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]
Description
This component creates regions around specified point objects in the input table.
Inputs
Source table [Table]Spatial Object Field of Point Source [Column]Radius, Doughnuts [String]Units [Selection]Include Point in Output [Boolean]Eliminate Overlap [Boolean]
Outputs
Result table [Table]
Description
This component combines two or more tables on column names, generating a new table that is the union of several input ones. The input tables must have the same schema.
Inputs
Tables [Table]
Outputs
Result table [Table]
Last modified 5d ago