Land Intelligence & Cadastral Portal
Source-line cadastral vectors beat retraced DWGs every time. Download the village from Trace My Land as a vector KML with every survey/gat boundary numbered, then bring it straight into QGIS for analysis, Google Earth Pro for visualisation, or AutoCAD / Civil 3D via a DXF export. One file, three destinations.
The KML is generated straight from the MRSAC MahaBHUMI village feature service — the same vector state the government's own map tools publish.
Every survey/gat number of the village is one closed polygon you can select, label, hatch and measure — no line work to trace and close yourself.
The parcel number travels in the feature's name/attributes, so joins to your 7/12 or rate tables happen in QGIS or Excel rather than manual labelling.
Coordinates are WGS84 (EPSG:4326), so the file overlays Google Earth perfectly and re-projects cleanly to UTM 43N (or your project CRS) inside QGIS.
Plot at 1:1000, 1:4000 or A0 village sheets straight from the vector geometry — the same file feeds both the PDF sheet generator and your CAD workflow.
Layer → Add Layer → Add Vector Layer → pick the .kml. QGIS reads KML natively (GDAL). Save as GeoPackage to edit or join tables; style the survey-number label field for immediate legibility.
File → Open → the .kml. Every parcel shows in its true position with the survey/gat name; use the ruler on any polygon or save a tour for site visits.
AutoCAD has no native KML import, so convert once: in QGIS, right-click the layer → Export → Save Features As → format DXF (pick a projected CRS such as UTM 43N so units are metres). Open the DXF in AutoCAD or Civil 3D — closed polylines with parcels intact.
The KML itself is always WGS84 — re-project during DXF export, not by editing the KML. If your site plan mixes cadastral vectors with a local grid, transform with QGIS rather than eyeballing offsets.
The vectors reproduce Maharashtra's official cadastral layer — mapping-grade geometry that can be off a few metres against a DGPS survey. Use it for planning, visualisation, land-budgeting and boundary context; commission fresh DGPS observations for construction layout or legal demarcation. Cite the source: vectors © the state cadastral GIS, delivered via Trace My Land.
Download the village KML from the Village Map tool, then in QGIS use Layer → Add Layer → Add Vector Layer and pick the .kml file — QGIS reads KML natively through GDAL. The parcels arrive as polygons with the survey/gat number in their attributes; export to GeoPackage or Shapefile for permanent storage.
Not natively. Convert KML to DXF first — the cleanest path is QGIS: open the KML, right-click the layer → Export → Save Features As, choose DXF as the format (and optionally a local CRS such as UTM zone 43N). The DXF then opens in AutoCAD and Civil 3D with every parcel boundary intact.
KML files are always WGS84 geographic coordinates (EPSG:4326), because that is what Google Earth consumes. If your AutoCAD project needs metres, re-project while exporting (QGIS handles every CRS) — don't try to re-project the KML itself.
Every survey/gat parcel polygon of the chosen village, each named and numbered with its survey/gat number, plus the village name metadata. It is the village's cadastral (Bhu Naksha) coverage as source-line vectors, not a scanned or traced image.
No — it reproduces the state cadastral layer, which is a mapping-grade representation of village boundaries, commonly within a few metres. For construction layout or legal demarcation, commission a DGPS survey; the KML is for planning, reference and visualisation.
KML for Earth & QGIS, PDF for the table — free, no login.
Download a village map