Output · Files

Write Geo File

Saves a table with geometry as GeoJSON, GeoPackage, Shapefile or GeoParquet, ready to open in QGIS or ArcGIS. GeoParquet takes lon/lat data only.

Also known as: Shapefile, GeoPackage export

How it works

Pick a Format: GeoJSON (the default), GeoPackage, Shapefile or GeoParquet. The File name takes the matching extension (output.geojson by default) and Location is the project folder unless you choose another. Geometry column is the first geometry column of the input unless you pick one. The write fails if the file already exists unless you tick Overwrite if the file already exists. The file carries the branch's CRS; GeoParquet records no CRS and so accepts lon/lat (EPSG:4326) data only, and the node blocks until you Reproject anything else. Shapefile holds one geometry type and splits into sidecar files (.dbf, .shx, .prj), so GeoPackage is the better choice for mixed shapes or a single file to hand on. The written file is passed on downstream as a File.

Inputs and outputs

Inputs

  • data — Table

Outputs

  • file — File

Settings

The Attributes panel of Write Geo File, as in the app: the controls work, but nothing runs — there is no data behind it.

The same settings, as the Assistant writes them
Writes the input to a geo file GIS tools read: GeoJSON, GeoPackage, Shapefile or GeoParquet. Needs a geometry column. The output carries the branch's CRS; GeoParquet records no CRS, so it accepts lon/lat data only — reproject first for anything else. Shapefile holds one geometry type and splits across sidecar files (.dbf/.shx/.prj), so prefer GeoPackage for mixed geometry or for a single file to hand on.

Example

You built store catchments with Trade Areas and a colleague wants them in QGIS. Choose GeoPackage, name the file catchments.gpkg and tick Overwrite if the file already exists so each run refreshes it.