Availability: Arranged through sales
What the API does not process, as present facts. Reading this before integration saves a scoping round trip, and descriptions outside these bounds are a conversation with the team rather than an API call.
Referential calls
Descriptions that depend on reference geometry not contained in the document cannot be plotted directly. Examples: a course running “along the north line of Oak Street” or “with the meanders of the river for 500 feet” requires external street or water boundary data the document does not carry.
Supported PLSS usage stands apart from this: section corners and quarter corners as starting points, township and range references for coordinate establishment, and standard section subdivision references combined with metes and bounds all process normally.
Lot and block descriptions
Platted subdivision lot and block descriptions require the recorded plat to plot, and the API does not process them directly. The API flags lot and block descriptions when it detects them in a submitted document. Backlogs containing plat-dependent records are a Bulk Processing Services conversation, where plat integration can be scoped into the engagement.
Internal angles
Descriptions written with internal angles rather than bearings are not handled.
Curves
Supported: simple circular arcs defined by radius and central angle, and chord bearing and distance. Not handled: spiral curves and station based width transitions, which together rule out highway right of way descriptions.
Input quality
- Scanned documents need enough resolution for reliable extraction; 300 DPI or better.
- Handwritten descriptions may require manual transcription before submission.
- Damaged or incomplete documents can produce incomplete call sets, which the check values will show.
Coordinate systems
Processing assumes standard survey coordinate systems. Custom coordinate systems belong in your access conversation so handling is set before documents flow.