Converting Planning Data to GIS – From Drawings to an Intelligent Spatial Database
For many years, planning dossiers have existed mainly in the form of paper/CAD drawings. While legally valid, they are limited in querying, interoperability, and spatial analysis. Converting planning data to GIS transforms these “static drawings” into an intelligent, structured database that can be integrated, shared, and analytically processed to support decision-making, monitoring, and planning transparency.
GIS Conversion Consulting Hotline/Zalo: 0938 309 808 • Email: lienhe@3dscan.vn
.webp)
3D urban model generated from UAV data for urban planning and design
1) Why Convert Planning Data to GIS?
- Interaction & analysis: GIS enables querying, scenario analysis, and spatial impact assessment (buffering, overlay, network analysis) that static drawings cannot perform.
- Interoperability & data sharing: A standardized data structure allows integration with national databases, public-information portals, and operational systems of multiple agencies.
- Updating & version control: Easily update changes, maintain revision history, and ensure data timeliness and traceability.
- Transparency & monitoring: WebGIS publication enhances public transparency and administrative efficiency.
- Data-driven decision-making: Optimize infrastructure investment, land-use administration, and assessment of urban carrying capacity.
.webp)
Symbol requirements for GIS maps under Circular 16/2025/TT-BXD (Ministry of Construction)
2) Understanding GIS Regulations is a Prerequisite
Converting CAD to GIS is not simply a format change. It is a process of standardization according to regulations (database schema, symbols, geometry types, attribute fields, topology rules, coordinate system, etc.) to ensure data validity and interoperability. Key components include:
- Database structure: Organized into data groups (Topography, Existing Conditions, Planning, Boundary Markers) and detailed layers (boundaries, land-use, transport, infrastructure…).
- Presentation rules: Unified layer names; correct point–line–polygon geometry types; standardized symbols/colors; unified fonts and encoding.
- Spatial relationships: Logical administrative hierarchy (commune ⊂ district ⊂ province); parcels within planning blocks; no illegal overlaps.
- Data integrity checks: Topology (no gaps, no overlaps, snapped nodes), mandatory attributes (document code, feature code, classification, planning phase), value domains, data dictionary.
- Coordinate system & accuracy: Proper georeferencing in VN-2000; acceptable accuracy; complete metadata (source, scale, update date).
.webp)
Naming conventions for land-use categories
3) What Defines a “Qualified” GIS Planning Database?
- Four mandatory data groups: Topographic base, Existing Conditions, Planning, Boundary Markers.
- Correct geometry types: Points (markers, stations), Lines (routes, non-closed boundaries), Polygons (blocks, parcels, land-use areas).
- Complete mandatory attributes: Layer code, feature code, classification, planning phase (initial/long-term), status (existing/planned), source & update date.
- Topology compliance: No gaps or overlaps; clean boundaries; continuous polylines; valid closed polygons.
- Unified coordinate system: VN-2000 (correct zone), meters; full projection metadata.
- Naming conventions: Prefix/suffix indicating group–purpose–level (e.g.,
DAT_DD_Residential,HTKT_WaterSupply_Main). - Quality control & constraints: Value domains, editor rules (split/merge), topology rules, QA/QC logs, version history.
- Interoperability & publication: GDB/GeoPackage; WMS/WFS/WMTS/Vector Tiles/3D Tiles; WebGIS with permissions.
- Legal linkage: References to planning decisions, drawing numbers, document identifiers, validity periods.
.webp)
Displaying existing-condition and planning data on UAV orthophoto
GIS Planning Database Structure
The table below outlines the data groups and detailed data content for urban and rural planning GIS databases as defined in Circular 16/2025/TT-BXD.
| No. | Database / Thematic data group | Data content |
|---|---|---|
| I | Topographic base database NenDiaHinh.* |
Contains topographic base layers produced by surveying and mapping authorities, meeting quality and technical requirements under regulations on surveying and mapping activities. |
| II | Existing-condition database – HienTrang.* | |
| 1 | Boundary location | Contains data layers on administrative boundaries and planning study boundaries. |
| 2 | Existing land use | Contains data layers on existing land use. |
| 3 | Existing architectural & landscape space | Contains data layers on existing architectural and landscape conditions. |
| 4 | Assessment of existing development land | Contains data layers on assessment of development land. |
| 5 | Existing transport | Contains data layers on existing transport. |
| 6 | Existing red building lines, building lines, and technical infrastructure corridors | Contains data layers on existing red building lines and protection corridors of technical infrastructure routes. |
| 7 | Existing site preparation | Contains data layers on existing site preparation (grading and stormwater drainage). |
| 8 | Existing wastewater drainage and environmental sanitation | Contains data layers on existing wastewater drainage and environmental sanitation. |
| 9 | Existing water supply | Contains data layers on existing water supply networks. |
| 10 | Existing power supply | Contains data layers on existing power supply. |
| 11 | Existing telecommunications | Contains data layers on existing telecommunications. |
| 12 | Assessment of existing environment | Contains data layers on existing environmental conditions. |
| 13 | Existing underground works | Contains data layers on existing underground works. |
| 14 | Existing energy facilities | Contains data layers on existing energy-related facilities. |
| III | Planning database – QuyHoach.* | |
| 1 | Boundary location | Contains data layers on administrative boundaries and planning study boundaries. |
| 2 | Planned land use | Contains data layers on planned land use. |
| 3 | Urban design | Contains data layers on urban design. |
| 4 | Planned architectural & landscape space | Contains data layers on spatial development and architectural landscape orientation. |
| 5 | Planned transport | Contains data layers on planned transport systems. |
| 6 | Planned red building lines, building lines, and technical infrastructure corridors | Contains data layers on planned red building lines and protection corridors of technical infrastructure routes. |
| 7 | Planned site preparation | Contains data layers on planned site preparation (grading and stormwater drainage). |
| 8 | Planned wastewater drainage and environmental sanitation | Contains data layers on planned wastewater drainage, solid waste management, and environmental sanitation. |
| 9 | Planned water supply | Contains data layers on planned water supply. |
| 10 | Planned power supply | Contains data layers on planned power supply. |
| 11 | Planned telecommunications | Contains data layers on planned telecommunications. |
| 12 | Environmental protection measures | Contains data layers on environmental protection measures. |
| 13 | Planned underground works | Contains data layers on planned underground works. |
| 14 | Planned energy facilities | Contains data layers on planned energy-related facilities. |
| IV | Planning boundary-marker database – MocGioi.* | |
| 1 | Planning boundary markers | Contains data layers of planning boundary-marker dossiers. |
.webp)
Existing-condition and planning data represented by map labels
4) CAD ➜ GIS Conversion Workflow (Recommended Best Practice)
- Receive & review planning dossiers: Collect drawings, decisions, reports, indicator tables; check for missing, redundant, or conflicting information.
- Standardize CAD: Filter layers by the approved list, rename layers, normalize geometry (line/polyline/polygon), close polygons, and explode point blocks.
- Georeference & adjust: Georeference to VN-2000; verify distortion; snap boundaries to adjacent administrative limits.
- Build the GIS data model: Create schema (feature datasets, feature classes), standardized fields, domains, subtypes, and topology rules.
- Load data & cross-check: Import by layer; validate topology; detect errors (gaps/overlaps, dangles); reconcile with indicator tables.
- Add legal attributes & metadata: Planning dossier ID, planning code, level and phase, source, update date; describe scope and purpose.
- QA/QC & acceptance: Generate error reports, rectify issues, export checklists, and obtain digital signatures on data acceptance records.
- Publish & operate: Publish mapping services; configure user permissions; set up change-update and backup procedures.
.webp)
Online querying of land-use information anytime, anywhere
List of Data Layers (Feature Classes) – “Existing-condition” Block & Related Layers
The table lists the themes, feature dataset names, feature class names together with descriptions (Aliases) and geometry types for direct use in the planning GIS database.
| Theme | No. | Feature class name | Description (Alias) | Geometry type | |
|---|---|---|---|---|---|
| 1. Boundary location | 1 | TenDonViHanhChinh_P | Administrative unit name | Point | |
| 2 | RanhGioiHanhChinh_L | Administrative boundary | Line | ||
| 3 | RanhGioiQuyHoach_L | Planning boundary | Line | ||
| 2. Existing land use | 4 | ChucNangCongTrinh_P | Building function (point) | Point | |
| 5 | ChucNangSuDungDat_A | Land-use function | Polygon | ||
| 6 | PhanVungSDDkhac_A | Other land-use zoning | Polygon | ||
| 3. Existing architectural & landscape space | 7 | CongTrinh_L | Existing structures – line representation | Line | |
| 8 | CongTrinh_A | Existing structures – polygon representation | Polygon | ||
| 4. Assessment of existing development land | 9 | DuAnLienQuan_A | Related projects | Polygon | |
| 10 | PhanVungDanhGia_A | Assessment zones | Polygon | ||
| 11 | CongTrinhGiaoThong_P | Transport structures – point features | Point | ||
| 12 | CongTrinhGiaoThong_L | Transport structures – line features | Line | ||
| 13 | CongTrinhGiaoThong_A | Transport structures – polygon features | Polygon | ||
| 14 | MangLuoiGiaoThongDuongBo_L | Road network – line (centerline) | Line | ||
| 15 | MangLuoiGiaoThongDuongBo_A | Road network – polygon | Polygon | ||
| 16 | MangLuoiGiaoThongDuongSat_L | Railway network | Line | ||
| 17 | MangLuoiGiaoThongDuongThuy_L | Waterway transport network | Line | ||
| 18 | MangLuoiGiaoThongDuongKhong_L | Air transport network | Line | ||
| 19 | MangLuoiTuyenBus_L | Bus route network | Line | ||
| 20 | BoViaDaiPhanCach_L | Median curbs | Line | ||
| 21 | HuongDi_L | Direction of travel | Line | ||
| 22 | MatCatNgang_L | Cross-section alignment | Line | ||
| 5–6. Existing red building lines, building lines & technical infrastructure corridors | 23 | ChiGioiXayDung_L | Building line | Line | |
| 24 | ChiGioiDuongDo_L | Red building line | Line | ||
| 25 | HanhLangAnToan_L | Safety corridor | Line | ||
| 7. Existing site preparation | 26 | CaoDoNen_P | Platform elevation | Point | |
| 27 | CongTrinhCBKT_P | Site preparation structures – point | Point | ||
| 28 | CongTrinhCBKT_L | Site preparation structures – line | Line | ||
| 29 | CongTrinhCBKT_A | Site preparation structures – polygon | Polygon | ||
| 30 | MangLuoiThoatNuocMua_L | Stormwater drainage network | Line | ||
| 31 | CaoDoCongThoatNM_P | Stormwater manhole / conduit elevation | Point | ||
| 32 | HuongThoatNuocMua_L | Stormwater flow direction | Line | ||
| 33 | MatNuoc_A | Water surface | Polygon | ||
| 34 | PhanLuuThoatNuocMua_L | Stormwater drainage branches | Line | ||
| 35 | PhanVungLuuVuc_A | Catchment zones | Polygon | ||
| 8. Existing wastewater drainage and environmental sanitation | 36 | CaoDoCongThoatTNT_P | Wastewater drainage manhole / conduit elevation | Point | |
| 37 | MangLuoiThoatNuocThai_L | Wastewater drainage network | Line | ||
| 38 | HuongThoatNuocThai_L | Wastewater flow direction | Line | ||
| 39 | PhanLuuThoatNuocThai_L | Wastewater drainage branches | Line | ||
| 40 | CongTrinhTNTvaVSMT_P | Wastewater & environmental sanitation facilities – point | Point | ||
| 41 | CongTrinhTNTvaVSMT_L | Wastewater & environmental sanitation facilities – line | Line | ||
| 44 | CongTrinhTNTvaVSMT_A | Wastewater & environmental sanitation facilities – polygon | Polygon | ||
| 9. Existing water supply | HienTrangCapNuoc | 45 | MangLuoiCapNuoc_L | Water supply network | Line |
| 46 | DiemDauNoi_P | Connection points | Point |
5) Common Errors & How to Avoid Them
- “Raw” format conversion only: Simply converting DWG→SHP without schema standardization ➜ no interoperability / fails topology checks.
- Open/overlapping polygons: Functional zones not properly closed or overlapping contrary to regulations ➜ enable topology rules and use controlled auto-fix.
- Missing legal fields: No dossier code, planning phase, approval decision number ➜ standardize mandatory attribute templates.
- Wrong coordinate system: Using the wrong zone / projection ➜ explicitly record EPSG and verify against control points / GCPs.
- Inconsistent layer names: Not following naming conventions ➜ apply a data dictionary and scripts to validate layer names and schemas.
6) How Can 3DScan.vn Support Your Project?
- Standardization & conversion of CAD → GIS according to approved schema, with full topology validation.
- Schema design (feature datasets, feature classes), domains, topology rules, data dictionary and QA/QC checklists.
- Integration & WebGIS publication (WMS, WMTS, Vector Tiles, 3D Tiles), access control, and update logging.
- Training & handover of workflows for operation, change updating, and quality control.
7) Online Visualization of Planning GIS Data – Topographic Maps, Planning Layers, Orthophotos, and 3D Models
GIS data can be published online without requiring paid desktop software, accessible anytime, anywhere via a web browser. A WebGIS system allows:
- Topographic base layers (DEM/contours, hydrography, base transport), and planning maps (land-use functions, spatial structure, infrastructure).
- High-resolution orthophotos for verifying existing conditions.
- 3D models (3D Tiles / Scene Layers): viewing building volumes, elevations, and urban facades; rotate–zoom–measure directly in the browser.
- Online tools: search/query by parcel or block, measure distance/area, toggle layers, show legend, filter by attributes, and download data according to user permissions.
- Open service standards: WMS/WFS/WMTS/Vector Tiles/3D Tiles – easy integration with open data portals, dashboards, and third-party applications.
Sample WebGIS datasets (2D/3D):
- Dong Van GIS database (geographic & planning maps): Open map
- Sample 2D/3D data – Kim Dong, Ninh Binh: View WebGIS
- 3D model of an urban area (Vietnam National University campus): View 3D online
Technical suggestion: store data in File/Enterprise Geodatabase or GeoPackage; publish via GeoServer/MapServer and Cesium/Deck.gl; enable caching to optimize loading performance.
Need a WebGIS to publish planning data, orthophotos, or 3D models?
3DScan.vn – “Accuracy in every point – Insight in every structure”.
Frequently Asked Questions (FAQ)
Is it mandatory to follow a schema when converting CAD to GIS?
Yes. If the schema (layer names, geometry types, attribute fields, domains) is not followed, the data will fail topology and interoperability requirements and may be rejected at acceptance.
What are the minimum topology checks required?
No overlaps and no gaps between polygons; continuous line networks without breaks; points located at valid positions (e.g. on lines or within polygons as required); seamless adjacency at boundaries; split/merge rules that preserve attributes.
Which coordinate system should be used for planning data?
VN-2000 with the appropriate projection zone, in meters. Full metadata (EPSG code, zone, ellipsoid parameters) should be recorded to ensure interoperability and accuracy.
Which formats are suitable for storing and publishing the data?
Store data in File/Enterprise Geodatabase or GeoPackage; publish via WMS/WFS/WMTS/Vector Tiles/3D Tiles on WebGIS, with access control and update logging enabled.
What services does 3DScan.vn provide for this type of project?
Standardization and conversion of CAD→GIS; schema/domain/topology design; QA/QC and validation; WebGIS publication; and training on operation and change-update workflows.
```
