Reality capture and BIM
Orthomosaic from drone photos, 360 walkthroughs and IFC models to see your project as it is today
You upload the flight photos and the platform builds the orthomosaic. You compare 360 walkthroughs across dates, measure on the map and pin issues and RFIs to the elements of an IFC model.
The problem
Looking at the site through loose photos doesn't let you compare what changed
Drone photos pile up in a folder and nobody knows which one belongs to which week. Measuring an area or an earthmoving volume takes a surveyor and days.
The BIM model lives in another program, far from the issues that happen in the field.
How it works
From photos to the map and the model
You upload the flight photos
Between 20 and 500 JPG photos, up to 40 MB each and 4 GB in total. Without location data in the photos they can't be georeferenced.
The orthomosaic is generated
An open-source engine (NodeODM) processes the images in a background job, with a cap of 12 hours.
You compare and measure
You see the orthomosaic for each date, compare 360 points with a slider, measure distances and areas, and calculate the cut-and-fill volume by subtracting two elevation models.
You upload the IFC model
You walk through it in 3D, look up the type, level and properties of each element and pin RFIs, punch-list items, findings or nonconformities to an element.
What sets it apart
What you can check, not just take on faith
- No dependence on a third-party map
- The orthomosaic is displayed without external base-map services.
- It says why it doesn't calculate
- The volume is not calculated if the grids don't match, if georeferencing is missing or if the coordinate system isn't supported, and it explains why. It also reports the coverage of the calculation.
- Issues anchored to the element
- An RFI or a finding is pinned to the model element, not to a lost drawing.
- From RVT to IFC, with guidance
- BIM Models accepts IFC and .ifczip. Selecting an RVT or RFA file opens guidance for exporting to IFC: the native file is not parsed.
- DWG drawings as input
- Drawings accepts DWG and the engine converts it to DXF for analysis. Drawing output remains DXF; it does not generate DWG.
What it doesn't do
The limits, stated up front
- Processing time depends on the flight and the server's capacity; 12 hours is a cap, not a typical time, and no measurement of real times is published.
- The accuracy of the result depends on the flight and the quality of the photos. It does not replace a certified topographic survey.
- The point cloud functions (deviation against the model) have not been tested with a real survey.
- The IFC file is loaded whole into the browser's memory: very heavy models will not open.
- No drone flight is included: you upload the photos.
Compared with what you use today
Compared with photo folders and a standalone BIM viewer
- Spreadsheets
- They're no use for seeing a construction site. Here progress is seen on the map of each date.
- WhatsApp and shared folders
- Photos lose their date and place. Here each capture has a date and is compared with the previous one.
- Generic ERP
- It doesn't process images or IFC models.
Frequently asked questions
What people usually ask before trying it
Do I need a specific drone?
The platform asks for JPG photos with location data; it doesn't depend on a brand. The quality of the result depends on the flight.
Does it measure with survey-grade accuracy?
No accuracy validation is published. Use it for tracking; for contractual deliverables, use a surveyor.
Which model formats does it accept?
Files in .ifc format, with a size limit shown when you upload them.
Next step
Let's upload a flight of your project and see it on the map
Tell us about your project and we'll show you this module with your own data, no commitment.
On the same topic
Other platform modules