ToolQuill

Private civil-data exchange preflight

LandXML Alignment / Profile / Surface Auditor

Inspect LandXML units, coordinate-system evidence, alignment stationing and continuity, design and sampled profiles, TIN points/faces, and named relationships—without uploading project coordinates.

LandXML XML input

Open or paste a LandXML document

No LandXML selected.

LandXML is limited to 24 MiB. Project names, coordinates, surfaces, alignments, and reports remain in this browser tab. No schema, CRS, or referenced file is fetched.

Paste or choose a LandXML document.

Private by design: project identity, control and design coordinates, stationing, profiles, surfaces, filenames, and reports stay in this browser tab. Nothing is uploaded, geocoded, or reprojected.

What the auditor checks

The bounded namespace-tolerant parser checks root/version evidence, Metric or Imperial unit declarations, coordinate-system metadata, unique alignment and surface names, declared versus component alignment length, line endpoint lengths, curve center/radius evidence, element continuity, cumulative station starts, station-equation ordering, design/sampled profile station ordering and ranges, TIN point IDs, triangle references and degeneracy, declared elevation extrema, and named alignment/surface references.

Coordinates and stationing

LandXML coordinate tuples are shown in file order as northing, easting, and optional elevation. Station values are kept in declared linear units. Station equations can make displayed station labels diverge from simple geometric distance, so cumulative mismatches are warnings that preserve the relevant evidence rather than silently rewriting station values.

Profile relationships

Design ProfAlign points and curves and sampled ProfSurf station/elevation pairs are plotted together for their parent alignment. The graph reveals range and relationship differences; it does not calculate a finished vertical curve, earthwork, grades, sight distance, or construction stakeout.

Engineering and survey boundary

This is a read-only exchange-file preflight, not complete LandXML schema validation or professional design review. It does not transform coordinate systems, resolve datums, prove point order or units, reproduce exact spiral/curve geometry, validate every LandXML object or vendor extension, test topology, calculate volumes, establish legal boundaries, repair data, or certify survey/design accuracy. Confirm results with the official schema, source drawings, known control, qualified professionals, and target civil software.

Frequently asked questions

Why are coordinates labeled northing before easting?

LandXML coordinate tuples use northing/easting order. The tool preserves and labels that order to avoid silently swapping it into generic X/Y display conventions.

Why can a station warning occur on valid geometry?

A station equation or producer convention can make displayed station values differ from cumulative physical length. The warning invites review; it does not automatically declare the design wrong.

Does a clean TIN result prove the surface is correct?

No. It means supported point/face references and structural checks passed. It does not establish source accuracy, correct triangulation, non-overlap, breakline behavior, datum, or design intent.

Authoritative references

The LandXML 1.2 namespace identifies the official LandXML 1.2 XML Schema. The buildingSMART Finland LandXML 1.2 alignment documentation details horizontal elements, stationing, coordinate order, and vertical profiles. Autodesk documents supported LandXML alignment, profile, surface, and reference structures.

Audit a world-file georeference · Audit a Shapefile bundle · Browse civil and surveying tools