Services

What Mathyra
does with a plan set.

Six services along one pipeline — from the ink on a sheet to a validated engineering model. Each is labelled with where it genuinely stands: working today, in development, or the vision.

01

Plan set extractionWorking today

Vector plan sets in, structured engineering data out — calibrated against each sheet’s own rulers rather than an assumed scale.

  • Cross-section geometry recovered as coordinates, not pixels
  • Stations, offsets and elevations read as engineering values with units
  • Scale and datum corroborated by two independent sources per band
  • Deterministic: the same plan set produces the same output, byte for byte
02

Evidence & provenanceWorking today

Every exported coordinate carries a trace back to the sheet, the band, and the drawn objects that produced it.

  • Per-value source: sheet number, station, page location
  • A conformance report stating what was read, what was withheld, and why
  • Revision-aware comparison between plan set versions
  • A value that cannot name its source does not ship
03

Ambiguity & refusal reviewWorking today

Where the drawing does not determine an answer, Mathyra flags it in a registered vocabulary instead of guessing.

  • Enumerated refusal reasons, counted in the denominator
  • Review queue of the values a human should adjudicate
  • Contradiction surfacing where two readings disagree
  • No silent averaging, no invented values
04

Cross-sheet reconciliationIn development

The same station lives on plan, profile, cross-section and control sheets. Mathyra compares what each one states.

  • Alignment attribution: which roadway a value belongs to
  • Profile-versus-section elevation agreement at shared stations
  • Disagreements reported as contradictions, not reconciled by fiat
05

Georeferencing & controlIn development

Coordinate systems, vertical datums and combined factors resolved from the sheets that state them — refused where they do not.

  • Survey control tables read from the drawing
  • CRS, datum and unit resolution with provenance
  • Explicit refusal when a plan set never declares its frame
06

Surfaces & model deliveryThe vision

Corridors and surfaces assembled only from geometry that survived validation — and exports into the tools your team already runs.

  • TIN surfaces built from qualified geometry only
  • LandXML, CAD and GIS export paths
  • Machine-control-ready deliverables with an audit trail

How an engagement runs

Four steps, and you see the evidence at every one.

01

SEND A PLAN SET

A representative volume — cross-sections, profiles, whatever the project runs on.

02

PRE-FLIGHT

We report what is readable before any commitment: page classes, vector coverage, expected refusals.

03

EXTRACTION

Geometry, values, provenance and a conformance report stating limits in plain terms.

04

REVIEW

You adjudicate the flagged items. Nothing ambiguous is resolved without you.

Mathyra is in private development. Engagements today are pilots run with the team, not self-serve — which is the honest state of a product still earning its accuracy claims.

Who it is for

Built for the people who pay when a number is wrong.

  • Contractors & estimatorsKnow what the plan set actually says before the bid, and where it contradicts itself.
  • Surveyors & modellersStart from recovered geometry with provenance instead of re-keying elevations by hand.
  • Design & QA teamsCatch cross-sheet inconsistencies while they are still cheap to fix.
  • Infrastructure ownersAn auditable record of what was extracted, what was withheld, and why.
43043043543544044044544545045014012010080604020020406080100120140-L-STA 142+00.00SHEET 42 · XS-14 · REV 2
CROSS-SECTION · STA 142+00.00illustration
138+00139+00140+00141+00142+00143+00144+00-L-18" RCPCURVE C-12PI STA 143+12.40Δ 12°40'00" R 1200.00L 265.32 T 133.05N
PLAN · -L-illustration

Have a plan set you want read?

Early access is shaped by the sets people bring to it. Tell us what you work with and we will tell you honestly what Mathyra can and cannot do with it today.