Month 4 - Not Enough Time

Due to the complexity of my project I was unable to complete all the required tasks of the project. By the time the pipeline was working from Image Gathering to Mesh Creation, I had less than a week to validate data and perform full run tests. This led to major flaws in my hypothesis that could not be accommodated with my remaining time.

Despite this, I was still able to present what I had and received valuable feedback and direction for the upcoming month. The Computer Science Master’s Committee were extremely gracious in providing me with positive feedback and I have a plan for month 5.

I will spend most of month 5 continuing to validate results and adjusting my hypothesis to account for the inherent error of the tools I am using. Specifically, phone GPS are only accurate to five meters, and Depth Anything 3 is only accurate to ± 20% of the actual distance from camera to pixel 92% of the time. This leaves a wide margin for error considering the objects I am trying to triangulate are anywhere from 10 to 100 meters away.

The biggest flaw in my original design is the resolution of the source imagery. Due to the distance of objects from many of the cameras, a very small amount of pixels are being provided to TripoSR for 3D generation. To counteract this, I would like to adjust the initial steps of my project to identify an object and then judge if the area of the bounding box is of a sufficient resolution for TripoSR. If the bounding box area is not large enough the user will be prompted to move closer or readjust their image.

Unfortunately, I will no longer be able to use Mapillary imagery as a source, but I will still be able to create a cheaper alternative to generating 3D meshes of individual objects in an area.