Skip to main content

🌍 GeoJSON Reader

The GeoJSON reader allows you to upload .geojson files directly into Geoflip for transformation. GeoJSON is the most common web-native geospatial format, making it ideal for lightweight data exchange and integration with modern applications.

📜 Format Details​

  • File type: .geojson (UTF-8 encoded)
  • Coordinate Reference System (CRS): Always assumed to be WGS84 (EPSG:4326), following the GeoJSON specification (RFC 7946).
  • Upload type: Must be uploaded as a file in a multipart form.
    • Inline JSON bodies are not supported.
    • Always attach the .geojson file as input_file.

⚙️ Example Config​

{
  "input": {
    "format": "geojson"
  },
  "transformations": [
    { "type": "buffer", "params": { "distance": 100, "units": "meters" } }
  ],
  "output": {
    "format": "shp",
    "epsg": 4326
  }
}

📑 Example API Call​

curl -X POST https://api.geoflip.io/transform \
  -F 'config={
    "input":{"format":"geojson"},
    "transformations":[{"type":"buffer","params":{"distance":100,"units":"meters"}}],
    "output":{"format":"shp","epsg":4326}
  }' \
  -F "input_file=@/path/to/data.geojson;type=application/geo+json"

Response

{ "job_id": "abcd-ef01-2345-6789" }

Then poll for status:

curl https://api.geoflip.io/result/status/abcd-ef01-2345-6789

And download from the output_url when status is SUCCESS.

✅ Notes​

  • CRS is always EPSG:4326, reprojection is handled at output stage.
  • Keep files small and simple for faster processing (large feature collections may take longer).
  • GeoJSON is best suited for workflows that are web-first or need JSON-native integration.

➡️ Next Steps​