Configuring to use the cached tiles

Tiles generated through Distributed Map Tiling service, including map tiles, vector tiles, and attribute tiles can be used automatically by the map, with no need for additional configuration. For a map service and existing tile, mapping request methods from the client includes:

• Browse the map through flash, flash3d, javascript, vectortile, silverlight representation of the map resource. You need to ensure that the fixed scales of the map be identical to scales of existing tiles and parameters for requesting map like picture format be identical to those of the existing tile.
• Send request to server through the tileImage resource, which allows you to request specified tile according to parameters such as scale, tile row, tile column, tile formats, etc. Request parameters need to be identical to those of the requested tile.
• Develop a map browsing script through the iClient and send request to map service. Request parameters need to be identical to those of the requested tile.

Of course, if you modified the default storage path or other custom settings, you can use these tiles through manual configuration. Among which, UGCV5 format tiles can be used through configuring Map service provider. FastDFS、MongoDB、SMTiles、MBTiles、UTFGrid、SVTiles tiles can be used through configuraitng Map service component.

• Configure to use SuperMap UCG map tiles
• Configure map component for using other tiles
  • Universal configuration
  • distributed tile repository configuration

Configure to use SuperMap UCG map tiles

SuperMap UGC map tiles can be generated through Distributed Tiling service or SuperMap iDesktop, SuperMap iObjects. Versions include5.0, 4.1, etc. Please refer to SuperMap UGC map tiles versions for details.

For generated SuperMap UGC tiles, you first need to make sure that the corresponding map has been published as map service, then you can use the map tiles through configuring the map service provider, SuperMap UGC5.0 tiles for instance. During operation, you can configure service provider through WebManager, or directly Modify XML service configuration. Take local map service provider as an example, open WebManager and enter the configuration page for the map providers, (http://<server>:<host>/iserver/manager/providers/<Map Service Provider Name>), set cache version in advanced settings (that is, version of SuperMap UGC map tiles), click Save to take effect.

SuperMap UGC map tiles used by SuperMap iServer are stored in picture output path, that is, [SuperMap iServer installation directory]\webapps\iserver\output\cache\, by default. Please refer to SuperMap UGC map tiles versions for specific paths of different SuperMap UGC map tile versions.

While using SuperMap UGC tiles, if the storage path of the map tiles are not paths described above, you need to copy the Map Tile to the corresponding paths. Also, you can modify the cache output path of the corresponding map service provider (<outputPath>../webapps/iserver/output</outputPath>) to make it identical to storage path, therefore ensuring that the map service can properly use the SuperMap UGC tiles.

Configure map component for using other tiles

We can use FastDFS, MongoDB, SMTiles map tiles, SVTiles vector tiles, UTFGrid attribute tiles through configuring map service components.

Modifying the configuration of map service components can be realized through WebManager or Modifying service configuration file.

Universal configuration

Open WebManager and enter the page for map service component configuration (http://<server>:<host>/iserver/manager/components/<Map Service Component Name>), check "Enable Cache" and set following parameters:

• Enable Cache: Whether to enable caching or not.
• Cache Read-only or not: Determines whether the cache files are editable or not. If checked, generated cache files will be read-only. If not checked, existing tile files will be able to be dynamically updated.
• Cache Survival Time: The survival time of the cache is calculated from the creation of the cache.The unit is minutes. 0 indicates that the cache will survive forever. This configuration is only valid for SMTiles cache, attribute tile cache, and vector tile cache.
• Use map tiles: Support SMTiles, FastDFS, MongoDB storage formats. If FastDFS or MongoDB format is selected, existing storage location needs to be imported or a new storage location needs to be added. If the newly added storage location is used by following tile service, the generated tiles will be automatically used by the current map service.
• Use attribute tiles: Currently support UTFGrid attribute tiles, and the default storage location is [SuperMap iServer installation directory]\webapps\iserver\output\sqlite\.
• Use vector tiles: Currently support SVTTiles tiles, and the default storage location is [SuperMap iServer installation directory]\webapps\iserver\output\sqlite\.

During configuration for SMTiles format, existing SMTiles (*.smtiles) will be employed for mapping of map services by default. However, if the current map service and mapping request are compliant to MBTiles rules and there are MBTiles (*.mbtiles) in the cache directory, the map service will employ existing MBTiles.

distributed tile repository configuration

For tiles in distributed tile repositories, you can click Configure to Map Service button corresponding to distributed tile repository on the distributed tile repository, select service component corresponding to map in the tile library to realize fast configuration.

While selecting service component:

• If there are no tiles for the current map component in the tile library, tiles will be able to be stored to tile library dynamically by default after configuring to map service component.
• If there are already tiles for the current map component in the tile library, the tile library will be readonly by default.

After configuring distributed tile repository to map service, the corresponding map service will employ the tileset of the newest version in the distributed tile repository for mapping by default.

If you need to configure tilset of old version, please refer to Configure to use the historical-version tiles .