Skip to main content

📥 Reader Formats Overview

Geoflip accepts multiple spatial input formats so you can work with the data you already have.
Each format has its own quirks and requirements when being uploaded to the API.

Currently supported reader formats:

🔄 How Readers Work​

All transform jobs in Geoflip require two parts:

  1. Config JSON (passed as the config form field)
    Defines the input format, transformations, and output settings.
  2. Input File (passed as the input_file form field)
    The actual data in one of the supported formats.

These are sent together as a multipart form request to:

POST https://api.geoflip.io/transform

Example skeleton request:

curl -X POST https://api.geoflip.io/transform \
  -F 'config={ ... }' \
  -F "input_file=@/path/to/file"

🗂️ Choosing the Right Reader​

  • Use GeoJSON when working with lightweight, web-native spatial data (always EPSG:4326).
  • Use Shapefile (SHP) when handling legacy GIS workflows or data coming from ESRI/desktop systems (requires zipped components).
  • Use DXF when ingesting CAD drawings; you must provide an EPSG code because DXF does not store CRS information.

✅ Summary​

ReaderUpload TypeCRS HandlingNotes
GeoJSON.geojson fileAlways EPSG:4326 (per spec)No inline JSON allowed, file upload only
SHP.zip with .shp, .shx, .dbf, .prjCRS read from .prjMost common desktop GIS format
DXF.dxf fileinput.epsg must be provided in configUsed for CAD-style drawings

➡️ Next Steps​