Send data to PostGIS¶
GeoJibe can write the result of a workflow straight into a PostGIS table.
You need to be signed in. Download is not involved — PostGIS is the Destination.
Before you start¶
You'll need:
- A PostGIS database you can write to (the database and PostGIS extension must already exist)
- Host, port, database name, username, and password
- A table name for this delivery
Save the connection once, then reuse it.
1. Save a PostGIS Destination¶
Open Destinations → Add Destination → PostGIS.
Fill in Host, Port (usually 5432), SSL mode, Database, Username, and Password. Default schema is optional.
Click Test, then Save. Name it something like Production PostGIS.
The saved Destination is the database login. Schema, table, and write mode belong to each workflow.
2. Add your data and any changes¶
Upload or import a vector dataset. Add Transform or Convert if you need them.
PostGIS is for vector data.
3. Choose PostGIS¶
Add PostGIS and select the saved Destination.
Then set:
| Field | Typical value |
|---|---|
| Schema | public, or another schema you are allowed to use |
| Table | neighborhoods |
| Write mode | See below |
4. Choose a write mode¶
| Mode | What it does |
|---|---|
| Create | Creates a new table. Fails if the table already exists. |
| Replace | Overwrites the table if it exists. |
| Append | Adds rows to an existing table. Fails if the table is missing. |
Warning
Replace mode can overwrite an existing destination table.
5. Run¶
Click Run, or Send to PostGIS in Classic.
You should see a successful delivery to schema.table.
What happens next?¶
GeoJibe writes the converted layer into that table (geometry column geom). Open it in QGIS or your database tool to confirm.
This is a one-off unless you save a Job.
Sync Jobs are different: they write a GeoPackage into a schema, not a named table. See Sync QFieldCloud with PostGIS.
Having trouble?¶
See PostGIS connection failed.