Using the Canvas¶
The Canvas is the visual way to build a GeoJibe workflow.
Sign in and go to Create. The Canvas is the workflow builder.
The subtitle says Start with a source from Components until you add data.
Components¶
Click Components to open the palette. It has three groups:
- Sources — Upload, URL, HTTP/API, S3, Azure Blob, Google Drive, ArcGIS, PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, DuckDB, Google BigQuery, Snowflake, GeoServer, GeoNode, OGC Features, STAC, CKAN, QFieldCloud, Mergin Maps, Hub
- Transform — Transform, Python, Convert, and Sync when field-data sync is enabled
- Destinations — Download, PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, DuckDB, Google BigQuery, Snowflake, S3, Azure Blob, Google Drive, SFTP, Hub, GeoServer, GeoNode, Webhook
Drag a component onto the canvas, or click it to add it.
A workflow has one Source, one Destination, and at most one of each processing component.
Add a Source¶
Start with where the data comes from.
For a file on your computer, add Upload. Drop a file onto the canvas, or choose Choose a file.
For other Sources, click the card and fill in Properties. URL, HTTP/API, S3, Azure Blob, Google Drive, ArcGIS, and similar remote Sources need Import before fields and layers are available.
QFieldCloud and Mergin Maps are for Sync Jobs, not ordinary conversion. See Sync QFieldCloud with PostGIS.
Add optional processing¶
Add only what you need:
- Convert — format and CRS
- Transform — Basic operations, or SQL against
source - Python — a custom script
Click a card to edit it in Properties. Click the canvas background to deselect.
Transform and Python cards include a × to remove that step.
Note
Transform is optional. If your data is already how you want it, you can go directly to the Destination.
Add a Destination¶
Choose where the finished data should go.
Download does not need a saved connection.
PostGIS, SQL Server, MySQL / MariaDB, Oracle Spatial, Google BigQuery, Snowflake, S3, Azure Blob, Google Drive, SFTP, Hub, GeoServer, GeoNode, and Webhook usually use a saved Destination. DuckDB is a downloadable file, like Download. Pick it in Properties, then fill in the table, object key, path, layer, or request format for this run.
Email and Job outcome webhooks are not Canvas components. Configure them when you save the Job.
Configured vs not configured¶
Each card shows a status:
| Status | Meaning |
|---|---|
| Configured | Ready to run |
| Not configured | Something is still missing |
| Running | GeoJibe is working |
| Error / Needs attention | Check Properties |
Connectors between cards are drawn for you. You do not draw the lines.
Run¶
Click Run.
If the Destination is Download, a Download button appears when the result is ready.
Save as Job¶
Save as Job is optional.
Use it when you want to run the same workflow again or put it on a schedule.
The canvas subtitle says Run this conversion without saving. Save as Job is optional.
Sync is different: Sync requires saving as a Job.
Clear canvas¶
Clear canvas removes the Source, processing, Destination, and unsaved settings. It asks for confirmation first.