If empty no data copyright will be displayed for the custom map. This copyright will only be used when using the CustomMap from above. This value is the amount of cache to be used in addition to the bare minimum.Ĭustom data copryright string is used when setting the Map::activeMapType to MapType.CustomMap via urlprefix parameter. Note that the texture cache has a hard minimum size which depends on the size of the map viewport (it must contain enough data to display the tiles currently visible on the display). The default size of the cache is 6 MiB when bytesize is the cost strategy for this cache, or 30 tiles, when unitary is the cost strategy.
The default value for this parameter is bytesize. Using unitary, they will be interpreted as number of tiles. Using bytesize, the related size parameter ( .size) will be interpreted as bytes. The cost strategy to use to cache decompressed map tiles in memory. The default size of the cache is 3 MiB when bytesize is the cost strategy for this cache, or 100 tiles, when unitary is the cost strategy. The cost strategy to use to cache map tiles in memory. The default size of the cache is 50 MiB when bytesize is the cost strategy for this cache, or 1000 tiles, when unitary is the cost strategy. The default value for this parameter is bytesize.ĭisk cache size for map tiles.
The cost strategy to use to cache map tiles on disk. On systems that have no concept of a shared cache, the application-specific QStandardPaths::CacheLocation is used instead. The default place for the cache is the QtLocation/osm subdirectory in the location returned by QStandardPaths::writableLocation(), called with QStandardPaths::GenericCacheLocation as a parameter. Instructs the plugin to include Nominatim-specific information (such as geometry and class) into the returned Location objects, exposed as extendedAttributes.Ībsolute path to map tile cache directory used as network disk cache. Instructs the plugin to inject the query url to nominatim into the geocode reply, for debugging purposes. Note: The API documentation is available at Project OSM Nominatim.
0 kommentar(er)
