Few remarks on Ortho processing et output:

• Despite importation of a perimeter (area of interest), it seems it is only used to define tile extension, but tiles are computed in their completness, including outside the AOI. It is not a problem if after processing it would be possible to export the tiles but cutting only inside AOI. but i did not find the way to it. We need to take tiles in external software (Global mapper, FME...) and make the cutting and export. Also impossible to export with a predefined tiling (like kilometer or hectometer grid in the CRS). It is the first time i see this lack of functionality in ortho production software. This is a serious lack and probably not the biggest to solve.

• Edition of ortho: as far as i understand, the mosaikinginside the tiles is performed on the fly during processing. When you edit a patch in a tile, the ortho is recomputed with the selected image. This process is slow compared to Metashape which is computing and store for each image the corresponding ortho. Thus when you edit and select another image for a patch, ortho is immediately updated and the process is fast. We had some case where we had to remove cars from roads in urban area. We had to compute the ortho in Metsahpe from Itwin DSM because of Edition which is too slow. This part must be improved so as to increase edition efficiency

• Constraints: the management of constarint polygon (for water area for example) is great but the interface is not very intuitive. it took me several tries to get my polygon accepted as constraint. I guess it could be improved or simplified. It could be also great to export a polygon that we digitize in the Itwin interface.