TBC Photogrammetry Ortho Rendering Errors
Has anyone noticed rendering errors in orthoimagery generated with Trimble Business Center’s photogrammetry module?
My survey team has been performing around forty photo and/or lidar UAS missions per year, typically for landfill volumes. We’ve experimented with Pix4D, Site Scan, LP360, DJI Terra and now TBC Enterprise to process data and produce large high quality orthoimages and C3D surfaces. We’re a Trimble shop and so, begrudgingly at first, I’ve learned to use and now like TBC. However, no matter what procedure I’ve used, if there are elevated structures such as overhead conveyors, parked trailer trucks, buildings etc., the TBC orthos warp or checkerboard said structures. Bare earth seems to be rendered correctly. The same data run through Pix4D or Site Scan comes out crisp with no warping or checkerboarding. In all cases, the orthoimage matches incredibly well with my aerial targets or painted checks. While the point cloud data continues to awe and amaze me, the clients only see the pretty picture and I haven’t been able to generate anything in TBC that matches the quality of Pix4D or Site Scan. I’ve tried tagging the photos and just processing with RTK or PPK.
General flight and equipment parameters:
1. DJI M350 RTK Drone
2. Zenmuse L1 Sensor
3. RTK corrections from NC-VRS (quite robust as compared to most real time networks)
4. 180ft AGL with DEM used for Terrain Follow
5. 50% side and 70% forward overlap
6. 10.6 MPH
7. Aerial targets
8. Triple Return with Repetitive Scanning
9. Lawnmower flight pattern with occasion cross hatch.
Is it me or TBC or maybe a bit of both?
Log in to reply.