Maptiler request count install#
Maptiler request count full#

In general, requirements will range from 10-20GB of storage, 4GB of memory, and a modern dual-core processor for a city-sized region to 1TB of fast storage, 24GB of memory, and a quad-core processor for the entire planet. Depending on the size of the area youвЂ™re interested in serving and the traffic you expect the system requirements will vary. Serving your own maps is a fairly intensive task.

Maptiler request count install#

Install locally on Debian 11, Ubuntu 22.04, Ubuntu 20.04 or Ubuntu 18.04. If you are setting up your own tile server, we recommend that you use Ubuntu Linux or Debian 11. This section explains how.Д«oth generating and serving tiles incur significant hardware requirements, especially if you need global coverage and regular updates.

Maptiler request count full#

However, if youвЂ™d like to take full control of your destiny, you can render and serve your own tiles. The TileServer-GL will try to find the file switzerland.mbtiles in root + mbtiles path.ДЄlternatively, you can use mbtiles://.pbf' will instruct TileServer-GL to look for the files such as fonts/Open Sans/0-255.pbf ( fonts come from the paths property of the config.json example above).Tiles from a third-party provider are the simplest way to make the switch to OpenStreetMap, and offer clarity of cost. To specify that you want to use local mbtiles, use to following syntax: mbtiles://switzerland.mbtiles. You can link various data sources from the style JSON (for example even remote TileJSONs). The mbtiles file does not need to be specified here unless you explicitly want to serve the raw data.

format and bounds can be especially usefulД®ach item specifies one data source which should be made accessible by the server.

tilejson - properties to add to the TileJSON created for the raster data.

serve_data - whether to allow access to the original tiles, sprites and required glyphs.

serve_rendered - whether to render the raster tiles for this style or not.(can also be specified per-style).Д®ach item in this object defines one style (map). Optional string to be rendered into the raster tiles (and static maps) as watermark (bottom-left corner).Д¬an be used for hard-coding attributions etc. It is recommended to also use the serveAllFonts option when using this option. The process will also watch for changes in this directory and remove/add more styles dynamically. If this option is enabled, all the styles from the paths.styles will be served. If you need to conserve memory, try lower values for scale factors that are less common. if you have four processors, try a value of. If you have plenty of memory, try setting these equal to or slightly above your processor count, e.g. The value and considerations are similar to minRendererPoolSizes above. Maximum amount of raster tile renderers per scale factor. If you need to conserve memory, you'll want something lower than maxRendererPoolSizes, possibly allocating more renderers to scale factors that are more common.Дefault is. If you have plenty of memory, you'll want to set this equal to maxRendererPoolSizes to avoid increased latency due to renderer destruction and recreation. Selecting renderer pool sizes is a trade-off between memory use and speed.ДЄ reasonable value will depend on your hardware and your amount of styles and scale factors. If the array has less elements than maxScaleFactor, then the last element is used for all remaining scale factors as well. The value is an array: the first element is the minimum amount of renderers for scale factor one, the second for scale factor two and so on. Minimum amount of raster tile renderers per scale factor. This is useful for resolving the issue with cropped labels,Д«ut it does come with a performance degradation, because additional, adjacent vector tiles need to be loaded to generate a single tile.Дefault is 0 to disable this processing.

Maximum image side length to be allowed to be rendered (including scale factor).Д«e careful when changing this value since there are hardware limits that need to be considered.ДЄdditional image side length added during tile rendering that is cropped from the delivered tile. Maximum scale factor to allow in raster tile and static maps requests (e.g. Quality of the compression of individual image formats.

Use false to disable the front page altogether (404). Use true (or nothing) to serve the default TileServer GL front page with list of styles and data. Path to the html (relative to root path) to use as a front page. This can be used for basic load-balancing or to bypass browser's limit for the number of connections per domain. You can use this to optionally specify on what domains the rendered tiles are accessible. The value of root is used as prefix for all data types. 'bounds': Дefines where to look for the different types of input data.