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.
Check a plot or boundary layer for the faults that ruin a cadastral dataset: areas that overlap, gaps left between neighbours, boundaries that stop just short of each other, and duplicated shapes.
Drop a plot or boundary layer here
Checked on your device · nothing is uploaded
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.
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.
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.
The arithmetic runs in your browser with proj4. No coordinate is transmitted, logged or stored anywhere.
Areas that overlap each other, gaps enclosed inside the merged layer, boundaries that stop just short of touching, and features whose geometry is identical to another. Every one is listed with a measurement and can be clicked to zoom straight to it.
A gap fully surrounded by plots shows up as a hole once the layer is merged. A gap open at both ends does not, because it is not enclosed by anything — so those are found separately by measuring how close two boundaries come without meeting.
It would. Nothing in the file records whether a hole was intended, so both are listed with their area and the judgement is left to you. A deliberate exclusion is usually obvious by its size.
An overlap covering less than about two per cent of the smaller area. That is almost always a digitising error rather than a real shared claim, so those are flagged separately.
A bounding-box filter runs first, so only genuinely nearby pairs are compared. A few thousand plots is comfortable; the number of pairs actually compared is shown with the results.
No. The whole check runs in your browser, which matters when the file is a village record.
Free, no sign-up, no file size limit — and your data never leaves your machine.
Open the KML converter