Tile Generate and Upload

Usage

The Oblique Import function can perform operations such as merging root nodes, texture compression, model individualization, and  modifying model center points on oblique photography 3D model data. This batch-processes and multi-threads the oblique photography 3D models into S3M tile data.

To use this function , the computer must meet  certain software and hardware requirements, which are   consistent with the requirements for using the   3D Scene   Rendering Engine  V1 . For details, refer to the usage instructions for the 3D Scene Rendering Engine  (Windows only).

Function Entries      

  • 3D Data Tab -> Oblique Photography Group -> Data Processing Drop-down Button -> Oblique Import Button
  • Toolbox -> 3D Data -> Oblique Data Processing -> Oblique Import-Generate S3M

Procedure

  1. In the "3D Data" tab, within the "Oblique Photography" group, click the "Oblique Import" button in the "Data Processing" drop-down menu. The "Oblique Import" dialog box will pop up.
  2. Source Configuration Files: You can add, batch add, delete, and set passwords for source configuration files in the toolbar.
    • Add: Click this button, then select a *.scp file as the source configuration file in the "Open" dialog box.
    • Add All Configuration Files in Folder: Click this button, then select a folder to batch add source configuration files in the "Browse for Folder" dialog box.
    • Delete: Remove the selected source configuration file from the current data list.
    • Set Password: Set a password for the result data. Password-protected data requires a password to open. Only compact-type data supports password setting. Click the "Set Password" button, enter the same password in the "Password" and "Confirm Password" boxes, then click "Confirm".
  3. Basic Settings:
    • Storage Path: Set the path for storing result data. By pre-setting Cloud Storage Service parameters, you can select a previously set cloud storage path in the opened browse folder dialog. The S3M tiles generated after oblique import can be directly uploaded to the specified cloud storage service (Huawei Cloud, Alibaba Cloud, SeaweedFS, MinIO, AWSS3).
    • S3M Version: Supported version numbers include: S3M 1.0, S3M 2.0, S3M 3.0, S3M 3.01. If you need to use the data files in iClient3D products before version 10.2.1, it is recommended to choose S3M 1.0.
    • Texture Compression Format: Currently supports 4 compression formats, default is CRN_DXT5 (PC devices). Using different texture compression methods for data with different purposes can reduce the amount of video memory used by texture images.
      • WebP: Significantly reduces total data volume, a texture compression format supported on both PC and mobile devices.
      • DXT (PC devices): Reduces video memory usage and improves rendering performance, but total data volume increases.
      • CRN_DXT5 (PC devices): Reduces video memory usage and total data volume, but requires longer processing time.
      • KTX2.0: Reduces video memory usage and total data volume. Processing the same data takes less time than CRN_DXT5.
    • Thread Count: Set the number of threads for the oblique import operation, default is 8.
    • Vertex Optimization Method: Currently provides two compression methods: MeshOpt, Draco Compression. Meshopt compression is not supported when the S3M version is S3M1.0 or S3M2.0.
      Note:

      For modified oblique photography 3D model data, it is recommended to specify the texture compression format as CRN_DXT5 and the vertex optimization method as MeshOpt, rather than directly using the default settings.

    • Storage Format: Supports original and compact. Original means no data compression, retaining original information; compact means using certain compression and encryption mechanisms to compress and encrypt data for storage when generating tiles.
      • If the resulting tile data is to be stored in MongoDB, the storage type must be original.
      • Currently, only when the source data is OSGB, generating compact-format tile data is supported.
    • Center Point Coordinate Unit: Set this parameter according to the center point coordinate unit of the configuration file. For example: if the original configuration file's center point coordinate unit is METER, then choose Meter for this parameter.
    • Rebuild Top Level: Selected by default. This function targets oblique photography 3D model data with poor top-level visualization. By rebuilding the top level to regenerate the root node, it can not only reduce data volume but also improve the overall visualization performance of the data.
    • Lightweight: Not selected by default. This function supports further reduction of tile data volume through geometry and texture lightweighting.
    • Color Adjustment File: Input a color adjustment file (*.colorAdj) to perform unified color adjustment on the data. The color/illumination adjustment file can be obtained via the Color Balance function.
  4. Advanced Settings:
    • Coordinate System Conversion: Selected by default, supports setting the target coordinate system and projection conversion parameters.
      • Target Coordinate System: Currently provides 3 methods.
        • Reset Coordinate System: Click the "Reset Coordinate System" button at the top of "Projection Settings", the "Coordinate System Settings" dialog box pops up. Select a projection as the coordinate system for the target file. For specific operations on setting the target projection, please refer to Projection Settings Window.
        • Import Coordinate System: Click the "Import Coordinate System" button at the top of "Projection Settings", in the popped-up "Import Coordinate System File" window, select and import the projection information file. Meanwhile, the details of the selected projection file's coordinate system will be displayed in the text box below.
        • Copy Coordinate System: Click the "Copy Coordinate System" button at the top of "Projection Settings", in the popped-up "Copy Coordinate System" window, select the coordinate system of a dataset. Meanwhile, the details of the selected dataset's coordinate system will be displayed in the text box below.
      • Reference System Conversion Settings:
        • Conversion Method: Click the dropdown button to the right of the "Conversion Method" label. The popped-up dropdown menu lists over ten reference system conversion methods provided by the system. Users can choose an appropriate reference system conversion method. For explanation of conversion methods, please refer to Reference System Conversion Methods.
        • Projection Conversion Parameters: Choosing different conversion methods allows for different customizable parameters in the "Projection Conversion Parameter Settings" dialog box. For detailed description of projection conversion parameter settings, please see Dataset Convert Projection.
    • Modify Center Point: Optional. After checking "Modify Center Point", supports setting the model center point X, Y, Z coordinate values.
    • Generate Normals: Optional. After checking "Normals", you can set the algorithm type and angle threshold parameters.
      • Algorithm Type: Sets the algorithm for recalculating normals of the oblique photography 3D model, including angle weight algorithm, average algorithm, and NelsonMax algorithm. Select by clicking the dropdown arrow to the right of algorithm type.
      • Angle Threshold: The normals recalculation algorithm involves an angle threshold parameter. The threshold range is 0-180, default is 80, and a custom angle threshold can be set. This parameter is not supported when the algorithm type is average algorithm.
  5. Optional Settings: The bottom of the dialog provides checkboxes for merging layers, texture remapping, and saving to MongoDB.
    • Merge Layers: When the center points of multiple configuration files are consistent, supports merging oblique photography models from multiple layers into one layer after oblique import. When the center points of multiple configuration files are inconsistent, you need to check the "Modify Center Point" function, use the center point of one configuration file as the standard, modify the model center points, then perform oblique import to merge oblique photography data from multiple layers into one layer.
    • Texture Remapping: Used to solve unreasonable texture splicing in some oblique data and improve loading performance.
    • Save to MongoDB: Data is directly stored to MongoDB, S3MB files are not generated locally, but a configuration file will be generated under the storage path. Checking "Save to MongoDB" will pop up a "Save to MongoDB" dialog box.

      The "Connection Information" area in the dialog box allows setting information related to the MongoDB server and database. Before using this function, the MongoDB service must be started. For MongoDB, please refer to MongoDB Usage Instructions. Parameter descriptions are as follows:

      If data needs to be saved to MongoDB, the MongoDB database must be enabled.
      • Server Name: Enter the IP address of the server.
      • Database Name: You can only enter the name of an existing database in the text box.
      • User Name: Enter the user name for the MongoDB database.
      • Password: Enter the password to access the MongoDB database.
      • Data Name: The name for saving to MongoDB.
  6. After setting the above parameters, click the "OK" button to execute the oblique import operation.

