DTM and TIN checked
Reads the points and finds duplicates in plan, break codes that didn't become breaklines and gaps in coverage before triangulating.
Deliverable: surface with a list of issuesOcto for terrain modeling
Cut and fill volumes, contour lines and stockpile measurement are differences between two surfaces, and almost all of it runs in batch with GDAL, PDAL and Python, checked against the program the office already uses (Carlson, Civil 3D, Topograph, DataGeosis). Octo builds the scripts, runs them with two grid spacings, draws the cut-and-fill map and points out what doesn't add up. Base, breaklines, tolerance, density and the measurement with an ART stay with the technical lead.
Six possible deliverables, drawn from the research. All of them work on a copy of the field files, and all of them go to review by the person who signs the measurement.
Reads the points and finds duplicates in plan, break codes that didn't become breaklines and gaps in coverage before triangulating.
Deliverable: surface with a list of issuesDifference between original and current ground at two grid spacings, a color map with a neutral band and daylight line, and a report with warnings.
Deliverable: volumes + map + reportIndex and intermediate contours on the client's layers, labels aligned and never upside down, short segments discarded, one sheet per DTM.
Deliverable: DXF per sheet + summaryTerrain sampled station by station, cut and fill areas per section, volumes by average end area and a cumulative volume table.
Deliverable: tables and drawing for checkingThe flight's point cloud becomes a grid per stockpile, volume over the chosen base, mass by the approved density and reconciliation with the recorded movements.
Deliverable: history per stockpile + open itemsThe same calculation in the office program and in the open script, with the same boundary. A difference above tolerance becomes a question, not an adjustment.
Deliverable: side-by-side table of the two calculationsThe same Octo cycle, applied to terrain modeling. Each arm has a narrow role; the ones who choose the base, approve the density and sign the measurement are people.
Surveys and dates, equipment, coordinate system, the office program and its version, volume reports already issued.
Horizontal and vertical reference frames, the boundary of each area, field codes, approved densities and the measurement history.
Reads the field files and calculates on a copy. Private areas, tonnage and shipments are the client's confidential information and don't go to an external service without agreement.
The office program, GDAL, PDAL or Python; grid or TIN; floor or toe as the stockpile base; DXF, GPKG or a report as the deliverable.
Dry run, two grid spacings, warnings and exit codes, with the source of each syntax noted in the file.
Compares with the office program or with an old measurement already accepted, by the numbers and the map, not by the absence of errors.
Only with the lead's OK, it writes DXF, report and history where the team works. Nothing goes to invoicing or inventory without a person.
Parameters, versions, base method and the result of each measurement, so next month's is comparable.
Octo works with read access and in a support role. It does not sign surveys, does not issue measurements for payment and does not adjust inventory: that belongs to a licensed professional, with an ART or TRT.
The criteria Octo uses to choose. Always with the documentation for the installed version and a check against a calculation already accepted.
| Task | Path | Notes |
|---|---|---|
| Volume between two point surveys | SciPy Delaunay + grid, or TIN to TIN in CAD | Two spacings and the same boundary |
| Volume between two drone DTMs | gdal_calc --calc="B-A" --extent=intersect | Same vertical reference |
| Cut-and-fill map | gdaldem color-relief with a diverging palette | Neutral band equal to the accuracy |
| Daylight line | gdal_contour -fl 0 on the difference grid | Vector for the drawing |
| Batch contour lines | gdal_contour or gdal raster contour | The client's contour interval |
| DXF contours with layers and labels | ezdxf over the GDAL output | The client's drafting standard |
| Grid from a point cloud | PDAL writers.gdal | Classes listed, not negated |
| Stockpile volume | Stockpile grid minus the base (floor or toe) | Method recorded on every row |
| Volume surface in Civil 3D | API: AddTinVolumeSurface and Statistics | Details in the Autodesk case |
Three steps. Each one only makes sense after the previous one has shown results on your survey team.
A proposal, not a promise
You send the original ground, the current one and the boundary; Octo redoes the calculation by script and puts it next to your program's number.
Contours, profiles and sections for many sheets come out in the client's standard, with a summary per sheet for review.
Stockpiles and work fronts measured every month with the same method, a comparable history and reconciliation with the client's system.
Every point below has a source published by the responsible agency (Planalto, INCRA, IBGE, ANAC, DECEA), by the vendor or by the project. ABNT standards appear only by number and title. The sources are in the next section.
4
points with a published source, each with its reference shown alongside.
gdal_contour accepts -i, -fl, -off, -3d and polygons with -p; the new CLI has had gdal raster contour since 3.11. gdal_calc has had --extent=intersect since 3.3 and depends on the Python bindings.Source: gdal.org, gdal_contour, gdal raster contour and gdal_calc pagesfilters.range, ranges on the same dimension are combined with OR and on different dimensions with AND. Two negations on the same dimension let everything through; the example lists the classes to keep.Source: pdal.io, filters.rangeAddTinVolumeSurface (base and comparison) and returns CutVolume, FillVolume and NetVolume in Statistics.Source: Autodesk, Civil 3D developer's guide (2023)Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and produces the documents: spreadsheets, reports, drawings and draft legal descriptions.
Deliverable: material ready to checkThe licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.
Step: checked by the person who signsOcto does not sign. Designs, technical reports, ART/RRT, statements of account and any official document are still signed by the licensed professional at the company or agency: here, the surveying or cartographic engineer with an ART filed with CREA, or the surveying technician with a TRT filed with CRT; for rural properties, the professional accredited by INCRA, who submits to SIGEF.
Signature: licensed professional, with ART or TRTDocumentation from open-source projects and vendors used in the research, consulted on Oct 31, 2026.
The assessment starts with a measurement your team has already done: the original ground, the current one and the accepted number. You get the same calculation by script, the map and the list of what can be automated, and you decide with that in hand.