Generate Tiles from Model

Usage Instructions

This tool can be used to generate a specified single model dataset into S3M tile data.

Parameter Descriptions

Parameter Name Parameter Description Parameter Type
Model Dataset: Select the source model dataset DatasetVector
Tile Name:
(Optional)		 Set the name of the resulting tile data String
Storage Path: Set the storage path for the resulting tile data String
S3M Version:
(Optional)		 Set the S3M tile version number, including S3M 1.0, S3M 2.0, S3M 3.0, S3M 3.01 S3MVersion
Target Coordinate System
(Optional)		 Set the coordinate system of the resulting tile data by entering an EPSG code or using a coordinate system file. Combined with the conversion method and projection conversion parameters, coordinate transformation of data can be achieved.
The coordinate system file only supports *.prj and *.xml files generated by functions such as Export Coordinate System in iDesktopX.
When the EPSG code is set to 0, no coordinate transformation will be performed, and the source coordinate system remains unchanged.
Coordinate system setting restrictions:
  • If the source data is in a planar non-projected coordinate system, the resulting coordinate system can only be set to a planar non-projected coordinate system.
  • If the source data is in a geographic or projected coordinate system, the target projection cannot be set to a planar non-projected coordinate system.
 String
Conversion Method
(Optional)		 Select the method for data coordinate system conversion via a dropdown menu. Options include:
1. Geocentric Translation (3-para): Suitable for geocentric three-parameter coordinate conversion.
2. Molodensky (3-para): Molodensky three-parameter conversion method.
3. Abridged Molodensky (3-para): Simplified three-parameter conversion method.
4. Position Vector (7-para): A seven-parameter conversion method.
5. Coordinate Frame (7-para): Geocentric seven-parameter conversion method.
6. Bursa-Wolf (7-para): A commonly used seven-parameter conversion method.
7. Molodensky-Badekas (10-para): A ten-parameter spatial coordinate conversion model.
8. China_3D_7P (7-para): Used for conversion between different coordinate systems and the China Geodetic Coordinate System 2000 (CGC2000). Suitable for control point coordinate conversion between geodetic coordinate systems with different earth ellipsoid baselines at national and provincial levels (3 degrees and above). The conversion method involves three translation parameters, three rotation parameters, and one scale parameter, while also considering the differences in the semi-major axis and flattening of the two corresponding earth ellipsoids.		 CoordSysTransMethod
Projection Conversion Parameters
(Optional)		 Set the parameters for data projection conversion, including scale difference, rotation angle, offset, rotation origin, etc. Specific parameter values are specified by the Projection Conversion Parameters tool. CoordSysTransParameter
Texture Compression Format:
(Optional)		 Set the texture compression format for data, including WebP, DXT, CRN_DXT5, KTX2.0. It is recommended to use different texture compression types for data with different purposes to reduce video memory usage.
  • WebP: Recommended for tile data used on mobile devices, supports transparent textures.
  • DXT: When selected, the resulting data has the smallest video memory footprint, shortest processing time, and largest total data size.
  • CRN_DXT5: When selected, the resulting data has a slightly smaller video memory footprint, longest processing time, and largest total data size.
  • KTX2.0: Works on both PC and mobile, but transparent textures are not supported on mobile devices.
Note: In iServer 11.1.1 and later versions on Linux, the corresponding parameter value must be set based on whether this node depends on concurrent processing.
  • If this node depends on concurrent processing, the texture compression type cannot be set to CRN_DXT5.
  • If this node does not depend on concurrent processing, all parameter values can be set. However, if the texture compression type is set to CRN_DXT5, the LD_PRELOAD parameter in the product package/bin/setenv.sh file must be temporarily commented out with a # symbol before starting iServer to ensure normal tile generation; otherwise, the tile generation process may become abnormal and result data cannot be generated.
 CompressedTextureType
Vertex Optimization Type:
(Optional)		 Set the vertex optimization type for data. Different S3M versions support different optimization types.
  • S3M 1.0 and S3M 2.0 support setting to no compression.
  • S3M 3.0 and S3M 3.01 support setting to no compression or MeshOpt compression.
    • No Compression: No compression is applied to the data.
    • MeshOpt Compression: Uses a series of algorithms to reduce data mesh complexity, thereby improving rendering efficiency and reducing data size.
 VertexOptimizationType
Tile Side Length (M):
(Optional)		 Set the side length of tiles in meters. Different tile side lengths correspond to different scales. When data is dense and both geometry and texture are simple, the tile side length can be set to a larger value, such as 1000. When data is sparse or geometry/texture is complex, the tile side length can be set to a smaller value, such as 200. Double
Scene Type:
(Optional)		 Set the scene type of the resulting tile data, including Planar and Spherical. The default value is Spherical.
  • If the source data is in a geographic coordinate system, this parameter can only be set to Spherical.
  • If the source data is in a projected coordinate system, the scene type is unrestricted and can be selected as needed.
  • If the source data is in a planar coordinate system without projection, this parameter can only be set to Planar.
 SceneType
Filter Threshold:
(Optional)		 Set a threshold to filter smaller sub-objects (smaller than the threshold) in the rough layers of the data, thereby improving rendering performance for large scene data. The default value is 2, in pixels. Double
Tile File Type:
(Optional)		 Set the tile file type, including S3MB and S3MBLOCK.
  • S3MB: An open and extensible compressed tile data format.
  • S3MBLOCK: A tile large-file data format, mostly used for fine models, effectively solving the problem of oversized tile files and improving data loading efficiency. S3M 1.0 does not support the S3MBLOCK format. S3MBLOCK tiles only support standard materials.
 CacheFileType
