Maps and POIs
OSM PBF, OSM XML, Mapsforge maps and Mapsforge POI databases can be combined, clipped and converted to the supported target formats.
MapTools Converter 1.11.0
Supported formats
What the converter imports, how the data is processed, and which output is available.
Clear roles
Maps, orthophotos, elevation and references remain separate
Maps, orthophotos and elevation data are processed and exported as separate content. GPX, ASMAPS, GeoJSON, KML/KMZ and GeoPackage are used only as visible references or for selecting an area.
Orthophotos
Multiband image GeoTIFFs are recognized as orthophotos. Compatible tiles are previewed together, mosaicked and cropped to the selected area as an RGBA GeoTIFF.
Elevation data
Single-band elevation rasters retain their georeferencing. LAS, LAZ and COPC point clouds are locally converted to an elevation raster that retains the highest valid Z value in each cell.
Reference geometry
Points, lines, outer rings and bounding boxes support area selection. Reference files are neither modified nor exported as GIS output.
Archives and companion files
ZIP contents pass bounded path-safety checks. Matching world, PRJ and GDAL AUX files are associated automatically with their primary raster or point-cloud file.
Format matrix
Import, export and limits
“Target format” means that this exact file format is written. An input-only format can still be converted to another supported target format.
| Role | Format | Import | Target format | Processing and limits |
|---|---|---|---|---|
| Map | OpenStreetMap PBF.osm.pbf, .pbf | Yes | Yes | Nodes, ways, relations and tags; referentially complete PBF extracts when every map source is PBF. |
| Map | OpenStreetMap XML.osm, .osm.gz, .osm.bz2 | Yes | Not as XML | OSM schema 0.6 is checked as a stream and materialized locally as a session PBF. .osc and .osh are excluded. |
| Map | Mapsforge map.map | Yes | Yes, v4/v5 | Multiple sources are combined geographically; large areas and multipolygons are reconstructed deterministically. |
| POI | Mapsforge POI.poi | Yes | Yes, v3/v4 | Multiple databases can be clipped spatially and merged into one POI database. |
| Elevation | SRTM HGT.hgt | Yes | Yes | One-degree tiles whose position is derived from the file name. Output uses integer elevation samples. |
| Elevation | DEM GeoTIFF.tif, .tiff, .geotiff | Yes | Yes | Recommended elevation format. Compatible GeoTIFF tiles retain their native CRS, pixel grid, GeoKeys and NoData value. |
| Orthophoto | Image GeoTIFF.tif, .tiff, .geotiff | Yes | Yes | Multiband RGB/RGBA image rasters. Compatible tiles must share the same CRS, resolution and aligned pixel grid; the native projection is preserved. |
| Elevation | ESRI ASCII Grid.asc | Yes | Yes | Transparent text format, but larger and slower than GeoTIFF. |
| Elevation | DTED.dt0, .dt1, .dt2 | Yes | Yes | One-degree cells; fixed grids and integer samples can discard source resolution or fractions. |
| Elevation | XYZ/CSV grid.xyz, .csv | Yes | Not as XYZ/CSV | Three numeric X/Y/Z columns forming a complete, regular row-major grid. Projected values require a matching .prj. |
| Elevation | LAS/LAZ/COPC.las, .laz, .copc.laz | Yes | Not as a point cloud | Withheld points are ignored and the highest Z is retained per raster cell. COPC is read locally and sequentially, not through HTTP ranges. |
| Reference | GPX.gpx | Yes | No | Waypoints, tracks and routes as visible references, polygons or a combined bounding box. |
| Reference | MapTools project.asmaps | Yes | No | Project areas and markers are validated read-only and loaded as references. |
| Reference | GeoJSON.geojson, .json | Yes | No | RFC 7946 / WGS 84; points, lines, outer rings and bounds. Polygon holes are not misrepresented as positive selections. |
| Reference | KML/KMZ.kml, .kmz | Yes | No | Longitude/latitude geometry; KMZ contents pass the same archive and XML safety checks. |
| Reference | GeoPackage.gpkg | Yes | No | Geometry tables and CRS are read from the GeoPackage system tables and transformed to WGS 84. |
| Container | ZIP.zip | Yes | Yes, MapTools package | Mixed supported input; recursive ZIPs are rejected. Output contains a manifest, roles, sizes and SHA-256 hashes. |
Georeferencing
Companion files and CRS
GeoTIFF can use .tfw, .tifw, .tiffw, .wld, .prj and .aux.xml. Embedded GeoKeys and metadata take precedence and are resolved with the locally bundled PROJ runtime. File names are never used to assign a CRS. If an unambiguous embedded CRS is missing, a matching projection file is required. Mosaicking never performs silent reprojection or resampling.
Important for DSM data: a DSM containing height samples remains an elevation model. An aerial image or orthophoto is processed as an image raster. The role can be overridden per file when a GeoTIFF is ambiguous.
Test status
Automatically tested, dataset-specific review required
Synthetic automated tests cover format detection, size and safety limits, CRS transformation, compressed OSM XML, ZIP companions, point-cloud rasterization and reference geometry. Every export also receives structural validation. This does not replace a visual subject-matter review of a concrete source dataset and is not a guarantee for every vendor-specific dialect.
Technical sources
Official specifications and project documentation
These links identify the file formats; they are not recommendations for a particular geodata supplier or licence.
OSM and Mapsforge
Raster and elevation
Point clouds
Reference geometry
Privacy and external content
This page embeds no content, trackers or scripts from the listed third parties. A connection is made only when an external link is deliberately opened, and this page sends no referrer. The respective operators alone are responsible for the content, availability and privacy practices of their sites. A link does not mean that ArxSilex adopts or recommends the linked content.
The converter's GPL-3.0-only licence covers the software only. Input and output data retain their own licences; OpenStreetMap data in particular require ODbL compliance and attribution.