Import from MySQL / MariaDB¶
Use MySQL / MariaDB when the data already lives in a MySQL or MariaDB spatial table.
You need to be signed in. Saving the connection once is the usual path.
MySQL / MariaDB appears only when GeoJibe's GDAL runtime includes the MySQL driver.
This is a spatial table import, not a database migration. GeoJibe copies one table into the workflow.
Before you start¶
You'll need:
- Host, port (usually
3306), and database name - A MySQL or MariaDB username and password
- A spatial table or view GeoJibe can read
The saved Source is the database connection. You choose the table each time you import or save a Job.
1. Save the MySQL / MariaDB Source¶
Open Sources → Add Source → MySQL / MariaDB.
Fill in host, port, database, username, and password. Click Test, then Save. Name it something like Production GIS.
2. Add MySQL / MariaDB on the Canvas¶
Add MySQL / MariaDB, choose the saved Source or enter the connection, then Connect.
Choose a table. Click Import. GeoJibe copies the table into the job workspace and inspects it.
After Import, Transform sees the real field names. Convert offers the same formats as an uploaded file.
You can also fill the connection in manually for a one-off run. You do not have to save a Job.
3. Process and deliver¶
Add Transform, Convert, or Python if you need them. Then choose a Destination — Download, GeoPackage, PostGIS, another MySQL table, and the rest work as usual.
Example: MySQL / MariaDB → Transform → GeoPackage.
Click Run.