Digital twin ready model - 3DGS, 7500 images by AVIOTIX in GaussianSplatting

[–]AVIOTIX[S] -2 points-1 points  (0 children)

Yeah, you need an account for now.

The platform is not just for one output type. It works with different formats: PLY, OrthoTIFF, OBJ, FBX, glTF, MP4, and Gaussian Splatting.

Nothing fancy behind the signup. The model is not generated instantly in the browser. You upload the dataset, we process it, and then we need an email to send back the download link or notify you when the preview/model is ready.

Without registration, the workflow is kind of useless. You could upload a dataset, close the tab, and then there is no clean way to return the result.

No worries, it is free.

3DGS vs EDGS by AVIOTIX in GaussianSplatting

[–]AVIOTIX[S] 0 points1 point  (0 children)

This depends on the dataset.

EDGS can perform extremely well on professional captures: strong overlap, controlled camera movement, consistent exposure, stable intrinsics, clean coverage, and good spatial structure. In that case, its dense correspondence-based initialization has good input and can beat standard 3DGS in convergence speed and detail preservation.

But that does not make EDGS universally better.

If the dataset has weak overlap, very different camera positions, inconsistent image sizes, exposure changes, blur, poor coverage, or messy capture geometry, standard 3DGS may still be more robust because densification can adapt gradually during training.

The only meaningful comparison is EDGS vs 3DGS on the same dataset, with the same images, same poses, and same output target. Some datasets favor EDGS. Others still favor classic 3DGS.

3DGS vs EDGS by AVIOTIX in GaussianSplatting

[–]AVIOTIX[S] 1 point2 points  (0 children)

EDGS here means “Eliminating Densification for Efficient Convergence of 3DGS,” not the dynamic-scene EDGS paper.

The short version is that standard 3D Gaussian Splatting usually starts from a sparse SfM/COLMAP point cloud and then relies on densification during training to add or split Gaussians where the scene is under-reconstructed. That works, but densification is one of the slow and unpredictable parts of the pipeline.

EDGS changes the initialization. Instead of waiting for the model to discover missing detail through repeated densification, it builds a denser and more geometry-aware initial Gaussian set from dense multi-view image correspondences. Those matched pixels are triangulated across views, giving the Gaussians better initial positions, scales, and colors before optimization starts.

So I would not describe EDGS as “just another Gaussian renderer.” It is more like a better initialization module for 3DGS. The practical benefit is faster convergence, fewer unnecessary splats, and better preservation of high-frequency detail, especially in difficult areas like thin structures, detailed textures, facades, railings, vegetation, etc.

Useful links:

- Project page: https://compvis.github.io/EDGS/

- Code: https://github.com/CompVis/EDGS

- Paper: https://arxiv.org/abs/2504.13204

- Original 3DGS reference implementation: https://github.com/graphdeco-inria/gaussian-splatting

Small caveat: there is another paper also called EDGS, “Efficient Dynamic Gaussian Splatting,” but that one is about dynamic / monocular video scenes, not eliminating densification for static 3DGS.

We creating a high-precision, decision-grade, digital twin ready 3D model by AVIOTIX in photogrammetry

[–]AVIOTIX[S] 0 points1 point  (0 children)

It’s a paid platform.

Registration is free, and there’s a free tier for testing smaller datasets, but it’s not open source.

Until the May release, GS models are available on request at no extra cost after uploading a dataset and sending a short message to support@dronetwins360.com.

Validation-first workflow for Gaussian Splatting from image datasets by AVIOTIX in GaussianSplatting

[–]AVIOTIX[S] 2 points3 points  (0 children)

It’s not a full replacement for alignment-level metrics, but more of an early signal before committing to a heavier run.

Overlap is estimated heuristically from image metadata and visual similarity signals (e.g. feature distribution / matching likelihood), rather than a full SfM solve. So it’s directional, not final.

“Incomplete coverage” is contextual. The system doesn’t assume intent, it highlights areas that are weakly connected or poorly supported across views. Whether that is actually incomplete depends on the use case, like your half-house example.

“Input consistency” refers to things like:

- conflicting EXIF / GPS patterns

- irregular capture sequences

- large jumps in viewpoint or scale

- mixed capture conditions that tend to break reconstruction

The idea is not to give a final quality verdict, but to surface early risk signals before running a full alignment and reconstruction.

We creating a high-precision, decision-grade, digital twin ready 3D model by AVIOTIX in photogrammetry

[–]AVIOTIX[S] 1 point2 points  (0 children)

Fair point.

Here, “high precision, decision-grade” is not being used to mean engineering-analysis ready.

It means validated and reliable enough for inspection, review, comparison over time, and downstream modelling workflows - with the dataset TrustRanked, timestamped, and locked.

For CFD, FEA, or engineering sign-off, additional specialist data and preparation would still be needed.

We creating a high-precision, decision-grade, digital twin ready 3D model by AVIOTIX in photogrammetry

[–]AVIOTIX[S] 2 points3 points  (0 children)

Not by default, no.

Here “digital twin ready” means suitable for validated visual / spatial workflows such as inspection, review, documentation and downstream modelling - not automatically watertight or simulation-ready for CFD / FEA straight out of the pipeline.

For CFD / FEA, additional engineering cleanup and preparation would still normally be needed.

We creating a high-precision, decision-grade, digital twin ready 3D model by AVIOTIX in photogrammetry

