Your system holds the documents and the data. The API adds the plots: post text or the document itself, and get back plotted geometry your product can display.
Pick the surface that fits the work: the app, the API, or bulk processing at volume.
Post the text of a legal description, or post the document itself and the built-in OCR reads it first. The response is structured data your product can store and display: the plotted geometry, the ordered calls, and the closure and precision checks.
POST .../documents/from-legal-description
{
"legalDescription": "N 40 15 30 W 176.87 ..."
}{
"geoJsonUrl": "[file URL]",
"dxfUrl": "[file URL]",
"boundaryClosurePercent": 99.98
}Many land systems manage text and documents, not geospatial data. The API is the shortest path across: your product keeps its data model and gains the plots, maps, and acreage your customers have been asking for.
POST .../documents/from-legal-description
{
"legalDescription": "N 40 15 30 W 176.87 ..."
}{
"geoJsonUrl": "[file URL]",
"dxfUrl": "[file URL]",
"boundaryClosurePercent": 99.98
}Plotting is our whole company, not a side feature. Curves, easement centerlines, PLSS aliquots, multi-tract descriptions: the hard cases are our everyday work, and support for new survey call types ships continuously.
We can process your customers' existing data at volume, so historical documents gain plots and geometry alongside the new records the API plots going forward.
Hold the output to your own standard before you write a line of code. Trace runs on the same core: plot your hardest descriptions in the app and see the geometry and checks your product would get.
Talk to sales about API access, or plot your test descriptions free in Trace today.