Site Scan Manager processing time matrix

[James_Wright]

Hi Site Scan team, 

I have a requirement to understand the processing time of Site Scan manager to create certain outputs (Ortho, mesh, etc).  This is for the purpose of being able to provide turnaround times for a product request. 

 I know a rough estimate is given when you start to process a set of imagery based on the number of images within that flight. Do you have those same estimates in a one-page matrix? Possibly with different times based on the desired output (ortho vs. mesh). Also what effect does changing the resolution of the output have on the expected processing time (e.g from high to medium ortho)? 

Regards, 

James Wright

[JasonYoscovits]

Hi James. In my experience, processing time is based on many variables, most of which you mention, but most importantly, the number of images obtained during each flight. I typically utilize the Processing Report available in file export to determine estimated processing time. I fly mostly large projects (2500 to 3000 images). I am given an estimate of 12-24 hours but typically see the mission processed fully in 18-20 hours. This with Ortho and Point Cloud set to Large and Mesh set to High. This certainly does not answer your question but I have found that scouring the Processing Report has been very helpful. 

[SalomonVielmaP]

Hello, with 411images, Site Scan took 4.5 hours, with all products in high quality. Site Scan delivers a report that can be downloaded, the time that appears there is very low, for the project of 411 images it indicates that it used 32 minutes. However to generate the products, like DSM, DTM, point cloud, contours, and publish those layers as a web service, is clearly very time consuming.

[James_Wright]

Hi Jason, 

Appreciate your response to this and it's useful to hear your own processing time experience. I'll definitely look into the processing report more and conduct some tests of my own. 

Cheers!

[NicoBonnafoux]

@James_Wright, there are too many variables to provide a processing time matrix. 
Image size, capture type (oblique vs nadir), type of site being mapped, output formats selected and resolutions... 
A rough rule of thumb currently is about 1 hour per 150 images.