Transform operations¶
Transform applies a short list of deterministic field operations. Geometry is always kept.
Build them by hand (Add transformation), with Output Fields, from a Recipe, or — if enabled — by describing the change with AI. AI only authors the operations. Run does not call AI again.
Operations you cannot pick in the Add dialog still exist when a Recipe, AI, or Output Fields emits them.
Operations you can add¶
Rename column¶
Purpose: Rename a field.
Required: From, To
Example: shape_len → perimeter
Limits: To must be a valid identifier and must not already exist. Geometry cannot be renamed.
Replace text¶
Purpose: Find and replace inside a text field.
Required: Column, Find ( Replace may be empty to delete the find text)
Example: Rd. → Road in column name
Limits: The value is treated as text.
Trim whitespace¶
Purpose: Strip leading and trailing spaces.
Required: Column
Convert type¶
Purpose: Cast a field.
Required: Column, Target type (integer, float, or string)
Filter rows¶
Purpose: Keep rows that match a comparison.
Required: Column, Operator, Value (or Values for “is one of”)
Operators: =, !=, >, <, >=, <=, is one of, is not one of
Example: status = active
Limits: No geometry column. No raw SQL.
Compute column¶
Purpose: Create a new numeric field.
Required: Expression, Target column
Example: shape_area / 10000 into hectares
Limits: Only + - * / ( ), numbers, and existing field names. Target name must not already exist.
Output Fields (keep / drop)¶
Unchecked names are omitted. This is how you remove columns without an extra “Remove column” card.
Internally that is keep_columns / drop_column. You will not usually add those from the Add dialog.
Geometry is never listed and cannot be dropped.
Execution order¶
Operations run in list order, then Output Fields. A later step cannot use a field you already renamed or removed.
Recipes¶
A Recipe stores operations plus Output Fields. Apply it in Transform. Save as Recipe stores the current set. Recipes are not Jobs.