Oblique Photogrammetry to S3M

Instructions

This tool uses SCP configuration files as source data and can generate oblique photogrammetry 3D model data into S3M tile data through operations such as texture compression, lightweight processing, and top-level reconstruction. Loading S3M tile data can improve data loading efficiency and enable multi-terminal sharing and interoperability of data.

This tool is typically used together with GPA tools such as Generate Configuration File, Oblique Photogrammetry to S3M - Monomerization, Oblique Photogrammetry to S3M - Generate Normal, Oblique Photogrammetry to S3M - Modify Center Point, and Oblique Photogrammetry to S3M - Clip.

Using this tool on the Windows operating system requires meeting certain software and hardware requirements:

  • Compatible with OpenGL 3.0 or lower versions;
  • Supports shader syntax of GLSL (OpenGL Shading Language) 1.30 or lower;
  • Graphics card memory greater than 1 GB.

When an online trial license is used, tile data generated by this tool will display a "SuperMap Trial Use" watermark when loaded in the scene.

Parameter Description

Parameter Name Description Parameter Type
Source Configuration File Add the source SCP configuration file. The configuration file can be obtained based on oblique photogrammetry 3D model data through the Generate Configuration File tool. String
Merge Layers
(Optional)		 When the number of configuration files in the file list is greater than or equal to 2, a new configuration file can be generated based on multiple configuration files by merging layers, that is, merging multiple data layers into one data layer.
Note: Checking this checkbox will modify the source data. It is recommended to back up the data before processing.		 Boolean
Storage Path: The file path to save the result data. String
Number of Threads:
(Optional)		 The number of threads allocated to this operation. Setting the number of threads to 0 means that the number of threads allocated to this operation is the maximum number of cores of the current computer. Integer
Rebuild Top Level
(Optional)		 Sets whether to perform top-level reconstruction. For oblique photogrammetry 3D data with poor top-level effects, finer-level data can be re-specified as the new root node, and then the top level can be rebuilt, which can improve the top-level visualization effect, reduce the data volume, and improve loading efficiency. Boolean
Texture Compression Format:
(Optional)		 Different texture compression formats are used for data of different purposes to reduce the amount of video memory used by texture images, including WebP, DXT, CRN_DXT5, and KTX2.0.
  • WebP: Common for PC and mobile devices, which can reduce file size and storage space; however, it does not reduce video memory usage. The processing time is relatively short.
  • DXT (PC Devices): Supported by PC devices, which can reduce video memory usage and improve rendering smoothness; however, the file size is usually larger than WebP. The processing time is relatively short.
  • CRN_DXT5 (PC Devices): Supported by PC devices, with a smaller file size than DXT and the same video memory usage as DXT. The processing time is relatively long.
  • KTX2.0: Common for PC and mobile devices, which can reduce both file size and video memory usage, and can be transcoded to adapt to various platform/modern GPU formats. The processing time is relatively long.
Note: In iServer 11.1.1 and later versions on the Linux environment, you need to set the corresponding parameter value according to whether this node depends on multi-concurrency.
  • If this node depends on multi-concurrency, the texture compression type cannot be set to CRN_DXT5.
  • If this node does not depend on multi-concurrency, all parameter values can be set. However, if the texture compression type is to be set to CRN_DXT5, you need to temporarily comment out the LD_PRELOAD parameter in the product package /bin/setenv.sh file with the # symbol before starting iServer to ensure normal tile generation; otherwise, the tile generation process may malfunction and fail to generate result data.
 TextureCompressType
Storage Type:
(Optional)		 The storage type of the result tile data, including Original and Compact.
  • Original indicates that the data is not compressed and the original information is retained.
  • Compact indicates that a certain mechanism is adopted to compress and encrypt the tile data.
Currently, only OSGB source data supports generating compact tile data.		 StorageType
Vertex Optimization Method:
(Optional)		 Sets the vertex optimization method of the data, including No Compression, Draco Compression, and MeshOpt Compression.
  • No Compression: The data is not compressed.
  • Draco Compression: The data is compressed based on a certain algorithm, which can significantly reduce the data volume and improve the data loading experience.
  • MeshOpt Compression: A series of algorithms are used to reduce the complexity of the data mesh, thereby reducing the data volume and improving data rendering efficiency.
 VertexOptimizationType
