Convert KML to MAPINFO
Turn KML 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 KML files on the dialor turn it to pick what to do
A MapInfo table from your KML.One zipped table with the attributes as columns.
What you get
A single zipped MapInfo table with its .tab, .dat, .map and .id parts. It keeps the source's coordinate system, and the attributes become columns.
If the KML has several layers, they are joined into one table. A layer column names the layer each feature came from.
What changes
Text is stored as UTF-8 under MapInfo's neutral character set. Coordinates are rounded to the grid that MapInfo's bounds allow, which is about a centimeter for systems in meters.
Lists and nested values have no column type of their own, so they become JSON text.
Going back
To return to Google Earth, MAPINFO to KML converts a MapInfo table back to KML.
KML and MAPINFO.What each format is.
The formats
KML
Placemarks, paths and polygons for Google Earth.
- Extensions
- .kml
- MIME type
- application
/vnd .google -earth .kml +xml - 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 KML to MAPINFO conversion through the API, for your app or your agent.
$ cv convert report.kml report.tab.zip$ cv convert report.kml report.tab.zipQuestions.What people ask about KML to MAPINFO.
You get one file: a zip holding the .tab, .dat, .map and .id parts of a MapInfo table.
The same one as the KML source. It is not changed to another system.
The layers are joined into one table. The layer column tells you which layer each feature came from.
Slightly. They are rounded to the grid MapInfo's bounds allow, about a centimeter for systems in meters.