The distributed tiling module of iServer supports the segmentation of 3D tiles from image and terrain data in 3D service scenarios, and stores them in MongoDB. The method of using distributed tiling function to split 3D tiles is basically the same as the process of 2D map tiles, with only slight differences in the specific parameter settings.
Access the service manager Web Manager, which is the master node for tiling, click the "Clusters" and "Distributed tiling Service" pages in turn, and then click "Add New Task". Set service components, 3D scene, layer, tile type, storage type, cache scale and other related parameters.
Basic setting
- Service component: The service components list displays all service components that have been published by the server. Please select a 3D component to be cut (currently, only 3D components published by workspace can be cut).
- Scene: All scenes contained in the current service components. Please select a 3D scene to be cut.
- Layer: All 3D images and 3D terrain layers in the current scene. Please select a layer to be cut.
- Tile type: The tile type corresponding to the selected layer. For example, the tile type corresponding to the image layer is "3D image".
- Storage type: Specifies the storage type of the generated tile. Currently only supports storing 3D tiles via MongoDB.
- Storage ID: The identification of the distributed storage location requires selecting the ID of the MongoDB distributed slicing library that has already been created. If a storage location has not been created yet, please add a distributed tiles storage .
- Scale scheme: Used to assist in determining the scale level of tiling. The scale options are:
- Tianditu, the scale scheme used by Tianditu, please refer to Table 1 for the specific scale level. Among them, the Tianditu website uses a scale of 2 to 18 by default, and you can choose according to your needs.
- Recommended scale, the scale scheme recommended by the system
- Custom scales, where you manually enter the scale as needed
- Cache scale: the currently set scale in the list box. You can enter a scale denominator in the text box and click "Add Scale Denominator" to add it to the list of scales, you can also removing unwanted scales from the list.
Advanced setting
- Cache bounds: It is used to specify the geographical range of tiling. The format is: -180, -90, 180, 90. The default is the full extent of the current layer.
- Original point: Calculate the starting coordinate point of the row and column number of the tile, which is the upper left corner of the cache range by default.
- Picture Format: When tile type is 3D image tile, supported tile formats include PNG, JPG, GIF, DXTZ, and WebP. Where DXTZ is a compression format for DDS format (DirectDraw Surface, DirectX Texture Compression Format) images. This type of texture compression greatly reduces texture memory consumption and is recommended DXTZ format. When the tile type is a 3D terrain tile, the default storage format is the bil grid data file format.
In addition, the default size of 3D tiles generated by image cutting is 256 * 256 pixels.
Add tile version and append tile
After setting the above parameters, click the "Create tile task" button to create a task.
If there are already 3D tiles of the same layer in the storage location specified by the above parameters, new tiles not in the original geographic range or scale will be added to the slice set after the task is created, or the existing tiles in the same location will be overwritten.