Convert MAPINFO to GEOJSON
Turn MAPINFO files into GEOJSON. A GeoJSON FeatureCollection in WGS 84 longitude and latitude, as the GeoJSON standard asks, with each feature's attributes as its properties.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop MAPINFO files on the dialor turn it to pick what to do
Map data that opens on the web.A GeoJSON file with every feature's attributes kept as properties.
What you get
A GeoJSON FeatureCollection with coordinates in WGS 84 longitude and latitude, as the GeoJSON standard asks. Each feature's attributes become its properties.
The result is one file, whether the MapInfo upload holds one layer or several.
Coordinates and layers
Coordinates in another system, such as Korea's EPSG:5186, are converted to WGS 84. Data that names no system is taken as WGS 84 when its coordinates fit. When they do not fit, the conversion stops with
unsupported_elements.If the upload holds several layers, they are joined into one FeatureCollection. A layer column names the layer each feature came from.
Going back
To return to MapInfo, use GEOJSON to MAPINFO. The page for every MAPINFO conversion lists the other formats.
MAPINFO and GEOJSON.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
GeoJSON
Points, lines and polygons as JSON, the web's map data format.
- Extensions
- .geojson
- MIME type
- application
/geo +json - Kind
- Text and data
In your code.The same MAPINFO to GEOJSON conversion through the API, for your app or your agent.
$ cv convert report.tab.zip report.geojson$ cv convert report.tab.zip report.geojsonQuestions.What people ask about MAPINFO to GEOJSON.
A zipped MapInfo TAB table with its .dat, .map and .id parts, or zipped MIF and MID interchange files. The extensions are tab.zip and mif.zip.
If they are in another system, such as EPSG:5186, they are converted to WGS 84 longitude and latitude. Coordinates already in WGS 84 stay as they are.
Each feature's attributes become its properties in the GeoJSON.
The data names no coordinate system, and its coordinates do not fit WGS 84. The conversion cannot tell which system they are in, so it stops.