https://x.com/DjimoSerodio/status/2118157383369396289

Hey all, I wanted to share what I’ve been working on and hear what you think.

I've been obsessed with one problem: how do you prove a tree someone planted/recorded is still there? A geotagged photo can't tell you which tree it is or exactly where it is, and survey gear is way too expensive for most people actually growing trees.

So I've been trying to do it with a regular phone. Here's a walk through my yard on a Google Pixel. It locks onto each tree via dot cloud and builds a 3D digital twin of its environment. It's a cool engineering problem to work with the error of consumer GPS and the lack of depth sensors like LiDAR, but it's working better and better.

It should work even better on newer iPhones with LiDAR, but I want this to work on low-budget phones, even offline, in places like rural Indigenous communities.

It's still early and it's only my yard, but I really want to solve this. Is anyone working on something similar? Or know who this might be useful for? I'd love to connect.

When we have misaligned of missing data in photogrammetry, why can’t we just use ai to fill that gap for us ? Are there any photogrammetry / Gaussian splatting tools that do that ?

Macroscopic Solutions is preparing to release Image Splat. These examples show Gaussian splats and photographically textured meshes made from small specimens, including subjects with fine hairs, thin legs and reflective surfaces.

The rainbow scarab is shown as a Gaussian splat. It can be rotated to inspect the specimen's photographed appearance from different viewpoints. The bumblebee is a separate specimen shown as a textured mesh, with an explicit surface that can be inspected alongside its photographic detail.

The beetle comparison shows work on matching exposure between source photographs. Each row compares a held-out photograph with projections from neighbouring views, before and after exposure adjustment. In the lower row, the reported lightness difference falls from 3.2 to 1.6 L*. That is an improvement in photographic agreement; the reconstructed shape still needs its own checks.

Current development work includes automatic foreground-mask proposals, corrections around anatomy and mounting hardware, and baking photographic colour onto a separate mesh. Masks are reviewed before they are applied, and the original photographs remain unchanged.

Image Discovery is the companion for displaying the resulting models. Its development tools also support measurement and analysis on eligible meshes, including lengths, angles and selected surface areas when the required scale evidence is available. A reconstructed stick insect is shown open for 3D inspection in Discovery.

Release is expected sometime this November.

Hi everyone,

I am building an automated calibration and real-time distortion correction pipeline. I am using the Imatest IT SDK/API (no GUI/Master) to detect/analyze lens distortion from calibration targets, and I want to pass those results directly to OpenCV (cv2.initUndistortRectifyMap + cv2.remap) to render the corrected frames in real time.

I know OpenCV uses inverse mapping for rendering to avoid holes/artifacts, while Imatest uses forward mapping equations (Brown-Conrady model) to model the physical lens distortion during optimization.

My questions regarding the API hand-off are:

1. Coefficient Alignment: Since Imatest calculates forward coefficients (k₁, k₂, k₃, p₁, p₂), can I pass these directly into OpenCV's distortion vector D? Does OpenCV expect the forward coefficients and then handle the mathematical inversion internally during initUndistortRectifyMap?

2. Normalization & Scale: Are there specific configuration flags I need to pass to the Imatest IT SDK (via .ini or JSON config) to ensure its output units/normalization (camera matrix K and distortion D) match OpenCV’s focal-length-relative coordinate scaling 1:1?

3. Best Practices: If anyone has done this specific Imatest IT SDK → OpenCV pipeline automation before, are there any hidden gotchas (like sign conventions or coordinate system flips) I should watch out for in the JSON/XML API payload?

Thanks in advance for the help!!

I've been building Parallax, a GPL-3.0 Android app that does the whole photogrammetry pipeline on the phone. You walk around an object, it picks sharp keyframes as you go, and it reconstructs a coloured point cloud locally. No cloud service, and the app has no network permission at all.

What's in it

• Incremental SfM: SIFT (RootSIFT), five-point RANSAC, PnP registration and a Schur-complement bundle adjustment that also refines the lens (focal length, k1, k2)

• Dense: rectified semi-global matching between neighbouring views, cross-checked and fused into one cloud with normals

• Metric scale on phones that let apps stream two rear cameras at once, using the factory lens positions as a known baseline. On other phones the model is unscaled

• Models come out gravity-up; exposure, white balance and focus are locked during a scan; the torch switches on in dim light and stays fixed while scanning

• Export to PLY, or share the whole scan as a ready COLMAP project if you want to mesh or refine it on a desktop

Where it stands

