One platform. Documents in, plots and data out.
One core reads a land description and returns a checked plot and structured data. You reach it three ways: Trace to plot by hand, the API to build it in, and Bulk Processing Services to send us the backlog.
Read. Plot. Check. Deliver.
- Read
BoundaryLogic extracts calls from PDFs, scans, and text: bearings, distances, curves, easement centerlines, PLSS aliquots.
bearings and distancescurveseasement centerlinesPLSS aliquotsscans and text - Plot
The boundary draws itself: lines, curves, corridors, multi-tract assemblies.
multi-tractcorridorscurve sweepsPOB remainder - Check
Closure, gap and overlap flags, and precision ratio, shown on every plot.
Closure errorPrecision ratioRemainder to POB - Deliver
Client-ready plats and structured data: PDF, DXF, Shapefile, KML, GeoJSON.
PDF platDXFSHPKMLGeoJSONstructured JSON
{
"tract": "A",
"area_ac": 2.2923,
"precision": "1:69,793",
"calls": 5
}Read. Plot. Check. Deliver.
Read
BoundaryLogic extracts calls from PDFs, scans, and text: bearings, distances, curves, easement centerlines, PLSS aliquots.
Plot
The boundary draws itself: lines, curves, corridors, multi-tract assemblies.
Check
Closure, gap and overlap flags, and precision ratio, shown on every plot.
Deliver
Client-ready plats and structured data: PDF, DXF, Shapefile, KML, GeoJSON.
{
"tract": "A",
"area_ac": 2.2923,
"precision": "1:69,793",
"calls": 5
}Use it, integrate it, or send us the backlog.
Trace
The plotting workspace. Sign up and plot today, free to start.
BoundaryLogic API
The plotting core behind Trace, in your own software. Documents or JSON in, geometry and checks out.
POST /v1/plots
{
"document": "spring-dale-deed.pdf",
"format": "metes_and_bounds"
}{
"tract": "A",
"area_ac": 2.2923,
"perimeter_ft": 1308.58,
"closure_error_ft": 0.02,
"precision": "1:69,793",
"calls": 5
}Bulk Processing Services
Send us the backlog. Outputs standardized to your spec, delivered.
Use it, integrate it, or send us the backlog.
The plotting workspace. Sign up and plot today, free to start.
The plotting core behind Trace, in your own software. Documents or JSON in, geometry and checks out.
POST /v1/plots
{
"document": "spring-dale-deed.pdf",
"format": "metes_and_bounds"
}{
"tract": "A",
"area_ac": 2.2923,
"perimeter_ft": 1308.58,
"closure_error_ft": 0.02,
"precision": "1:69,793",
"calls": 5
}Send us the backlog. Outputs standardized to your spec, delivered.
Trace: the plotting workspace.
Upload a document, review a closure-checked plot, and export to your client, CAD, or GIS. These are four of the things you will use every day.
The BoundaryLogic API: the core, in your software.
The same core that runs Trace, called from your own systems. Send a document or a description, get geometry and the checks back.
POST /v1/plots
{
"document": "spring-dale-deed.pdf",
"format": "metes_and_bounds"
}{
"tract": "A",
"area_ac": 2.2923,
"perimeter_ft": 1308.58,
"closure_error_ft": 0.02,
"precision": "1:69,793",
"calls": 5
}POST /v1/plots
{
"description": "Beginning at a point ...",
"format": "metes_and_bounds"
}{
"tract": "A",
"area_ac": 2.2923,
"closure_error_ft": 0.02,
"precision": "1:69,793",
"geometry": { "type": "Polygon" }
}Bulk Processing Services: your backlog, delivered.
BPS is a partnership that starts with a pilot. Here is how an engagement runs, from your requirements to delivery.
- 01
Send your requirements.
Share sample documents and an output spec: formats, title blocks, naming, and coordinate system. That spec is what everything downstream is built against.
Customer specFormatsPDF · DXF · SHPTitle block[client template]Namingtract-{id}Coordinate system[EPSG code] - 02
Run a pilot together.
We process a pilot batch and review it side by side. You set the acceptance criteria, and every output carries a flagged-for-review count, because outputs are checked, not promised perfect.
Pilot manifestDocuments in50Outputs out50Flagged for review3 - 03
We build to your spec.
Once the pilot is accepted, we build the intake and output tooling around your exact requirements, so the run works the way you defined it.
config.ymlintakebatch/deedsoutput.formatspdf,dxf,shpoutput.namingtract-{id}crs[EPSG code] - 04
Bulk processing begins.
The backlog runs at volume against the agreed spec. Standardized outputs come through with their review flags intact.
Processing · in progress - 05
Delivery.
You receive standardized outputs and a delivery manifest with rolled-up totals, on the schedule you set.
Delivery manifestDocuments1,240Tracts1,318Flagged for review12FormatsPDF · DXF · SHP
From one document to a million.
The same core runs Trace, the API, and Bulk Processing Services. Whether you plot one deed or a county backfile, the work is read the same way. Scale volume without scaling headcount.
Documents become a data asset.
Every legal description becomes geometry and structured data your GIS, CAD, and systems can use. Export to PDF, DXF, Shapefile, KML, or GeoJSON, or take the JSON straight from the API. The record stops being a scan and starts being data.
One connected experience for your whole team.
Operators plot in Trace, systems pull from the API, and admins see every project. Everyone works from one source of data, so nothing is stranded on a single person's machine.
A platform you can trust.
Cloud-based and always current, improving every month. The work travels with you across devices and never gets trapped on one machine.
Start with a free plot, a doc key, or a pilot.
Plot your first description in Trace, pull the same core from the API, or send us a backlog to process. Manual plotting, PDF export, and DXF export are free.