S3M Version:
(Optional)		 Sets the version of the S3M tile data, including: S3M 1.0, S3M 2.0, S3M 3.0, and S3M 3.01.
  • S3M 1.0: Basic version, where the geographic coordinate system adopts a spherical datum.
  • S3M 2.0: The geographic coordinate system still adopts a spherical datum. Based on 1.0, it adds support for the Draco compression vertex optimization method, supports WebP and CRN texture compression formats, supports physically based rendering (PBR) materials, adjusts the storage method of IDs, upgrades the attribute file storage structure (supports binary stream storage), and supports storing tiles in SQLite/MongoDB databases.
  • S3M 3.0: The geographic coordinate system is upgraded to an ellipsoidal datum. Based on 2.0, it adds support for the MeshOpt compression vertex optimization method, supports the KTX 2.0 texture compression format, supports OBB bounding boxes, adds support for semantic textures and mask textures in PBR materials, supports multiple LOD switching modes, supports skeletal animation, supports expressing more dimensions of vertex attributes, and supports pixel-level semantic information of textures.
  • S3M 3.01: The geographic coordinate system adopts an ellipsoidal datum. Based on 3.0, it is fully adapted to the CH/T 9040 industry standard, provides a variety of open resources for data parsing or format conversion, upgrades the attribute data storage structure (DB large files), supports expressing BIM component tree information, and supports expressing multi-temporal and multi-feature eigenvalues.
 S3MVersion
Lightweight Processing
(Optional)		 Sets whether to perform lightweight processing. After checking the Lightweight Processing checkbox, the geometry and texture objects of the data can be simplified to reduce the data volume of the result data after oblique photogrammetry to S3M. Boolean
Texture Remapping
(Optional)		 Sets whether to perform texture remapping on the data. It is not checked by default. Texture remapping can solve the problem of unreasonable texture stitching in some oblique photogrammetry 3D model data, thereby improving data selection performance. Boolean
Watermark Parameter Settings
(Optional)		 Sets the watermark parameters to be added. The specific parameters are specified by the Watermark Parameter Settings tool. WatermarkParameters
Oblique Photogrammetry Color Equalization Parameters
(Optional)		 The color adjustment of the data can be performed through the oblique photogrammetry color equalization operation. The specific parameters are specified by the Oblique Photogrammetry Color Equalization Parameters tool. ColorAdjustmentParameters
Cloud Storage Connection
(Optional)		 Sets whether to upload the result S3M data to a cloud storage service (Huawei Cloud, Alibaba Cloud, SeaweedFS, MinIO, AWS S3). The specific parameters are specified by the Cloud Storage Connection tool. CloudStorageConnectionInfo
Target Coordinate System
(Optional)		 The target coordinate system of the tile data. iDesktopX can set it by specifying a coordinate system, copying a coordinate system, and importing a coordinate system. iServer can set it by entering the EPSG Code of the specified coordinate system.
Coordinate system files only support *.prj and *.xml files generated by functions such as Export Coordinate System in iDesktopX.		 Integer
Scale Difference:
(Optional)		 Projection transformation parameter, indicating the scale scaling amount when converting from the original coordinate system to the new coordinate system. Double
Rotation Angle X:
(Optional)		 Projection transformation parameter, indicating the rotation angle around the X axis, in seconds, with a default value of 0. Double
Rotation Angle Y:
(Optional)		 Projection transformation parameter, indicating the rotation angle around the Y axis, in seconds, with a default value of 0. Double
Rotation Angle Z:
(Optional)		 Projection transformation parameter, indicating the rotation angle around the Z axis, in seconds, with a default value of 0. Double
Offset X:
(Optional)		 Projection transformation parameter, indicating the offset along the X axis, with a default value of 0. Double
Offset Y:
(Optional)		 Projection transformation parameter, indicating the offset along the Y axis, with a default value of 0. Double
Offset Z:
(Optional)		 Projection transformation parameter, indicating the offset along the Z axis, with a default value of 0. Double
Rotation Origin X:
(Optional)		 Projection transformation parameter, indicating the X coordinate value of the rotation origin, with a default value of 0. Double
Rotation Origin Y:
(Optional)		 Projection transformation parameter, indicating the Y coordinate value of the rotation origin, with a default value of 0. Double
Rotation Origin Z:
(Optional)		 Projection transformation parameter, indicating the Z coordinate value of the rotation origin, with a default value of 0. Double
Projection Transformation Method:
(Optional)		 Sets the method for performing projection transformation on the data. For more information, see Dataset Coordinate System Transformation.
Currently, only transformations between geographic coordinate systems and projected coordinate systems based on a unified reference ellipsoid are supported.		 CoordSysTransMethod
Center Point Coordinate Unit:
(Optional)		 Sets the unit of the center point coordinates, including Meter and Degree. DataUnit
Encryption Algorithm:
(Optional)		 Sets the encryption algorithm for coordinate encryption. The specific algorithm is specified by the Coordinate Encryption tool. EncryptCoordinatesSetting
Parameter Settings
(Optional)		 No separate configuration is required. It is automatically set when linked with other GPA tools. obliqueBuilderParameters

Output Result

Parameter Name Description Parameter Type
Oblique Photogrammetry to S3M The storage path of the result tile data String