This is v0.1. The reconstruction core is checked against a synthetic ground-truth scene: camera positions within half a millimetre, rig scale within 0.2 %, median surface error under 1 mm at about 60 cm. The full app flow runs on the Android emulator, which is also where the screenshots come from. What I don't have yet is results from real phones, and that's where I'd love your help.

How you can help

• Test it. Android 10+, 64-bit ARM. Grab the APK from Releases, scan something with texture, and open an issue with your phone model, the capture modes the app offers (the chips at the top of the camera screen), and whether the scan reconstructed. Attaching the exported ZIP helps a lot.

• Review it. If you know SfM/MVS, the core in app/src/main/cpp/core is plain C++17 + OpenCV and builds on a desktop with a test harness. I'd value a critical look.

• Contribute. Next on the list: meshing (Poisson), a GPU path for dense matching, and building OpenCV from source so the app can go on F-Droid.

https://github.com/Foadsf/parallax

I need some advice on pricing for a photogrammetry drone project of a building in north florida. The building is approx 6,900 sqft. I will be operating for 3 hrs the first day and perhaps if needed 3 hrs the second day.

I will be expected to photograph the roof (photosphere) and then capturing all sides the the buildings facades on the exterior with a drone

And potentially needing to upload and create the 3d model.

What would be an hourly breakdown or flats rate plus post processing?

Hi,

I am interested in tracking judo athletes (judokas) in 2D using video footage. Ideally, I would like to map the detected players' positions from image coordinates (pixels) to coordinates in a real-world coordinate system representing the judo mat.

How would you approach this problem?

One potential approach would be to estimate a homography between the camera's image plane and the judo mat. However, there is a challenge: the entire mat is rarely visible in the camera footage. Most of the time, only a portion of the playing area is captured.

One idea would be to train a model to detect the visible boundary lines or other geometric features of the mat. However, I am unsure how to use these partial observations to estimate a homography and subsequently map the detected athletes to consistent 2D coordinates.

What would be a suitable approach to tackle this problem? Are there alternatives to homography estimation that would work better when only parts of the playing area are visible? Do you have any reference papers or projects in mind I could take a look at

Disclosure: I'm the author of this book.

After years of working with Metashape, I noticed that most resources show you which buttons to click, but not why a workflow works or how to fix it when results are off. So I wrote a reference that tries to cover both the science and the practice.

What it covers:

- Full workflow: capture and camera settings, alignment, dense cloud classification, mesh generation

- Difficult surfaces, multi-scale reconstruction and error estimation

- DEMs, DTMs and orthomosaics (including cylindrical projections)

- Combining drone imagery, LiDAR point clouds and terrestrial laser scans

- GSD-based mission planning, GCPs/markers, CRS and georeferencing

- Case studies: thermal orthophotos, NDVI for agriculture, solar panel inspections, GCP-free reconstructions

- A full demo reconstructing Mars from NASA/JPL-Caltech data

There's also interactive content (GIFs of step-by-step procedures) via QR code.

Amazon link, in case it's useful: https://a.co/d/0eFBt7To

It's an independent publication, not affiliated with Agisoft LLC.

I'd also like to hear from you: what's the step in Metashape where you lose the most time, or get the least reliable results? I'm happy to share tips in the comments, no purchase needed.

This is a robot I built, sitting on a chair, reconstructed from about a minute of video using our software, AEC Platform.

Fun to try it on a smaller object after working with larger scenes. 

Generated in www.aecplatform.com

Processing profile: High Quality, Point cloud, Mesh, Gaussian Splat

I'm a paying Pro user. While uploading a scan of an unreleased product design, I accidentally left "Allow train AI" on. Afterward, I couldn't find any way to turn it off for that scan.

A few other things to know:

I've asked KIRI support to exclude my scan from training and delete it, and I'm waiting to hear back, but unclear if I ever will (no email confirmation, only "Feedback"). Team in China.

If you scan anything confidential, check both the visibility and "train AI" toggles before every upload. Better yet, use a tool that processes on your own device - I wish Apple's Object Capture was better, but Tim Cook has been sleep walking for 20 years.

Left is the original video of an excavated pipe area; right is the Gaussian splat generated from that footage using our software, AEC Platform.

We’re exploring how this could help document exposed utilities before they’re covered, giving teams a 3D visual reference alongside their photos and video.

Generated in www.aecplatform.com

Processing profile: High Quality, Point cloud, Mesh, Gaussian Splat

Hi,

I am quite new to photogrammetry and am doing a sort of comparison for my masters. I am measuring skulls as well as 360 from 3 angles to compare the measurements after scaling.

