How a description becomes a shapefile.

Parse

The description becomes structured calls.

TractEdge reads the description and transcribes it into bearings, distances, adjoiners and natural features. Every value has to ground against the exact span of the deed it came from, or its confidence goes to zero. Text that never became a call stays marked in the source pane.

Anchor

TractEdge places the calls on public survey geometry.

TractEdge resolves the survey reference against RRC original-land-survey geometry and uses the matched reference to place the point of beginning. Adjoiner calls follow the matched reference line. Anchoring decisions include confidence values. The public reference geometry is a digital interpretation and has no legal survey authority.

Traverse

A deterministic engine does all the geometry.

The engine computes bearings, distances, closure and an optional Bowditch adjustment in ordinary code. Once the calls and anchor are fixed, the resulting geometry is repeatable.

Edit

Review and edit the draft.

The editor puts the deed text, the calls table and the map side by side. Selection links them: click a call and its phrase highlights; click the phrase and the leg highlights on the map. TractEdge automatically finds state-reported oil and gas wells in and around the tract and adds them as a map layer. Vertices are draggable and closure recomputes live. Where the point of beginning couldn't be resolved with confidence, you place it yourself.

Export

Export a GIS-ready bundle.

Boundary, vertices and wells as shapefiles, with GeoJSON, KML and a README, in the Texas State Plane datum you ask for: NAD27 or NAD83, ftUS. NAD27 exports use grid-based NADCON5 transforms. TractEdge does not export NAD27 when the required grid is unavailable.