Generate Tiles from Model

use-speak

This tool can be used to generate a specified single model dataest as S3M tile data.

Parameter Description

Parameter Name Parameter Description Parameter Type
Model Dataset: Select Source Model Dataest DatasetVector
Tile Name:
(Optional)
Sets the name of the resulting Tile Data String
Storage Path: Set the storage path of the result Tile Data String
S3M Version:
(optional)
Set result S3MTile version number including S3M 1.0, S3M 2.0, S3M 3.0, S3M 3.01 S3MVersion
Target Coordinate System
(Optional)

Sets the coordinate system of the resulting tile data by entering an EPSG code or a coordinate system file (*.prj or *.xml). Combined with the conversion method and projection transformation parameters, coordinate transformation of the data can be achieved.
When the EPSG code is set to 0, no coordinate transformation will be performed, and the source coordinate system will be retained.
Coordinate system setting restrictions:

  • If the source data is in a planar non-projected coordinate system, the result coordinate system can only be set to a planar non-projected coordinate system.
  • If the source data is in a geographic coordinate system or projected coordinate system, the target projection cannot be set to a planar non-projected coordinate system.
String
Conversion Method
(Optional)
Selects the method for data coordinate system conversion from the dropdown menu. Options include:
1. Geocentric Translation (3-para): Suitable for geocentric three-parameter coordinate transformation.
2. Molodensky (3-para): Molodensky three-parameter transformation method.
3. Abridged Molodensky (3-para): Three-parameter transformation method.
4. Position Vector (7-para): A type of seven-parameter transformation method.
5. Coordinate Frame (7-para): Geocentric seven-parameter transformation method.
6. Bursa-Wolf (7-para): A commonly used seven-parameter transformation method.
7. Molodensky-Badekas (10-para): A ten-parameter spatial coordinate transformation model.
8. China_3D_7P (7-para): Used for transformation between different coordinate systems and the China Geodetic Coordinate System 2000 (CGCS2000). Suitable for coordinate transformation of control points between geodetic coordinate systems under different earth ellipsoid baselines at the provincial and national levels with 3-degree or more ellipsoidal surfaces. The transformation method involves three translation parameters, three rotation parameters, and one scale change parameter, while also considering the differences in the semi-major axis and flattening of the two earth ellipsoids corresponding to the two geodetic coordinate systems.
CoordSysTransMethod
Projection Transformation Parameters
(Optional)
Sets the parameters for projection transformation of the data, including scale difference, rotation angle, offset, rotation origin, etc. The specific parameter values are specified by the Projection Transformation Parameters tool. CoordSysTransParameter
Compressed Type:
(optional)
Set data Texture Compression format, including WebP, DXT, CRN _ DXT5, KTX2.0. It is suggested that different Texture Compression types should be used for different purposes of data, which can reduce the amount of video memory used by texture images.
  • WebP: It is recommended to select this value when Tile Data is used on the mobile side, and transparent texture is supported.
  • DXT: When this value is selected, Result Data has the smallest video memory occupation, the shortest processing time, and the largest total amount of data.
  • CRN _ DXT5: When this value is selected, the Result Data takes up slightly less video memory, takes the longest processing time, and has the largest amount of data.
  • KTX2.0: It is common for PC and mobile terminal, and the mobile terminal does not support transparent texture temporarily.
Note: In iServer 11.1.1 and above in the Linux environment, you need to set the corresponding parameter value according to whether the node depends on multiple concurrency.
  • The Texture Compression type cannot be set to CRN _ DXT5 if the node depends on multiple concurrency.
  • If the node does not depend on multiple concurrency, all parameter values can be set. However, if the Texture Compression type is to be set to CRN _ DXT5, it is necessary to temporarily comment out the LD _ PRELOAD parameters in the product package/bin/setenv. Sh file by using the # symbol before starting the iServer, so as to ensure normal generation of the Tile. Failure to do so may result in an exception to the Tile generation process and failure to generate Result Data.
CompressedTextureType
Vertex optimization method:
(Optional)
Sets the way the data is optimized for vertexing. Vertex optimization differs between S3m versions.
  • S3M 1.0 and S3M 2.0 support setting no compression.
  • S3M 3.0 and S3M 3.01 support setting No Compression, MeshOpt Compression.
    • No compression: Data is not compressed.
    • MeshOpt Compression: Uses a series of algorithms to reduce the complexity of the data grid, thereby improving the efficiency of data rendering and reducing the amount of data.
VertexOptimizationType
Tile Width (m):
(optional)
Sets the Tile side length in meters. Different side lengths of Tile correspond to different scales. When the data is dense and the geometry and texture are simple, the Tile edge length can be set to a large value, such as 1000. When the data is sparse and the geometry or texture is complex, the Tile side length can be set to a small value, such as 200 Double
Scene Type
(Optional)
Sets the Scene Type of the resulting Tile Data, including Planar and Spherical. The default is Spherical.
  • If the source data is under Geographic Coordinate System, this parameter can only be set to spherical.
  • If the source data is in the Projected Coordinate System, the Scene Type is not limited and can be selected as required.
  • If the source data is in the Planar Coordinate System without projection, this parameter can only be set to plane.
SceneType
Filter Threshold:
(Optional)
Sets a threshold to filter smaller (less than threshold) sub-objects in the rough layer of data, improving rendering performance on large scene data. The default is 2 in pixels Double
Tile File Type:
(optional)
Sets the TileFile Type, including S3MB and S3MBLOCK.
  • S3MB: An open and extensible Tile compressed data format.
  • S3MBLOCK: Tile large file data format, mostly used for fine models, which can effectively solve the problem of too large Tile files and improve the efficiency of data loading. S3M 1.0 does not support the S3MBLOCK format. S3MBLOCK tiles only support standard materials.
