GISela Buffer
Buffer zones around points, lines or polygons at a distance in metres, merged or one per feature.
How it works
Creates buffer polygons at a true distance in metres around every feature of GeoJSON, KML, GPX, CSV or shapefile data: circles around points, corridors around lines, grown or shrunk polygons. Overlapping zones can be merged into one area. Returns GeoJSON, the ellipsoidal area of each zone and a map preview.
- Each feature (or all features when merging) is projected to a local Transverse Mercator plane centred on the data, so distances are in metres with a scale error below 0.03 % within 250 km of the centre.
- Points become circles; every line segment and polygon edge becomes a stadium (two half circles joined by straight sides); the stadiums are merged with GISela’s polygon overlay (exact edge splitting on a snapped grid, even-odd classification). A positive polygon buffer is the polygon united with its edge band, a negative one the polygon minus the band.
- Results are converted back to WGS 84. Areas and perimeters are ellipsoidal (Karney’s geodesic polygon algorithm on WGS 84).
Circles are polygons with the chosen number of segments, so the area is slightly smaller than the true disc (0.6 % at 32 segments).
Sources
- Algorithms for geodesics (Karney 2013) (Journal of Geodesy 87)
- Transverse Mercator with an accuracy of a few nanometers (Karney 2011) (Journal of Geodesy 85)
- RFC 7946: The GeoJSON Format (IETF)
Part of GISela
-
GISela Browser GIS
A GIS in your browser: layers, attribute tables, styling, analysis and print layouts.
How to draw buffer zones around points, lines and polygons
Make zones at a distance in metres around features — merged into one area or one per feature — with area and perimeter of every zone, measured on the ellipsoid.
What it is for
A buffer is the area within a given distance of something: everything within 300 m of a tram stop, a 150 m corridor along a road, a 50 m protection strip inside a parcel boundary. Buffers are the first step of many questions — how many people live near a stop, which buildings are inside a noise zone — and the GISela app uses the same code in Analysis → Buffer.
The tool accepts points, lines and polygons as GeoJSON, KML, GPX, CSV, WKT or TopoJSON, in any supported coordinate system. Positive distances grow features; negative distances shrink polygons.
Worked example
The first example puts 300 m around seven tram stops of an invented town, with Merge overlapping zones ticked. The tool reports 7 input features, 1 buffer polygon, and a total area of 1,929,855.3 m² (about 1.93 km²) with a perimeter of 12,336.5 m.
Without merging, the same run returns seven circles of 280,930 m² each, together 1,966,510.5 m². The difference — about 36,700 m² — is where neighbouring circles overlap; merging counts that ground once. Each circle is slightly smaller than π × 300² = 282,743 m² because it is drawn with 32 straight segments. More segments make it rounder.
The second example draws a 150 m corridor along the tram line: one polygon of 1,185,347.3 m². The third shrinks the six district polygons by 100 m: Altstadt goes from 1.32 km² to 900,033.2 m².
How to read the result
- Input features / Buffer polygons — merged runs give one polygon (possibly with several parts); unmerged runs give one per feature.
- Total area — sum of the buffer polygons, measured on the WGS 84 ellipsoid.
- Table — area and perimeter per zone, with the feature's name when it has one.
- Map — a small SVG preview.
- Download — the buffers as GeoJSON in WGS 84, with the original attributes.
Tips and common mistakes
- Distances are in metres, whatever system the data is in. Internally the tool works on a local transverse Mercator plane around the data (scale error below 0.03 % within 250 km), so buffers are round on the ground, not stretched like circles drawn in degrees.
- Negative distances only work on polygons. A polygon narrower than twice the distance disappears; the tool says how many did.
- For very large areas (whole countries), buffers far from the centre become slightly less exact; split the data by region.
- Use merge for "the area covered", and separate zones when you need a zone per feature (for example to count people per stop).
- 32 segments are enough for maps; 64–128 are better if you need the area to within 0.1 %.
FAQ
Why is my 300 m circle not exactly π × 300²?
A circle is drawn as a polygon with straight sides, which lies just inside the true circle: with 32 segments the area is 0.64 % smaller, with 128 segments 0.04 %.
Can I buffer lines with flat ends?
No — ends and corners are always round, which is what "everything within a distance" means.
Do holes in polygons stay holes?
Yes. A positive buffer fills small holes from inside; a negative buffer makes them larger.
Guide last updated:
For scripts and AI agents
- JSON API:
POST https://giselabuffer.usefulweb.site/api/v1/calculate(same calculation as this page) - Interface description: OpenAPI 3.1 · AI guide: llms.txt
- MCP server (Streamable HTTP):
https://giselabuffer.usefulweb.site/mcp· tool namegisela_buffer
Example request
curl -s -X POST https://giselabuffer.usefulweb.site/api/v1/calculate \
-H 'content-type: application/json' \
-d '{…see OpenAPI examples…}'