Photomesh datasets are high detail, photo-realistic 3D meshes generated automatically from photogrammetry. Photomesh data is typically provided in both tiled and non-tiled formats.
Tiled vs Non-Tiled
Tiled formats are optimised for high performance loading and real-time rendering. The photomesh is split into several tiles each containing a tree structure representing several levels of detail. Small sections of the photomesh dynamically load and unload at an appropriate level of detail based on the distance from the camera. This ensures only the smallest quantity of data is loaded and rendered at a time, resulting in high performance and short load times. Urban Circus recommends the use of Tiled Photomeshes.
Non-tiled formats have a fixed level of detail, typically a very high resolution. Urban Circus does not recommend the use of non-tiled formats as they require large quantities of memory and impact rendering performance and load times significantly. They are not suitable for web streaming delivery.
Supported Data Formats and Types
Photomesh can be converted into an Urban Engine format using our model conversion pipeline. Note: All data sets must be geo-located in the same coordinate system as your model. If your data differs from the below requirements, contact Urban Circus.
- Type: Tiled Photomesh
- Format: Open Scene Graph Binary (.OSGB) in an Open Scene Graph Paged LOD structure
- A typical OSGB photomesh dataset is comprised of thousands of small OSGB files arranged in a folder layout such as this.
- Due to the complexity of these datasets, correct naming conventions are crucial as they define the relationship between each individual file in the dataset.
- Supported Applications: Bentley Context Capture and Airbus Street Factory can generate OSGB compatible tiled photomesh.
- Unsupported Applications: Agisoft Photoscan can generated tiled photomesh, but it does not support the OSGB format. Contact Urban Circus to discuss solutions for supporting Agisoft Photoscan data.