Merge Tiles

Instructions for use

SuperMap iDesktop supports the Merge Tiles function, which can merge tiles stored in different MongoDB databases and Merge to Existing Tile MongoDB Tiles. Or a Merge to New MongoDB database.

It can be used to integrate the data of different regions or the data of different periods in the same region, which avoids the repeated cutting of the user and improves the work efficiency. For example, there is a MongoDB database cache for the annual precipitation data of the same place, and the annual data can be merged into a MongoDB database to make a Multi-version Cache.

Merge Tiles Condition

Before

MongoDB Merge Tiles, make sure that the MongoDB service is started locally, and the merged Tile also needs the following conditions:

  • Merge Tiles coordinate systems agree.
  • Tile block size is consistent.
    • The source coordinates
  • of Merge Tiles are consistent, and the source coordinates, i.e. Index Bounds, are consistent, which can be adjusted to be consistent during Generate Map Tiles and Tile Bound sParameter Settings.
  • Merge Tiles has the same type of picture.

Note: Merge Tiles must meet the above four conditions at the same time to be merged successfully. Otherwise, you will be prompted with the Union failed.

.

Function entrance

Map tab-> Data-> Tile Management button to pop up the MongoDB Tile Management window.

Operating instructions

  1. Add Tile: Add the MongoDB Tile to be merged. For detailed operations, see the Add a MongoDB Tile.
  2. Merge Tiles: Click the Merge button in the toolbar to pop up the Merge MongoDB Tiles dialog box.
      Set the storage mode of merged data
    • on the left side of the dialog box. The program provides two modes:
      • Method 1: Merge to Existing Tile, that is, to merge the data of multiple versions into the Tile Data of an existing version, click the drop-down box on the right, and select Tile Name from the drop-down list.
      • Method 2: Merge to New, namely, set a new MongoDB database as the storage location of the merged data. Enter the following MongoDB Tile parameters: Server Name, Database Name, and set the name of the merged Tile (that is, the name of the Tile root).
    In the " Settings" area on the right side of the
  3. dialog box, set the Tile participating in the merge, the merge order, and the Target Version after the merge:
    • Participate in merging version: check the Tile participating in merging in front of the Tile list;
    • Tile Order: The upper and lower order of the tiles in the list affects the Union Result. Adjust the merging order of the tiles through the order adjustment button on the upper side of the Tile list box. The order of the merge operation is from top to bottom. Merge Tiles1 and Tile2 are taken as examples in the following figure:
    Tile Name
    Tile sort
    Illustration
    		When the merging order is 1 before 2 or Tile2 is merged into Tile1, the overlapped part is Tile2 covering Tile1
    		When the merging order is 2 before 1 or Tile1 is merged into Tile2, the overlapping part is Tile1 covering Tile2

    Merge Tiles Overlap Processing:

    • When the merged Tile image type is PNG and Background Transparency is selected, the Tile overlapping area program will perform fusion processing, which can be used to deal with the problem of data merging.
    • When Merged Tile Type: is selected as the JPG _ PNG format, the file format of the slice (at the boundary of the map) containing invalid data pixels is PNG, otherwise it is JPG. The Tile overlapping area program can automatically judge which format to use according to whether the tile contains invalid data pixels, and can be used to solve the white image problem at the edge of the tile.
    • Except for the above two types of Tile Type:, the overlapping areas of other types of Merge Tiles are covered in the order of Merge Tiles.
  4. Target Version: supports merging multiple versions into one version, and supports merging multiple versions into one database.
    • If you want to merge multiple versions into one version, the name of Target Version here should be set to the same name. For example, if you merge the Digital Maps of Sichuan Province and Qinghai Province into one data, the names of Target Version here are the same.
    • If different versions of different databases are merged into multiple versions of the Current Data database, the names of different versions can be kept, that is, different versions under the same database. For example, the precipitation data of different months in five databases are merged into different versions under one database, and different Versions are maintained here.
  5. Enable multi-process merging: Support setting of multi-process Merge Tiles. The user can reasonably set the number of processes according to the machine resources to improve the merging performance.

  6. Click OK to execute the merge operation. After the merge is completed, a prompt indicating that the merge is successful will be displayed in the Output Window. You can view the merged Tile Data through the Load MongoDB Tile ".

Application example

The Raster Tile data of global halo rendering is divided into upper and lower parts, which are stored in the local and MongoDB respectively. Now, the two parts of data need to be merged into one part for use. The results shown in the following figure are obtained through the Merge Tiles function:

Figure: Local Tiles and MongoDB Merge Tiles Result

Related topics

Tile Management

Map Tiles