Convert FGB to MAPINFO
Turn FGB 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 FGB files on the dialor turn it to pick what to do
A zipped MapInfo table from FGB.Your map features arrive as one file with the attributes as columns.
What you get
One zip file holding a MapInfo table with its .tab, .dat, .map and .id parts. It stays in the coordinate system of the FGB file, and the attributes become columns.
Text is stored as UTF-8 under MapInfo's neutral character set.
What changes
Coordinates are rounded to the grid that MapInfo's bounds allow. For systems in meters, that is about a centimeter.
Lists and nested values become JSON text in their columns.
To go the other way, use MAPINFO to FGB.
FGB and MAPINFO.What each format is.
The formats
FlatGeobuf
FlatGeobuf, a compact binary format for map features that streams over the web.
- Extensions
- .fgb
- MIME type
- application
/flatgeobuf - 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 FGB to MAPINFO conversion through the API, for your app or your agent.
$ cv convert report.fgb report.tab.zip$ cv convert report.fgb report.tab.zipQuestions.What people ask about FGB to MAPINFO.
One zip file with the .tab, .dat, .map and .id parts of a MapInfo table. The attributes are columns.
No. The table keeps the coordinate system of the source.
They are rounded to the grid MapInfo's bounds allow. For systems in meters, that is about a centimeter.
They become JSON text.