When two systems don't speak the same language By this point, we had a fairly complete inspection workflow inside our own platform. Data was collected in the field. Images were processed and correlated to inspection assets. Inspectors could review the results and annotate anomalies. That covered the part
Building software that inspectors actually wanted to use When we finished the mission planner and the processing pipeline, we finally had an end-to-end system. The drone could execute repeatable missions. Thousands of images could be uploaded and processed automatically. Every image could be correlated to the correct inspection asset. From
Technology
Why drone inspection planning is a data management problem, not a navigation problem In my previous post, I talked about how I stopped thinking of mission planning as simply making a drone fly from one waypoint to another. The real challenge was making inspections repeatable. That realization changed the way
Drone
Why building a mission planner for substations had little to do with maps—and everything to do with safety, repeatability, and engineering constraints When I first started building mission planning software for substation inspections, I thought the hard part would be making the drone fly autonomously. What I didn'