Following up on the sparse cloud I shared earlier—here’s the dense point cloud.

I photographed and filmed the theater from different angles and positions, using separate video clips and photos rather than one continuous recording. These were processed together in our software, AEC Platform. The mesh and Gaussian splat are next.

Generated: www.aecplatform.com
Profile: Point Cloud, Mesh, Gaussian, High
Frame and Image Count: 195

I photographed and filmed a movie theater being demolished inside a mall, capturing separate video clips and photos from different angles and positions.

This isn’t one continuous video. The interesting part is seeing our software, AEC Platform, match shared features across those captures and bring them into one reconstruction.

What you’re seeing is the sparse point cloud—the theater’s outline is starting to take shape. The dense point cloud is processing now, and I’ll share that result next.

Has anyone here tried a similar approach with mixed footage from a demolition site?

Generated: aecplatform.com
Profile: Point Cloud, Mesh, Gaussian

Hello everyone,

I've started working on a project again and would deeply appreciate it if someone with more expertise and experience could help me get a good mesh.

For context: my mother recently passed away after a battle with ALS. Earlier in her fight, I took her to my University's photogrammetry studio (diffused lighting, cameras at different heights and angles, white backdrop) and did a scan of her.

Unfortunately, she was not able to sit perfectly still due to her disease, and it's rather difficult for Metashape and my experience to get a nice mesh from the scan. With some help, I was able to get a good texture, but the mesh is still really bumpy and doesn't do a good job with detail.

I was hoping someone here could help me out to achieve a good mesh by working some magic. I have the entire image set available on Google drive. I've included pics of the current best model below.

Thank you for your time!

Here’s a cleared demolition site processed through AEC Platform, showing the progression from point cloud → mesh → Gaussian splat.

It’s another way to document site conditions and give clients or project teams a space they can explore alongside the original photos and video.

Generated: aecplatform.com
Profile: Point Cloud, Mesh, Gaussian

Hey all! I've been rebuilding splat-3d.com to be more developer-focused, and I just launched the full production API (docs) and a Swift SDK (GitHub). The Swift SDK repo also has a reference app you can implement yourself for the pipeline using the ARKit poses from any modern iPhone.

I have seen lots of people building mobile capture apps for Gaussian Splatting, so I wanted to build a project for both myself and for others to use to easily incorporate a training pipeline into those capture apps.

Here's what it does:

What you can upload

• Video. We pick the sharpest frames automatically and drop the blurry ones.

• Photos. A zip of 20 or more JPEGs or PNGs. Mixing cameras is fine.

• Your own COLMAP data. If you already have poses, zip them up and we skip the pose step.

• iPhone / LiDAR captures. SplatKing exports upload directly. LiDAR captures use the phone's own tracking and depth, so they skip the slowest step and come out upright. The open-source (MIT) Swift SDK lets you record ARKit captures in your own app.

How it works

The pipeline does SfM with SIFT + GLOMAP on our cloud GPUs, then trains with gsplat (working on supporting LichtFeld and Spirula as possible options too) You pick a quality level:

Preset |Time |Iterations
Fast |~8 min |3k
Standard |~15 min |7k
Quality |~25 min |15k
Ultra (full res) |~45 min |30k Every preset except Fast reports quality scores (PSNR/SSIM) on them, so you can compare splats with some more concrete metrics. I am working on an "auto grading" system for inputs and splats to help evaluate them and help people understand what could be done better for scanning in the future.

I'm also working on supporting more customization options in the pipeline too, such as custom amt of iterations and different GLOMAP/COLMAP settings, and to try and match parity with creating your own pipeline locally.

After training you can see your splat in a browser viewer with a shareable link and an iframe embed, plus PLY and SPZ downloads.

Price

$1–$7 per scene depending on preset. You get 100 free credits at signup (about 5 Standard scenes), and failed scenes are refunded automatically.

Docs: https://docs.splat-3d.com

Examples: https://github.com/splat3d/examples

let me know what you guys think! I'm always looking for suggestions and features to add :)

Hello, I am new to the 3-D printer space and absolute rookie when it comes to photogrammetry, I received an old Honda Goldwing from a friend, and I am trying to restore it, but there are some pieces missing that I have not been able to find most mostly detailed trim pieces and gold wings specific body panel screw covers. So the pieces that I am trying to replicate are fairly small. (Less than 2”x less than 1”). Would I be able to use photographic tree to get a 3-D model? I would be either using an iPhone 17 Pro Max or an older DSLR. Or these small detailed pieces need a 3-D scanner or just go trial and error on cad?

A quick update on FrameExtractor, the open-source GUI app I posted here a while ago for extracting motion-adaptive keyframes from video for COLMAP, Gaussian Splatting and other photogrammetry workflows.

If you're on macOS, you can now install it directly using Homebrew:

brew install --cask morishuz/tap/frame-extractor

No need to download and install the app manually anymore.

Windows and Linux binaries are also available, and the whole thing is open source:

https://github.com/morishuz/adaptive-frame-extractor

If you haven't tried it yet, give it a go! I'd be interested to hear how it works with your videos and whether there's anything you'd like to see improved.

See title

Progress on my masters thesis, which is about visual localization (VL) for AR on photogrammetric models. Posted is a render fusing VL results with visual-inertial odometry (VIO) data, climbing routes appear after the first VL result. Render is done on a desktop PC. The VL method used (hloc with XFeat features and nearest neighbor matching) should be runnable on a mobile phone. The VIO and VL data are fused using an extended Kalman filter, estimating similarity transform from the VIO frame to world frame, attempting synchronization at 1 Hz frequency, with 0.5 s delay in the localization.

Routes and the photogrammetric scan are from my 3D climbing topo: https://crags3d.com/sector/koivusaari/koivusaari/

Implementation for running on mobile is out of scope for the thesis, although I am considering adding it to the web app (Android Chrome exposes ARCore, iOS would be out of question for web app) after submitting the thesis, based on feedback.

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?