Tips & gotchas

Big designs take time. A 30,000-point design takes several minutes to triangulate. Don't kill the app — wait for the percent ring.

LandXML files need a CRS. NAD83 State Plane (Nebraska, Iowa North/South, Kansas North/South) and UTM are recognized automatically. Other zones fall back to OGC WKT parsing. NAD27 zones that need a datum grid shift (including the Dakotas) are not supported — they fail cleanly on import rather than placing the design in the wrong location. If the import fails, your file may not have a recognized CRS.

LandXML unit handling. Files declare their linear unit. The importer recognizes US Survey Foot (commonly used in older US State Plane datasets), International Foot (most newer files), and metric metres. Mismatches cause elevations to be off by ~6 mm per km — rarely operator-visible but matters when stitching surfaces with adjacent jobs.

XYZ vs XYZP. If your file has only existing elevations and no proposed, you cannot grade it as a Forming surface — there is no target. Either use it as a survey for Slope-IQ instead, or get the XYZP version from your design software.

Section by section. Use AGD boundary loops to split the field into 1-2 acre chunks. Finish one before moving to the next so the coverage map tells a clear story.

Drive-to BM works while moving. You don't have to stop the machine to enter drive-to-BM mode. Tap the BM in the list, drive toward it, and only stop when the headline says "On the benchmark".

The simulator drives the design. When the simulator is running and a Forming design is loaded, the simulated machine drives at ~2 mph from the design centroid in a coverage pattern. Useful for office demos.