Convert MAPINFO to FGB
Turn MAPINFO files into FlatGeobuf. A FlatGeobuf with the features and their attributes in the source's coordinate system and a spatial index.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop MAPINFO files on the dialor turn it to pick what to do
MapInfo tables as one FlatGeobuf file.Features and attributes keep their coordinate system and get a spatial index.
What you get
One FGB file with the features and their attributes. The coordinate system of the source is kept, and the file has a spatial index.
The input is a zipped MapInfo TAB table or a zipped MIF and MID pair. FlatGeobuf is a compact binary format for map features that streams over the web.
What changes
Features without a geometry are left out of the FGB file.
Lists and nested values become JSON text.
When the source has several layers, they are joined into one. A layer column names the layer each feature came from.
Going back
To return to MapInfo, use FGB to MAPINFO. For other options, see every FGB conversion.
MAPINFO and FGB.What each format is.
The formats
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
FlatGeobuf
FlatGeobuf, a compact binary format for map features that streams over the web.
- Extensions
- .fgb
- MIME type
- application
/flatgeobuf - Kind
- Text and data
In your code.The same MAPINFO to FGB conversion through the API, for your app or your agent.
$ cv convert report.tab.zip report.fgb$ cv convert report.tab.zip report.fgbQuestions.What people ask about MAPINFO to FGB.
Yes. The features stay in the coordinate system of the source.
The layers are joined into one. A layer column tells you which layer each feature came from.
No. Features without a geometry are left out.
They become JSON text.