Convert MAPINFO to FILEGDB

Turn MAPINFO files 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 MAPINFO files on the dialor turn it to pick what to do

A geodatabase from your MapInfo tables.One zipped file with a feature class for each kind of geometry.

  1. What you get

    A zipped Esri file geodatabase. It holds one feature class for each kind of geometry in the source: points, lines and polygons. The coordinate system of the source is kept, and the attributes become fields.

    When the source has more than one kind of geometry, each kind gets its own .gdb folder.

  2. What changes

    A column named OBJECTID or SHAPE is renamed with _1 added to the end. Lists and nested values become JSON text.

    Features without a geometry are left out, so they do not appear in the geodatabase.

  3. Several layers

    When the source has several layers, they are joined into one. A layer column names where each feature came from, so you can still tell the layers apart.

    If you need the data back in MapInfo, FILEGDB to MAPINFO goes the other way.

MAPINFO and FILEGDB.What each format is.

The formats

From · MAPINFO

MapInfo Table

MapInfo TAB tables zipped with their .dat, .map and .id parts, or MIF and MID interchange files, from MapInfo Pro.

Extensions
.tab.zip .mif.zip
MIME type
application/x-mapinfo+zip
Kind
Text and data
To · FILEGDB

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 MAPINFO to FILEGDB conversion through the API, for your app or your agent.

terminal
$ cv convert report.tab.zip report.gdb.zip
$ cv convert report.tab.zip report.gdb.zip

Questions.What people ask about MAPINFO to FILEGDB.

01OF 04

Yes. The output uses the coordinate system of the source.

They are left out of the geodatabase.

It is renamed with _1 added, so OBJECTID becomes OBJECTID_1 and SHAPE becomes SHAPE_1.

Yes. The layers are joined into one, and a layer column names the layer each feature came from.

More conversions.Other ways in and out of MAPINFO and FILEGDB.