Convert DGN to FILEGDB
Turn DGN documents into FILEGDB. A zipped Esri file geodatabase with one feature class for each kind of geometry among points, lines and polygons, in the source's coordinate system with the attributes as fields.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop DGN files on the dialor turn it to pick what to do
A geodatabase from your MicroStation drawing.One feature class per geometry kind, in the source's coordinate system.
What you get
A zipped Esri file geodatabase with one feature class for each kind of geometry found among points, lines and polygons. The coordinate system of the DGN file is kept, and the attributes become fields.
When the drawing holds more than one kind of geometry, each kind gets its own .gdb folder.
What changes
A column named OBJECTID or SHAPE is renamed with _1. Lists and nested values become JSON text, so they are stored in a text field.
Features without a geometry are left out of the output.
DGN and FILEGDB.What each format is.
The formats
MicroStation Design
MicroStation V7 design files, the CAD drawings of road, rail and utility engineering.
- Extensions
- .dgn
- MIME type
- image
/vnd .dgn - Kind
- Documents
Esri File Geodatabase
An ArcGIS file geodatabase, the .gdb folder of feature classes, zipped to send as one file.
- Extensions
- .gdb.zip
- MIME type
- application
/x -filegdb +zip - Kind
- Text and data
In your code.The same DGN to FILEGDB conversion through the API, for your app or your agent.
$ cv convert report.dgn report.gdb.zip$ cv convert report.dgn report.gdb.zipQuestions.What people ask about DGN to FILEGDB.
Points, lines and polygons. Each kind that appears in the DGN file gets its own feature class.
You get one file, a zip. Inside it, each kind of geometry has its own .gdb folder when there are several.
Yes. The output stays in the coordinate system of the source.
Lists and nested values become JSON text. Their content is kept as text in the field.