Trimble Business Center

Just came across this issue today. (Version 2025.20)

Still plagued by the fractured UAV deliverables (That's a discussion for another time) I opted to reduce the quality in an effort to get the entire area into a single image.

Noticed that the medium quality deliverables were the same size as the high quality. Thought it was my mistake for not correctly selecting the correct option.

Reprocessed another time just to be sure and again after a full system power cycle

------------------------------
Rory Prendergast
------------------------------

Hi Rory,

we made changes to the processing engines, impacting the "Digital Surface Model" selection. 

Digital Surface Model focuses heavily the true-orthomosaic generation in our production. Both, Medium and High, are running the pointcloud on the highest resolution, allowing with both methods to generate a high-detailed true-orthomosaic.

Medium uses some speed improvements, as some of the internal processing steps do not impact the final deliverable of the true-orthophoto as much and allow us therefore to create the true-orthomosaic with some processes being executed on lower level content internally.

High adds additionally some edge-enhancements, so if the drone flight includes enough overlap, you can see better solutions for High then Medium for buildings. We left Medium and High as options, but will in the future move the "High" option to the advanced option.

You can always manually change the orthomosaic resolution to a lower GSD, creating smaller orthos but also lower resolution of course. Just click on the [Automatic (0.0121 m/pixel)] enter the GSD you want into the:

Output Resolutions
True Orthomosaics: _______

We announced the change in the release notes for TBC v2025.20, but sorry if this did not reach you.

Just came across this issue today. (Version 2025.20)

Still plagued by the fractured UAV deliverables (That's a discussion for another time) I opted to reduce the quality in an effort to get the entire area into a single image.

Noticed that the medium quality deliverables were the same size as the high quality. Thought it was my mistake for not correctly selecting the correct option.

Reprocessed another time just to be sure and again after a full system power cycle

------------------------------
Rory Prendergast
------------------------------

Thanks Thomas.

I have adjusted the resolution and that seems to have fixed the problem. Obviously the main problem of the fractured deliverables still persists.

I am aware of the 4gb hard limit for file size but I feel like an option to merge the exported tiles back together would be a great addition

Is there any talk about adding this function in the future?

Thanks

Rory

Hi Rory,

we made changes to the processing engines, impacting the "Digital Surface Model" selection. 

Digital Surface Model focuses heavily the true-orthomosaic generation in our production. Both, Medium and High, are running the pointcloud on the highest resolution, allowing with both methods to generate a high-detailed true-orthomosaic.

Medium uses some speed improvements, as some of the internal processing steps do not impact the final deliverable of the true-orthophoto as much and allow us therefore to create the true-orthomosaic with some processes being executed on lower level content internally.

High adds additionally some edge-enhancements, so if the drone flight includes enough overlap, you can see better solutions for High then Medium for buildings. We left Medium and High as options, but will in the future move the "High" option to the advanced option.

You can always manually change the orthomosaic resolution to a lower GSD, creating smaller orthos but also lower resolution of course. Just click on the [Automatic (0.0121 m/pixel)] enter the GSD you want into the:

Output Resolutions
True Orthomosaics: _______

We announced the change in the release notes for TBC v2025.20, but sorry if this did not reach you.

Just came across this issue today. (Version 2025.20)

Still plagued by the fractured UAV deliverables (That's a discussion for another time) I opted to reduce the quality in an effort to get the entire area into a single image.

Noticed that the medium quality deliverables were the same size as the high quality. Thought it was my mistake for not correctly selecting the correct option.

Reprocessed another time just to be sure and again after a full system power cycle

------------------------------
Rory Prendergast
------------------------------

Rory can I ask about your favorite workflow you would like to run? Assuming you run a drone project and your mosaic output would reach a non-compressed GeoTIFF with larger 4GB, what would you expect? Please try first to think yourself about your solution and read later my 3 options. But of course, feel free to peak at my options.

A) compressing the mosaic but keeping it a GeoTIFF as much as possible, but keeping the original resolution of the GSD, even when the compression goes so far to loose some details

B) compressing the mosaic but keeping it a GeoTIFF as much as possible until a specific compression rate. As soon as the compressed size reaches again the 4GB range, reducing the resolution of the GSD automatically by half

C) compressing the mosaic but keeping it a GeoTIFF as much as possible until a specific compression rate. As soon as the compressed size reaches again the 4GB range, switching to a strong compressed BigTIFF or ECW file

Thanks Thomas.

I have adjusted the resolution and that seems to have fixed the problem. Obviously the main problem of the fractured deliverables still persists.

I am aware of the 4gb hard limit for file size but I feel like an option to merge the exported tiles back together would be a great addition

Is there any talk about adding this function in the future?

Thanks

Rory

Hi Rory,

we made changes to the processing engines, impacting the "Digital Surface Model" selection. 

Digital Surface Model focuses heavily the true-orthomosaic generation in our production. Both, Medium and High, are running the pointcloud on the highest resolution, allowing with both methods to generate a high-detailed true-orthomosaic.

Medium uses some speed improvements, as some of the internal processing steps do not impact the final deliverable of the true-orthophoto as much and allow us therefore to create the true-orthomosaic with some processes being executed on lower level content internally.

High adds additionally some edge-enhancements, so if the drone flight includes enough overlap, you can see better solutions for High then Medium for buildings. We left Medium and High as options, but will in the future move the "High" option to the advanced option.

You can always manually change the orthomosaic resolution to a lower GSD, creating smaller orthos but also lower resolution of course. Just click on the [Automatic (0.0121 m/pixel)] enter the GSD you want into the:

Output Resolutions
True Orthomosaics: _______

We announced the change in the release notes for TBC v2025.20, but sorry if this did not reach you.

Just came across this issue today. (Version 2025.20)

Still plagued by the fractured UAV deliverables (That's a discussion for another time) I opted to reduce the quality in an effort to get the entire area into a single image.

Noticed that the medium quality deliverables were the same size as the high quality. Thought it was my mistake for not correctly selecting the correct option.

Reprocessed another time just to be sure and again after a full system power cycle

------------------------------
Rory Prendergast
------------------------------