Aerial mapping processing
Aerial photography and airborne LiDAR turned into orthophotos, classified point clouds and 3D meshes, published straight into GEORIZON.
Each exposure carries a position and an attitude from the onboard GNSS and IMU, but those alone are not accurate enough to hold a block of several hundred images together. Aerotriangulation solves the geometry properly: tie points measured automatically between overlapping images, ground control where the project requires it, and a bundle adjustment that resolves every camera station at once.
The LiDAR strips get the same treatment. Overlapping flight lines are adjusted onto each other, which removes the step you otherwise see along the seam between two passes. Only after that adjustment does anything get orthorectified, classified or published, because a correction applied afterwards cannot repair a block that was never solved.
A nadir orthophoto tells you where something is; an oblique image tells you what it looks like. Together they answer most questions a maintenance or permitting team has, which is why we publish them side by side rather than as two separate deliveries.
The orthophoto is mosaicked with seamlines that avoid buildings where possible, and the colour is balanced between flight lines so the result does not band along the strips. The oblique imagery keeps its exterior orientation, so you can measure in it and project features onto the point cloud instead of only looking at it.
The finished flight lands in your own tenant: orthophoto as a WMTS layer you can add to QGIS or ArcGIS without conversion, oblique imagery in the viewer, the point cloud streamable and downloadable in LAZ or COPC, and a mesh as 3D Tiles where the project asks for one.
Because every dataset carries the same metadata, an aerial survey from this year sits next to a mobile mapping run from two years ago in the same viewer, in the same coordinate reference system, without anyone first working out what came from where.
