Dissolve and Merge Boundaries

Merge adjoining areas into one, optionally grouped by an attribute. Wards into a village, villages into a taluka, plots into a survey number.

The layer to dissolve

Drop a file or choose one

Why this matters here

Older Indian survey and revenue records sit on the Everest spheroid, not WGS 84. Treating one as the other puts everything a few hundred metres out — enough to move a plot boundary onto a neighbour.

Indian systems included

Kalianpur 1880, 1937 and 1975, the India zone grids, UTM zones 42N to 47N on both WGS 84 and Indian datums, and the WGS 84 state systems.

Bulk paste

Paste a column straight out of a spreadsheet. Anything after the first two values is carried through as a label, and the result downloads as CSV.

Nothing leaves your device

The arithmetic runs in your browser with proj4. No coordinate is transmitted, logged or stored anywhere.

Frequently asked questions

What does dissolve actually do?

It removes the shared edges between touching areas so they become one shape. Group by an attribute and it does that separately for each value, which turns a ward layer into a village layer.

Why did I get a MultiPolygon?

Because some of the areas in a group do not touch. They stay as separate parts of a single feature, which is correct.

Which attributes survive?

The field you grouped by, plus a count of how many original areas went into each result. Other attributes cannot survive a merge, since the pieces disagree.

Is my file uploaded anywhere?

No.

Ready to convert without uploading?

Free, no sign-up, no file size limit — and your data never leaves your machine.

Open the KML converter