How GeoJibe works¶
Every GeoJibe workflow is the same idea:
You pick where data comes from, change it only if you need to, then choose where it should go.
Source — where the data comes from¶
Examples:
- A file on your computer (Upload)
- A file on the web (URL)
- An object in S3
- A layer from an ArcGIS FeatureServer
Field-data projects use a different path. QFieldCloud and Mergin Maps are for Sync, not for ordinary file conversion.
Processing — what you want to change¶
Processing is optional. You can upload a file and download it as-is when that is what you need.
When you do want changes, add only the steps you need:
| Component | Use it to |
|---|---|
| Convert | Change format or coordinate system |
| Transform | Rename fields, keep or drop columns, filter rows |
| Python | Custom changes Transform cannot do |
You do not have to use all three.
Examples:
Destination — where the finished data goes¶
- Download — get a file back
- PostGIS — write a table
- S3 — store the file
- SFTP — send the file to a server
- GeoServer — publish a layer
- GeoNode — publish a catalog resource
Download is available without signing in. The others need an account and usually a saved connection.
One-off vs Job vs Sync¶
One-off — build, Run, done. No saved Job.
Job — save the workflow so you can run it again or schedule it.
Sync — a special Job for QFieldCloud or Mergin Maps. GeoJibe checks the remote project and updates PostGIS when the data has changed.
Tip
You don't need to save a Job for a one-time conversion.
Canvas and Classic¶
The Canvas and the Classic wizard configure the same kind of workflow. Canvas is visual. Classic is a short sequence of steps.
If you are signed in, start with the Canvas. See Using the Canvas.