Trimble Business Center

Thomas Widmer posted 10-15-2023 23:43

Hi Darren,

TBC divides the ortho deliverables, when it reaches the TIFF related limit of 4GB. Merging them together with the same resolution would not work, as you cannot store a TIFF with more than 4GB of size.

Let us know what prefered workflow with this situation you would be interested in. Would it be a solution to down sample the 4 pieces, so that they would fit into a single mosaic, but with lower ground sample resolution? Or is there another file format you would prefer without the 4GB limits? 

Looking forward to your answer!

Nelson Hays posted 10-17-2023 13:16

How about .ECW support? We can import but not export.

Thomas Widmer posted 10-18-2023 00:28

Hi Nelson,

as I remember there are different license models with the ECW libraries. I would need to check with our development group what license model we have and what possibilities we would have at the moment with this ECW library.

Update: Nelson I double-checked with the DEV group and as I assumed, the current solution we have integrated was a request to be able to import ECW files. The current ECW library we use can only read the ECW files. If we want to offer the export of ECW, TBC would need to add a different library, which will cost money. You can ask Ben Messer, the Product Manager of TBC to check if this would be an option for a future TBC release to implement.

Mike Racz posted 10-23-2023 08:08

"Let us know what prefered workflow with this situation you would be interested in. Would it be a solution to down sample the 4 pieces, so that they would fit into a single mosaic, but with lower ground sample resolution? Or is there another file format you would prefer without the 4GB limits?"

What about Bigtiff ? Almost all of our UAV orthos are over 4GB and 1 file however we convert these to MrSID files to use in Civil 3D.

Thomas Widmer posted 10-24-2023 01:53

Hi Mike,

BigTIFF would be an option. We offer e.g. already BigTIFF in UASMaster to store the result in UASMAaster itself. As TBC does not support at the moment BigITFF, we splitted the results in multiple standard GeoTIFF files, as this format is very common used world wide and can be read by most software packages.

I check currently with the development team, if we can "upgrade" the license we use to handle ECW and check if we can offer ECW as output.

Concerning BigTIFF - would Civil 3D be able to support BigTIFF?

Titus Emanuel posted 10-24-2023 07:17

I would appreciate it if you could export the orthophots in smaller tiles, as many programmes have problems with the large TIFFs. It would be nice if you could define it e.g. by the area (100m x 100m) or by the number of pixels (10000px x 10000px). 

Thomas Widmer posted 10-25-2023 07:58

Hi Titus,

some of our clients are using SHP files, which define the tiles, including metadata information for the naming of the files and some additional meta-information about the data itself (Year, Camera, Flight Operator, etc...). In case we would go this way to offer a tiling into more systematic tiles, I would prefer this solution as you would see in before the tiling structure and you can easily share it with some other system or software. 

We also offer for aerial photogrammetry the professional software solution Inpho OrthoVista which allows additional use of pixel-based tiling files, which would only need an origin point, pixel resolution size (keeping it simple and having square pixels) and the number of tiles to North, East, West, South. I would really prefer to keep it simple and have the orthos face north and not allow some rotated pixels, as this makes things much more complicated.

What solution do you use to create your 100m x 100m tiles or your 10.000 x 10.000 px tiles?

Mike Racz posted 10-26-2023 12:25

"Concerning BigTIFF - would Civil 3D be able to support BigTIFF?"

No, any large image files brings Civil to it's knees which is why we convert our orthos to MrSID format to bring into Civil.