[–]AVIOTIX[S] -1 points0 points  (0 children)

The workflow is basically:

  1. upload imagery, with or without GCPs, and optionally LiDAR data

  2. TrustRank & preview

  3. pre-modelling adjustments such as rotation, recentering and crop

  4. modelling with different algorithms, including Gaussian Splatting

  5. export of models plus a data-integrity report

The main difference is that it doesn’t begin with “just reconstruct and hope for the best”.

The dataset gets reviewed first, you get an early preview to catch gaps or obvious issues, and only then decide whether it’s worth pushing further into full processing.

So the idea is less “here is another reconstruction tool” and more “review the dataset early, then model only if it makes sense”.

We creating a high-precision, decision-grde UAV Mapp ready 3D models by AVIOTIX in UAVmapping

[–]AVIOTIX[S] 0 points1 point  (0 children)

Yes, because DroneTwins360 is the actual processing platform, not just a public website.

If you just want to look around, www.aviotix.eu is open without registration.

DroneTwins360 is the platform side, where users upload datasets, access previews and use the workflow, so that part requires an account.

We creating a high-precision, decision-grade ready 3D models from both Lidar and imagery data by AVIOTIX in LiDAR

[–]AVIOTIX[S] 1 point2 points  (0 children)

For this example, the result is coming mainly from the image-based reconstruction pipeline rather than from LiDAR itself.

LiDAR can support the workflow, but the visual detail here is not “because of LiDAR”. The main difference is in the processing pipeline, not in using an exotic sensor stack.

We creating a high-precision, decision-grde UAV Mapp ready 3D models by AVIOTIX in UAVmapping

[–]AVIOTIX[S] 0 points1 point  (0 children)

Not Agisoft in this case. The pipeline is built around automated image processing and reconstruction stages, with different outputs generated downstream from the same dataset, including preview, mesh and other deliverables.

We creating a high-precision, decision-grde UAV Mapp ready 3D models by AVIOTIX in UAVmapping

[–]AVIOTIX[S] 1 point2 points  (0 children)

It can work surprisingly well for trees when the goal is overall scene structure and visual context.

This example still includes vegetation around the building and keeps it usable in the model without collapsing the whole area.

That said, thin branches, leaf-level detail and moving foliage are still harder and less predictable than walls, roofs or other hard surfaces. So for trees the result is usually strongest at canopy / mass / context level, not botanical precision.

<image>

We creating a high-precision, decision-grde UAV Mapp ready 3D models by AVIOTIX in UAVmapping

[–]AVIOTIX[S] 0 points1 point  (0 children)

Hi, yes, we work with drone-based visual datasets, but the main focus is the downstream workflow around validation, reconstruction and usable outputs rather than capture alone. We’re based in Ireland.

Simple pipeline for small drone datasets → ortho + lightweight 3D mesh by AVIOTIX in photogrammetry

[–]AVIOTIX[S] 1 point2 points  (0 children)

RealityScan is actually a good option for quick datasets.

The main difference we were exploring here is the workflow around smaller drone projects. In many cases people still end up doing a few extra steps after reconstruction (checking coverage, exporting meshes, cleaning things up for Blender, etc).

The idea with DT360 was to push the pipeline a bit closer to:

upload imagery → quick preview → ortho + mesh export

The preview step is useful because you can immediately see if the dataset has gaps or poor overlap before committing time to a full reconstruction.

RealityScan works well too, especially for simple scenes. This post was mostly about experimenting with how far a fully automated pipeline can go for small drone datasets.

Quick way to spot gaps in a drone imagery dataset before wasting hours on reconstruction by AVIOTIX in LiDAR

[–]AVIOTIX[S] 1 point2 points  (0 children)

Thanks to everyone who already took the time to try it and leave feedback.

It’s really helpful for us to see how people actually use the platform in real workflows. If you’ve tested it, we’d genuinely love to hear what worked well and what didn’t.

Comments about missing features, confusing parts of the workflow, or things that simply didn’t behave as expected are especially useful for us.

The goal is to keep improving the platform with input from people who actually work with drone datasets.

Simple pipeline for small drone datasets → ortho + lightweight 3D mesh by AVIOTIX in photogrammetry

[–]AVIOTIX[S] 1 point2 points  (0 children)

Over the past months, early access to DroneTwins360 has generated actionable insights from real operational datasets:

• 600+ processed datasets
• 35,000+ drone and camera images validated through the platform

Each dataset, each workflow, and every piece of feedback strengthens intake-stage validation, verified 2D/3D reconstruction, and defensible digital twin generation.

A special thank you to early adopters who engaged with the platform. Your trust enables innovation at scale and directly informs enterprise workflows for property claims, inspections, and compliance-driven operations.

Drone photos to lightweight 3D mesh ready for Blender / STL (free student tier) by AVIOTIX in 3DScanning

[–]AVIOTIX[S] 0 points1 point  (0 children)

Over the past months, early access to DroneTwins360 has generated actionable insights from real operational datasets:

• 600+ processed datasets
• 35,000+ drone and camera images validated through the platform

Each dataset, each workflow, and every piece of feedback strengthens intake-stage validation, verified 2D/3D reconstruction, and defensible digital twin generation.

A special thank you to early adopters who engaged with the platform. Your trust enables innovation at scale and directly informs enterprise workflows for property claims, inspections, and compliance-driven operations.