webp_lossy Lossy WebP compression switch. webp_lossless Lossless WebP compression switch. webp_alpha_quality The quality of WebP alpha channel compression. webp_quality The quality of WebP compression. If you experience issues with the visual quality of generated tiles with quantization involved try to set -quant_speed to lower values. Speed 10 has usually 5% lower quality but is 8 times faster than speed 8. Speed 1 gives marginally better quality at significant CPU cost. Higher speed levels disable expensive algorithms and reduce quantization precision. quant_quality The quality of quantization. jpg_quality The quality of JPEG compression. There are some options to specify parameters of the conversion into image formats, which can significantly reduce the size of produced tiles by degrading the output. 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 Fills 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. sparse 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 Default background color is white (255,255,255), but you can specify your own with the option: -bg The color of the background replacing transparency in the non-transparent tile formats. 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. Tile transparency or a background color ¶ See the appropriate section under the Advanced options chapter for more information.Įxample: command for producing tiles for use with Google Earth: custom You can specify your own tiling system. garmin To produce the format for Garmin GPS devices, with a size 1024x1024 pixels and output to. raster Rendering raster files without a need of georeferencing is also possible. These are the alternatives: -gearth 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. A global option defining the output system of tiles - the target coordinate system, tile pixel size, etc.
0 kommentar(er)