Notes

  1. The storage path cannot be modified when not merging layers.
  2. When merging layers, if the sum of all layer nodes is greater than 10, you can use "Rebuild Top Level", but cannot modify the S3M version, texture compression format, and vertex optimization method parameters. When merging layers, if the sum of all layer nodes is less than 10, you cannot use "Rebuild Top Level Only", and cannot modify the S3M version, texture compression format, and vertex optimization method parameters.
  3. The source data for oblique import supports *.scp files in OSGB and S3MB formats, but does not support importing *.scp files of both formats simultaneously.
  4. The oblique import function currently supports data in ENU and projected coordinate systems; it does not yet support data in planar non-projected coordinate systems.
  5. The oblique import function only supports coordinate conversion for a unified reference ellipsoid (projection to geographic), and does not support other coordinate system conversions.
  6. When adding encrypted oblique photography 3D model data to a scene, a password is required.
  7. If data using an ENU coordinate system is to be loaded on a sphere after oblique import, the target coordinate system needs to be selected as EPSGCode:4326.
  8. The oblique import function can merge multiple oblique photography 3D model data that are already in S3MB format into one layer. The following points should be noted when merging:
    • The S3M version, storage type, geometry compression method, texture compression method, and target coordinate system need to be consistent with the original oblique import settings.
    • If the S3MB format oblique data to be merged is in a geographic coordinate system, the center point coordinate unit needs to be selected as Degree. Otherwise, the center point coordinate unit needs to be selected as Meter.
    • You need to uncheck the "Merge Root Nodes" checkbox.
    • You need to check the "Merge Layers" checkbox.
  9. If data using a projected coordinate system is to be used in a spherical scene after oblique import, the corresponding geographic coordinate system must be selected during import. For example, if the original OSGB data coordinate system is EPSGCode:4546, the target coordinate system EPSGCode must be set to 4490 during oblique import.
  10. When performing oblique import again on data that has already been imported, if the number of root nodes in the data is less than 10, no processing will be performed on the data because the performance of the source data already meets the basic requirements.