Convert a file
Home › Shapefile converter › DGN to Shapefile
DGNSHP

DGN to Shapefile converter

A GIS team wants layers it can query, not a drawing it has to trace. This DGN to Shapefile converter turns MicroStation levels of line strings and shapes into point, line and polygon layers for ArcGIS or QGIS. The level, color and text come along as attributes.

Nothing uploadedGDAL engineReviewed

Drop a file, or click to browse

KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more

Nothing uploadedGDAL engineWorks offlineNo account

How to convert DGN to Shapefile

  1. Drop the .dgn file; the preview shows the elements it found.
  2. Choose the coordinate system the drawing was produced in; it is written into the .prj.
  3. Choose Shapefile and convert; the zip holds one shapefile per geometry type. The reader handles DGN V7, so save a V8 file as V7 or export it to DXF first.

What changes when you convert DGN to Shapefile

WhatDGN → Shapefile
GeometryChangesPoints, lines and polygons are all carried over, but a Shapefile holds a single geometry type per file. A layer that mixes types is written one type at a time.
AttributesChangesDGN is a CAD format with no attribute table, so the output carries only the fields the drawing exposes: layer or level, color, line weight, line style and the text of text entities.
Styling & labelsChangesCAD layer/level organization is mapped where it can be, but CAD line styles do not translate to GIS symbology.
Coordinate systemChangesDGN carries no coordinate system. Choose the drawing's grid before converting and it is written into the Shapefile; if the values look projected and none is set, the converter stops and asks for one.
Elevation (Z)Kept3D Z values carry from DGN into Shapefile wherever the source records them.
File structureChangesA working Shapefile is several files, so you download one .zip holding .shp, .shx, .dbf, .prj and .cpg. Keep them together.

Why convert DGN to Shapefile?

MicroStation deliverables arrive as drawings, and redrawing them in GIS by hand is slow, error-prone work. Converted to Shapefile, levels full of line strings and shapes become point, line and polygon layers that ArcGIS and QGIS treat as ordinary data, so an as-built pipeline or a parcel boundary from the engineers slots straight into the corporate geodatabase workflow.

Coordinate system handling

A DGN stores raw eastings and northings and almost never says which grid they belong to. If the values look projected and no system is set, the converter stops and asks for one instead of guessing.

The system you pick is written into the shapefile's .prj, so the layer opens in the right place in QGIS or ArcGIS. Choose WGS84 only when the numbers really are degrees of longitude and latitude.

What to check when converting DGN to Shapefile

Decide the coordinate system before you convert, because a DGN rarely records one, and its eastings and northings only mean something once you say which grid they belong to. The converter writes your choice into the shapefile's .prj, where every GIS will trust it. A drawing that mixes points, linework and closed shapes comes back as one zip holding a separate shapefile per geometry type.

Troubleshooting DGN to Shapefile

  • The file is rejected or reads as empty. The reader handles DGN V7 only, and current MicroStation writes V8 by default. Save the file as V7 through File > Save As, or export it to DXF and convert the export.
  • Field names in the .dbf look cut short. The shapefile format caps field names at 10 characters, so longer names are truncated in the .dbf; the values themselves are never cut.
  • Levels did not become separate layers. A shapefile has no level concept; every feature carries its level number in the attribute table. Filter or split on that field in QGIS or ArcGIS to rebuild the levels.

About the formats

DGN is the MicroStation design file: elements on numbered levels, drawn to engineering precision in a local or projected grid, with no attribute table behind them. The Shapefile is the exchange format of desktop GIS, a set of files (.shp, .shx, .dbf and .prj) in which every feature has a row of attributes and a declared coordinate system. The conversion fills that table with what the drawing exposes: element type, level number, graphic group, color index, line weight, line style and the text string of text elements. Anything held in a linked database or in cell names is not part of the drawing geometry and does not come across.

Frequently asked questions

Why are there several shapefiles in the zip?

A shapefile holds one geometry type, and a DGN mixes them on the same levels, so each type is written to its own shapefile inside the zip. Load each one as its own layer in QGIS or ArcGIS.

The layer is nowhere near my basemap. Why?

The coordinate system chosen at conversion did not match the drawing's grid. A wrong choice is written into the .prj and follows the data everywhere, so convert again with the right EPSG code.

Can I view the drawing in Google Earth too?

Yes. Use DGN to KML, and the same elements arrive as paths and polygons over the imagery.

Are closed shapes written as polygons or as lines?

Closed shape elements and complex shapes are written as polygons, line strings and arcs as lines, and zero-length or point elements as points. Linework drawn as an unclosed outline stays a line even if it looks like a boundary, so close those shapes in MicroStation first if you need area features.

Related converters

Ready to convert?

Drop a file and download the result in seconds. Nothing is uploaded, nothing is stored.