Point clouds, no CAD package needed

Supported files

Drop a point cloud into the Start surface or End surface field, anywhere a DXF/OBJ/STL/LandXML surface goes. Accepted formats:

• LAS / LAZ: the standard for drone photogrammetry and laser scans.
• PLY: common from handheld and SLAM scanners.
• XYZ / PTS / CSV: plain text points, comma- or space-separated. The first three columns must be X, Y, Z (Easting, Northing, Elevation). Columns after Z are ignored, but a leading ID or code column will be misread, so put X, Y, Z first, or use LAS/LAZ/PLY.

Points must already be on the same coordinate grid as the rest of your survey; EOMeasy doesn't reproject.

How EOMeasy turns points into a volume

A point cloud has no surface, so EOMeasy builds one for you. By default it triangulates the points into a surface (a Delaunay TIN, the same kind of surface Vulcan and PointStudio build) and trims the long stray triangles around the edge the way those packages do, so the cut and fill reconcile to your native figures. Very large clouds (over about 3 million points) fall back to a fast grid instead, with a note on the report.

Two per-volume controls fine-tune it, both for point clouds only:

• Ground points sets how repeated shots at the same spot are resolved:
  • Average (default): matches how CAD packages read the points, so volumes reconcile to Vulcan/PointStudio. Best for clean pit and scan data.
  • Lowest: the lowest shot at each spot wins, giving bare earth under vegetation or equipment. Best for drone photogrammetry over grass or scrub.
• Edge trim sets the longest triangle edge (in metres) to trim at the boundary. Leave it blank to auto-detect (about twice the point spacing), or set it to the same "trim large triangles" distance you use in your CAD package to reconcile exactly.

From there it's the same engine as a CAD surface: the cut, fill and net reconcile the same way.

You can skip the boundary

No package usually means no boundary string either. Leave the Boundary field blank and EOMeasy measures over the area both surveys cover (the overlapping surveyed footprint), and notes on the report that the boundary was auto-derived.

Tip: survey only the area that actually moved. Because there's no boundary to trim it, anything both surveys cover counts toward the volume. If you want to scope it precisely, drop in a boundary (DXF or CSV) as usual.

Same report, same reconciliation

Everything downstream is identical: the plan-view render, the PDF report, the CSV, running totals and warnings all work exactly as they do with CAD surfaces. Point clouds are just another way in.