Mesh Converter Tool
SURE offers a Graphical User Interface that allows the conversion of *.osgb Meshes to several other formats.
Access from SURE GUI: Tools → Mesh Converter
A CLI version (MeshConverter.exe) is documented here.
This tool can be used only if the SURE license contains the Meshing add-on.
This field takes the path to the input osgb Mesh. This can either be a main.osgb linking file, or a tile Main_xx_xx_xx.osgb file.
The tool can read only LOD Meshes in osgb format.
This field retains the path to the folder where the output Mesh will be written. The folder will be created, if it doesn't exist beforehand.
Input Coordinate System
This field is only necessary for the cesium, lod_dae, lod_obj and slpk output formats. It takes the path to the text file containing the coordinate system attached to the mesh; this must be provided in a WKT (Well-Known-Text) format and can be found inside an Inpho project file (*.prj). Please note this file must refer to the input coordinate system as SURE does not convert to new coordinate systems.
When converting to LODTreeExport, it is necessary that a line containing the EPSG code is available within the PROJCS node. In this example it is the third line from the bottom: AUTHORITY["EPSG","25832"]. If such a definition is missing, it must be added by the user.
No local coordinate systems are allowed. The user is advised to perform the whole SURE workflow with cartesian coordinate systems.
Furthermore, no additional vertical coordinate system is supported. If such a vertical coordinate system is detected, the user gets a message saying that the entry should be removed. In this case, because the height of the dataset will not be correct anymore, a vertical shift with the corresponding argument can be forced.
Vertical Shift (optional)
Provided in meters, the default value is 0. This may be necessary only for the cesium, lod_dae, lod_obj and slpk formats, in case the model's height is not correct, as it was imported from the input coordinate system. Can be used by the users that have orthomertric heights in the Cesium Mesh as way to visualize the mesh in a Cesium Viewer at the correct height.
Cesium: Always show lowest geometry resolution
When this option is activated the visualization of the mesh output in Cesium viewer will be slower. Because the exported mesh is always displayed in the viewer by default, no matter the zooming scale.
If the user wants to speed up the process when visualizing the mesh in Cesium Viewer, then he has to deactivate this option.
As a consequence the exported mesh will not be displayed in the viewer, if the user zooms out at a lower resolution level. Please refer toTexturing Parameters for more details.
Cesium: Over-impose heights on the target ellipsoid
If this option is activated (also by default), the height values of the input mesh will be interpreted as heights above the Cesium ellipsoid. Thus the exported mesh is over-imposed on top of the Cesium ellipsoid in Cesium Viewer. For example the users that performed the aerial triangulation in a datum referring to the geoid of DHHN92 can benefit from it, because in this way the mesh will still display the DHHN92 heights in the Cesium viewer.
If not activated, then the input height values (ellipsoidal heights) will be converted to the ellipsoidal heights used in Cesium Viewer (WGS84).
The format of the output Mesh. Possible choices: cesium, lod_dae, lod_obj, ive, slpk.
See also output formats.
The format in which the texture atlases are stored.
Supported combinations of mesh formats ↔ texture formats:
|Mesh format||Texture format|
|ive / cesium||s3tc|
|lod_dae / lod_ obj||jpg / png / dds|
Simultaneous multiple output
It is possible to convert to multiple Mesh formats simultaneously. Click the "Mesh and Texture Output Formats" widget to enable the desired choices.