Rename or remove fields¶

Need shape_len to become perimeter? Or want to drop extra columns before you publish?

Use Transform.

Source Transform Destination

Note

Transform is optional. If your data is already how you want it, skip this step.

Before you start¶

Fields appear after GeoJibe inspects the Source. Import a URL, S3 object, FeatureServer layer, PostGIS table, GeoServer layer, or GeoNode dataset first. For an upload, wait until inspect finishes.

If Output Fields is empty, the Source has not been inspected yet. See My fields don't appear in Transform.

1. Add Transform¶

Add Transform from Components and click it.

Choose Manual to build the changes yourself.

If your site has AI enabled, AI can describe the same changes in plain language. GeoJibe turns that into the same operations you would add by hand. Running the workflow later does not call AI again.

2. Rename a field¶

Click Add transformation, choose Rename column, then set:

Field	Example
From	`shape_len`
To	`perimeter`

shape_len  →  perimeter

The new name must be a simple identifier. Geometry cannot be renamed here.

3. Choose which fields to keep¶

Open Output Fields.

Output Fields

☑ name
☑ perimeter
☐ shape_area

Unchecked fields are omitted from the result. Geometry is always kept.

Use Select all or Clear all when the list is long. Filter fields searches by name.

4. Other useful changes¶

From Add transformation you can also:

Operation	What it does
Compute column	New field from a calculation. Expression mode allows more advanced formulas
Replace text	Find / replace in a text field
Trim whitespace	Strip leading and trailing spaces
Convert type	Cast to integer, float, or string
Filter rows	Keep rows that match a comparison. Expression mode allows `AND` / `OR` conditions
Clip	Keep only the part of each feature inside an area
Simplify	Reduce geometry detail
Buffer	Create an area around points, lines, or polygons

The full list, including required values, is in Transform operations. Geometry steps such as Clip, Simplify, and Buffer are covered in Clip, simplify, or buffer geometry.

Saved Recipes reuse a set of these operations. Apply a Recipe from Transform if you already have one.

For filters, calculated fields, and spatial SQL that Basic operations cannot express, use SQL Transform.

5. Preview and Run¶

Classic shows a Transformation preview with schema changes and a few sample values. On the Canvas, configure Transform, then Run the whole workflow.

What happens next?¶

GeoJibe applies the operations in order, then writes the Destination. The original Source is not modified.

Having trouble?¶

Fields missing → inspect/import the Source first
Rename rejected → the target name already exists, or is not a valid identifier
Filter did nothing useful → check the column, operator, and value