Hey Andrew, I have also been dealing with similar issues. I think I have found a partial workaround to gain some additional water surface (Please note this does not fix the capability of being able to crop, once processing is complete, and yes that should be incorporated immediately). I cannot say how the processing works, but it appears when i apply the processing boundary, in circumstances where i’m processing shoreline, The processing boundary may cut out the few point cloud points in the water used to generate the dsm. Once the dsm/ortho is run, the resulting dsm leaves gaps where photos cannot be applied (The jagged edge look).
What ive done is; (please note ive only done this once so far, could be luck? haha)
- Run steps 1 & 2
- manually built a csv of Water points all set at the same elevation (water elevation) on a grid (25’ x 25’) through the water regions. converted the CSV into a PTS point cloud file, and then converted the PTS into an LAS (This was a pain, but i was able to do it in Trimble Business Center).
- Combine original point cloud and water point cloud
- Used the import point cloud for DSM generation functionality.
-Run Process 3
This gave a nice flat surface with enough definition out beyond for the photos to cleanly project to. If you have the software capable of creating/editing point clouds, its worth playing around with. Then the final imagery falls directly at the nice polygon you drew for processing area.
PS… at minimum, if they cannot add mosiac cropping boundary, they should at least provide the ability to apply a processing boundary in the mosaic editor (Where you can actually see what needs to be cut off and what does not.