

gearthTile profile specific for Google Earth according to the KML SuperOverlay definition.-rasterRendering raster files without a need of georeferencing is also possible.-garminTo produce the format for Garmin GPS devices, with a size 1024x1024 pixels and output to. In case you wish to use a different tiling system, you must specify it as the first command on the command line. It uses a coordinate system defined as EPSG:3857 or EPSG:900913. The spherical Mercator tile profile compatible with Google, Bing, Yahoo Maps, MapQuest, OpenStreetMap, and mobile maps on iOS and Android. MapTiler Engine comes with these predefined most popular systems and the possibility to specify a custom profile.

Available output options Tiling profile / Tile Matrix SetĪ global option defining the output system of tiles - the target coordinate system, tile pixel size, etc. Only arguments specified BEFORE the input filenames are applied to all files!Īrguments that should be applied only to a single file are specified AFTER the name of such file (for example zoom level range specific only to that file) and has higher priority than the global options. The global options apply to all input files, in other words: This simplifies the transfer and management of the tilesets and is practical for mobile applications. MapTiler Engine supports direct output of the rendered map tiles into an SQLite database (MBTiles or GeoPackage format). The produced directory structure contains also a simple HTML viewer and description of the dataset in metadata.json, compatible with mb-util and TileServer project supporting OGC WMTS standard. Where z is the zoom level, and x and y tile coordinates on relevant zoom level in the tiling profile. The default behavior of MapTiler Engine is to write tiles each into its own file, under the directory structure:
