Skip to main content

📤 Writer Formats Overview

Geoflip supports writing outputs in multiple spatial formats so you can use the results in your preferred tools or workflows.
Each writer has its own delivery method and requirements.

Currently supported writer formats:

🔄 How Writers Work​

When you submit a job, the output section of your config defines the format, EPSG code, and delivery style:

"output": {
  "format": "geojson | shp | dxf",
  "epsg": 4326,
  "to_file": true
}
  • format → Desired output type.
  • epsg → Target CRS; defaults to 4326 (WGS-84) if not specified.
  • to_file → Controls whether output is delivered as a downloadable file (true, default) or inline JSON (false, supported only for GeoJSON).

🗂️ Choosing the Right Writer​

  • Use GeoJSON for web workflows or when you want JSON data inline in the API response.
  • Use Shapefile (SHP) for compatibility with traditional GIS software.
  • Use DXF when results need to be consumed by CAD or engineering systems.
  • Use Geopackage (GPKG) if you want to store multiple geometries within a single tidy file.
  • Use CSV (WKT) if you need geometry in WKT - commonly required for loading into big data platforms like BigQuery or Snowflake.

✅ Summary​

WriterDeliveryNotes
GeoJSONInline JSON (to_file=false) or downloadable .geojson fileOnly format that supports inline response
Shapefile.zip containing .shp, .shx, .dbf, .prjCRS in .prj reflects output.epsg
DXF.dxf fileEntities grouped into layers: annotation, point, polyline, polygon, multipatch
Geopackage.gpkg filea modern spatial data format based on sqlite file databases
CSV (WKT).csv filea CSV file with a geometry columned expressed as WKT geometries

➡️ Next Steps​