The generated GeoPackage will be MBTiles-compatible. The options to control it are: -mbtiles_compatibleĭEFAULT. MapTiler Engine provides a toggle to make the generated GeoPackage conform to the MBTiles specification. Setting the sparse option in GUI is in Advanced options dialog. This is a default option for -store mbtiles and -store geopackage. This option can take longer to render and take more disk space, if there are huge areas between maps, as these have to be created. no_sparseįills the empty space between separate maps (if there is some) with empty tiles in the background colour. This is the default option for -store dir. This option can improve the speed of rendering if there are huge areas between maps. Skip the empty space between separate maps and don’t create empty tiles. Note: for more details on this subject read the section Output in the chapter Usage above. This option specifies the store form explicitly. gpkg then rendering into MBTiles or GeoPackage is selected, respectively. The default is the directory, but in case the -o parameter ends with. Possible options are the directory (dir), the MBTiles (mbtiles) and the GeoPackage (geopackage). This option enforces the form of storage which is used for saving the rendered tiles. Tile store format -store dir|mbtiles|geopackage Maptiler -f png32 -ignore_alpha input_4bands.tif. The color of the background replacing transparency in the non-transparent tile formats. Default background color is white (255,255,255), but you can specify your own with the option: -bg If partly transparent tiles are saved in a tile format without support for transparency (such as JPEG specified with -f jpg option) then the background color is applied. Otherwise, the tile is marked as partly transparent with alpha. opaque, maximum alpha is 255), the alpha channel is discarded and the tile is marked as non-transparent / opaque. If all of the pixels are fully visible (eg. If the tile is completely transparent it is never saved to the disk to save the storage space. The transparency can come from the image itself as an alpha channel (with support for partly transparent areas), it can be derived from a selected color (so-called NODATA color), or can be just a result of the transformation with the GDAL warping algorithm - for areas without available input data.

No matter what input datasets you specify, after transforming them into the tiling profile projection, MapTiler Engine will handle them as RGBA images. RGB WebP image Tile transparency or a background color Progressive JPEG image in the YCbCr color space -f png8 RGBA WebP image Non-transparent formats -f jpg or -f jpeg Formats with support for transparency -f png8aĭEFAULT. MapTiler Engine includes optimization of the final filesize and used a number of colors (quantization), to minimize the disk size occupied by the rendered maps as well as the time necessary to transfer the maps to clients once the tiles are online. The produced tiles can be saved in one of several image format. Maptiler -o tiles map.tif -zoom 0 -1 Tile formats See the appropriate section under the Advanced options chapter for more information.Įxample: command for producing tiles for use with Google Earth: To produce the format for Garmin GPS devices, with a size 1024x1024 pixels and output to. Rendering raster files without a need of georeferencing is also possible. Tile profile specific for Google Earth according to the KML SuperOverlay definition. In case you wish to use different tiling system, you must specify it as the first command on the command line. It uses 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 possibility to specify a custom profile. Output system of tiles - the target coordinate system, tile pixel size, etc. This simplifies 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 behaviour of MapTiler Engine is to write tiles each into its own file, under the directory structure:

Maptiler command line