🔧 Transformations Overview
Transformations are the core operations in Geoflip.
They allow you to modify, analyze, or combine your spatial data as part of a processing pipeline.
Each transformation is defined in the transformations array of your request config.
Multiple transformations can be chained together in the order they appear.
🔄 How Transformations Work
A typical request config looks like this:
{
"input": { "format": "geojson" },
"transformations": [
{ "type": "buffer", "params": { "distance": 100, "units": "meters" } },
{ "type": "union" }
],
"output": { "format": "shp", "epsg": 4326 }
}
bufferexpands geometries by a given distance.unionmerges overlapping geometries into a single shape.- Transformations are executed in the order provided.
🧩 Supported Transformations
1. Buffer
- Creates zones at a given distance around points, lines, or polygons.
- Parameters:
distance— buffer radius (float)units— one ofmeters,kilometers,feet,miles
- Read more → Buffer Transformation
2. Union
- Combines overlapping or adjacent geometries into a single feature.
- No parameters required.
- Read more → Union Transformation
⚡ Example Pipeline
You can chain multiple transformations together in one request:
{
"input": { "format": "dxf", "epsg": 28350 },
"transformations": [
{ "type": "buffer", "params": { "distance": 500, "units": "meters" } },
{ "type": "union" }
],
"output": { "format": "geojson", "epsg": 4326 }
}
This example:
- Buffers all geometries by 500 meters.
- Unions them into a single geometry.
- Outputs the result in GeoJSON (EPSG:4326).
✅ Notes
- Transformations are stateless and do not persist data — every request is standalone.
- You can include zero, one, or many transformations.
- Unsupported transformations will cause a
400 Bad Requestwith an error message.
➡️ Next Steps
- Learn about Buffer Transformation
- Learn about Union Transformation
- Revisit the API Overview