CacheFileType
Password
(Optional)
Set Password is supported for data encryption when S3MBLOCK is selected for TileFile Type String
Process Thread Count:
(Optional)
Sets the number of threads assigned to the current operation. When the number of threads is 0, it means that the number of threads is the maximum number of cores of the current computer.  Integer
Object ID field:
(optional)
Select Property Field String
EigenValue Field:
(Optional)
This option is only available when the vertex weight mode is set to Dataset Field. Click the drop-down arrow Specify Field at the right end. String
Vertex Weight Mode:
(Optional)
Sets the vertex weight mode used to determine the key attribute values used to distinguish and describe objects in the resulting Tile Data. The choices are None, Dataset Field, Height, and Original feature value. The default is Height.
  • Dataset Field: Specify the field as the vertex weight.
  • Height: Use height as the vertex weight.
  • Original feature value: The feature value of the Model Data itself is used as the vertex weight.
VertexWeightMode
Pyramid Split Type:
(Optional)
Sets the data pyramid partition type, including quadtree, octree, and KD-tree. The default is quadtree.
  • Quadtree is suitable for large-scale 3D Data at the city level
  • Octree is suitable for small-scale 3D Data, which is often applied to BIM data, such as a single high-rise model. The
  • uses the KD tree, which can perform adaptive subdivision on Model Data. It is not necessary to set the LOD level, but it is recommended not to select the KD tree for fine model data.
PyramidSplitType
Texture Size Limit:
(Optional)
Sets the texture size. The default is unlimited in pixels. Options include: Unlimited, 1024 \ * 1024, 2048 \ * 2048, and 4096 \ * 4096. CacheLimitTextureSize
Texture:
(Optional)
Sets texture processing, including stitching, Splicing and Remapping, and remapping. Splicing is applicable to data with dense triangulation. This parameter can improve Tile generation efficiency TextureProcessingType
Texture Settings:
(Optional)
Sets whether to apply one or more textures to Model Data. Options include Single Texture and Multiple Textures. The default is Multiple Textures.
  • Single Texture: Apply a single texture to the model.
  • Multiple Textures: Apply multiple textures to the model. Currently supports dual textures. Multiple Textures can be used to create more complex effects that enhance the visuals and realism of the Model Object.
MultiTextureMode
Property Storage Type:
(Optional)
Sets the Attributes storage type of the data, including S3MD, ATTRIBUTE, and DB.
  • S3MD: Store data Attributes in JSON format, able to quickly extract all Attributes for a single object.
  • ATTRIBUTE: Store data Attributes in the form of binary stream, which is more suitable for data with many Attributes, and can quickly extract Attributes of Specify Field of multiple objects.
  • DB: stored as a DB large file, available only when the S3M version is S3M 3.01. Support the quick query of S3MTile Object Properties with large amount of data on the Web side and the quick Create Thematic Map by using Property Field.
AttributeExtentType
Material Type:
(Optional)

Sets the material type of the resulting tile data, including Common Material, PBR Material, UE, and Unity Material.

Note:  When the source model dataset already contains PBR materials, the resulting tile data will be generated in PBR material format regardless of whether Standard Material or PBR Material is selected.

  • Common Material: When this option is selected, the resulting tile data will use standard materials.
  • PBR Material: When the S3M version is 2.0, 3.0, or 3.01, selecting this option will generate the resulting tile data with PBR materials.
  • UE Material: When the resulting tile data is intended for use and enhancement in Unreal Engine, this option is recommended.
  • Unity Material: When the resulting tile data is intended for use and enhancement in Unity, this option is recommended.
MaterialType
Texture-Relevant Document:
(Optional)
Import Texture Related File in *.json format.
Material Related File records the material mapping relationship between UE or Unity and Model Dataest. When Tile Data is used in UE or Unity, the corresponding material can be mapped directly to improve the data visualization effect.
String
With Normal or Not
(Optional)
Set Result Data with Normal or Not, with Normal checked by default. Normals can be used to determine how rays interact with surfaces, affecting rendering Boolean
With border or not
(optional)
Set whether Model Object has border or not. Boolean
Repeat Map Group
(optional)
Set whether to repeat Map Group for the data. It is not checked by default.
In the process of modeling, a large number of duplicate Texture Maps are often used on a building. For example, railings, guardrails, etc. on different floors often have the same appearance. This parameter can reduce resource consumption by sharing a map
Boolean
Whether to instantiate
(optional)
Set whether to instantiate Model Object for storage. It is not checked by default. Instantiated storage means that only one object is stored in the memory for the reused object, and only the position, rotation, scaling and other States are recorded for the reused object. Boolean
LOD Lavel:
(Optional)
Sets the LOD level number for Tile Data. The default is 3 Integer
Simplification rate:
(optional)
Different simplification percentages for different levels of Data Settings. Default values are 25, 50, 75 String
Storage Type:
(optional)
Sets the file storage type, including Compact and Raw. The default is Compact.
  • Compact: When Generate Tiles, a mechanism is used to compress and encrypt the data.
  • Original: The data is not compressed and the original information of Model Data is retained.
StorageType
Encryption algorithm: (optional) Sets the encryption algorithm for Coordinate Encryption. The specific algorithm is specified by the Coordinate Encryption tool. EncryptCoordinatesSetting

Output Result

Parameter Name Parameter Description Parameter Type
Tile Output Address Model DataestGenerate Tiles String