SuperMap iServer supports version management for map tiles that are stored in distributed places to distinguish tiles created at different time for the same map of the same bounds and scale, which assists tile management of users and supports viewing tiles of history versions.

Version ID is UUID automatically generated by the system for map tiles created every time. Version ID is unique for a map tile version. For a map, the system will assign a version ID for the tile when a tile task is created for the first time, and the parent version number is null because the current version is the first version. When new versions are generated, the system will automatically assign parent version for it.

tile set version for caching

While Creating caching task, if the distributed tile repository indicated by the parameters passed already has map tiles with the same map name, tile size, and transparency setting, that is, tile set name is identical with existing tile set, after you click the Create Tiling Task button at the bottom of the page, the system will prompt that in the tile library "Tile already exists. Do you want to create a new version or append tiles?"

Create new-version tiles

Select "Yes", the system will create a new version. And it will re-cache all the tiles according to your settings.

  1. Select "Yes", the system will create the newest version for the tile and generate the ID to uniquely identify the version.
  2. You can input the descriptive information for the version. The default information is the creation time of the current version.
  3. Click OK to finish the creation of the tiling task.

Check the tile set in the distributed tile repository above, you can view the number of the newest version of the tile set and the parent version number.

While Configuring to use the cached tiles, the tile set of the newest version in the distributed tile library will be employed.

Append tiles

If you choose to append tiles in to an existing-version tile set, the system will partitioning tiles according to your new tiling settings, and then append the new tiles into the existing-version tiles set. If the current tile data is changed compared with the existing-version, the changed tile will be automatically updated.

Steps:

  1. Select Append tiles
  2. Click OK to start caching

Configure to use the historical-version tiles

You can adopt the following methods to use map tile of the specified version while using distributed tile repository:

  1. Determine the version number of the tiles set that needs to be employed
  • Method 1: In WebManager, click Cluster>Data Registration, click the needed storage ID, tileset name to view all versions of the current tileset, select the version needed and record the version number.
  • Method 2: View all versions of the specified storage ID, map name, picture format, picture size, and transparency setting through the tileVersions resource, and select suitable version in those versions.
  • Method 3: View the current map's tile set and version information through tilesets resource
  1. Use multi-version tiles
  • Method 1: Specify version number for the requested tile through the tileVersion parameter of the tileImage resource

Example: Get tiles according to the specified version

http://supermapiserver:8090/iserver/services/map-world/rest/maps/WorldMap/tileImage.png?scale=0.00000002&x=9&y=2&width=256&height=256&tileversion=51de5c76-c994-4207-94a7-d31f948f56e3

  • Method 2: Browser multi-version-tile map using JavaScript representation

Example 1: Browser with JavasScript representation of map services

http://supermapiserver:8090/iserver/services/map-china400/rest/maps/China.ijs#5.408523429128511e-8/12016024.995088/4414132.6990077

Example 2: Quickly publish multi-version tile set into map services, then browser with JavasScript representation

http://supermapiserver:8090/iserver/services/map-mongodb-china400/rest/maps/China.ijs#5.408523429128511e-8/12016024.995088/4414132.6990077