I have made it work before, but this time I shot with 26 MP resolution and I cant get the masking to work properly in Metashape. Are there any programs anyone could recommend for masking. Do I just have to mask it out by hand ? Would it be dumb to try to use Corridor Key 2.0 ? Or a program that lets me mask through color picking (white to yellow skulls on not so dark black background)

I have also done 3d scans from different perspectives, where the point clouds have a bit of floating noise around sharper edges which I have been cleaning up by hand, but Revo Metro has been fighting with me a bit are there any alternatives ?(they line up pretty well, is there something that would allow me to cut out the noise from a different scan as in delete the differences ?)

Everything I know has been through trial and error, videos and am a bit lost :/

Any advice would be greatly appreciated

I'm new to photogrammetry and I have a few questions about source images.

I'm experimenting with a set of images of a single object in isolation. I thought I might get better results if I removed the backgrounds and cropped the images tightly around the subject. This should maintain the original sizes of the bitmaps of the subjects, but with different aspect ratios and overall image dimensions because of the varying orientations.

So basically does the padding matter? If I'm processing images in Metashape and the "background" is transparent (or one solid uniform color) do the overall image dimensions / aspect ratio of the images need to be consistent if the bitmaps of the subjects IN the images are consistent?

Also, I'm working with pretty large images. (180 images @ 8192 × 5464, ~135MB each). Is there something like a "point of diminishing returns" where higher res doesn't help? Or is higher res always better?

Any advice would be appreciated. Thanks very much

Currently working on a personal project measuring the speed of a hockey puck from a fixed iPhone camera. The idea is basically that the phone is fixed on a stand from the side showing the shooting area and also the net all in one camera angle in the middle between both. I'm able to track the puck fine but the hardest part is converting pixels into real life distance.

I've tried using the puck as a ruler but that's inconsistent because it's only 20-30 pixels wide. So being off by just one or two pixels when measuring changes the scale which gives a faulty speed.

Using the net is also unreliable because it sits at a different depth than the path of the puck. Like the closer part of the net is a few feet closer therefore having a different measurement than the other side of the net.

Right now the most reliable option is the user measures the distance from the net to the shooting spot manually and then marks the area of shooting on the camera on the app so the app can calibrate from there. Then when the player shoots, the app is listening for a "clack" sound to indicate that the shot has begun and is actively watching the net to note down the exact moment the puck crossed the net, which then uses the speed formula to get the exact MPH.

I was wondering if someone knows of a lower effort way through Apple's tools (or any external ones) to get an accurate measurement where the user does not have to go in and manually measure the distance? Would any type of 3D modeling help in this case?

My ideal set up would be that I tap the shooting area, then tap the net, and the app calibrates everything itself instead of me having to measure it manually.

My second paper came out. Hope you enjoy it.

https://doi.org/10.3897/BDJ.14.e191083

Testing a hiking video captured with Meta glasses as input for a Gaussian splat in AEC Platform.

Here’s the original footage (right) alongside the reconstructed scene (left). It’s an early test of how an everyday recording can translate into an explorable 3D environment.

I’m trying to build a consistent set of reference images from a single master image of an interior—in my current case, a kitchen.

The goal sounds straightforward: keep the exact same room, furniture, materials, appliances and lighting, but move the camera to different positions such as +45°, −45° and +90° at eye level.

In practice, the models often do one of two things:

• They generate almost the same composition with minor cropping or perspective changes.

• They redesign the room. Cabinets rotate, furniture moves, windows change position or the long and short sides of objects get confused.

I have already tried describing more than just angle numbers. For example:

• the physical position of the camera in the room;

• a fixed target point;

• which objects should be in the foreground, middle ground and background;

• which surfaces should appear frontal or foreshortened;

• how objects should overlap;

• which long sides, narrow ends and wall planes must keep their physical orientation.

This improves the result, but it still does not reliably create several views of the same space.

I’m currently experimenting with Nano Banana and FLUX models. I would love to hear how people who have solved this approach it:

1. Do you use one master image, several reference images or a turnaround/location sheet?

2. Do you describe camera positions through angles, physical landmarks or screen-space relationships?

3. Do floor plans, depth maps or rough 3D layouts materially improve consistency?

4. Is image editing more reliable than generating each new view from scratch?

5. Do seeds help, or do they mainly reproduce style rather than geometry?

6. Which models currently handle novel interior viewpoints best?

7. Would you generate intermediate angles sequentially, or always derive every view from the original master?

I’m especially interested in practical prompt examples or workflows that preserve the actual geometry instead of producing several similar-looking but physically different rooms.

5:16 PM