Password
(Optional)		 When the tile file type is S3MBLOCK, a password can be set for data encryption. String
Number of Threads:
(Optional)		 Set the number of threads allocated for the current operation. When the number of threads is 0, it means the maximum number of cores of the current computer. If the number of threads is set too high, tile generation may fail. It is recommended to reduce the parameter value appropriately. Integer
Object ID Field:
(Optional)		 Select an attribute field to uniquely identify object IDs via a dropdown menu. String
Feature Value Field:
(Optional)		 This option is available only when the vertex weight mode is set to Dataset Field. Click the dropdown arrow on the right to specify the field. String
Vertex Weight Mode:
(Optional)		 Set the vertex weight mode, which determines the key attribute values used to distinguish and describe objects in the resulting tile data. Options include None, Dataset Field, Height, and Original Feature Value. The default value is Height.
  • Dataset Field: Uses the specified field as the vertex weight.
  • Height: Uses height as the vertex weight.
  • Original Feature Value: Uses the feature value of the model data itself as the vertex weight.
 VertexWeightMode
Pyramid Split Type:
(Optional)		 Set the data pyramid split type, including Quadtree, Octree, and KD-tree. The default value is Quadtree.
  • Quadtree is suitable for large-scale 3D data at the city level.
  • Octree is suitable for small-scale 3D data, often used for BIM data, such as a single tall building model.
  • Using KD-tree allows adaptive splitting of model data without setting LOD levels, but it is not recommended for fine model data.
 PyramidSplitType
Texture Size Limit:
(Optional)		 Set the texture size. The default value is No Limit, in pixels. Options include No Limit, 1024*1024, 2048*2048, and 4096*4096. CacheLimitTextureSize
Texture Processing Method:
(Optional)		 Set the texture processing method, including Merge, Merge and Remap, and Remap. Among these, Merge is suitable for data with dense triangle meshes, and this parameter can improve tile generation efficiency. TextureProcessingType
With Normals
(Optional)		 Set whether the resulting data includes normals. Default is checked (with normals). Normals determine how light interacts with surfaces, thus affecting rendering effects. Boolean
With Borders
(Optional)		 Set whether the model object includes borders. Default is unchecked. Boolean
Group Repeated Textures
(Optional)		 Set whether to group repeated textures in the data. Default is checked.
When there are a large number of repeated textures in the data, grouping them for storage can reduce resource consumption and improve rendering performance.		 Boolean
Instancing
(Optional)		 Set whether to store data using instancing. Default is unchecked. Instancing storage means that for reused objects, only one object is stored in memory, while reused instances only record their position, rotation, and scale states. Boolean
Texture Settings:
(Optional)		 Set whether to apply one or multiple textures to the model data. Options include Single Texture and Multi-Texture. The default is Multi-Texture.
  • Single Texture: Applies a single texture to the model.
  • Multi-Texture: Applies multiple textures to the model, currently supporting dual textures. Multi-Texture can be used to create more complex effects and enhance the visual appearance and realism of model objects.
 MultiTextureMode
Attribute Storage Type:
(Optional)		 Set the storage type for attribute information of the data, including S3MD, ATTRIBUTE, and DB.
  • S3MD: Stores attribute information in JSON format, allowing quick extraction of all attribute information for a single object.
  • ATTRIBUTE: Stores attribute information in binary stream format, more suitable for data with many attributes, allowing quick extraction of specified field attribute information for multiple objects.
  • DB: Stores as DB large file format, only available when the S3M version is S3M 3.01. Supports fast query of object attributes for large S3M tile data on the web and quick thematic map creation using attribute fields.
 AttributeExtentType
Material Type:
(Optional)		 Set the material type of the resulting tile data.Note: When the source model dataset already contains PBR materials, regardless of choosing Standard Material or PBR Material, the resulting tile data will be generated in PBR material format.
  • Standard Material: When selected, the resulting tile data has standard materials.
  • PBR Material: When the S3M version is 2.0, 3.0, or 3.01, selecting this option results in PBR materials for the tile data.
  • UE Material: Recommended when the tile data will be used and enhanced in UE.
  • Unity Material: Recommended when the tile data will be used and enhanced in Unity.
 MaterialType
Material Association File:
(Optional)		 Import a *.json format material association file.
The material association file records the mapping relationship between UE/Unity and the model dataset. When tile data is used in UE or Unity, it can directly map corresponding materials to improve data visualization.		 String
With Normals
(Optional)		 Set whether the resulting data includes normals. Default is checked (with normals). Normals determine how light interacts with surfaces, thus affecting rendering effects. Boolean
With Borders
(Optional)		 Set whether the model object includes borders. Default is unchecked. Boolean
Group Repeated Textures
(Optional)		 Set whether to group repeated textures in the data. Default is unchecked.
During modeling, a large number of repeated textures are often used on a building. For example, railings on different floors often have the same appearance. This parameter can reduce resource consumption by sharing a single texture.		 Boolean
Instancing
(Optional)		 Set whether to store model objects using instancing. Default is unchecked. Instancing storage means that for reused objects, only one object is stored in memory, while reused instances only record their position, rotation, and scale states. Boolean
Number of LOD Levels:
(Optional)		 Set the number of LOD levels for the tile data. Default value is 3. Integer
Simplification Rate:
(Optional)		 Set different simplification percentages for different levels of data. Default values are 25,50,75. String
Storage Format:
(Optional)		 Set the file storage type, including Compact and Original. Default is Compact.
  • Compact: Uses certain mechanisms to compress and encrypt data when generating tiles.
  • Original: Does not compress data, retaining the original information of the model data.
 StorageType
Encryption Algorithm:
(Optional)		 Set the encryption algorithm for coordinate encryption. The specific algorithm is specified using the Coordinate Encryption tool. EncryptCoordinatesSetting

Output Results

Parameter Name Parameter Description Parameter Type
Tile Result Address The address of the tiles generated from the model dataset String