Convert OSM to MAPINFO
Turn OSM 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 OSM files on the dialor turn it to pick what to do
OpenStreetMap data as a MapInfo table.Points, lines and polygons with their tags as columns, in one zipped table.
What you get
One zipped MapInfo table with its .tab, .dat, .map and .id parts. It keeps the source's coordinate system, and the attributes become columns.
Tagged nodes become points. Ways become lines, or polygons when they are closed and tagged as areas. Route and multipolygon relations become multilines and multipolygons.
How tags are stored
Common tags such as name, highway and building become columns. All other tags are kept as JSON text in the other_tags column.
Text is stored as UTF-8 under MapInfo's neutral character set. Lists and nested values also become JSON text.
What changes or is dropped
Coordinates are rounded to the grid MapInfo's bounds allow. For systems in meters, that is about a centimeter.
Untagged nodes, other kinds of relations, versions and authors are dropped.
If the file has several layers, they are joined into one table. A layer column names where each feature came from.
OSM and MAPINFO.What each format is.
The formats
OpenStreetMap Data
OpenStreetMap nodes, ways and relations with their tags, as .osm XML or the smaller .osm.pbf.
- Extensions
- .osm .osm.pbf
- MIME type
- application
/vnd .openstreetmap .data +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 OSM to MAPINFO conversion through the API, for your app or your agent.
$ cv convert report.osm report.tab.zip$ cv convert report.osm report.tab.zipQuestions.What people ask about OSM to MAPINFO.
Yes, in one place or another. Common tags such as name, highway and building get their own columns, and the rest are kept as JSON in other_tags.
No. The table stays in the coordinate system of the source.
No. Route and multipolygon relations are converted. Other relations are dropped.
They are dropped. Only tagged nodes become points.