Convert GDB to MAPINFO
Turn GDB files into MAPINFO. A zipped MapInfo table with its .tab, .dat, .map and .id parts, in the source's coordinate system with the attributes as columns.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop GDB files on the dialor turn it to pick what to do
Garmin waypoints, routes and tracks as a MapInfo table.One zipped table with points, lines and multilines, and the attributes as columns.
What you get
A zip with the MapInfo table in its .tab, .dat, .map and .id parts. It keeps the coordinate system of the source, and the attributes become columns.
Waypoints become points. Routes become lines. Tracks become multilines with one part for each segment.
Every point of a route or track also becomes a point of its own. It carries its time in UTC and the values the device logged with it, such as satellites, heart rate as hr and cadence as cad.
How the columns work
A layer column names the GPX layer each feature comes from: waypoints, routes, tracks, route_points or track_points. The columns track_fid and route_fid tie each point to its track or route.
Columns that no feature fills are left out, so the table holds only the columns your file uses.
What changes
Text is stored as UTF-8 under MapInfo's neutral character set. Lists and nested values become JSON text.
Coordinates are rounded to the grid MapInfo's bounds allow. For systems in meters, that is about a centimeter.
The shapes are written in 2D. Only the ele column of points keeps heights, so lines and multilines carry no heights of their own.
GDB and MAPINFO.What each format is.
The formats
Garmin MapSource Database
Waypoints, routes and tracks saved by Garmin MapSource and BaseCamp in their GDB database.
- Extensions
- .gdb
- MIME type
- application
/x -garmin -gdb - Kind
- Text and data
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
In your code.The same GDB to MAPINFO conversion through the API, for your app or your agent.
$ cv convert report.gdb report.tab.zip$ cv convert report.gdb report.tab.zipQuestions.What people ask about GDB to MAPINFO.
It is a zipped table with its .tab, .dat, .map and .id parts. All the features of the GDB file go into this one file.
Tracks become multilines, with a part for each segment. Each track point also becomes a point of its own, tied to its track by track_fid.
Only on points, in the ele column. The shapes of routes and tracks are written in 2D.
They are rounded to the grid MapInfo's bounds allow. For systems in meters, that is about a centimeter. For more on this format, see every MAPINFO conversion.